Boot Issue After upgrading from 2.1.5 to 2.2

stephenw10

Is it possible that you had tweaked something in the bios to make it run an earlier pfSense version?
Such as set the drive controller to some lower mode or disabled ACPI?

Steve

kejianshi

Yep - Thats the kind of thing I was talking about.

"Aint broke" is good enough though. I'm glad its working.

It just made me wonder if others might try the same thing.

De-optimize for 2.1.5 and try defaults rather than giving up.

There is always some fall out at each update.

stephenw10

Indeed. I've been running 2.2 snaps pretty much since they were released but I still got bitten by something I hadn't seen coming. ::)

Plenty of older hardware wouldn't boot unless AHCI or ACPI or APIC (or all three!) were disabled. Now that support for many more of these things is included a lot of that 'de-optimising' is either unnecessary or, worse, actually causing problems.

Steve

cmb

@zero_snowman:

Ok, well, call this crazy, I was tweaking around on my bios because I wanted to try installing from a USB drive. I ended up telling it to restore default bios settings after not being able to get it work. BAM working firewall again. Not sure how the upgrade tweaked my bios, but it did.

It didn't touch your BIOS config (and can't, it's completely and totally impossible), you had something there that wasn't right but just happened to work fine with FreeBSD 8.x. Come the upgrade to a FreeBSD 10.x base, something was no longer fine with whatever was wrong there.

@stephenw10:

Plenty of older hardware wouldn't boot unless AHCI or ACPI or APIC (or all three!) were disabled. Now that support for many more of these things is included a lot of that 'de-optimising' is either unnecessary or, worse, actually causing problems.

Yeah as with every significant base OS jump we've made, sometimes things that were necessary to make things work previously now are undesirable and make things no longer function.

Resetting BIOS to factory defaults is always a good idea if the system won't boot at all post-upgrade.

ramymamlouk

@zero_snowman:

I ended up telling it to restore default bios settings after not being able to get it work.

Do you have the same computer as mine? The HP Compaq dc5750 Small Form Factor?
I might trying to restore default bios settings next weekend while booting from a USB with 2.2 on it.

ramymamlouk

Restoring default bios settings did not work for me. I even tried to disable the onboard SATA controller, and attempt to install pfSense 2.2 on a USB, but that failed too.

I guess I'll wait for either a new release or a new computer :(

stephenw10

Try booting FreeBSD 10.1 on it. At least that will narrow down the issue somewhat.

Steve

zero_snowman

@ramymamlouk:

@zero_snowman:

I ended up telling it to restore default bios settings after not being able to get it work.

Do you have the same computer as mine? The HP Compaq dc5750 Small Form Factor?
I might trying to restore default bios settings next weekend while booting from a USB with 2.2 on it.

Mine is much much older than that. :D

zero_snowman

@cmb:

@zero_snowman:

Ok, well, call this crazy, I was tweaking around on my bios because I wanted to try installing from a USB drive. I ended up telling it to restore default bios settings after not being able to get it work. BAM working firewall again. Not sure how the upgrade tweaked my bios, but it did.

It didn't touch your BIOS config (and can't, it's completely and totally impossible), you had something there that wasn't right but just happened to work fine with FreeBSD 8.x. Come the upgrade to a FreeBSD 10.x base, something was no longer fine with whatever was wrong there.

@stephenw10:

Plenty of older hardware wouldn't boot unless AHCI or ACPI or APIC (or all three!) were disabled. Now that support for many more of these things is included a lot of that 'de-optimising' is either unnecessary or, worse, actually causing problems.

Yeah as with every significant base OS jump we've made, sometimes things that were necessary to make things work previously now are undesirable and make things no longer function.

Resetting BIOS to factory defaults is always a good idea if the system won't boot at all post-upgrade.

Yes, I know, I should have better thought out my response.

stephenw10

I saw this same error while invetigating something else also on some pretty ancient hardware. I saw this:

Trying to mount root from ufs:/dev/ada0s1a [rw]...
mountroot: waiting for device /dev/ada0s1a ...
Mounting from ufs:/dev/ada0s1a failed with error 19.

But importantly it was preceeded by this:

ada0 at ata0 bus 0 scbus0 target 0 lun 0
ada0: <toshiba mk2018gap="" m1.42="" a=""> ATA-5 device
ada0: Serial Number 32K60131T
ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
ada0: 0MB (0 512 byte sectors: 16H 63S/T 16383C)</toshiba>

Clearly 0MB is not a good size for a drive. ;) Do you see anything like that? I got past it by setting the access mode to LBA in the BIOS.

Steve

ramymamlouk

I think I have already tried playing around with the LBA mode. One of my attempts was to disable the hard drive from the BIOS completely, and attempt to install on a USB thumbdrive, which also failed.

An interesting attempt though, is that I tried booting off a nano-bsd image placed on a USB drive, while the hard drive disabled from the BIOS, which also failed.

Could it be anything to do with the GPT partitioning that FreeBSD 10.1 uses by default?

HandleX

Did you read this solution: [ https://forums.freebsd.org/threads/error-19-on-boot-from-usb-after-8-2-9-0-upgrade.30254/#post-173564 ]?

It seems to be with old devices/BIOS etc.

stephenw10

Nope hadn't tried that. Not confirmed in the linked thread though. However it does sound like something that could potentially solve a number of open threads here. Thanks. :)

Steve

kaioh

Hi,
I Just had the error 19 problem and I solved it by booting with

ufs:/dev/ada0s1a

Thanks for the support.

Unfortunately, I'm using a XenServer box (dit not snapshot :( ) so the nics changed name and now I have a long long night for reconfigure all the settings (about 10 nics)

How about making the boot settings change permanent? Where should I look and edit configs?

stephenw10

Any setting you make at the bootloader prompt can be added to /boot/loader.conf.local to make it permanent. Create that file if it doesn't exis.

Steve

kaioh

@stephenw10:

Any setting you make at the bootloader prompt can be added to /boot/loader.config.local to make it permanent. Create that file if it doesn't exis.

Steve

Thanks for your reply, I looked at the files inside /boot but did not find "ad0s1a" to change it to "ada0s1a"

stephenw10

Ah, sorry I misunderstood.
If that's a full install then just make the change in /etc/fstab

Steve

kaioh

Oh, my head! ;D

Did not just think about it, soo tired.

Thank you!

andrew867

@ramymamlouk:

I don't think I can since I reverted back to 2.15. However, here are snipets from dmidecode hoping it would help:

System Information
Product Name: HP Compaq dc5750 Small Form Factor

Base Board Information
Manufacturer: Hewlett-Packard
Product Name: 0A64h

Processor Information
Version: AMD Athlon 64 X2 Dual Core Processor 3800+

I'm working with the same machine and found that changing the system to 'Native Mode IDE' in the BIOS (Storage->Storage Options->SATA Emulation) and changing /etc/fstab to ada0s1a allows the machine to start working normally again.

Hopefully this helps other people using legacy HP PCs!

-Andrew

briankelly63

I have an older HP PC that would not boot after the upgrade to 2.2. After trying many suggestions I'll confirm that turning off packet mode during the install process (not quick install) solved the issue….