burnaby_boy

After months of stability, I noticed a red ball beside one of the drives this morning. I checked the syslog (attached) numerous errors on disk 13, and also that the syslog had been restarted for some reason this morning (I have not restarted the array in a couple of months). I then ran a smart report (attached) and noticed that the value for Current_Pending_Sector is 54. Any suggestions on how to proceed? Cheers

Thanks for the suggestion, but I'm not using LSI controllers - just an Adaptec 1430SA and an AOC-SASLP-MV8 (plus the motherboard connections). So far there have not been further errors on Disk 4. Cheers

I decided to hold off on changing out the drive. After running a parity check last night there were no parity errors, and no increase in the number of errors on disk 4 on the status page. The only change in a subsequent smart report was the Raw_Read_Error_Rate increased by one to 19. The Current_Pending_Sector remains 4.

OK - thanks for the suggestion. Cheers

I have a spare drive available. Would it be wise to just replace the disk 4 with the new one?

Thanks, Joe. I have attached the smart report for the drive. I notice the Current_Pending_Sector is 4. Would you mind having a look? Cheers smart.txt

I woke up this morning to find 49 errors on disk 4 of my server. I'm running unRaid 5.0-beta13 and have not had any major problems to this point. The portion of the syslog with the errors is below. Any assistance would be appreciated. Cheers Nov 9 16:33:24 Media kernel: mdcmd (157): spindown 1 Nov 9 16:33:24 Media kernel: mdcmd (158): spindown 9 Nov 9 16:33:25 Media kernel: mdcmd (159): spindown 11 Nov 9 16:33:26 Media kernel: mdcmd (160): spindown 12 Nov 9 16:33:27 Media kernel: mdcmd (161): spindown 13 Nov 9 16:33:58 Media kernel: mdcmd (162): spindown 0 Nov 9 16:33:58 Media kernel: mdcmd (163): spindown 3 Nov 9 16:44:31 Media kernel: mdcmd (164): spindown 8 Nov 9 16:44:32 Media kernel: mdcmd (165): spindown 10 Nov 9 16:44:32 Media kernel: mdcmd (166): spindown 14 Nov 9 16:44:33 Media kernel: mdcmd (167): spindown 15 Nov 9 18:32:30 Media kernel: mdcmd (168): spindown 1 Nov 9 18:32:31 Media kernel: mdcmd (169): spindown 9 Nov 9 18:32:32 Media kernel: mdcmd (170): spindown 11 Nov 9 18:32:33 Media kernel: mdcmd (171): spindown 12 Nov 9 18:32:34 Media kernel: mdcmd (172): spindown 13 Nov 9 18:32:55 Media kernel: mdcmd (173): spindown 7 Nov 9 18:33:16 Media kernel: mdcmd (174): spindown 6 Nov 9 20:10:21 Media kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 20:10:21 Media kernel: ata9.00: irq_stat 0x40000001 Nov 9 20:10:21 Media kernel: ata9.00: failed command: READ DMA EXT Nov 9 20:10:21 Media kernel: ata9.00: cmd 25/00:00:af:ac:20/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 9 20:10:21 Media kernel: res 51/40:00:2c:af:20/00:00:03:00:00/e0 Emask 0x9 (media error) Nov 9 20:10:21 Media kernel: ata9.00: status: { DRDY ERR } Nov 9 20:10:21 Media kernel: ata9.00: error: { UNC } Nov 9 20:10:22 Media kernel: ata9.00: configured for UDMA/133 Nov 9 20:10:22 Media kernel: ata9: EH complete Nov 9 20:10:23 Media kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 20:10:23 Media kernel: ata9.00: irq_stat 0x40000001 Nov 9 20:10:23 Media kernel: ata9.00: failed command: READ DMA EXT Nov 9 20:10:23 Media kernel: ata9.00: cmd 25/00:00:af:ac:20/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 9 20:10:23 Media kernel: res 51/40:00:2c:af:20/00:00:03:00:00/e0 Emask 0x9 (media error) Nov 9 20:10:23 Media kernel: ata9.00: status: { DRDY ERR } Nov 9 20:10:23 Media kernel: ata9.00: error: { UNC } Nov 9 20:10:24 Media kernel: ata9.00: configured for UDMA/133 Nov 9 20:10:24 Media kernel: ata9: EH complete Nov 9 20:10:25 Media kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 20:10:25 Media kernel: ata9.00: irq_stat 0x40000001 Nov 9 20:10:25 Media kernel: ata9.00: failed command: READ DMA EXT Nov 9 20:10:25 Media kernel: ata9.00: cmd 25/00:00:af:ac:20/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 9 20:10:25 Media kernel: res 51/40:00:2c:af:20/00:00:03:00:00/e0 Emask 0x9 (media error) Nov 9 20:10:25 Media kernel: ata9.00: status: { DRDY ERR } Nov 9 20:10:25 Media kernel: ata9.00: error: { UNC } Nov 9 20:10:26 Media kernel: ata9.00: configured for UDMA/133 Nov 9 20:10:26 Media kernel: ata9: EH complete Nov 9 20:10:27 Media kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 20:10:27 Media kernel: ata9.00: irq_stat 0x40000001 Nov 9 20:10:27 Media kernel: ata9.00: failed command: READ DMA EXT Nov 9 20:10:27 Media kernel: ata9.00: cmd 25/00:00:af:ac:20/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 9 20:10:27 Media kernel: res 51/40:00:2c:af:20/00:00:03:00:00/e0 Emask 0x9 (media error) Nov 9 20:10:27 Media kernel: ata9.00: status: { DRDY ERR } Nov 9 20:10:27 Media kernel: ata9.00: error: { UNC } Nov 9 20:10:28 Media kernel: ata9.00: configured for UDMA/133 Nov 9 20:10:28 Media kernel: ata9: EH complete Nov 9 20:10:29 Media kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 20:10:29 Media kernel: ata9.00: irq_stat 0x40000001 Nov 9 20:10:29 Media kernel: ata9.00: failed command: READ DMA EXT Nov 9 20:10:29 Media kernel: ata9.00: cmd 25/00:00:af:ac:20/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 9 20:10:29 Media kernel: res 51/40:00:2c:af:20/00:00:03:00:00/e0 Emask 0x9 (media error) Nov 9 20:10:29 Media kernel: ata9.00: status: { DRDY ERR } Nov 9 20:10:29 Media kernel: ata9.00: error: { UNC } Nov 9 20:10:30 Media kernel: ata9.00: configured for UDMA/133 Nov 9 20:10:30 Media kernel: ata9: EH complete Nov 9 20:10:31 Media kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 20:10:31 Media kernel: ata9.00: irq_stat 0x40000001 Nov 9 20:10:31 Media kernel: ata9.00: failed command: READ DMA EXT Nov 9 20:10:31 Media kernel: ata9.00: cmd 25/00:00:af:ac:20/00:04:03:00:00/e0 tag 0 dma 524288 in Nov 9 20:10:31 Media kernel: res 51/40:00:2c:af:20/00:00:03:00:00/e0 Emask 0x9 (media error) Nov 9 20:10:31 Media kernel: ata9.00: status: { DRDY ERR } Nov 9 20:10:31 Media kernel: ata9.00: error: { UNC } Nov 9 20:10:32 Media kernel: ata9.00: configured for UDMA/133 Nov 9 20:10:32 Media kernel: sd 9:0:0:0: [sdh] Unhandled sense code Nov 9 20:10:32 Media kernel: sd 9:0:0:0: [sdh] Result: hostbyte=0x00 driverbyte=0x08 Nov 9 20:10:32 Media kernel: sd 9:0:0:0: [sdh] Sense Key : 0x3 [current] [descriptor] Nov 9 20:10:32 Media kernel: Descriptor sense data with sense descriptors (in hex): Nov 9 20:10:32 Media kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Nov 9 20:10:32 Media kernel: 03 20 af 2c Nov 9 20:10:32 Media kernel: sd 9:0:0:0: [sdh] ASC=0x11 ASCQ=0x4 Nov 9 20:10:32 Media kernel: sd 9:0:0:0: [sdh] CDB: cdb[0]=0x28: 28 00 03 20 ac af 00 04 00 00 Nov 9 20:10:32 Media kernel: end_request: I/O error, dev sdh, sector 52473644 Nov 9 20:10:32 Media kernel: ata9: EH complete Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473576/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473584/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473592/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473600/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473608/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473616/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473624/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473632/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473640/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473648/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473656/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473664/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473672/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473680/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473688/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473696/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473704/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473712/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473720/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473728/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473736/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473744/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473752/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473760/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473768/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473776/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473784/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473792/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473800/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473808/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473816/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473824/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473832/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473840/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473848/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473856/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473864/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473872/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473880/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473888/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473896/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473904/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473912/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473920/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473928/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473936/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473944/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473952/4, count: 1 Nov 9 20:10:32 Media kernel: md: disk4 read error Nov 9 20:10:32 Media kernel: handle_stripe read error: 52473960/4, count: 1 Nov 9 21:10:35 Media kernel: mdcmd (175): spindown 1 Nov 9 21:10:36 Media kernel: mdcmd (176): spindown 3 Nov 9 21:10:37 Media kernel: mdcmd (177): spindown 5 Nov 9 21:10:38 Media kernel: mdcmd (178): spindown 6 Nov 9 21:10:38 Media kernel: mdcmd (179): spindown 7 Nov 9 21:10:40 Media kernel: mdcmd (180): spindown 8 Nov 9 21:10:40 Media kernel: mdcmd (181): spindown 9 Nov 9 21:10:41 Media kernel: mdcmd (182): spindown 10 Nov 9 21:10:42 Media kernel: mdcmd (183): spindown 11 Nov 9 21:10:43 Media kernel: mdcmd (184): spindown 12 Nov 9 21:10:44 Media kernel: mdcmd (185): spindown 13 Nov 9 21:10:45 Media kernel: mdcmd (186): spindown 14 Nov 9 21:10:46 Media kernel: mdcmd (187): spindown 15 Nov 9 21:10:56 Media kernel: mdcmd (188): spindown 2 Nov 9 21:10:57 Media kernel: mdcmd (189): spindown 16 Nov 9 21:11:27 Media kernel: mdcmd (190): spindown 0 Nov 9 21:13:18 Media kernel: mdcmd (191): spindown 4 Nov 9 21:31:46 Media kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 21:31:46 Media kernel: ata9.00: irq_stat 0x40000001 Nov 9 21:31:46 Media kernel: ata9.00: failed command: READ DMA EXT Nov 9 21:31:46 Media kernel: ata9.00: cmd 25/00:60:97:29:24/00:02:03:00:00/e0 tag 0 dma 311296 in Nov 9 21:31:46 Media kernel: res 51/40:00:89:2a:24/00:00:03:00:00/e0 Emask 0x9 (media error) Nov 9 21:31:46 Media kernel: ata9.00: status: { DRDY ERR } Nov 9 21:31:46 Media kernel: ata9.00: error: { UNC } Nov 9 21:31:46 Media kernel: ata9.00: configured for UDMA/133 Nov 9 21:31:46 Media kernel: ata9: EH complete Nov 9 22:46:04 Media kernel: mdcmd (192): spindown 4 Nov 9 22:46:15 Media kernel: mdcmd (193): spindown 3 Nov 9 22:46:26 Media kernel: mdcmd (194): spindown 2 Nov 9 22:46:27 Media kernel: mdcmd (195): spindown 6 Nov 9 22:46:28 Media kernel: mdcmd (196): spindown 16 Nov 9 22:46:58 Media kernel: mdcmd (197): spindown 1 Nov 9 22:46:59 Media kernel: mdcmd (198): spindown 7 Nov 9 22:47:01 Media kernel: mdcmd (199): spindown 9 Nov 9 22:47:01 Media kernel: mdcmd (200): spindown 11 Nov 9 22:47:03 Media kernel: mdcmd (201): spindown 12 Nov 9 22:47:04 Media kernel: mdcmd (202): spindown 13

