Boot Issue After upgrading from 2.1.5 to 2.2
-
It's a full install on an IDE drive. Old Compaq SFF PC. 512MB memory, Onboard NIC + PCI ethernet card. I've used it for several years and and several different versions of pFsense. Never had an issue with an upgrade before.
-
Have the same exact issue after the upgrade on an old HP computer.
-
Any solution other than re-installing completely?
-
Does it give you options when you enter ? at the mountroot> prompt?
You read this in the upgrade guide:
The disk drivers in FreeBSD changed between the underlying OS versions and now the CAM-based ATA drivers and AHCI are used by default. As such, ATA disks are labeled as /dev/adaX rather than /dev/adX.
Your box is trying to use the old drive naming scheme ad0s1a, that drive and slice is now ada0s1a. At the mountroute> prompt type:
ufs:/dev/ada0s1aThen edit your fstab when it's booted to make the change permanent.
Steve
-
When entering ? it just says:
List of GEOM managed disk devices:
fd0 -
Hmm, OK that's bad. Try what I wrote above anyway but it should be listed there. :-\
Steve
-
Does it give you options when you enter ? at the mountroot> prompt?
You read this in the upgrade guide:
The disk drivers in FreeBSD changed between the underlying OS versions and now the CAM-based ATA drivers and AHCI are used by default. As such, ATA disks are labeled as /dev/adaX rather than /dev/adX.
Your box is trying to use the old drive naming scheme ad0s1a, that drive and slice is now ada0s1a. At the mountroute> prompt type:
ufs:/dev/ada0s1aThen edit your fstab when it's booted to make the change permanent.
Steve
Yes. I do have the prompt. I tried "ufs:/dev/ada0s1a" it tried to load it, but it crapped out again with error code 19. :/
-
And you don't see any options in you enter ? either? (Other than a floppy drive)
-
Reverted back to 2.1.5 for the time being until another update is released.
-
If it isn't listed as a detected device it's odd that it failed with 'error 19' because that implies it tried to mount the device with an option that isn't supported. It tried to mount it so it must have already detected it.
Can you get a boot log up to that point at all?
What drive and drive controller are you using?Steve
-
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 FactorBase Board Information
Manufacturer: Hewlett-Packard
Product Name: 0A64hProcessor Information
Version: AMD Athlon
64 X2 Dual Core Processor 3800+ -
Reverted back to 2.1.5 for the time being until another update is released.
This is my plan as well.
-
I feel like I lucked out and dodged a bullet. Seems like most people having issues have older computers or are using Xen. AHCI is wonderful.
-
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. Several reboots and shutdowns later, seems to still be working from console.
-
More likely either your drive interfaces or usb with default motherboard settings was incompatible with the BSD OS version that pfsense 2.1.5 was built on but not incompatible with BDS 10.
So yeah - That would be a good thing.
-
More likely either your drive interfaces or usb with default motherboard settings was incompatible with the BSD OS version that pfsense 2.1.5 was built on but not incompatible with BDS 10.
So yeah - That would be a good thing.
I don't exactly follow you there kejianshi. This system was the same setup I had 2.1.5 running on for many years before hand. Only thing was upgrading to 2.2. There were no hardware changes made. Not sure, but all is well again. I hope the others get their kinks worked out.
-
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
-
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.
-
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
-
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.
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.
