August 17, 201312 yr Hey everyone. First time I have run into any issues since I started using UnRaid and I am trying to figure out what is going on. I picked up some new drives the other day and shut down my server to install them. After starting back up I began preclearing a single new drive and later went to copy some new files to the array. In the past I have had no issues with this. For some reason I have started seeing errors stating Handle_Stripe Read Error when I transfer files to the array while the other drive is preclearing. I have a full syslog I can provide but it's too large to attach and I have posted an excerpt. I don't think it would be a loose cable but any thoughts or ideas are appreciated. Resolution: *The disk ended up having multiple bad sectors that were not being reported in Smart Reports.*
August 17, 201312 yr Author Aug 15 18:13:48 Cerberus kernel: sd 0:0:0:0: [sdd] Unhandled sense code Aug 15 18:13:48 Cerberus kernel: sd 0:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 Aug 15 18:13:48 Cerberus kernel: sd 0:0:0:0: [sdd] Sense Key : 0x3 [current] [descriptor] Aug 15 18:13:48 Cerberus kernel: Descriptor sense data with sense descriptors (in hex): Aug 15 18:13:48 Cerberus kernel: 72 03 11 00 00 00 00 0c 00 0a 80 00 00 00 00 01 Aug 15 18:13:48 Cerberus kernel: 44 49 17 78 Aug 15 18:13:48 Cerberus kernel: sd 0:0:0:0: [sdd] ASC=0x11 ASCQ=0x0 Aug 15 18:13:48 Cerberus kernel: sd 0:0:0:0: [sdd] CDB: cdb[0]=0x88: 88 00 00 00 00 01 44 49 17 78 00 00 04 00 00 00 Aug 15 18:13:48 Cerberus kernel: end_request: critical target error, dev sdd, sector 5440608120 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608056/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608064/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608072/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608080/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608088/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608096/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608104/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608112/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608120/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608128/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608136/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608144/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608152/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608160/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608168/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608176/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608184/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608192/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608200/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608208/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608216/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608224/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608232/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608240/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608248/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608256/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608264/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608272/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608280/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608288/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608296/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608304/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608312/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608320/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608328/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608336/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608344/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608352/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608360/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608368/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608376/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608384/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608392/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608400/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608408/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608416/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608424/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608432/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608440/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608448/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608456/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608464/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608472/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608480/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608488/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608496/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608504/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608512/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608520/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608528/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608536/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608544/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608552/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608560/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608568/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608576/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608584/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608592/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608600/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608608/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608616/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608624/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608632/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608640/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608648/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608656/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608664/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608672/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608680/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608688/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608696/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608704/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608712/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608720/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608728/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608736/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608744/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608752/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608760/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608768/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608776/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608784/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608792/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608800/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608808/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608816/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608824/3, count: 1 Aug 15 18:13:48 Cerberus kernel: md: disk9 read error Aug 15 18:13:48 Cerberus kernel: handle_stripe read error: 5440608832/3, count: 1 Aug 16 02:46:33 Cerberus kernel: sd 0:0:2:0: attempting task abort! scmd(f621ef00) Aug 16 02:46:33 Cerberus kernel: sd 0:0:2:0: [sdf] CDB: cdb[0]=0x12: 12 00 00 00 24 00 Aug 16 02:46:33 Cerberus kernel: scsi target0:0:2: handle(0x000b), sas_address(0x4433221103000000), phy(3) Aug 16 02:46:33 Cerberus kernel: scsi target0:0:2: enclosure_logical_id(0x500605b0047941f0), slot(0) Aug 16 02:46:33 Cerberus kernel: sd 0:0:2:0: task abort: SUCCESS scmd(f621ef00) Aug 16 02:46:54 Cerberus kernel: sd 0:0:2:0: attempting task abort! scmd(e0915780) Aug 16 02:46:54 Cerberus kernel: sd 0:0:2:0: [sdf] CDB: cdb[0]=0x12: 12 00 00 00 40 00 Aug 16 02:46:54 Cerberus kernel: scsi target0:0:2: handle(0x000b), sas_address(0x4433221103000000), phy(3) Aug 16 02:46:54 Cerberus kernel: scsi target0:0:2: enclosure_logical_id(0x500605b0047941f0), slot(0) Aug 16 02:46:54 Cerberus kernel: sd 0:0:2:0: task abort: SUCCESS scmd(e0915780) Aug 16 02:47:25 Cerberus kernel: sd 0:0:2:0: attempting task abort! scmd(ef2b9840) Aug 16 02:47:25 Cerberus kernel: sd 0:0:2:0: CDB: cdb[0]=0x0: 00 00 00 00 00 00 Aug 16 02:47:25 Cerberus kernel: scsi target0:0:2: handle(0x000b), sas_address(0x4433221103000000), phy(3) Aug 16 02:47:25 Cerberus kernel: scsi target0:0:2: enclosure_logical_id(0x500605b0047941f0), slot(0) Aug 16 02:47:25 Cerberus kernel: sd 0:0:2:0: task abort: SUCCESS scmd(ef2b9840) Aug 16 02:47:46 Cerberus kernel: sd 0:0:2:0: attempting task abort! scmd(d52f7000) Aug 16 02:47:46 Cerberus kernel: sd 0:0:2:0: [sdf] CDB: cdb[0]=0x12: 12 00 00 00 24 00 Aug 16 02:47:46 Cerberus kernel: scsi target0:0:2: handle(0x000b), sas_address(0x4433221103000000), phy(3) Aug 16 02:47:46 Cerberus kernel: scsi target0:0:2: enclosure_logical_id(0x500605b0047941f0), slot(0) Aug 16 02:47:46 Cerberus kernel: sd 0:0:2:0: task abort: SUCCESS scmd(d52f7000) Aug 16 02:48:07 Cerberus kernel: sd 0:0:2:0: attempting task abort! scmd(f2b69c00) Aug 16 02:48:07 Cerberus kernel: sd 0:0:2:0: [sdf] CDB: cdb[0]=0x12: 12 00 00 00 40 00 Aug 16 02:48:07 Cerberus kernel: scsi target0:0:2: handle(0x000b), sas_address(0x4433221103000000), phy(3)
August 17, 201312 yr Author ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 9 3 Spin_Up_Time 0x0027 183 181 021 Pre-fail Always - 5816 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 191 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1656 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 189 194 Temperature_Celsius 0x0022 122 120 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
August 17, 201312 yr Author So as an update. After the preclear was done I rebooted the server and copied over 40gb of data. Not a single error. The only thing I can think of is that maybe there was a power issue? I have a splitter feeding the back plane where both the preclearing disk, the data disk experiencing errors, and the parity drive are located. I was thinking about swapping the power supplies in my servers tomorrow to see if the issue is resolved when I start to preclear another drive. My corsair power supply has more molex connectors than my rosewill so maybe that will solve the issue? In the meantime is there anything I should do because of the errors I did have? I'm wondering if I should run a parity check and write corrections to the parity drive?
August 17, 201312 yr Author Well I swapped the power supplies in my servers this morning and have not seen any errors afterwards when preclearing another drive and copying files. So maybe that was it? I will keep an eye on it for a while and after this disk finishes preclearing I will probably run a parity check.
August 18, 201312 yr Author Well I started to see the errors again today. So definitely not a power supply issue. And it's definitely not an issue with loose cables since I made sure to reseat all of them yesterday when I swapped power supplies. So if anyone has any ideas I would appreciate some thoughts.
August 19, 201312 yr Update to the latest release. There's no point in debugging with an old release.
August 19, 201312 yr Author I already downloaded the files but want to run a parity check before I upgrade. Also based on the release notes for the newer builds there was nothing that stuck out in my mind that might help fix this issue. I had planned to upgrade anyways though. For another test I swapped bays between the disk having issues and a disk that has been working. Then I copied files directly to each. I had zero problems with the good drive, but the drive that has been having issues was showing "Specified network name is no longer available" in TeraCopy and only transferred 2gb of a 15gb file. Then it failed. No errors were logged. The second time I transferred it was fine. I have another disk that is cleared and waiting to be added. I am wondering if I should either transfer all the files off to another disk in the array then replace the disk or maybe drop the disk out of the array and load the new one in then rebuild and run some preclears on the disk with issues to see if it fails.
August 20, 201312 yr Author The parity check is almost done and so far I have seen thousands of errors on the drive again but no sync errors. I'm feeling like this drive is probably bad especially since the issue is specific to this drive and not to the bay. I may just transfer all the files to another drive in the array and swap in my new drive. Should I upgrade to the new rc before or after this?
August 20, 201312 yr The parity check is almost done and so far I have seen thousands of errors on the drive again but no sync errors. I'm feeling like this drive is probably bad especially since the issue is specific to this drive and not to the bay. I may just transfer all the files to another drive in the array and swap in my new drive. Should I upgrade to the new rc before or after this? If a parity check completes without errors then do the upgrade first. After the upgrade do a parity check and then swap the disk.
August 20, 201312 yr Author I am getting ready to do the upgrade now. The parity check completed with 0 sync errors but 2450 errors on the disk that has been having issues. I will run another check tonight.
August 20, 201312 yr Author I have successfully upgraded to 5.0rc16c. So I will run the parity check and see how that goes. Fingers crossed that alone corrected my issues but I am not overly optimistic.
August 21, 201312 yr Author Well the parity check is running and I have already seen 900 errors. I think its safe to say the drive is bad at this point.
August 21, 201312 yr Author I started to copy all the files off the drive to another drive in the array. When that finishes I will pull the drive and swap in the new one. I'm guessing I should just RMA the drive immediately instead of trying to run preclears on it. If I move all the files off the disk will the rebuild be faster or will it take roughly the same time? I was trying to find the safest way to do this with minimal chances of dataloss.
August 21, 201312 yr As far as I know the rebuild time is not affected by how much content there is on the disk as it takes place at the physical (sector) level.
August 21, 201312 yr Author Thanks. I haven't had to rebuild a drive yet so I wasn't sure. Glad I chose to use unraid. Otherwise I probably wouldn't have even known my drive was having issues.
August 21, 201312 yr Author Should I bother with a preclear on the drive before I RMA it or just send it in?
August 22, 201312 yr Author The drive rebuild is underway. Does 24 hours sound right for a rebuild? Its moving at ~30mb/sec. I have all SATA 6/GB/s drives and controllers with mostly WD Red drives. update: Drive rebuild only ended up taking roughly 7-8 hours. Speeds picked up after it started running for a while. Definitely good to know for the future.
September 10, 201312 yr Author So to make this situation that much more fun. I sent the drive back to Newegg as an RMA which they ended up denying because it was apparently out of their warranty. Then I created an RMA with Western Digital to get it replaced through them instead. Newegg shipped the drive back in their usual terrible fashion which took over a week to get back to me. And of course with the fantastic packaging they did there is now a small nick/scratch in one corner of the drive. So I expect Western Digital to deny my claim which is great because I did the Advanced RMA since I have already been down my spare drive for a few weeks. They of course sent a re-manufactured drive to replace my almost new drive, and if my RMA is declined I expect that they will charge my credit card for the full amount for a brand new drive. Has anyone run across these kinds of issues before??
September 10, 201312 yr ... I sent the drive back to Newegg as an RMA which they ended up denying because it was apparently out of their warranty. Newegg is very firm about their 30-day limit for returns ... and that's from the order date. They're quite good a replacing drives WITHIN that 30 day window; but miss it by a day and you're SOL. I've had a bad drive that was replaced with a bad drive (very rare, but it can happen) ... and by the time I sent back the 2nd one, it was 32 days after the order date, and they wouldn't accept it. That was years ago, but I've never forgotten the lesson, and am very careful to be sure I test drives immediately upon receipt so I don't get close to the 30-day limit. I did the Advanced RMA since I have already been down my spare drive for a few weeks. They of course sent a re-manufactured drive to replace my almost new drive, and if my RMA is declined I expect that they will charge my credit card for the full amount for a brand new drive. Newegg's packing definitely leaves a good bit to be desired !! But I wouldn't be overly concerned. It's VERY unlikely that WD will have any issue with the drive, as long as you return it within the timeframe they allow (I believe it's 30 days). I've done many Advance RMAs, and it's never been a problem. I do always buy the return label from WD -- their prices are very reasonable (less than going to UPS) and that way it's all filled in with the correct details.
September 10, 201312 yr Author Thanks for the reassurance. I have had good luck with newegg RMAs before. I'm not upset about it being denied I totally understand the time frame issue, I just wish that they would have returned the drive in good packaging. I also test my drives asap because I have had so many bad ones in the last year.
Archived
This topic is now archived and is closed to further replies.