Firebox x1250e crash after upgrading
-
-
Are you sure your HD is mounted as ad0s1a
because I see you entered this line:```
set vfs.root.mountfrom=ufs:/dev/ad0s1abut your HD in the fstab file is ada0s1a so the mountpount should be:``` set vfs.root.mountfrom=ufs:/dev/ada0s1a -
If you type dmesg in console you can see the boot messages and find out the name of your HD.
-
Not if you never get to a console. ;)
There should be aliases in place to take care of anything that still points at ad0 as opposed to ada0. I speculated that perhaps that isn't working for swap.There is a thread that collates all the reports of this error, lets try and keep all info there:
https://forum.pfsense.org/index.php?topic=87542.0Steve
-
Didn't know about the aliases :)
I just modified the fstab file
-
No reason to know, it should 'just work'. ;)
Did you update to BIOS 8_1 to make this load do you think?
Steve
-
I got Bios_81 on mine yes, and the HD settings are set to auto.
The only thing i had to change is the fstab file or when booting, testing it with set vfs.root.mountfrom=ufs:/dev/adxxxxxx -
I think it's the swapper process trying to use DMA and failing. On my box I had to enable UDMA for the IDE channel I was using, did you have to make that change?
Also:
@unknown001:Also enable ACPI function and IDE primary slave UDMA is now "auto" mode. No longer crashing
Steve
-
yes i also did those steps
-
Ok this is an ACPI problem, it must be enabled:
https://forum.pfsense.org/index.php?topic=87542.msg484384#msg484384Steve
-
I am a little lost on what I should try next….
-
The HDD is being detected as stephenw10 stated since it starts the boot process but ends with that kernel panic info I posted with a trace after.
-
You need to enable ACPI in the BIOS or at least check it's enabled. It could potentially be something else but that will definitely cause the panic you're seeing.
Steve
-
On it! Thanks stephenw10…Ill try it in about 30min. All I did the other night was pull the FSTAB, I did not reset/check the HDD BIOS settings so I will do that as well since I have to go there for ACPI. Oh I did flash the 8.1 BIOS you created after no change with 8.
-
It actually looks like the underlying cause of this is a regression in the gpioapu driver. See: https://redmine.pfsense.org/issues/4363
Enabling ACPI in the BIOS works around it on the firebox though.Steve
-
Thats what some of the info was pointing to, GPIOAPU and I thought that was an issue, but found so many things pointing the other way and other people fixed it with those commands and other easier things than fixing the GPIO code, wishful thinking….Haven't gotten a chance to check the BIOS settings yet, but I will post when I so. Thanks for all the help, very appreciated. Love my fireboxes.
-
So got it to boot once. Now after turning it off and turning it on today I get:
(ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 51 8d 1d 46 00 00 00 00 01 00
(ada0:ata0:0:0:0): CAM status: ATA Status Error
(ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
(ada0:ata0:0:0:0): RES: 51 40 51 8d 1d 06 06 00 00 01 00And it just keeps going and going. I had it up and running for an hour before shutting it down for the night.
-
Hmm, looks a lot like this:
https://doc.pfsense.org/index.php/DMA_and_LBA_Errors#Fatal_Errors
How do you have the drive mounted? Could it be a loose cable or something similar?Steve
-
I started over, ill let you know what happens with a new install same drive. I do have another and another type of drive. I did secure the HDD in there so I would guess it the cable/adapter are not loose.
-
New install worked, but now I have to figure out why the LCD works, but shows no info
