OK, I can now boot the system. I fixed the menu.list to correspond to
the drives as they are installed today. However, I have now discovered
that I may have a bad spot on the drive.
My first two entries in menu.list:
title Debian GNU/Linux, kernel 2.6.26-2-686
root (hd0,4)
kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hda5 ro
initrd /boot/initrd.img-2.6.26-2-686
title Debian GNU/Linux, kernel 2.6.26-2-686 (recovery mode)
root (hd0,4)
kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hda5 ro single
initrd /boot/initrd.img-2.6.26-2-686
will
not boot. I get the dreaded "Error 24 Attempt to access block outside
partition". But I can boot into the rest of the entries:
title Debian GNU/Linux, kernel 2.6.26-1-686
root (hd0,4)
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda5 ro
initrd /boot/initrd.img-2.6.26-1-686
title Debian GNU/Linux, kernel 2.6.26-1-686 (recovery mode)
root (hd0,4)
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda5 ro single
initrd /boot/initrd.img-2.6.26-1-686
and so on.
I forced a fsck on a reboot, and that I get the same error 24 when I try to boo the first two entries in menu.lst, but I can still boot into the other ones.
Should
I apt-get reinstall linux-image-2.6.26-2-686 (assumption: the vmlinuz
file is corrupted), or do something else more basic to repair the drive
(assumption: there is bad sector)?
Thanks!
Mark
did you do any recent updates that involved grub? if so, it may have renamed a partition on you. I can't be sure though as I use linux inside a VM these days and I don't much mess with grub. upon looking at your info, you might have to reinstall grub. if its saying that its attempting to access block outside of the partition, it may thing your kernel is in the wrong spot. someone please correct me on this if I am in error.
thanks
- Eric
On 8/10/10 10:48 AM, Mark Phillips wrote:
> I have a system running Debian testing. It is a dual boot with a
> Windows partition. It has worked for years, but now somehow grub got
> confused. When I try to boot, I get an error 22 - partition not
> found. I booted uo knoppix, and the drive is there and I can see all
> the files.
>
> menu.list has title Debian GNU/Linux, kernel 2.6.26-2-686 root
> (hd1,4) kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hdb5 ro
> initrd /boot/initrd.img-2.6.26-2-686
>
> parted from the knoppix disk shows: (parted) print all
> Model: ATA ST3200822A (scsi) Disk /dev/sda: 200GB Sector size
> (logical/physical): 512B/512B Partition Table: msdos
>
> Number Start End Size Type File system Flags 1
> 32.3kB 200GB 200GB extended 5 64.5kB 198GB 198GB logical
> ext3 boot 6 198GB 200GB 2048MB logical linux-swap
>
>
>
> Model: ATA WDC WD2500AAJB-0 (scsi) Disk /dev/sdb: 250GB Sector size
> (logical/physical): 512B/512B Partition Table: msdos
>
> Number Start End Size Type File system Flags 1
> 32.3kB 250GB 250GB primary ext3
>
> I remember mucking with the drives a long time (years) ago - I moved
> the boot drive from the second position to the first position), but
> it booted fine after that and ran for years. I am surprised that the
> menu.list shows the boot drive in the second position. Anyway, when
> the system boots, the grub menu comes up. I tried editing the boot
> parameters from root (hd1,4) kernel
> /boot/vmlinuz-2.6.26-2-686 root=/dev/hdb5 ro
>
> to root (hd0,4) kernel /boot/vmlinuz-2.6.26-2-686
> root=/dev/hda5 ro
>
> but I get this error message:
>
> root (hd0,4) Filesystem type is ext2fs, partition type 0x83
> kernal..... [Linux-bz-Image, setup=0x3000, size=ox16ce50] Error 24
> Attempt to access block outside partition
>
> All of the data seems to be intact when viewed from Knoppix.
>
> Any ideas on how to fix grub and get the system to boot?
>
> Thanks,
>
> Mark
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss