Can you try fdisk -l /dev/hda, and cat /etc/fstab, and post the output??
Cheers,
Steve
On Sat, 13 Jan 2007 17:13:23 +1300
Chris Downie <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I had occasion to reboot and got GRUB Error 17. I ran my Mepis LiveCD and
> dmesg reported the following (I have deleted every line that I understood
> and didn't appear (to me!) to be relevant):
>
> [17179569.184000] Linux version 2.6.15-26-386 (gcc version 4.0.3 (Ubuntu
> 4.0.3-1ubuntu5)) #1 PREEMPT 19 Jul 2006
> [17179572.396000] checking if image is initramfs...it isn't (no cpio magic);
> looks like an initrd
> [17179572.540000] ACPI: Looking for DSDT ... not found!
> [17179573.672000] hda: Maxtor 6E040L0, ATA DISK drive
> [17179576.488000] **** SET: Misaligned resource pointer: dfd42502 Type 07
> Len 0
> [17179587.620000] VFS: Can't find ext3 filesystem on dev hda.
> [17179587.624000] VFS: Can't find an ext2 filesystem on dev hda.
> [17179587.640000] ReiserFS: hda: warning: sh-2021: reiserfs_fill_super: can
> not find reiserfs on hda
> [17179587.640000] FAT: bogus number of reserved sectors
> [17179587.640000] VFS: Can't find a valid FAT filesystem on dev hda.
> [17179604.844000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
> }
> [17179604.844000] hda: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=2303280, sector=2303280
> [17179604.844000] ide: failed opcode was: unknown
> [17179604.844000] end_request: I/O error, dev hda, sector 2303280
> [17179604.844000] Buffer I/O error on device hda3, logical block 0
> [17179605.316000] **** SET: Misaligned resource pointer: df0c0ec2 Type 07
> Len 0
> [17179605.508000] **** SET: Misaligned resource pointer: df0c06c2 Type 07
> Len 0
> [17179605.884000] **** SET: Misaligned resource pointer: df0c00c2 Type 07
> Len 0
> [17179605.952000] **** SET: Misaligned resource pointer: df0c00c2 Type 07
> Len 0
> [17179606.580000] **** SET: Misaligned resource pointer: dc341f02 Type 07
> Len 0
> [17179606.584000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
> }
> [17179606.584000] hda: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=2303280, sector=2303280
> [17179606.584000] ide: failed opcode was: unknown
> [17179606.584000] end_request: I/O error, dev hda, sector 2303280
> [17179606.584000] Buffer I/O error on device hda3, logical block 0
> [17179606.596000] **** SET: Misaligned resource pointer: dc341f02 Type 07
> Len 0
> [17179606.936000] **** SET: Misaligned resource pointer: dc341602 Type 07
> Len 0
> [17179606.936000] ACPI: PCI interrupt for device 0000:01:0a.0 disabled
> [17179608.320000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
> }
> [17179608.340000] hda: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=2303280, sector=2303280
> [17179608.364000] ide: failed opcode was: unknown
> [17179608.384000] end_request: I/O error, dev hda, sector 2303280
> [17179608.384000] Buffer I/O error on device hda3, logical block 0
> [17179608.556000] eth0: no link during initialization.
> [17179609.804000] NET: Registered protocol family 17
> [17179610.164000] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [AP3C] -> GSI
> 20 (level, high) -> IRQ 193
> [17179610.168000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
> }
> [17179610.192000] hda: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=2303280, sector=2303280
>
> [17179610.216000] ide: failed opcode was: unknown
> [17179610.240000] end_request: I/O error, dev hda, sector 2303280
> [17179610.240000] Buffer I/O error on device hda3, logical block 0
> [17179614.204000] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error
> }
> [17179614.228000] hda: dma_intr: error=0x40 { UncorrectableError },
> LBAsect=2303280, sector=2303280
>
> ***Dozens (hundreds?) of repeats of of the above five lines***
>
> [17182585.080000] ide: failed opcode was: unknown
> [17182585.080000] end_request: I/O error, dev hda, sector 2303280
> [17182617.720000] EXT3-fs warning: mounting fs with errors, running e2fsck
> is recommended
> [17182617.720000] kjournald starting. Commit interval 5 seconds
> [17182617.720000] EXT3 FS on hda4, internal journal
> [17182617.720000] EXT3-fs: mounted filesystem with ordered data mode.
> [17191947.980000] MCE: The hardware reports a non fatal, correctable
> incident occurred on CPU 0.
> [17191947.980000] Bank 1: 9400400000000152
> [17220735.428000] EXT3-fs warning: mounting fs with errors, running e2fsck
> is recommended
> [17220735.428000] kjournald starting. Commit interval 5 seconds
> [17220735.428000] EXT3 FS on hda4, internal journal
> [17220735.428000] EXT3-fs: mounted filesystem with ordered data mode.
> [17221542.920000] ppdev0: registered pardevice
> [17221542.932000] ppdev0: negotiated back to compatibility mode because
> user-space forgot
> [17221542.932000] ppdev0: unregistered pardevice
> [17221544.576000] ppdev0: registered pardevice
> [17221544.592000] ppdev0: negotiated back to compatibility mode because
> user-space forgot
> [17221544.592000] ppdev0: unregistered pardevice
> [17221552.004000] ppdev0: registered pardevice
> [17221552.020000] ppdev0: negotiated back to compatibility mode because
> user-space forgot
> [17221552.020000] ppdev0: unregistered pardevice
> [17252992.468000] EXT3-fs: journal inode is deleted.
> End
>
> I tried to mount hda3 with KwikDisc and got the following:
>
> Called: mount -text3 -onoauto,users,exec /dev/hda3 /mnt/hda3
> mount: wrong fs type, bad option, bad superblock on /dev/hda3, missing
> codepage or other error
>
> I ran fsck which reported:
>
> [EMAIL PROTECTED] e2fsck /dev/hda3
> e2fsck 1.38 (30-Jun-2005)
> /dev/hda3: recovering journal
> /dev/hda3: Attempt to read block from filesystem resulted in short read
> while reading block 3078
> JBD: Failed to read block at offset 2551
> e2fsck: Input/output error while recovering ext3 journal of /dev/hda3
>
> I ran fdisk which reported:
>
> [EMAIL PROTECTED] fdisk /dev/hda3
> Device contains neither a valid DOS partition table, nor Sun, SGI or OSF
> disklabel
> Building a new DOS disklabel.
> The number of cylinders for this disk is set to 20806.
> There is nothing wrong with that, but this is larger than 1024, and could in
> certain setups cause problems with:
> 1) software that runs at boot time (e.g. old versions of LILO)
> 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2
> FDISK)
> Warning: invalid flag 0x0000 of partition table 4 will be corrected by
> w(rite)
>
> Where do I start to try and recover this? Grub is not recognising the
> partition because something (a lot by the look of it) has gone west. What
> other info can I supply.
>
> Cheers,
> Chris
