* "raid5:md0: read error not correctable (sector 795463080 on sdf1)" error on controller with SIL 3114
@ 2010-02-08 11:11 Håkon Løvdal
2010-02-09 5:13 ` Robert Hancock
2010-02-20 13:05 ` Håkon Løvdal
0 siblings, 2 replies; 4+ messages in thread
From: Håkon Løvdal @ 2010-02-08 11:11 UTC (permalink / raw)
To: linux-ide
Hi. I have had some trouble with the machine I want to have as a file server.
After having let the "get raid up and running reliably" project lie
dormant for some time, I tried again this Friday. After connecting the
disks, the status was the following: 4 out of 6 disk in a raid6 setup
were recognised (see log-1). I was able to mount the volume when the
machine was finished booting.
I then added the two missing disks with mdadm, one of them started
rebuilding and the other one were not recognised in some way (log-2).
The rebuild of the disk was successfull (log-3), but later some errors
occured, see log-4 below, and now only three disks are left in the
array (log-5).
Are these errors related to Tejun's recent statement "Sil3112/3114 are
now virtually the only controllers with occassional and unresolved data
corruption issues."? Disks sda (hosting root file system for os), sdb
sdc and sdd are connected the motherboard while sde, sdf and sdg are
connected to a controller card using 3114:
01:04.0 RAID bus controller: Silicon Image, Inc. SiI 3114
[SATALink/SATARaid] Serial ATA Controller (rev 02)
Feb 6 01:55:34 localhost kernel: sata_sil 0000:01:04.0: version 2.3
Feb 6 01:55:34 localhost kernel: ACPI: PCI Interrupt Link [LNKA]
enabled at IRQ 19
Feb 6 01:55:34 localhost kernel: sata_sil 0000:01:04.0: PCI INT A ->
Link[LNKA] -> GSI 19 (level, low) -> IRQ 19
Feb 6 01:55:34 localhost kernel: sata_sil 0000:01:04.0: Applying
R_ERR on DMA activate FIS errata fix
Feb 6 01:55:34 localhost kernel: scsi6 : sata_sil
Feb 6 01:55:34 localhost kernel: scsi7 : sata_sil
Feb 6 01:55:34 localhost kernel: scsi8 : sata_sil
Feb 6 01:55:34 localhost kernel: scsi9 : sata_sil
Feb 6 01:55:34 localhost kernel: ata7: SATA max UDMA/100 mmio
m1024@0xfebffc00 tf 0xfebffc80 irq 19
Feb 6 01:55:34 localhost kernel: ata8: SATA max UDMA/100 mmio
m1024@0xfebffc00 tf 0xfebffcc0 irq 19
Feb 6 01:55:34 localhost kernel: ata9: SATA max UDMA/100 mmio
m1024@0xfebffc00 tf 0xfebffe80 irq 19
Feb 6 01:55:34 localhost kernel: ata10: SATA max UDMA/100 mmio
m1024@0xfebffc00 tf 0xfebffec0 irq 19
While I have not tested this time, I have previously when getting similar
errors run spinrite (http://www.grc.com/sr/spinrite.htm) on the disks
without finding any problems. So I do believe that this is not disk errors.
The machine is running Fedora 10 with kernel 2.6.27.41-170.2.117.fc10.x86_64,
mdadm updated to the latest 3.0.3 release from Fedora 12.
Unfortunately I have too little time to do any thorough investigation
on this. My plan is to upgrade to Fedora 12 and maybe build some latest
kernel to see if that makes any difference, and if not (or probably in
any case) swap out the 3114 card with a Promise TX4 card instead.
BR Håkon Løvdal
---BEGIN log-1---
Feb 6 01:55:34 localhost kernel: md: md0 stopped.
Feb 6 01:55:34 localhost kernel: md: bind<sdc1>
Feb 6 01:55:34 localhost kernel: md: bind<sdd1>
Feb 6 01:55:34 localhost kernel: md: bind<sde1>
Feb 6 01:55:34 localhost kernel: md: bind<sdf1>
Feb 6 01:55:34 localhost kernel: md: bind<sdg1>
Feb 6 01:55:34 localhost kernel: md: bind<sdb1>
Feb 6 01:55:34 localhost kernel: md: kicking non-fresh sdd1 from array!
Feb 6 01:55:34 localhost kernel: md: unbind<sdd1>
Feb 6 01:55:34 localhost kernel: md: export_rdev(sdd1)
Feb 6 01:55:34 localhost kernel: md: kicking non-fresh sdc1 from array!
Feb 6 01:55:34 localhost kernel: md: unbind<sdc1>
Feb 6 01:55:34 localhost kernel: md: export_rdev(sdc1)
...
Feb 6 01:55:34 localhost kernel: raid6: using algorithm sse2x4 (7152 MB/s)
Feb 6 01:55:34 localhost kernel: md: raid6 personality registered for level 6
Feb 6 01:55:34 localhost kernel: md: raid5 personality registered for level 5
Feb 6 01:55:34 localhost kernel: md: raid4 personality registered for level 4
Feb 6 01:55:34 localhost kernel: raid5: device sdb1 operational as raid disk 0
Feb 6 01:55:34 localhost kernel: raid5: device sdg1 operational as raid disk 5
Feb 6 01:55:34 localhost kernel: raid5: device sdf1 operational as raid disk 4
Feb 6 01:55:34 localhost kernel: raid5: device sde1 operational as raid disk 3
Feb 6 01:55:34 localhost kernel: raid5: allocated 6396kB for md0
Feb 6 01:55:34 localhost kernel: raid5: raid level 6 set md0 active
with 4 out of 6 devices, algorithm 2
Feb 6 01:55:34 localhost kernel: RAID5 conf printout:
Feb 6 01:55:34 localhost kernel: --- rd:6 wd:4
Feb 6 01:55:34 localhost kernel: disk 0, o:1, dev:sdb1
Feb 6 01:55:34 localhost kernel: disk 3, o:1, dev:sde1
Feb 6 01:55:34 localhost kernel: disk 4, o:1, dev:sdf1
Feb 6 01:55:34 localhost kernel: disk 5, o:1, dev:sdg1
Feb 6 01:55:34 localhost kernel: md0: bitmap initialized from disk:
read 22/22 pages, set 350044 bits
Feb 6 01:55:34 localhost kernel: created bitmap (350 pages) for device md0
Feb 6 01:55:34 localhost kernel: device-mapper: multipath: version 1.0.5 loaded
---END log-1---
---BEGIN log-2---
prompt>cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sdd1[2](S) sdc1[1] sdb1[0] sdg1[5] sdf1[4] sde1[3]
2930287360 blocks super 1.2 level 6, 64k chunk, algorithm 2 [6/4] [U__UUU]
[==>..................] recovery = 10.5% (77381344/732571840)
finish=1096.9min speed=9954K/sec
bitmap: 350/350 pages [1400KB], 1024KB chunk
unused devices: <none>
prompt>mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sun Apr 5 02:04:26 2009
Raid Level : raid6
Array Size : 2930287360 (2794.54 GiB 3000.61 GB)
Used Dev Size : 732571840 (698.63 GiB 750.15 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sat Feb 6 03:39:42 2010
State : active, degraded, recovering
Active Devices : 4
Working Devices : 6
Failed Devices : 0
Spare Devices : 2
Chunk Size : 64K
Rebuild Status : 10% complete
Name : localhost:0 (local to host localhost)
UUID : 21dc7bab:50f114aa:d3cfc5e4:24d0ec1f
Events : 201694
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 8 33 1 spare rebuilding /dev/sdc1
2 0 0 2 removed
3 8 65 3 active sync /dev/sde1
4 8 81 4 active sync /dev/sdf1
5 8 97 5 active sync /dev/sdg1
2 8 49 - spare /dev/sdd1
---END log-2---
---BEGIN log-3---
Feb 6 03:04:45 localhost kernel: md: bind<sdc1>
Feb 6 03:04:46 localhost kernel: RAID5 conf printout:
Feb 6 03:04:46 localhost kernel: --- rd:6 wd:4
Feb 6 03:04:46 localhost kernel: disk 0, o:1, dev:sdb1
Feb 6 03:04:46 localhost kernel: disk 1, o:1, dev:sdc1
Feb 6 03:04:46 localhost kernel: disk 3, o:1, dev:sde1
Feb 6 03:04:46 localhost kernel: disk 4, o:1, dev:sdf1
Feb 6 03:04:46 localhost kernel: disk 5, o:1, dev:sdg1
Feb 6 03:04:46 localhost kernel: md: recovery of RAID array md0
Feb 6 03:04:46 localhost kernel: md: minimum _guaranteed_ speed:
1000 KB/sec/disk.
Feb 6 03:04:46 localhost kernel: md: using maximum available idle IO
bandwidth (but not more than 200000 KB/sec) for recovery.
Feb 6 03:04:46 localhost kernel: md: using 128k window, over a total
of 732571840 blocks.
Feb 6 03:05:01 localhost CROND[4458]: (root) CMD (LANG=C LC_ALL=C
/usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l
--confcache-file /var/lib/mrtg/mrtg.ok)
Feb 6 03:05:13 localhost kernel: md: bind<sdd1>
Feb 6 03:08:22 localhost kernel: kjournald2 starting. Commit
interval 5 seconds
Feb 6 03:08:22 localhost kernel: EXT4-fs warning: checktime reached,
running e2fsck is recommended
Feb 6 03:08:22 localhost kernel: EXT4 FS on dm-0, internal journal
Feb 6 03:08:22 localhost kernel: EXT4-fs: delayed allocation enabled
Feb 6 03:08:22 localhost kernel: EXT4-fs: file extents enabled
Feb 6 03:08:22 localhost kernel: EXT4-fs: mballoc enabled
Feb 6 03:08:22 localhost kernel: EXT4-fs: mounted filesystem with
writeback data mode.
Feb 6 03:08:22 localhost kernel: SELinux: initialized (dev dm-0, type
ext4), uses xattr
---END log-3---
---BEGIN log-4---
Feb 6 07:09:57 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:09:57 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:09:57 localhost kernel: ata8.00: cmd
25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
Feb 6 07:09:57 localhost kernel: res
51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:09:57 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:09:57 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:09:58 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:09:58 localhost kernel: ata8: EH complete
Feb 6 07:09:59 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:09:59 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:09:59 localhost kernel: ata8.00: cmd
25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
Feb 6 07:09:59 localhost kernel: res
51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:09:59 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:09:59 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:00 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:00 localhost kernel: ata8: EH complete
Feb 6 07:10:01 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:01 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:01 localhost kernel: ata8.00: cmd
25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
Feb 6 07:10:01 localhost kernel: res
51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:01 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:01 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:01 localhost CROND[8331]: (root) CMD (LANG=C LC_ALL=C
/usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l
--confcache-file /var/lib/mrtg/mrtg.ok)
Feb 6 07:10:02 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:02 localhost kernel: ata8: EH complete
Feb 6 07:10:03 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:03 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:03 localhost kernel: ata8.00: cmd
25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
Feb 6 07:10:03 localhost kernel: res
51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:03 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:03 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:04 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:04 localhost kernel: ata8: EH complete
Feb 6 07:10:05 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:05 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:05 localhost kernel: ata8.00: cmd
25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
Feb 6 07:10:05 localhost kernel: res
51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:05 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:05 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:06 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:06 localhost kernel: ata8: EH complete
Feb 6 07:10:07 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:07 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:07 localhost kernel: ata8.00: cmd
25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
Feb 6 07:10:07 localhost kernel: res
51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:07 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:07 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:08 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:08 localhost kernel: sd 7:0:0:0: [sdf] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Feb 6 07:10:08 localhost kernel: sd 7:0:0:0: [sdf] Sense Key : Medium
Error [current] [descriptor]
Feb 6 07:10:08 localhost kernel: Descriptor sense data with sense
descriptors (in hex):
Feb 6 07:10:08 localhost kernel: 72 03 11 04 00 00 00 0c 00 0a
80 00 00 00 00 00
Feb 6 07:10:08 localhost kernel: 2f 69 cd e4
Feb 6 07:10:08 localhost kernel: sd 7:0:0:0: [sdf] Add. Sense:
Unrecovered read error - auto reallocate failed
Feb 6 07:10:08 localhost kernel: end_request: I/O error, dev sdf,
sector 795463140
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463072 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5: Disk failure on sdf1, disabling device.
Feb 6 07:10:08 localhost kernel: raid5: Operation continuing on 3 devices.
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463080 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463088 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463096 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463104 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463112 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463120 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463128 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463136 on sdf1).
Feb 6 07:10:08 localhost kernel: raid5:md0: read error not
correctable (sector 795463144 on sdf1).
Feb 6 07:10:08 localhost kernel: ata8: EH complete
Feb 6 07:10:09 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:09 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:09 localhost kernel: ata8.00: cmd
25/00:10:4f:ce:69/00:03:2f:00:00/e0 tag 0 dma 401408 in
Feb 6 07:10:09 localhost kernel: res
51/40:00:65:ce:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:09 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:09 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:11 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:11 localhost kernel: ata8: EH complete
Feb 6 07:10:12 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:12 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:12 localhost kernel: ata8.00: cmd
25/00:10:4f:ce:69/00:03:2f:00:00/e0 tag 0 dma 401408 in
Feb 6 07:10:12 localhost kernel: res
51/40:00:66:ce:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:12 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:12 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:13 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:13 localhost kernel: ata8: EH complete
Feb 6 07:10:14 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:14 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:14 localhost kernel: ata8.00: cmd
25/00:10:4f:ce:69/00:03:2f:00:00/e0 tag 0 dma 401408 in
Feb 6 07:10:14 localhost kernel: res
51/40:00:66:ce:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:14 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:14 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:15 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:15 localhost kernel: ata8: EH complete
Feb 6 07:10:16 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:16 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:16 localhost kernel: ata8.00: cmd
25/00:10:4f:ce:69/00:03:2f:00:00/e0 tag 0 dma 401408 in
Feb 6 07:10:16 localhost kernel: res
51/40:00:66:ce:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:16 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:16 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:17 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:17 localhost kernel: ata8: EH complete
Feb 6 07:10:18 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:18 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:18 localhost kernel: ata8.00: cmd
25/00:10:4f:ce:69/00:03:2f:00:00/e0 tag 0 dma 401408 in
Feb 6 07:10:18 localhost kernel: res
51/40:00:66:ce:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:18 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:18 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:19 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:19 localhost kernel: ata8: EH complete
Feb 6 07:10:20 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 6 07:10:20 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
Feb 6 07:10:20 localhost kernel: ata8.00: cmd
25/00:10:4f:ce:69/00:03:2f:00:00/e0 tag 0 dma 401408 in
Feb 6 07:10:20 localhost kernel: res
51/40:00:66:ce:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 6 07:10:20 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 6 07:10:20 localhost kernel: ata8.00: error: { UNC }
Feb 6 07:10:21 localhost kernel: ata8.00: configured for UDMA/100
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Sense Key : Medium
Error [current] [descriptor]
Feb 6 07:10:21 localhost kernel: Descriptor sense data with sense
descriptors (in hex):
Feb 6 07:10:21 localhost kernel: 72 03 11 04 00 00 00 0c 00 0a
80 00 00 00 00 00
Feb 6 07:10:21 localhost kernel: 2f 69 ce 66
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Add. Sense:
Unrecovered read error - auto reallocate failed
Feb 6 07:10:21 localhost kernel: end_request: I/O error, dev sdf,
sector 795463270
Feb 6 07:10:21 localhost kernel: __ratelimit: 4 callbacks suppressed
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463200 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463208 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463216 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463224 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463232 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463240 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463248 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463256 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463264 on sdf1).
Feb 6 07:10:21 localhost kernel: raid5:md0: read error not
correctable (sector 795463272 on sdf1).
Feb 6 07:10:21 localhost kernel: ata8: EH complete
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] 1465149168
512-byte hardware sectors (750156 MB)
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Write Protect is off
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] 1465149168
512-byte hardware sectors (750156 MB)
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Write Protect is off
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Mode Sense: 00 3a 00 00
Feb 6 07:10:21 localhost kernel: sd 7:0:0:0: [sdf] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Feb 6 07:10:21 localhost kernel: md: md0: recovery done.
Feb 6 07:10:21 localhost kernel: RAID5 conf printout:
Feb 6 07:10:21 localhost kernel: --- rd:6 wd:3
Feb 6 07:10:21 localhost kernel: disk 0, o:1, dev:sdb1
Feb 6 07:10:21 localhost kernel: disk 1, o:1, dev:sdc1
Feb 6 07:10:21 localhost kernel: disk 3, o:1, dev:sde1
Feb 6 07:10:21 localhost kernel: disk 4, o:0, dev:sdf1
Feb 6 07:10:21 localhost kernel: disk 5, o:1, dev:sdg1
Feb 6 07:10:21 localhost kernel: RAID5 conf printout:
Feb 6 07:10:21 localhost kernel: --- rd:6 wd:3
Feb 6 07:10:21 localhost kernel: disk 0, o:1, dev:sdb1
Feb 6 07:10:21 localhost kernel: disk 3, o:1, dev:sde1
Feb 6 07:10:21 localhost kernel: disk 4, o:0, dev:sdf1
Feb 6 07:10:21 localhost kernel: disk 5, o:1, dev:sdg1
Feb 6 07:10:21 localhost kernel: RAID5 conf printout:
Feb 6 07:10:21 localhost kernel: --- rd:6 wd:3
Feb 6 07:10:21 localhost kernel: disk 0, o:1, dev:sdb1
Feb 6 07:10:21 localhost kernel: disk 3, o:1, dev:sde1
Feb 6 07:10:21 localhost kernel: disk 4, o:0, dev:sdf1
Feb 6 07:10:21 localhost kernel: disk 5, o:1, dev:sdg1
Feb 6 07:10:21 localhost kernel: RAID5 conf printout:
Feb 6 07:10:21 localhost kernel: --- rd:6 wd:3
Feb 6 07:10:21 localhost kernel: disk 0, o:1, dev:sdb1
Feb 6 07:10:21 localhost kernel: disk 3, o:1, dev:sde1
Feb 6 07:10:21 localhost kernel: disk 5, o:1, dev:sdg1
---END log-4---
---BEGIN log-5---
localhost>mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Creation Time : Sun Apr 5 02:04:26 2009
Raid Level : raid6
Array Size : 2930287360 (2794.54 GiB 3000.61 GB)
Used Dev Size : 732571840 (698.63 GiB 750.15 GB)
Raid Devices : 6
Total Devices : 6
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sat Feb 6 07:10:21 2010
State : active, degraded
Active Devices : 3
Working Devices : 5
Failed Devices : 1
Spare Devices : 2
Chunk Size : 64K
Name : localhost:0 (local to host localhost)
UUID : 21dc7bab:50f114aa:d3cfc5e4:24d0ec1f
Events : 202400
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 0 0 1 removed
2 0 0 2 removed
3 8 65 3 active sync /dev/sde1
4 0 0 4 removed
5 8 97 5 active sync /dev/sdg1
1 8 33 - spare /dev/sdc1
2 8 49 - spare /dev/sdd1
4 8 81 - faulty spare /dev/sdf1
---END log-5---
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: "raid5:md0: read error not correctable (sector 795463080 on sdf1)" error on controller with SIL 3114
2010-02-08 11:11 "raid5:md0: read error not correctable (sector 795463080 on sdf1)" error on controller with SIL 3114 Håkon Løvdal
@ 2010-02-09 5:13 ` Robert Hancock
2010-02-17 2:42 ` Håkon Løvdal
2010-02-20 13:05 ` Håkon Løvdal
1 sibling, 1 reply; 4+ messages in thread
From: Robert Hancock @ 2010-02-09 5:13 UTC (permalink / raw)
To: Håkon Løvdal; +Cc: linux-ide
On 02/08/2010 05:11 AM, Håkon Løvdal wrote:
> Hi. I have had some trouble with the machine I want to have as a file server.
>
> After having let the "get raid up and running reliably" project lie
> dormant for some time, I tried again this Friday. After connecting the
> disks, the status was the following: 4 out of 6 disk in a raid6 setup
> were recognised (see log-1). I was able to mount the volume when the
> machine was finished booting.
>
> I then added the two missing disks with mdadm, one of them started
> rebuilding and the other one were not recognised in some way (log-2).
> The rebuild of the disk was successfull (log-3), but later some errors
> occured, see log-4 below, and now only three disks are left in the
> array (log-5).
>
> Are these errors related to Tejun's recent statement "Sil3112/3114 are
> now virtually the only controllers with occassional and unresolved data
> corruption issues."? Disks sda (hosting root file system for os), sdb
> sdc and sdd are connected the motherboard while sde, sdf and sdg are
> connected to a controller card using 3114:
..
> ---BEGIN log-4---
> Feb 6 07:09:57 localhost kernel: ata8.00: exception Emask 0x0 SAct
> 0x0 SErr 0x0 action 0x0
> Feb 6 07:09:57 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
> Feb 6 07:09:57 localhost kernel: ata8.00: cmd
> 25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
> Feb 6 07:09:57 localhost kernel: res
> 51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
> Feb 6 07:09:57 localhost kernel: ata8.00: status: { DRDY ERR }
> Feb 6 07:09:57 localhost kernel: ata8.00: error: { UNC }
That's fairly definitive, uncorrected read error reported by the drive.
You might want to check its SMART status. Could be a bad drive, or
potentially other causes like excessive vibration, high temperature,
power issues..
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: "raid5:md0: read error not correctable (sector 795463080 on sdf1)" error on controller with SIL 3114
2010-02-09 5:13 ` Robert Hancock
@ 2010-02-17 2:42 ` Håkon Løvdal
0 siblings, 0 replies; 4+ messages in thread
From: Håkon Løvdal @ 2010-02-17 2:42 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-ide
On 9 February 2010 06:13, Robert Hancock <hancockrwd@gmail.com> wrote:
> On 02/08/2010 05:11 AM, Håkon Løvdal wrote:
>> ---BEGIN log-4---
>> Feb 6 07:09:57 localhost kernel: ata8.00: exception Emask 0x0 SAct
>> 0x0 SErr 0x0 action 0x0
>> Feb 6 07:09:57 localhost kernel: ata8.00: BMDMA2 stat 0x6c0009
>> Feb 6 07:09:57 localhost kernel: ata8.00: cmd
>> 25/00:80:cf:cd:69/00:00:2f:00:00/e0 tag 0 dma 65536 in
>> Feb 6 07:09:57 localhost kernel: res
>> 51/40:00:e4:cd:69/00:00:2f:00:00/e0 Emask 0x9 (media error)
>> Feb 6 07:09:57 localhost kernel: ata8.00: status: { DRDY ERR }
>> Feb 6 07:09:57 localhost kernel: ata8.00: error: { UNC }
>
> That's fairly definitive, uncorrected read error reported by the drive. You
> might want to check its SMART status. Could be a bad drive, or potentially
> other causes like excessive vibration, high temperature, power issues..
For all of sdb, sdc, sdd, sde, sdf and sdg they all have had a
normalized value of 100 for the whole lifetime of the disk (I have
a cron job to capture output from smartctl nightly for reference
and have now checked those files) for all the critical attributes listed at
http://en.wikipedia.org/wiki/S.M.A.R.T.#ATA_S.M.A.R.T._attributes
1 Raw_Read_Error_Rate
5 Reallocated_Sector_Ct
10 Spin_Retry_Count
184 Unknown_Attribute
188 Unknown_Attribute
196 Reallocated_Event_Count
197 Current_Pending_Sector
198 Offline_Uncorrectable
201 Soft_Read_Error_Rate
except for Soft_Read_Error_Rate which switches between either 100 or 253.
The disks are now placed in a Image Shapetek EYE-981SC tower[1] with good space,
and the disks are placed in 5.25" bays with rubber hard disk stabilizers[1] to
reduce vibration. There is therefore good airflow around all the
disks, and I keep
one side of the tower case open, so temperature should not be a
problem (any longer).
In the previous case space could be more tight. I see that last summer
hde and hdf had temperatures of around 45-55°C in June/July which does not
sound too good[3]. They are still part of the raid, whereas hdc which has
an excellent temperature profile of 35-45°C and hdd (28-38) are the two
disks being currently kicked out of the rad.
There might be some issues with the PSU[4] (I am waiting for a new one). I doubt
there are any problem with line electricity because the quality is
generally quite
good here in Norway and besides the machine is behind an UPS.
smartctl -l selftest /dev/sde gives
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90%
795 1465145815
# 2 Conveyance offline Completed: read failure 90%
794 1465145815
# 3 Offline Completed: read failure 00%
790 1465145815
# 4 Short offline Completed: read failure 20%
787 1465145815
None of the other disks report any selftest failures.
So sde and sdf show some sign of trouble (temperature, selftest and ata8.00
exception above), but they are not kicked out of the raid. On the other hand
sdc and sdd are both kicked out and I cannot see any obvious signs of hardware
trouble here. Any suggestions?
BR Håkon Løvdal
[1]
http://translate.google.com/translate?js=y&prev=_t&hl=en&ie=UTF-8&layout=1&eotf=1&u=http%3A%2F%2Fwww.hardware.no%2Fartikler%2Fi_s_981_servertower%2F46558%2Futskrift&sl=no&tl=en
[2]
http://www.scythe-eu.com/en/products/pc-accessory/hard-disk-stabilizer-2.html
[3]
http://en.wikibooks.org/wiki/Minimizing_hard_disk_drive_failure_and_data_loss#Temperature_control
[4]
350W, Point of view, VP-3504
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: "raid5:md0: read error not correctable (sector 795463080 on sdf1)" error on controller with SIL 3114
2010-02-08 11:11 "raid5:md0: read error not correctable (sector 795463080 on sdf1)" error on controller with SIL 3114 Håkon Løvdal
2010-02-09 5:13 ` Robert Hancock
@ 2010-02-20 13:05 ` Håkon Løvdal
1 sibling, 0 replies; 4+ messages in thread
From: Håkon Løvdal @ 2010-02-20 13:05 UTC (permalink / raw)
To: linux-ide
On 8 February 2010 12:11, Håkon Løvdal <hlovdal@gmail.com> wrote:
> While I have not tested this time, I have previously when getting similar
> errors run spinrite (http://www.grc.com/sr/spinrite.htm) on the disks
> without finding any problems. So I do believe that this is not disk errors.
>
> The machine is running Fedora 10 with kernel 2.6.27.41-170.2.117.fc10.x86_64,
> mdadm updated to the latest 3.0.3 release from Fedora 12.
>
> Unfortunately I have too little time to do any thorough investigation
> on this. My plan is to upgrade to Fedora 12 and maybe build some latest
> kernel to see if that makes any difference, and if not (or probably in
> any case) swap out the 3114 card with a Promise TX4 card instead.
Update: Seems to be disk error after all. I changed to Promise TX4
and updated to Fedora 12. Rebuilding the raid went ok, but then the
following day the following occurred:
Feb 19 09:54:30 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:30 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:30 localhost kernel: ata8.00: cmd
25/00:00:30:cc:69/00:03:2f:00:00/e0 tag 0 dma 393216 in
Feb 19 09:54:30 localhost kernel: res
51/40:00:e4:cd:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:30 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:30 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:31 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:31 localhost kernel: ata8: EH complete
Feb 19 09:54:32 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:32 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:32 localhost kernel: ata8.00: cmd
25/00:00:30:cc:69/00:03:2f:00:00/e0 tag 0 dma 393216 in
Feb 19 09:54:32 localhost kernel: res
51/40:00:e4:cd:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:32 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:32 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:33 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:33 localhost kernel: ata8: EH complete
Feb 19 09:54:34 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:34 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:34 localhost kernel: ata8.00: cmd
25/00:00:30:cc:69/00:03:2f:00:00/e0 tag 0 dma 393216 in
Feb 19 09:54:34 localhost kernel: res
51/40:00:e4:cd:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:34 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:34 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:35 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:35 localhost kernel: ata8: EH complete
Feb 19 09:54:36 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:36 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:36 localhost kernel: ata8.00: cmd
25/00:00:30:cc:69/00:03:2f:00:00/e0 tag 0 dma 393216 in
Feb 19 09:54:36 localhost kernel: res
51/40:00:e4:cd:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:36 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:36 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:37 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:37 localhost kernel: ata8: EH complete
Feb 19 09:54:38 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:38 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:38 localhost kernel: ata8.00: cmd
25/00:00:30:cc:69/00:03:2f:00:00/e0 tag 0 dma 393216 in
Feb 19 09:54:38 localhost kernel: res
51/40:00:e4:cd:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:38 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:38 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:39 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:39 localhost kernel: ata8: EH complete
Feb 19 09:54:40 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:40 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:40 localhost kernel: ata8.00: cmd
25/00:00:30:cc:69/00:03:2f:00:00/e0 tag 0 dma 393216 in
Feb 19 09:54:40 localhost kernel: res
51/40:00:e4:cd:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:40 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:40 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:41 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:41 localhost kernel: sd 7:0:0:0: [sdf] Unhandled sense code
Feb 19 09:54:41 localhost kernel: sd 7:0:0:0: [sdf] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 19 09:54:41 localhost kernel: sd 7:0:0:0: [sdf] Sense Key : Medium
Error [current] [descriptor]
Feb 19 09:54:41 localhost kernel: Descriptor sense data with sense
descriptors (in hex):
Feb 19 09:54:41 localhost kernel: 72 03 11 04 00 00 00 0c 00 0a
80 00 00 00 00 00
Feb 19 09:54:41 localhost kernel: 2f 69 cd e4
Feb 19 09:54:41 localhost kernel: sd 7:0:0:0: [sdf] Add. Sense:
Unrecovered read error - auto reallocate failed
Feb 19 09:54:41 localhost kernel: end_request: I/O error, dev sdf,
sector 795463140
Feb 19 09:54:41 localhost kernel: ata8: EH complete
Feb 19 09:54:43 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:43 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:43 localhost kernel: ata8.00: cmd
25/00:e0:30:cf:69/00:00:2f:00:00/e0 tag 0 dma 114688 in
Feb 19 09:54:43 localhost kernel: res
51/40:00:36:cf:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:43 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:43 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:44 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:44 localhost kernel: ata8: EH complete
Feb 19 09:54:45 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:45 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:45 localhost kernel: ata8.00: cmd
25/00:e0:30:cf:69/00:00:2f:00:00/e0 tag 0 dma 114688 in
Feb 19 09:54:45 localhost kernel: res
51/40:00:36:cf:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:45 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:45 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:46 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:46 localhost kernel: ata8: EH complete
Feb 19 09:54:47 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:47 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:47 localhost kernel: ata8.00: cmd
25/00:e0:30:cf:69/00:00:2f:00:00/e0 tag 0 dma 114688 in
Feb 19 09:54:47 localhost kernel: res
51/40:00:36:cf:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:47 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:47 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:48 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:48 localhost kernel: ata8: EH complete
Feb 19 09:54:49 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:49 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:49 localhost kernel: ata8.00: cmd
25/00:e0:30:cf:69/00:00:2f:00:00/e0 tag 0 dma 114688 in
Feb 19 09:54:49 localhost kernel: res
51/40:00:36:cf:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:49 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:49 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:50 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:50 localhost kernel: ata8: EH complete
Feb 19 09:54:51 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:51 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:51 localhost kernel: ata8.00: cmd
25/00:e0:30:cf:69/00:00:2f:00:00/e0 tag 0 dma 114688 in
Feb 19 09:54:51 localhost kernel: res
51/40:00:36:cf:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:51 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:51 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:52 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:52 localhost kernel: ata8: EH complete
Feb 19 09:54:53 localhost kernel: ata8.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Feb 19 09:54:53 localhost kernel: ata8.00: port_status 0x20200000
Feb 19 09:54:53 localhost kernel: ata8.00: cmd
25/00:e0:30:cf:69/00:00:2f:00:00/e0 tag 0 dma 114688 in
Feb 19 09:54:53 localhost kernel: res
51/40:00:36:cf:69/40:00:2f:00:00/e0 Emask 0x9 (media error)
Feb 19 09:54:53 localhost kernel: ata8.00: status: { DRDY ERR }
Feb 19 09:54:53 localhost kernel: ata8.00: error: { UNC }
Feb 19 09:54:54 localhost kernel: ata8.00: configured for UDMA/133
Feb 19 09:54:54 localhost kernel: sd 7:0:0:0: [sdf] Unhandled sense code
Feb 19 09:54:54 localhost kernel: sd 7:0:0:0: [sdf] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Feb 19 09:54:54 localhost kernel: sd 7:0:0:0: [sdf] Sense Key : Medium
Error [current] [descriptor]
Feb 19 09:54:54 localhost kernel: Descriptor sense data with sense
descriptors (in hex):
Feb 19 09:54:54 localhost kernel: 72 03 11 04 00 00 00 0c 00 0a
80 00 00 00 00 00
Feb 19 09:54:54 localhost kernel: 2f 69 cf 36
Feb 19 09:54:54 localhost kernel: sd 7:0:0:0: [sdf] Add. Sense:
Unrecovered read error - auto reallocate failed
Feb 19 09:54:54 localhost kernel: end_request: I/O error, dev sdf,
sector 795463478
Feb 19 09:54:54 localhost kernel: ata8: EH complete
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461088 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461096 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461104 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461112 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461120 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461128 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461136 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461144 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461152 on sdf1)
Feb 19 09:54:54 localhost kernel: raid5:md0: read error corrected (8
sectors at 795461160 on sdf1)
A new disk is ordered to replace sdf.
BR Håkon Løvdal
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-02-20 13:06 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-08 11:11 "raid5:md0: read error not correctable (sector 795463080 on sdf1)" error on controller with SIL 3114 Håkon Løvdal
2010-02-09 5:13 ` Robert Hancock
2010-02-17 2:42 ` Håkon Løvdal
2010-02-20 13:05 ` Håkon Løvdal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).