[SOLVED] Forced reboot, now GRUB reset and cannot find Arch

MeisBarry · 2013-08-13 21:21:21

2 nights ago, my area had a fairly large storm. When I woke up, my Arch box had rebooted itself, and was stuck on a GRUB error screen. I had not updated, nor had I recently touched anything in /boot.

The major complaints from GRUB were "file not found" when trying to load the kernel, and complaints about invalid UUIDs when trying to mount the root filesystem. It's also worth noting that GRUB's menu resolution had changed back to the default lowest setting, and was colorless. This, I think, indicates a problem with the configuration. I could still see all my files and systems through grub's prompt. Everything was still there and the HDD seemed fine.

Yesterday, I was able to boot into Arch successfully by simply doing:

grub> set root=(hd0,msdos1)
grub> linux /boot/vmlinuz-linux
grub> initrd /boot/initramfs-linux.img
grub> boot

Once I got in I updated the system, ran pacdiffviewer, ran grub-mkconfig as per the wiki (to hopefully fix the config issue), and rebooted. Now I cannot get into Arch at all. Using the Arch GRUB menu item, I just get "file not found" and booted back to the menu. Using the above commands gets me the following errors, and a recovery shell:

ERROR: device '' not found. Skipping fsck.
ERROR: Unable to find root device ''.

One last thing: I have an old Ubuntu 10.10 partition on the same drive. I can get to that partition through GRUB's menu just fine. This is strictly an issue with Arch. Perhaps the hard reboot caused something to change related to UUIDs? What should I do?

Last edited by MeisBarry (2013-08-13 22:16:51)

cfr · 2013-08-13 21:29:39

Post grub.cfg, fstab and lsblk -f.

MeisBarry · 2013-08-13 22:16:32

Well this is embarrassing.

While getting grub.cfg, I noticed that when I had done grub-mkconfig, ...I saved it as grub.conf by accident. I fixed it and my system works again!

So I'll mark it Solved. Any idea why a reboot would corrupt grub's configuration?

cfr · 2013-08-13 22:43:08

Was it a reboot? Or was it an unclean shutdown followed by a boot?

Arch Linux

#1 2013-08-13 21:21:21

[SOLVED] Forced reboot, now GRUB reset and cannot find Arch

#2 2013-08-13 21:29:39

Re: [SOLVED] Forced reboot, now GRUB reset and cannot find Arch

#3 2013-08-13 22:16:32

Re: [SOLVED] Forced reboot, now GRUB reset and cannot find Arch

#4 2013-08-13 22:43:08

Re: [SOLVED] Forced reboot, now GRUB reset and cannot find Arch

Board footer