January 19, 201115 yr so last night i noticed my parity drive was showing 1 error. i did a parity check and now it shows 8. what should i do? thx my sys log is 830mb so i cannot attach it and its to long to post so i only included the last few days Jan 16 23:38:35 THE shfs: shfs_flush: close: (9) Bad file descriptor Jan 16 23:38:35 THE shfs: shfs_flush: close: (9) Bad file descriptor Jan 17 00:45:56 THE kernel: mdcmd (658): spindown 1 Jan 17 00:55:06 THE kernel: mdcmd (659): spindown 0 Jan 17 01:00:17 THE kernel: mdcmd (660): spindown 2 Jan 17 01:00:38 THE kernel: mdcmd (661): spindown 4 Jan 17 01:00:49 THE kernel: mdcmd (662): spindown 3 Jan 17 02:05:54 THE kernel: mdcmd (663): spindown 5 Jan 17 02:06:25 THE kernel: mdcmd (664): spindown 4 Jan 17 09:07:26 THE kernel: mdcmd (665): spindown 2 Jan 17 09:07:37 THE kernel: mdcmd (666): spindown 1 Jan 17 09:07:38 THE kernel: mdcmd (667): spindown 4 Jan 17 09:07:49 THE kernel: mdcmd (668): spindown 3 Jan 17 18:11:24 THE kernel: mdcmd (669): spindown 4 Jan 17 19:21:51 THE kernel: mdcmd (670): spindown 2 Jan 17 19:22:02 THE kernel: mdcmd (671): spindown 4 Jan 17 19:22:23 THE kernel: mdcmd (672): spindown 3 Jan 17 19:22:44 THE kernel: mdcmd (673): spindown 5 Jan 17 19:23:25 THE kernel: mdcmd (674): spindown 1 Jan 17 20:34:59 THE kernel: mdcmd (675): spindown 0 Jan 17 22:50:56 THE kernel: mdcmd (676): spindown 1 Jan 17 22:56:37 THE kernel: mdcmd (677): spindown 2 Jan 17 22:56:38 THE kernel: mdcmd (678): spindown 3 Jan 17 22:56:39 THE kernel: mdcmd (679): spindown 5 Jan 17 23:17:36 THE shfs: shfs_rmdir: rmdir: /mnt/disk4/MUSIC/UNSORTED/RISA OLD SCHOOL SHIT (39) Directory not empty Jan 17 23:17:36 THE shfs: shfs_rmdir: rmdir: /mnt/disk4/MUSIC/UNSORTED/RISA OLD SCHOOL SHIT/SEP 06 JAMS (39) Directory not empty Jan 17 23:17:36 THE shfs: shfs_rmdir: rmdir: /mnt/disk4/MUSIC/UNSORTED/RISA OLD SCHOOL SHIT/FEB O7 JAMS (39) Directory not empty Jan 17 23:17:38 THE shfs: shfs_rmdir: rmdir: /mnt/disk4/MUSIC/UNSORTED/RISA OLD SCHOOL SHIT/JUL 07 JAMS (39) Directory not empty Jan 17 23:17:40 THE shfs: shfs_rmdir: rmdir: /mnt/disk4/MUSIC/UNSORTED/RISA OLD SCHOOL SHIT/MAY 2007 JAMS (39) Directory not empty Jan 17 23:17:41 THE shfs: shfs_rmdir: rmdir: /mnt/disk4/MUSIC/UNSORTED/RISA OLD SCHOOL SHIT/JUNE 06 JAMS (39) Directory not empty Jan 17 23:17:42 THE shfs: shfs_rmdir: rmdir: /mnt/disk4/MUSIC/UNSORTED/RISA OLD SCHOOL SHIT/APR 06 JAMS (39) Directory not empty Jan 18 00:21:16 THE kernel: mdcmd (680): spindown 0 Jan 18 00:31:57 THE kernel: mdcmd (681): spindown 1 Jan 18 00:32:17 THE kernel: mdcmd (682): spindown 2 Jan 18 00:32:18 THE kernel: mdcmd (683): spindown 3 Jan 18 00:32:59 THE kernel: mdcmd (684): spindown 5 Jan 18 01:15:00 THE kernel: mdcmd (685): spindown 4 Jan 18 13:00:46 THE kernel: mdcmd (686): spindown 0 Jan 18 13:00:46 THE kernel: mdcmd (687): spindown 4 Jan 18 13:11:17 THE kernel: mdcmd (688): spindown 2 Jan 18 14:32:29 THE kernel: mdcmd (689): spindown 0 Jan 18 14:35:50 THE kernel: mdcmd (690): spindown 2 Jan 18 15:11:31 THE kernel: mdcmd (691): spindown 5 Jan 18 15:13:12 THE kernel: mdcmd (692): spindown 3 Jan 18 15:15:13 THE kernel: mdcmd (693): spindown 1 Jan 18 16:44:45 THE kernel: mdcmd (694): spindown 2 Jan 18 16:45:26 THE kernel: mdcmd (695): spindown 1 Jan 18 16:45:37 THE kernel: mdcmd (696): spindown 3 Jan 18 17:42:08 THE kernel: mdcmd (697): spindown 5 Jan 18 18:25:30 THE kernel: mdcmd (698): spindown 4 Jan 18 19:50:43 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 18 19:50:43 THE kernel: ata4.00: irq_stat 0x40000001 Jan 18 19:50:43 THE kernel: ata4.00: failed command: READ DMA EXT Jan 18 19:50:43 THE kernel: ata4.00: cmd 25/00:08:3f:00:ac/00:00:e7:00:00/e0 tag 0 dma 4096 in Jan 18 19:50:43 THE kernel: res 51/40:00:3f:00:ac/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 18 19:50:43 THE kernel: ata4.00: status: { DRDY ERR } Jan 18 19:50:43 THE kernel: ata4.00: error: { UNC } Jan 18 19:50:43 THE kernel: ata4.00: configured for UDMA/33 Jan 18 19:50:43 THE kernel: ata4: EH complete Jan 18 19:50:46 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 18 19:50:46 THE kernel: ata4.00: irq_stat 0x40000001 Jan 18 19:50:46 THE kernel: ata4.00: failed command: READ DMA EXT Jan 18 19:50:46 THE kernel: ata4.00: cmd 25/00:08:3f:00:ac/00:00:e7:00:00/e0 tag 0 dma 4096 in Jan 18 19:50:46 THE kernel: res 51/40:00:3f:00:ac/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 18 19:50:46 THE kernel: ata4.00: status: { DRDY ERR } Jan 18 19:50:46 THE kernel: ata4.00: error: { UNC } Jan 18 19:50:46 THE kernel: ata4.00: configured for UDMA/33 Jan 18 19:50:46 THE kernel: ata4: EH complete Jan 18 19:50:49 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 18 19:50:49 THE kernel: ata4.00: irq_stat 0x40000001 Jan 18 19:50:49 THE kernel: ata4.00: failed command: READ DMA EXT Jan 18 19:50:49 THE kernel: ata4.00: cmd 25/00:08:3f:00:ac/00:00:e7:00:00/e0 tag 0 dma 4096 in Jan 18 19:50:49 THE kernel: res 51/40:00:3f:00:ac/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 18 19:50:49 THE kernel: ata4.00: status: { DRDY ERR } Jan 18 19:50:49 THE kernel: ata4.00: error: { UNC } Jan 18 19:50:49 THE kernel: ata4.00: configured for UDMA/33 Jan 18 19:50:49 THE kernel: ata4: EH complete Jan 18 19:50:52 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 18 19:50:52 THE kernel: ata4.00: irq_stat 0x40000001 Jan 18 19:50:52 THE kernel: ata4.00: failed command: READ DMA EXT Jan 18 19:50:52 THE kernel: ata4.00: cmd 25/00:08:3f:00:ac/00:00:e7:00:00/e0 tag 0 dma 4096 in Jan 18 19:50:52 THE kernel: res 51/40:00:3f:00:ac/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 18 19:50:52 THE kernel: ata4.00: status: { DRDY ERR } Jan 18 19:50:52 THE kernel: ata4.00: error: { UNC } Jan 18 19:50:52 THE kernel: ata4.00: configured for UDMA/33 Jan 18 19:50:52 THE kernel: ata4: EH complete Jan 18 19:50:55 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 18 19:50:55 THE kernel: ata4.00: irq_stat 0x40000001 Jan 18 19:50:55 THE kernel: ata4.00: failed command: READ DMA EXT Jan 18 19:50:55 THE kernel: ata4.00: cmd 25/00:08:3f:00:ac/00:00:e7:00:00/e0 tag 0 dma 4096 in Jan 18 19:50:55 THE kernel: res 51/40:00:3f:00:ac/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 18 19:50:55 THE kernel: ata4.00: status: { DRDY ERR } Jan 18 19:50:55 THE kernel: ata4.00: error: { UNC } Jan 18 19:50:55 THE kernel: ata4.00: configured for UDMA/33 Jan 18 19:50:55 THE kernel: ata4: EH complete Jan 18 19:50:58 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 18 19:50:58 THE kernel: ata4.00: irq_stat 0x40000001 Jan 18 19:50:58 THE kernel: ata4.00: failed command: READ DMA EXT Jan 18 19:50:58 THE kernel: ata4.00: cmd 25/00:08:3f:00:ac/00:00:e7:00:00/e0 tag 0 dma 4096 in Jan 18 19:50:58 THE kernel: res 51/40:00:3f:00:ac/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 18 19:50:58 THE kernel: ata4.00: status: { DRDY ERR } Jan 18 19:50:58 THE kernel: ata4.00: error: { UNC } Jan 18 19:50:58 THE kernel: ata4.00: configured for UDMA/33 Jan 18 19:50:58 THE kernel: sd 4:0:0:0: [sdd] Unhandled sense code Jan 18 19:50:58 THE kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 Jan 18 19:50:58 THE kernel: sd 4:0:0:0: [sdd] Sense Key : 0x3 [current] [descriptor] Jan 18 19:50:58 THE kernel: Descriptor sense data with sense descriptors (in hex): Jan 18 19:50:58 THE kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jan 18 19:50:58 THE kernel: e7 ac 00 3f Jan 18 19:50:58 THE kernel: sd 4:0:0:0: [sdd] ASC=0x11 ASCQ=0x4 Jan 18 19:50:58 THE kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 e7 ac 00 3f 00 00 08 00 Jan 18 19:50:58 THE kernel: end_request: I/O error, dev sdd, sector 3886809151 Jan 18 19:50:58 THE kernel: ata4: EH complete Jan 18 19:50:58 THE kernel: md: disk0 read error Jan 18 19:50:58 THE kernel: handle_stripe read error: 3886809088/0, count: 1 Jan 18 20:51:02 THE kernel: mdcmd (699): spindown 2 Jan 18 21:37:50 THE kernel: mdcmd (700): spindown 1 Jan 18 21:48:46 THE kernel: mdcmd (701): spindown 0 Jan 18 22:28:39 THE kernel: mdcmd (702): spindown 5 Jan 18 22:46:43 THE kernel: mdcmd (703): spindown 1 Jan 18 23:55:18 THE emhttp: Spinning down all drives... Jan 18 23:55:18 THE kernel: mdcmd (704): spindown 0 Jan 18 23:55:18 THE kernel: mdcmd (705): spindown 1 Jan 18 23:55:19 THE kernel: mdcmd (706): spindown 2 Jan 18 23:55:20 THE kernel: mdcmd (707): spindown 3 Jan 18 23:55:21 THE kernel: mdcmd (708): spindown 4 Jan 18 23:55:22 THE kernel: mdcmd (709): spindown 5 Jan 19 00:04:29 THE emhttp: Spinning down all drives... Jan 19 00:04:29 THE kernel: mdcmd (710): spindown 0 Jan 19 00:04:29 THE kernel: mdcmd (711): spindown 1 Jan 19 00:04:30 THE kernel: mdcmd (712): spindown 2 Jan 19 00:04:31 THE kernel: mdcmd (713): spindown 3 Jan 19 00:04:32 THE kernel: mdcmd (714): spindown 4 Jan 19 00:04:32 THE kernel: mdcmd (715): spindown 5 Jan 19 00:05:07 THE kernel: mdcmd (716): check CORRECT Jan 19 00:05:07 THE kernel: md: recovery thread woken up ... Jan 19 00:05:07 THE kernel: md: recovery thread checking parity... Jan 19 00:05:07 THE kernel: md: using 1152k window, over a total of 1953514552 blocks. Jan 19 07:04:52 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 19 07:04:52 THE kernel: ata4.00: irq_stat 0x40000001 Jan 19 07:04:52 THE kernel: ata4.00: failed command: READ DMA EXT Jan 19 07:04:52 THE kernel: ata4.00: cmd 25/00:00:77:fc:bb/00:04:e7:00:00/e0 tag 0 dma 524288 in Jan 19 07:04:52 THE kernel: res 51/40:2f:3f:00:bc/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 19 07:04:52 THE kernel: ata4.00: status: { DRDY ERR } Jan 19 07:04:52 THE kernel: ata4.00: error: { UNC } Jan 19 07:04:52 THE kernel: ata4.00: configured for UDMA/33 Jan 19 07:04:52 THE kernel: ata4: EH complete Jan 19 07:04:55 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 19 07:04:55 THE kernel: ata4.00: irq_stat 0x40000001 Jan 19 07:04:55 THE kernel: ata4.00: failed command: READ DMA EXT Jan 19 07:04:55 THE kernel: ata4.00: cmd 25/00:00:77:fc:bb/00:04:e7:00:00/e0 tag 0 dma 524288 in Jan 19 07:04:55 THE kernel: res 51/40:2f:3f:00:bc/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 19 07:04:55 THE kernel: ata4.00: status: { DRDY ERR } Jan 19 07:04:55 THE kernel: ata4.00: error: { UNC } Jan 19 07:04:55 THE kernel: ata4.00: configured for UDMA/33 Jan 19 07:04:55 THE kernel: ata4: EH complete Jan 19 07:04:58 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 19 07:04:58 THE kernel: ata4.00: irq_stat 0x40000001 Jan 19 07:04:58 THE kernel: ata4.00: failed command: READ DMA EXT Jan 19 07:04:58 THE kernel: ata4.00: cmd 25/00:00:77:fc:bb/00:04:e7:00:00/e0 tag 0 dma 524288 in Jan 19 07:04:58 THE kernel: res 51/40:2f:3f:00:bc/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 19 07:04:58 THE kernel: ata4.00: status: { DRDY ERR } Jan 19 07:04:58 THE kernel: ata4.00: error: { UNC } Jan 19 07:04:58 THE kernel: ata4.00: configured for UDMA/33 Jan 19 07:04:58 THE kernel: ata4: EH complete Jan 19 07:05:01 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 19 07:05:01 THE kernel: ata4.00: irq_stat 0x40000001 Jan 19 07:05:01 THE kernel: ata4.00: failed command: READ DMA EXT Jan 19 07:05:01 THE kernel: ata4.00: cmd 25/00:00:77:fc:bb/00:04:e7:00:00/e0 tag 0 dma 524288 in Jan 19 07:05:01 THE kernel: res 51/40:2f:3f:00:bc/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 19 07:05:01 THE kernel: ata4.00: status: { DRDY ERR } Jan 19 07:05:01 THE kernel: ata4.00: error: { UNC } Jan 19 07:05:01 THE kernel: ata4.00: configured for UDMA/33 Jan 19 07:05:01 THE kernel: ata4: EH complete Jan 19 07:05:04 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 19 07:05:04 THE kernel: ata4.00: irq_stat 0x40000001 Jan 19 07:05:04 THE kernel: ata4.00: failed command: READ DMA EXT Jan 19 07:05:04 THE kernel: ata4.00: cmd 25/00:00:77:fc:bb/00:04:e7:00:00/e0 tag 0 dma 524288 in Jan 19 07:05:04 THE kernel: res 51/40:2f:3f:00:bc/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 19 07:05:04 THE kernel: ata4.00: status: { DRDY ERR } Jan 19 07:05:04 THE kernel: ata4.00: error: { UNC } Jan 19 07:05:04 THE kernel: ata4.00: configured for UDMA/33 Jan 19 07:05:04 THE kernel: ata4: EH complete Jan 19 07:05:07 THE kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 19 07:05:07 THE kernel: ata4.00: irq_stat 0x40000001 Jan 19 07:05:07 THE kernel: ata4.00: failed command: READ DMA EXT Jan 19 07:05:07 THE kernel: ata4.00: cmd 25/00:00:77:fc:bb/00:04:e7:00:00/e0 tag 0 dma 524288 in Jan 19 07:05:07 THE kernel: res 51/40:2f:3f:00:bc/36:00:e7:00:00/e0 Emask 0x9 (media error) Jan 19 07:05:07 THE kernel: ata4.00: status: { DRDY ERR } Jan 19 07:05:07 THE kernel: ata4.00: error: { UNC } Jan 19 07:05:07 THE kernel: ata4.00: configured for UDMA/33 Jan 19 07:05:07 THE kernel: sd 4:0:0:0: [sdd] Unhandled sense code Jan 19 07:05:07 THE kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 Jan 19 07:05:07 THE kernel: sd 4:0:0:0: [sdd] Sense Key : 0x3 [current] [descriptor] Jan 19 07:05:07 THE kernel: Descriptor sense data with sense descriptors (in hex): Jan 19 07:05:07 THE kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Jan 19 07:05:07 THE kernel: e7 bc 00 3f Jan 19 07:05:07 THE kernel: sd 4:0:0:0: [sdd] ASC=0x11 ASCQ=0x4 Jan 19 07:05:07 THE kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 e7 bb fc 77 00 04 00 00 Jan 19 07:05:07 THE kernel: end_request: I/O error, dev sdd, sector 3887857727 Jan 19 07:05:07 THE kernel: ata4: EH complete Jan 19 07:05:07 THE kernel: md: disk0 read error Jan 19 07:05:07 THE kernel: handle_stripe read error: 3887857664/0, count: 1 Jan 19 07:05:07 THE kernel: md: disk0 read error Jan 19 07:05:07 THE kernel: handle_stripe read error: 3887857672/0, count: 1 Jan 19 07:05:07 THE kernel: md: disk0 read error Jan 19 07:05:07 THE kernel: handle_stripe read error: 3887857680/0, count: 1 Jan 19 07:05:07 THE kernel: md: disk0 read error Jan 19 07:05:07 THE kernel: handle_stripe read error: 3887857688/0, count: 1 Jan 19 07:05:07 THE kernel: md: disk0 read error Jan 19 07:05:07 THE kernel: handle_stripe read error: 3887857696/0, count: 1 Jan 19 07:05:07 THE kernel: md: disk0 read error Jan 19 07:05:07 THE kernel: handle_stripe read error: 3887857704/0, count: 1 Jan 19 07:05:07 THE kernel: md: disk0 read error Jan 19 07:05:07 THE kernel: handle_stripe read error: 3887857712/0, count: 1 Jan 19 07:08:39 THE kernel: md: sync done. time=25408sec rate=76885K/sec Jan 19 07:08:39 THE kernel: md: recovery thread sync completion status: 0 Jan 19 08:08:48 THE kernel: mdcmd (717): spindown 0 Jan 19 08:08:48 THE kernel: mdcmd (718): spindown 1 Jan 19 08:08:49 THE kernel: mdcmd (719): spindown 2 Jan 19 08:08:49 THE kernel: mdcmd (720): spindown 3 Jan 19 08:08:50 THE kernel: mdcmd (721): spindown 4 Jan 19 08:08:51 THE kernel: mdcmd (722): spindown 5 Jan 19 11:32:53 THE kernel: mdcmd (723): spindown 2 Jan 19 12:03:31 THE in.telnetd[8543]: connect from 192.168.1.106 (192.168.1.106) Jan 19 12:04:02 THE login[8544]: ROOT LOGIN on `pts/0' from `192.168.1.106'
January 19, 201115 yr UNC errors are unreadable sectors. It looks like your parity disk might be a candidate for a SMART report as a minimum, and a replacement if the un-readable sectors continue. (they do not typically stop, and frequently get worse, especially if the drive has been in service for a while) Hint: now is not a good time to be waiting for a sale on a replacement drive. purchase/order one, even if not on sale. Joe L.
January 19, 201115 yr Author i have 1 drive in my array that i could move the data onto the other drives to free it up. can i remove it from the array then use it for my parity drive so i can rma the failing one?
January 19, 201115 yr i have 1 drive in my array that i could move the data onto the other drives to free it up. can i remove it from the array then use it for my parity drive so i can rma the failing one? You could, but you would need to Empty the drive to free it up, moving files elsewhere. Un-assign the drive as a data drive Assign the drive as the new parity drive Log in and type initconfig Respond with "Yes" (Capital "Y", lower case "es") Start the array and let it re-compute parity on the substitute drive. Then, press "Check" to make sure what was written to the parity drive is readable, let it do a full parity check. Then, Stop the array, power down, remove the bad drive for an RMA Joe L.
January 19, 201115 yr Author ok thx i will do that and rma the drive. dont really want to but a new drive at this moment as i have about 3tbs of free space still and the parity drive is only 2
January 19, 201115 yr Author ok change of plan just did the rma process and saw that i can do the advanced replacement so a new drive is on the way and ill just swap it and mail them the defective one.once its here do i just unassign it sawp the new drive in and reassign it? thx
January 20, 201115 yr do i just unassign it sawp the new drive in and reassign it? thx Don't even need to un-assign. Just replace the old drive with the new and unraid will notice the replacement. It will not start until you press "Start"
Archived
This topic is now archived and is closed to further replies.