Spoke too soon - I tried to access the server this evening and there was a delay again. Initially most of the drives were shown as being spun down. I then refreshed the page and then it showed most of the drives as spinning - very peculiar. (syslog attached) Cheers Mine does it to. despite what people are saying with certain cards it seems to be waking the drives up to get the temp or something when accessing the main page. Are you using any add-ons? No add-ons being used here.

Spoke too soon - I tried to access the server this evening and there was a delay again. Initially most of the drives were shown as being spun down. I then refreshed the page and then it showed most of the drives as spinning - very peculiar. Cheers

It is a different behavior that I've never experienced in 4.7 but have experienced intermediately after taking the dive with beta10. I added an Intel PRO/1000 GT PCI Ethernet adapter card to my server and disabled the onboard Realtek chip. What a difference! - the delay in accessing the unRaid status page is gone and the transfer times - both ways - seem to have improved.

I sometimes get that long delay and can hear drives spinning up one by one. When the page displays, I see that the drives are spun down but if I refresh the page, they're all show as spinning. I just accessed the server for the first time this morning and the status page came up immediately. All drives were spinning. So does attempting to access the status page in 5.0-beta13 cause certain drives to be spun up, thus causing the delay? This would be different behaviour from 4.7 where the page would load instantly no matter what the status of the drives. I am using a Gigabyte GA-P35-DS3P motherboard (HPA off), ultilizing all 8 onboard SATA connections, a Supermicro AOC-SASLP-MV8 card and an Adaptec 1430SA card. Cheers

