You are not logged in.
A year ago i bought and built a new PC with:
Mobo MSI P55-GD65
CPU Core i5 2.8 GHz
SATA harddisk WD20EARS
From dmesg:
MICRO-STAR INTERNATIONAL CO.,LTD MS-7583/P55-GD65 (MS-7583) , BIOS V1.9 06/19/2010
CPU0: Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz stepping 05
ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
For a year this has been running Archlinux (alongside with Windows7) without any problems. A month or so ago i refeshed Archlinux to the latest kernel. This has run more or less ok (i had a small problem with the GRUB loader). But since yesterday i have major disk problems with the /home partition. The system hung itself up, out of the blue while opening a gnumeric file. I had to do a hard reset. During reboot the fsck failed with loads of READ DMA EXT failed messages. See log below for similar logging. It did not recover so i used a fresh 2011.08.19 Archlinux cd. With that fsck also failed with similar results.
But now the weird part, i downloaded an old 2010.05 Archlinux cd iso and retried the fsck and with that everything went fine. Thank god the partition was still intact as i had no backup.
Then i rebooted the installed Archlinux which booted ok but when i ran (in init S mode) fsck -f /dev/sda6 it failed again with identical errors.
The dmesg logging below is from this last attempt.
The root partition seems to be doing fine btw., i only have this with the /home partition (250GB EXT3).
Again the previous Archlinux iso (with 2.6.xx) works without problems.
I typing this from the very PC albeit from Windows7 (which runs OK, i therefore suspect the mobo is intact).
What could this be, is this a problem with my hardware of with the new Linux 3.x kernel?
[ 1024.857143] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1024.864655] ata6.00: BMDMA stat 0x25
[ 1024.871892] ata6.00: failed command: READ DMA EXT
[ 1024.879297] ata6.00: cmd 25/00:00:80:75:a7/00:02:24:00:00/e0 tag 0 dma 262144 in
[ 1024.879298] res 51/40:af:c8:76:a7/40:00:24:00:00/e0 Emask 0x9 (media error)
[ 1024.894491] ata6.00: status: { DRDY ERR }
[ 1024.902058] ata6.00: error: { UNC }
[ 1024.922039] ata6.00: configured for UDMA/133
[ 1024.922054] ata6: EH complete
[ 1027.580119] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1027.588065] ata6.00: BMDMA stat 0x25
[ 1027.595791] ata6.00: failed command: READ DMA EXT
[ 1027.603695] ata6.00: cmd 25/00:00:80:75:a7/00:02:24:00:00/e0 tag 0 dma 262144 in
[ 1027.603696] res 51/40:af:c8:76:a7/40:00:24:00:00/e0 Emask 0x9 (media error)
[ 1027.619915] ata6.00: status: { DRDY ERR }
[ 1027.628008] ata6.00: error: { UNC }
[ 1027.647907] ata6.00: configured for UDMA/133
[ 1027.647928] ata6: EH complete
[ 1030.303062] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1030.311352] ata6.00: BMDMA stat 0x25
[ 1030.319888] ata6.00: failed command: READ DMA EXT
[ 1030.328014] ata6.00: cmd 25/00:00:80:75:a7/00:02:24:00:00/e0 tag 0 dma 262144 in
[ 1030.328015] res 51/40:af:c8:76:a7/40:00:24:00:00/e0 Emask 0x9 (media error)
[ 1030.345052] ata6.00: status: { DRDY ERR }
[ 1030.353743] ata6.00: error: { UNC }
[ 1030.373943] ata6.00: configured for UDMA/133
[ 1030.373964] ata6: EH complete
[ 1033.026988] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1033.035630] ata6.00: BMDMA stat 0x25
[ 1033.043778] ata6.00: failed command: READ DMA EXT
[ 1033.052235] ata6.00: cmd 25/00:00:80:75:a7/00:02:24:00:00/e0 tag 0 dma 262144 in
[ 1033.052236] res 51/40:af:c8:76:a7/40:00:24:00:00/e0 Emask 0x9 (media error)
[ 1033.069764] ata6.00: status: { DRDY ERR }
[ 1033.078382] ata6.00: error: { UNC }
[ 1033.099830] ata6.00: configured for UDMA/133
[ 1033.099852] ata6: EH complete
[ 1035.749948] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1035.758687] ata6.00: BMDMA stat 0x25
[ 1035.767155] ata6.00: failed command: READ DMA EXT
[ 1035.775936] ata6.00: cmd 25/00:00:80:75:a7/00:02:24:00:00/e0 tag 0 dma 262144 in
[ 1035.775936] res 51/40:af:c8:76:a7/40:00:24:00:00/e0 Emask 0x9 (media error)
[ 1035.794270] ata6.00: status: { DRDY ERR }
[ 1035.803714] ata6.00: error: { UNC }
[ 1035.825840] ata6.00: configured for UDMA/133
[ 1035.825861] ata6: EH complete
[ 1038.472891] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1038.482387] ata6.00: BMDMA stat 0x25
[ 1038.491617] ata6.00: failed command: READ DMA EXT
[ 1038.500620] ata6.00: cmd 25/00:00:80:75:a7/00:02:24:00:00/e0 tag 0 dma 262144 in
[ 1038.500621] res 51/40:af:c8:76:a7/40:00:24:00:00/e0 Emask 0x9 (media error)
[ 1038.519386] ata6.00: status: { DRDY ERR }
[ 1038.528895] ata6.00: error: { UNC }
[ 1038.551762] ata6.00: configured for UDMA/133
[ 1038.551801] sd 5:0:0:0: [sda] Unhandled sense code
[ 1038.551805] sd 5:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
[ 1038.551810] sd 5:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
[ 1038.551816] Descriptor sense data with sense descriptors (in hex):
[ 1038.551820] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 1038.551832] 24 a7 76 c8
[ 1038.551837] sd 5:0:0:0: [sda] ASC=0x11 ASCQ=0x4
[ 1038.551842] sd 5:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 24 a7 75 80 00 02 00 00
[ 1038.551854] end_request: I/O error, dev sda, sector 614954696
[ 1038.561262] Buffer I/O error on device sda6, logical block 3442649
[ 1038.570780] Buffer I/O error on device sda6, logical block 3442650
[ 1038.580081] Buffer I/O error on device sda6, logical block 3442651
[ 1038.589373] Buffer I/O error on device sda6, logical block 3442652
[ 1038.598446] Buffer I/O error on device sda6, logical block 3442653
[ 1038.607410] Buffer I/O error on device sda6, logical block 3442654
[ 1038.616077] Buffer I/O error on device sda6, logical block 3442655
[ 1038.624779] Buffer I/O error on device sda6, logical block 3442656
[ 1038.633177] Buffer I/O error on device sda6, logical block 3442657
[ 1038.633178] Buffer I/O error on device sda6, logical block 3442658
[ 1038.633190] ata6: EH completeLast edited by jeroenv (2011-11-29 20:31:36)
Offline
It turned out to be some bad sectors after all. While backing up my stuff (with tar) some errors were reported but i managed to save the important stuff.
Then i checked the partition with the badblocks command in readonly mode. This clearly reported a few sectors that could not be read.
Then i rechecked with badblocks in (destructive) write/read mode. This cleared all of the bad sectors. I'm not really sure how they got to be bad (so soon, the drive is hardly a year old). Although i did have a power failure a month or so ago, while i was working with this PC. Anyway i'll keep a eye on this partition and i'll keep my (~90 GB) backup for now.
What i still don't understand is why the current kernel / fs tools reported problems with fsck while the older 2010.05 Archlinux did not. But on the other hand, i can't be bothered anymore.
Offline