Mailinglist Archive: opensuse (3506 mails)
| < Previous | Next > |
RE: [SLE] Grub loading Stage2 read error
- From: "Greg Wallace" <gregwallace@xxxxxxxxxxx>
- Date: Sun, 17 Sep 2006 03:48:29 +0000 (UTC)
- Message-id: <!&!AAAAAAAAAAAYAAAAAAAAABYv/fsiAbFHuuseWu7lbHnCgAAAEAAAAGHB7U6op+RBjZdog9YwM98BAAAAAA==@xxxxxxxxxxx>
On Saturday, September 16, 2006 @ 8:27 PM, Paul Abrahams wrote:
>I just tried the following at a grub prompt, combining several suggestions:
>root (hd0,7)
>setup (hd0)
>kernel /vmlinuz root=/dev/hda7 vga=normal
>initrd /initrd
>The last of these gave the message:
> Error 16. Inconsistent filesystem structure
>I did the obvious:
> fsck -fy /dev/hda7
> fsck -fy /dev/hda8
>and got no errors.
>Just to cover all the bases, I also tried:
>root (hd0,7)
>kernel /boot/vmlinuz root=/dev/hda7 vga=normal
>initrd /boot/initrd
>and got the same error message with Error 16.
>I was running the rescue system with /dev/hda7 mounted and then chrooted.
>The /boot directory did not have an initrd file. I then ran mkinitrd, but
>that did not create a mkinitrd file in /boot either.
>I am very puzzled.
>Paul
Just for the heck of it, you might check /boot/grub/device.map and
/etc/grub.conf to make sure they're in sync with /boot/grub/menu.lst. I
somehow had those out of sync once upon a time, which, of course, caused me
all sorts of problems.
Greg Wallace
>I just tried the following at a grub prompt, combining several suggestions:
>root (hd0,7)
>setup (hd0)
>kernel /vmlinuz root=/dev/hda7 vga=normal
>initrd /initrd
>The last of these gave the message:
> Error 16. Inconsistent filesystem structure
>I did the obvious:
> fsck -fy /dev/hda7
> fsck -fy /dev/hda8
>and got no errors.
>Just to cover all the bases, I also tried:
>root (hd0,7)
>kernel /boot/vmlinuz root=/dev/hda7 vga=normal
>initrd /boot/initrd
>and got the same error message with Error 16.
>I was running the rescue system with /dev/hda7 mounted and then chrooted.
>The /boot directory did not have an initrd file. I then ran mkinitrd, but
>that did not create a mkinitrd file in /boot either.
>I am very puzzled.
>Paul
Just for the heck of it, you might check /boot/grub/device.map and
/etc/grub.conf to make sure they're in sync with /boot/grub/menu.lst. I
somehow had those out of sync once upon a time, which, of course, caused me
all sorts of problems.
Greg Wallace
| < Previous | Next > |