Install error 19 with virtual disk

[reep]

Back to playing again

I am trying to install this on a SuperMicro 1U Atom machine with the install pointed to a virtual disk on the network.

This used to work fine on the 15.x series but the 16.7 fails

I can see that there are a lot of issues with this with FreeBSD online.

I've added a few screenshots for reference. Looks like the Virtual CD is assigned cd0 but when I try

cd9660:/dev/cd0

I get the error 19.

I have tried various permutations without success. Yes, I can probably install from a USB but for various reasons this is not always practical and would much prefer over the network installs.

Any advice appreciated.

B. Rgds
John

[reep]

As a follow up I disconnected the 'virtual' drive and noticed that it seems to be at

umass-sim0

I have tried

cd9660:/umass/sim0 ro

Again error 19

I tried adding this which I found online but no difference

kern.cam.boot_delay=10000

Just tied 16.1 and it is the same - not tried the boot_delay yet.

Would disabling ACPI help ?

B. Rdgs
John

[franco]

Hey John,

Nice to hear from you again. 

"umass" would indicate some sort of USB, FreeBSD has this to say:

USB 3.0 support is not compatible with some hardware, including Haswell (Lynx point) chipsets. If FreeBSD boots with a failed with error 19 message, disable xHCI/USB3 in the system BIOS.[1]


Cheers,
Franco

[1] https://www.freebsd.org/doc/handbook/usb-disks.html

[reep]

Hi Franco !

Hey John,

Nice to hear from you again. 

I never really left - just very busy with other things that had higher priority. Life get in the way sometimes...

Have a bit more time so will play again.

"umass" would indicate some sort of USB, FreeBSD has this to say:

USB 3.0 support is not compatible with some hardware, including Haswell (Lynx point) chipsets. If FreeBSD boots with a failed with error 19 message, disable xHCI/USB3 in the system BIOS.[1]

I very much doubt this ageing beast has ever heard of USB :-)

It's akin to this :

http://www.supermicro.nl/products/system/1U/5015/SYS-5015A-EHF-D525.cfm

You can mount a remote image and boot/install from it. My guess is the BIOS does some sort of USB emulation.

EFW 3.2a 64bit boots happily....

Whatever it does v16.* x64 seems to barf on it.

Just found an old copy of OPNsense-15.7.11-OpenSSL-cdrom-i386.iso - that booted perfectly. May try a 16.x 386 but my guess is that is not the issue

See the screen shot - it hangs at this point for several seconds before continuing. Note the IPMI Virtual CD. Clearly *BSD 10 does not like this for some reason.

Here is a similarish thread https://forums.freebsd.org/threads/27260/ re *BSD 9

I may need to try and up the kern.cam.boot_delay - I tried 10000 but may need to go higher (not sure how long that actually is ?)

Let me know if there is anything else I can do to debug this - I need to be able to either 'Virtual CD' like this or PXE boot - local install media is out for me.

B. Rgds
John

[reep]

PS - is there anywhere I can get a copy of a 15.7.x x64 iso rather than the i386 I have ?

I can test, and also upgrade from 15-16 it seems ?

B. Rgds
John

[reep]

Managed to get to 16.1.18 from the 15.7.11 BUT I am stuck now on i386

Any chance of a link to a x64 version of 15.x please ? Seem to be in short supply out there !

B. Rgds
John

[franco]

Hi John,

Here's the 15.7.18 amd64 ISO:

https://pkg.opnsense.org/snapshots/OPNsense-15.7.18-OpenSSL-cdrom-amd64.iso.bz2


Cheers,
Franco

[reep]

Hi John,
Here's the 15.7.18 amd64 ISO:

Thanks Franco. Makes installing a little easier ! Still would like to get to the bottom of the issue though.

Seem like the IPMI system creates a USB based virtual CD from the ISO image. From the looks of things this is getting timed out when the system tries to mount it across the network. Do you have any idea what units are used by kern.cam.boot_delay ?

I'm away on business for about 10 days so won't have much time to actually have a go at this but I will try and do some reading.

B. Rgds
John

[franco]

The boot delay is specified in milliseconds, typically 10000 to good measure. We're still debating this for install media vs. non-install media and how to strip it afterwards, but we're not really satisfied with it either way adding arbitrary delays to all users (it's not just about install media).

Some more discussion here: https://github.com/opnsense/tools/issues/28

OTOH, it looks like something else is wrong, something that got introduced in FreeBSD 10.2 with 16.1, because 15.7 uses 10.1 and that works fine. Unfortunately, unless we bring this to FreeBSD it may be lost forever if not fixed on FreeBSD 11 now.


Cheers,
Franco

[reep]

I have tried boot delays out to 60000 now still with no joy.

More I read, the more I think something is fundamentally broken in there that no one wants to really sort out.

Similar 'USB' orientated issues all over the show.

Ah well, can't do any more now. Let me know if you have suggestions to test.

B. Rgds
John