No, the last time I logged in, all the drives were spun down.

Since upgrading my server to 5.0-beta13, I've noticed that there can sometimes be a 20-30 second delay when I'm accessing the status page of the server in my web browser. With 4.7, when I clicked on the bookmark in Firefox I would immediately be taken to the page. Any ideas as to what might be causing the delay? I'm wondering if it might be the Realtek NIC on the motherboard, and have an Intel PRO/1000 GT PCI adapter on order to test. Anyway, I'd appreciate some guidance with this. Cheers

I rebooted the PC and am now able to access the share and the flash drive. Thanks for the suggestion. Also, thanks too for the info regarding the orange dot. Cheers

I upgraded from 4.7 to 5 b13 following all the steps necessary. For some reason I can no longer access that flash drive via the network (error message saying it is unavailable) and one of my shares (Recorded TV) is unavailable and has an orange dot beside it. Cheers

A correcting parity check resolved the errors, and a second one confirmed it. I'll upgrade to the new version of unRaid when it is released, before adding any more disks. Cheers

Thanks again for the assistance, Joe - much appreciated. Cheers

Thanks for the suggestions regarding how to proceed if this happens again. After putting the precleared disk back into the system last night as the cache drive, I started a noncorrect parity check. I woke up this morning to find 8 parity errors. The syslog is attached. Also, I obtained smart reports for every drive - all seemed fine except for disk 12 which reported a raw_read_error_rate of 1. Disk 5 and 9 also reported runtime_bad_block of 6 and 7 respectively. What should be my next step? - to run a regular parity check to correct the errors? syslog.txt

