Stardust9876

I am getting an Error during Post Read verification, for the 2nd time now. Does anyone know what could cause that? Do you guys think the disc is good to use anyways? ############################################################################################################################ # # # unRAID Server Preclear of disk ZCT0DTK5 # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [16:18:25 @ 136 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [16:59:16 @ 130 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: FAIL # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 34:02:11 | Total elapsed time: 34:02:11 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status (device type: default) # # # # # # ATTRIBUTE INITIAL STATUS # # Reallocated_Sector_Ct 0 - # # Power_On_Hours 207 - # # Runtime_Bad_Block 0 - # # End-to-End_Error 0 - # # Reported_Uncorrect 0 - # # Airflow_Temperature_Cel 28 - # # Current_Pending_Sector 0 - # # Offline_Uncorrectable 0 - # # UDMA_CRC_Error_Count 0 - # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ Oct 3 18:36:46 TheArk preclear_disk_ZCT0DTK5[26100]: Zeroing: progress - 90% zeroed @ 106 MB/s Oct 3 21:11:11 TheArk rc.diskinfo[8155]: SIGHUP received, forcing refresh of disks info. Oct 3 21:11:13 TheArk preclear_disk_ZCT0DTK5[26100]: Zeroing: dd - wrote 8001563222016 of 8001563222016 (0). Oct 3 21:11:13 TheArk preclear_disk_ZCT0DTK5[26100]: Zeroing: elapsed time - 16:59:13 Oct 3 21:11:13 TheArk preclear_disk_ZCT0DTK5[26100]: Zeroing: dd exit code - 0 Oct 3 21:11:13 TheArk preclear_disk_ZCT0DTK5[26100]: Zeroing: zeroing the disk completed! Oct 3 21:11:14 TheArk preclear_disk_ZCT0DTK5[26100]: Signature: writing signature: 0 0 2 0 0 255 255 255 1 0 0 0 255 255 255 255 Oct 3 21:11:14 TheArk preclear_disk_ZCT0DTK5[26100]: Signature: verifying unRAID's signature on the MBR ... Oct 3 21:11:15 TheArk preclear_disk_ZCT0DTK5[26100]: Signature: Unraid preclear signature is valid! Oct 3 21:11:15 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: post-read verification started (1/5).... Oct 3 21:11:15 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: verifying the beginning of the disk. Oct 3 21:11:15 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: cmp /tmp/.preclear/sdg/fifo /dev/zero Oct 3 21:11:15 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd if=/dev/sdg of=/tmp/.preclear/sdg/fifo count=2096640 skip=512 iflag=nocache,count_bytes,skip_bytes Oct 3 21:11:16 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: verifying the rest of the disk. Oct 3 21:11:16 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: cmp /tmp/.preclear/sdg/fifo /dev/zero Oct 3 21:11:16 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd if=/dev/sdg of=/tmp/.preclear/sdg/fifo bs=2097152 skip=2097152 count=8001561124864 iflag=nocache,count_bytes,skip_bytes Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: cmp command failed - disk not zeroed Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd - read 480839204864 of 8001563222016 (7520724017152). Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: elapsed time - 0:44:24 Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd command failed, exit code [141]. Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 459993513984 bytes (460 GB, 428 GiB) copied, 2525.4 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 220437+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 220436+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 462287798272 bytes (462 GB, 431 GiB) copied, 2537.64 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 221426+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 221425+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 464361881600 bytes (464 GB, 432 GiB) copied, 2549.79 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 222396+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 222395+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 466396119040 bytes (466 GB, 434 GiB) copied, 2561.99 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 223367+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 223366+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 468432453632 bytes (468 GB, 436 GiB) copied, 2574.1 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 224428+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 224427+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 470657531904 bytes (471 GB, 438 GiB) copied, 2587.39 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 225417+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 225416+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 472731615232 bytes (473 GB, 440 GiB) copied, 2599.69 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 226373+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 226372+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 474736492544 bytes (475 GB, 442 GiB) copied, 2611.91 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 227350+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 227349+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 476785410048 bytes (477 GB, 444 GiB) copied, 2624.21 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 228315+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 228314+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 478809161728 bytes (479 GB, 446 GiB) copied, 2636.37 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 229282+0 records in Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 229281+0 records out Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: dd output: 480837107712 bytes (481 GB, 448 GiB) copied, 2648.52 s, 182 MB/s Oct 3 21:55:52 TheArk preclear_disk_ZCT0DTK5[26100]: Post-Read: post-read verification failed! Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Error: Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Reallocated_Sector_Ct 0 0 - Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Power_On_Hours 207 241 Up 34 Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Runtime_Bad_Block 0 0 - Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: End-to-End_Error 0 0 - Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Reported_Uncorrect 0 0 - Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Airflow_Temperature_Cel 28 32 Up 4 Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Current_Pending_Sector 0 0 - Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: Offline_Uncorrectable 0 0 - Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 - Oct 3 21:55:55 TheArk preclear_disk_ZCT0DTK5[26100]: S.M.A.R.T.: SMART overall-health self-assessment test result: PASSED Oct 3 21:55:56 TheArk preclear_disk_ZCT0DTK5[26100]: error encountered, exiting...

