Boot Issue After upgrading from 2.1.5 to 2.2
-
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
-
Hi,
I Just had the error 19 problem and I solved it by booting withufs:/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?
-
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
-
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"
-
Ah, sorry I misunderstood.
If that's a full install then just make the change in /etc/fstabSteve
-
Oh, my head! ;D
Did not just think about it, soo tired.
Thank you!
-
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+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
-
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….
-
Hope i can jump into this Topic. I actually want to install pfs on astaro 110/120 from cd-rom and got same message with disk ad0s1a. where can i change to da0s1a?
-
any hint to do a successfull installation with above error message for wrong disk?
-
Where in the install process are you getting stuck?
How is the CD-ROM drive connected?Steve
-
Hi stephenw10,
the cd-rom is connected via usb2 port of the box.
On screen:
loading boot/kernel/kernel text=…data=...syms=...
fast scrolling ?!
loading usb ports with external keyboard
next loading usb -> cd-rw ... serial number ... transfers ... cd present 102493x2048 byte records
quirks=0x10<10_byte_only>thats it, after press enter i see panic: mountroot: unable to remount root ... panic ... command line on which help shows from hd_dump to x commands
does this help?
-
Ok, if you're booting from USB did you try choosing 'boot from USB' at the boot menu?
Steve
-
Sorry Steve, where do you mean in detail at the boot menu? Bios or pfSense Menu? Bios, yes because i still boot from cd. pfSense, i cant find any option to expliciet say this is a boot from cd? My problem is, that i boot form usb cd-rom with live-cd installer and want to install pfsense x86 on astaro 110/120. As the kernel loads and the devices are recognized i got the error like the thread creator with wrong disk-device-name. Solution should to change the name to ada0s1a, but i dont where to say this at installation process.
-
Any new idea?
-
When you boot from the CD (or a USB flash drive) after the bootloader you reach a boot menu with a list of options. One of them is 'boot from USB'. It sets a delay to give the USB device time to initialise before trying to mount root.
See: https://doc.pfsense.org/index.php/Boot_Troubleshooting#Booting_from_USBSteve
-
Hello,
sorry but on my Welcome to pfSense Boot-Menu i have:
1 - boot multi..
2 - boot single..
3 - escape to …
4 - rebootoptions
5 - kernel...
6 - configure boot ...as you see and not like in the documents there is no option for boot from usb, but i tried the set boot kernel option and so the installation goes on.
thx for the hint to the docs ;) -
Hmm, odd.
Well glad you got past it anyway.Steve
-
Hello,
I bought a new setup(Mini ITX Q-6 Black, GA-C1037UN-EU, 2GB DDR3 & 250GB SATA2 spinner) to replace my old Core2Duo, 2 GB DDR2 and 80GB Maxtor and I'm having the same issue as OP(error 19 on mount) when trying to install 2.2.4(iso burned to a cd), booted from a USB optical drive. I tried several versions, 2.1.5 iso burned to a disk and embedded(on a USB stick), my old trusty 2.1.3 burned(to the cleanest CD I've ever owned) and on the USB thumb stick, all of which worked on my old setup but not on the new one. I ended up burning half a dozen CDs with 2.2.4, 2.1.5 and 2.1.3 aswell as trying several USB thumb drives, two Kingston(USB 2 and 3) and a no-name one.
With 2.1.5 I can install but only seconds into the installation I get the dreaded
((ada0:ata0:0:0:0): READ_DMA. ACB …
(ada0:ata0:0:0:0): CAM status: Command timeout
(ada0:ata0:0:0:0): Retrying command)Installation finishes, I get the reboot prompt but as soon as the system reboots I'm stuck at the boot prompt for:
F1 pfsense
F2 PXE
Boot: F1
\To make sure the new rig isn't at fault I've installed Ubuntu, Windows 8.1 and cloned my Arch distro to both the 250GB HDD and another spare I had laying around and they simply work. Also tried different SATA cables, different SATA port on the motherboard just to be sure.
The ISOs and the embedded imgs(used the ones with vga) were downloaded from the pfsense page and I made sure not to write an img to a cd or something crazy like that.
As for writing imgs to thumb drives I've tried both dd and 'win32 disk imager' aswell as 'USB image tool'.Currently running pfsense from a live cd, sad as I'm not able to try out the various packages I had on my old rig.
Hope there isn't anything I forgot to mention.Please help.
Thank you,
a sad person -
When you see nothing after the bootloader prompt you may be looking at the wrong console. Did you choose the embedded kernel?
Try different HD access modes if you can.
Make sure you are running the latest BIOS. There were some other similar Gigabyte boards that had boot issues with early BIOS versions.
https://doc.pfsense.org/index.php/Boot_Troubleshooting#BIOS.2FDisk_Errors
Steve
