You are not logged in.
Pages: 1
Facing a BIOS to MBR handoff failure...
Left system on unattended, came back a few hours later with a "boot error" message on the screen. Bios itself provides an "AE" error message. On my Gigabyte MB this should mean "legacy boot event". From there I did the following and attempted to boot after each step with no luck:
BIOS
1) Tried to use bios to manually boot from SSD (where /boot is located)
2) Made sure bios recognized SSD.
3) Made sure the SSD was set as the primary boot device in bios.
4) Made sure boot settings were "Legacy".
PHYSICAL
4) Made sure power and SATA cables were secure.
5) Replaced power and SATA cables.
6) Steps 2 and 3 again.
OS
7) Mounted partitions to live-usb and chroot into root.
Verified mkinitcpio -p linux was without error.
Checked /boot/syslinux/syslinux.cfg to make sure the correct boot device was set.
Updated system using pacman.
8) Made sure boot flag was set to correct partition.
9) 1 - 8 again.
At this point I'm thinking maybe my bios needs updating.
Possibly I may have missed an t-shoot step that would be obvious to a more advanced user.
Would anyone have any suggestions to help narrow or define root cause before I update bios?
Thanks.
Last edited by TrAzE (2017-03-13 00:21:47)
“Just because you're paranoid doesn't mean they aren't after you.” -Catch 22
Offline
chroot back into my system and took a closer look at /boot/syslinux.cfg before an attempt to reinstall syslinux.
There was a inadvertent character on the first line of syslinux.cfg before the comment. Remove it... and system booted fine.
“Just because you're paranoid doesn't mean they aren't after you.” -Catch 22
Offline
Pages: 1