Messages in this thread | | | Date | Fri, 13 Feb 2004 08:54:03 +0100 | From | Nico Schottelius <> | Subject | harddisk or kernel problem? |
| |
Hello!
Since yesterday I have the problem that at bootup my cryptoloop (/home) does not get mounted anymore. These messages are produced by the kernel:
---------------- snip ------------------
Freeing unused kernel memory: 140k freed XFS mounting filesystem hda1 Ending clean XFS mount for filesystem: hda1 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458, sector=8305454 end_request: I/O error, dev hda, sector 8305454 I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090 ("xfs_trans_read_buf") error 5 buf count 8192 8139too Fast Ethernet driver 0.9.26 eth0: RealTek RTL8139 at 0xd8850e00, 00:0a:e6:ba:f6:c2, IRQ 5 eth0: Identified 8139 chip type 'RTL-8100B/8139D' hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=8305458, sector=8305454 end_request: I/O error, dev hda, sector 8305454 I/O error in filesystem ("hda3") meta-data dev hda3 block 0x776090 ("xfs_trans_read_buf") error 5 buf count 8192
---------------- snap ------------------
if I log in as root and issue `mount /home`, it works:
---------------- snip ------------------
XFS mounting filesystem loop0 Ending clean XFS mount for filesystem: loop0
---------------- snap ------------------
Yesterday the errors `hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }` repeated (don't have the dmesg, forgot to dump kernel messages).
Now I am trying the following: enabling Anticipatory I/O scheduler (additionaly to the Deadline I/O scheduler) and disabling Vector-based interrupt indexing.
This is just a guess, can someone tell me if that is senseless or if my harddisk is most likely broken?
Attached dmesg from 'running' system and the new .config (changes see above) I made.
Help is very much appreciated,
Nico, who just had a hard disk crash some weeks ago - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |