You are not logged in.
Pages: 1
Hi,
since the last updates, which included kernel 3.15.7, my system refuses to boot. It got stuck at "Loading initial ramdisk" vor way too long.
I then grabbed the next grml live linux, chrooted into my system and did a
# pacman -S linux
# grub-mkconfig -o /boot/grub/grub.cfg
# grub-install /dev/sdcAll of them ran without errors (or at least with the same errors as they had before).
Now, I'm stuck with a new problem: Grub stops with
error: no such device: a7f6c2a3-dd23-48d7-ac6b-e4ef64fdf422
Entering rescue mode...
grub rescue>Now it's getting really strange. I do not have a disk or partition of this UID. I checked with
$ grep -r a7f6 /etcand did not find any occurence of this UID anywhere in my configuration. However, there was a binary match in, as far as i remember, /boot/vmlinuz-linux.
Can you help me out?
Best regards,
Raphael
Last edited by raphaelm (2014-08-01 20:23:03)
Offline
Is that a UUID? Did it change somehow between boots? Can you the LTS kernel or 3.15.8 from testing?
Offline
Is that a UUID?
I guess so, from the format and the error message.
Did it change somehow between boots?
No, it staid the same, even between grub reinstalls.
Can you the LTS kernel or 3.15.8 from testing?
I'll try that tonight.
Offline
Okay. This was a good lecture in bug hunting. At the exact time when I deliberately rebooted because of a kernel update, my BIOS forgot about my hard drive boot order. m(
Offline
Pages: 1