Oh OK, so I guess I move the data from that disk via unBALANCE and buy another one... After the problematic disc is empty, I could preclear it and see if that throws up any issues...

I ran into a hickup while migrating/copying from my HDDs to Unraid. The first 2 discs went perfectly, now the 3rd disc is throwing the error mentioned above while copying data onto it. What I tried so far: move data via Krusader move data from other PC via LAN to share use different SATA cable use different power cable use different SATA port on mainboard connect sata cable to my 9207-8i instead of onto the motherboard directly sadly everytime the same outcome and I ran out of ideas... Mainboard: MSI Z170A Gaming Pro Carbon PSU: BeQuiet Dark Power Pro 11 1200W The error from the Log: Sep 26 14:31:04 TheArk nmbd[11597]: Samba name server THEARK is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Sep 26 14:31:04 TheArk nmbd[11597]: Sep 26 14:31:04 TheArk nmbd[11597]: ***** Sep 26 14:32:25 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x00000000d6d58b17), outstanding for 30278 ms & timeout 30000 ms Sep 26 14:32:25 TheArk kernel: sd 2:0:0:0: [sdc] tag#4893 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 5b 78 00 00 03 d0 00 00 Sep 26 14:32:25 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:25 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x00000000d6d58b17) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x000000009e4df483), outstanding for 34186 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4892 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 5b 48 00 00 00 30 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x000000009e4df483) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x000000009e4df483) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x0000000058078eec), outstanding for 34202 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4891 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 57 48 00 00 04 00 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x0000000058078eec) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x0000000058078eec) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x0000000020949da3), outstanding for 34203 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4890 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 53 48 00 00 04 00 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x0000000020949da3) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x0000000020949da3) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x000000008116cfc1), outstanding for 34204 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4889 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 4f 48 00 00 04 00 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x000000008116cfc1) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x000000008116cfc1) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x00000000b4f1b982), outstanding for 34204 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4888 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 4b 48 00 00 04 00 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x00000000b4f1b982) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x00000000b4f1b982) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x0000000066b21240), outstanding for 34204 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4887 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 47 48 00 00 04 00 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x0000000066b21240) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x0000000066b21240) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x000000006a86c860), outstanding for 34204 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4886 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 43 48 00 00 04 00 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x000000006a86c860) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x000000006a86c860) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: attempting task abort!scmd(0x00000000aab52fff), outstanding for 34204 ms & timeout 30000 ms Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4885 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 3f 48 00 00 04 00 00 00 Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: handle(0x0009), sas_address(0x4433221103000000), phy(3) Sep 26 14:32:29 TheArk kernel: scsi target2:0:0: enclosure logical id(0x500605b009bd3fc0), slot(0) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: No reference found at driver, assuming scmd(0x00000000aab52fff) might have completed Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0x00000000aab52fff) Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4895 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=26s Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4895 Sense Key : 0x2 [current] Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4895 ASC=0x4 ASCQ=0x0 Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4895 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Sep 26 14:32:29 TheArk kernel: blk_update_request: I/O error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4896 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=34s Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4896 Sense Key : 0x2 [current] Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4896 ASC=0x4 ASCQ=0x0 Sep 26 14:32:29 TheArk kernel: sd 2:0:0:0: [sdc] tag#4896 CDB: opcode=0x8a 8a 00 00 00 00 00 03 f3 5b 78 00 00 03 d0 00 00 Sep 26 14:32:29 TheArk kernel: blk_update_request: I/O error, dev sdc, sector 66280312 op 0x1:(WRITE) flags 0x0 phys_seg 122 prio class 0 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280248 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280256 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280264 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280272 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280280 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280288 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280296 Sep 26 14:32:29 TheArk kernel: md: disk3 write error, sector=66280304 SMART Status from the HDD: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 224 177 021 - 5766 4 Start_Stop_Count -O--CK 100 100 000 - 166 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 100 100 000 - 166 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 72 192 Power-Off_Retract_Count -O--CK 200 200 000 - 34 193 Load_Cycle_Count -O--CK 200 200 000 - 544 194 Temperature_Celsius -O---K 126 098 000 - 26 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 100 253 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning

