On Mon, May 13, 2013 at 09:16:49PM +0200, Erich Schubert wrote: > I believe I was bitten by the same bug. At least I have the same symptoms: > grub in rescue mode, unable to load even the normal module. > > I tried grub-install and upgrade-grub, but they did *not* resolve the issue > for me. I now tried "dpkg-reconfigure grub-pc" as suggested. Judging from > "tar --compare" with my backup, the files in boot/grub/i386-pc were touched > but not changed, so most likely my next boot still will not work. > But maybe the boot sector was now updated. > > For recovery, I had to create a USB boot stick with grub, which would allow > me to boot the system again. Note that I use cryptroot, so maybe it also is > related to the RAID bug report. > > One thing that strikes me as odd: > search --no-floppy --fs-uuid --set=root 07D6-0A0F > > This number is the output of: > > grub-probe -d -t fs_uuid /dev/sda1 > whereas > > tune2fs -l /dev/sda1 > reports the UUID 03422ef5-491c-4b05-b0fe-0a22e04e0fd0 > > So maybe grub has problems with my partition table / mtab? > OTOH, it doesn't actually get that far, it fails to load the normal > module already...
Could you please file a separate bug if this is still a problem? The same symptom might arise for all kinds of different reasons, and if there's a problem with UUID detection it's definitely not the same as the original problem in this bug. In your case, I'd need the output when you add -vv to that grub-probe command as well as the other information. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