If this issue happens again, what is the best way to deal with errors caused by a loose connection? I initially tried plugging the problem drive into an empty slot in the case, but after powering on again and assigning it to the proper position, there was still the red dot beside the drive. Should I have then run a parity check to allow the array to see the drive as healthy? Sorry, I still have so much to learn. Cheers

Thanks so much for the analysis, bjp999. I may just use this drive as a cache drive for the time being, as the former cache was used as the replacement drive. Cheers

Sorry, of the 3 reports in the preclear folder I chose the "preclear_finish" one. Here is the "preclear_rpt" from the same folder. ========================================================================1.11 == invoked as: ./preclear_disk.sh -a /dev/sda == WDC WD20EARS-00MVWB0 == Disk /dev/sda has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:31:34 (73 MB/s) == Last Cycle's Zeroing time : 6:24:50 (86 MB/s) == Last Cycle's Post Read Time : 14:08:48 (39 MB/s) == Last Cycle's Total Time : 28:06:19 == == Total Elapsed Time 28:06:19 == == Disk Start Temperature: 28C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Up_Time = 230 203 21 ok 3500 Seek_Error_Rate = 100 200 0 ok 0 No SMART attributes are FAILING_NOW 3 sectors were pending re-allocation before the start of the preclear. 3 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, a change of -3 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================

Hi Joe, Below is the result of the preclear. Anything to be concerned about here? Device Model: WDC WD20EARS-00MVWB0 SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: 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 - 0 3 Spin_Up_Time 0x0027 230 164 021 Pre-fail Always - 3500 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1183 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 093 093 000 Old_age Always - 5800 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 - 60 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 24 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3076 194 Temperature_Celsius 0x0022 122 103 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 200 200 000 Old_age Offline - 3 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 13 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 5772 3531113007 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0):

OK - Thanks, Joe. I'll do a preclear. Cheers

Thanks, Joe. Yes, after the initial panic wore off, I did a bit more reading and a loose cable came up as a possibility. The system is installed in a Norco RPC-4224 case and the drive was connected via an SAS cable to a Supermicro AOC-SASLP-MV8. The other 3 drives on that cable seem to be working fine and I have since moved the replacement drive into the original slot. It seems to be working fine there. I put the problem drive in a backup computer and, after running a SMART short test, obtained a report for it. The test seems to indicate read failure - am I reading that right? Is the next step to run a preclear or just RMA? Cheers SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: 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 - 0 3 Spin_Up_Time 0x0027 204 164 021 Pre-fail Always - 4791 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1179 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 093 093 000 Old_age Always - 5772 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 - 56 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 20 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3075 194 Temperature_Celsius 0x0022 119 103 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 3 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 3 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 13 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 5772 3531113007 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

I have since replaced the disk with a new one and the data has been rebuilt successfully. Before I did this, I tried to run a SMART report, but the disk could not be reached.