Nice, thx it worked

Here it is theark-diagnostics-20210926-1223.zip

I have a 9207-8i attached in my setup. No HDDs on it yet. I "think" it is recognized by unraid: [1000:0087]02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) It is running in IT mode, FW: 20.00.00.00. So I wanted to update it to 20.00.07.00, but for some reason it is not listed: sas3flash -listall Avago Technologies SAS3 Flash Utility Version 17.00.00.00 (2018.04.02) Copyright 2008-2018 Avago Technologies. All rights reserved. No Avago SAS adapters found! Limited Command Set Available! ERROR: Command Not allowed without an adapter! ERROR: Couldn't Create Command -listall Exiting Program. What could be the issue here?

So I am currently in the process of setting up Unraid. I have to move the Data HDDs one by one from my old system (non Raid) to Unraid. Which means plug the HDD into a USB Case and connect to the Unraid server, move data with Krusader, afterwards plugging that same HDD into the server directly (SATA) and adding it to array. Rinse and repeat. It went fine for 2 disks so far. The 3rd disk started good. I had it running over night and woke up to the error message that some files could not be copied (also the errors in the Main Tab appeared). I tried to copy over another folder and got the error message "Could not make Folder". There is data already in that specific folder. Krusader is running with root privileges. Fix common Problems doesn't show any problems. What could be the error here? EDIT: The disk itself also showing: A mandatory SMART command failed:exiting. To continue, add one or more '-T permissive' options. This is the log: Sep 25 22:08:41 TheArk avahi-daemon[8166]: Registering new address record for fe80::42:a1ff:fe65:3489 on docker0.*. Sep 26 01:18:02 TheArk kernel: ata5.00: exception Emask 0x0 SAct 0x3f8000 SErr 0x0 action 0x6 frozen Sep 26 01:18:02 TheArk kernel: ata5.00: failed command: WRITE FPDMA QUEUED Sep 26 01:18:02 TheArk kernel: ata5.00: cmd 61/40:78:78:3c:76/05:00:20:00:00/40 tag 15 ncq dma 688128 out Sep 26 01:18:02 TheArk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Sep 26 01:18:02 TheArk kernel: ata5.00: status: { DRDY } Sep 26 01:18:02 TheArk kernel: ata5.00: failed command: WRITE FPDMA QUEUED Sep 26 01:18:02 TheArk kernel: ata5.00: cmd 61/40:80:b8:41:76/05:00:20:00:00/40 tag 16 ncq dma 688128 out Sep 26 01:18:02 TheArk kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Sep 26 01:18:02 TheArk kernel: ata5.00: status: { DRDY } Sep 26 01:18:02 TheArk kernel: ata5.00: failed command: WRITE FPDMA QUEUED Sep 26 01:18:02 TheArk kernel: ata5.00: cmd 61/40:88:f8:46:76/05:00:20:00:00/40 tag 17 ncq dma 688128 out Sep 26 01:18:02 TheArk kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Should I try and exchange the SATA Cable? Edit2: I changed the Sata cable, SMART and Temperature works again and Krusader is copying files again/being able to create directories... Edit3: Same happened again, Errors again... Is the HDD Toast?

So I am currently in the process of setting up Unraid. I have to move the Data HDDs one by one from my old system (non Raid) to Unraid. Which means plug the HDD into a USB Case and connect to the Unraid server, move data with Krusader, afterwards plugging that same HDD into the server directly (SATA) and adding it to array. Rinse and repeat. It went fine for 2 disks so far. The 3rd disk started good. I had it running over night and woke up to the error message that some files could not be copied (also the errors in the Main Tab appeared). I tried to copy over another folder and got the error message "Could not make Folder". There is data already in that specific folder. Krusader is running with root privileges. Fix common Problems doesn't show any problems. What could be the error here?

I'm currently preparing my LSI Logic LSI00301 Host Bus Adapter (SAS 9207-8i) for Unraid. The Config Utility is showing me: SAS9207-8i FW Revision: 20.00.00.00-IT I saw that the latest version on the Broadcom HP is: 9207-8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows Package_P20_Firmware_BIOS_for_MSDOS_Windows Version: 20.00.07.00 The card is currently in a Windows 10 PC, with no HDDs attached. Can I use the included sas2flash_win_x64_rel and the corresponding flash file from the HBA_9207_8i_IT Folder to just upgrade it in Windows?

So I read up about all the different Systems/OS there are out there and I think Unraid is exactly what I am looking for. I currently have a Raid 1 System running, 4x WD RED 3TB with a useable capacity of 6TB in a HP N54L for my more "important" data. That will stay as is. My other data is currently spread between 6 Disks and running on the following setup (on Windows 10, no Raid or anything, just the discs connected): Intertech 4U 4129-N (should fit around 15-20 HDD's) MSI Z170A Gaming Pro Carbon Intel Pentium G4520 Kingston FURY DIMM 4GB, DDR4-2133 (HX421C14FB/4) BeQuiet Dark Power Pro 11 1200W What I have additionally sitting here: LSI Logic LSI00301 Host Bus Adapter (SAS 9207-8i) with cables and adapters What I am gonna buy: 16TB Toshiba Enterprise MG08ACA16TE HDD 3x 16GB Sandisk Cruzer Fit USB2.0 (SDCZ33-016G-G35) retail So my plan is to use the 16TB drive as a parity drive, then add an empty 8TB drive as data disk and move stuff from one full HDD to the 8TB data disk. Then add the disk I just copied to the array (since I copied the data and it will be formatted upon adding to Array), and so on. Is the Hardware (CPU/RAM) sufficient for running Unraid? Do I need a Cache drive? From what I read the only downside would be that without a Cache drive the speed would be around 50MB/s For now I also plan to shut down the server since I usually only switch it on every 2-3 month to move data (I use my "regular" PC which has around 15TB of "buffer space") The plan is to expand the array once I need space/buy new HDDs to ~12 drives, should I get 2 Parity discs or is 1 enough? Edit: I totally forgot, that is just to store the data and access it when needed, no streaming, no PLEX, no VM, no Docker for now, just storage with Parity and access via LAN