trevisthomas Posted January 26, 2016 Share Posted January 26, 2016 I'm running preclear in V6 (using plugin). I had the system clear a 4TB drive and a 5TB drive. The 4tb completed successfully, the 5tb fails and when it fails it disappears from the system completely at about the 16 hour mark. This time i had the little status window opened when it failed and i can now see the results. Basically, all of the steps say DONE DONE DONE but at the botom it says Sorry: Disk /dev/sdb MBR could not be precleared This drive was never in unraid. It was actually an external usb drive that i'm re-purposing. The drive seemed fine prior to this but i know that pre-clear can extensively test a drive. I've just never seen any one fail like this. I've tried running the drive on different hard drive conrollers but as luck would have it, my other PCI sata controllers don't work with this drive at all. I assume because it's 5TB and they are quite old. Could it be that the mother board isn't properly addressing the drive either? It's an intel P45 chipset based board (circa 2008). I was clearing the drive in an old system with the intention of moving it to a new Skylake Z170 based system. I guess i'll try to pre-clear the drive in the new system to see if it goes any better before giving up on it completely, but i was curious if anyone had experienced anything like this before. Quote Link to comment
trevisthomas Posted January 26, 2016 Author Share Posted January 26, 2016 The exact report: ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 16:11:45 ========================================================================1.15 == == SORRY: Disk /dev/sdb MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000106051 s, 0.0 kB/s 0000000 root@Tower:/usr/local/emhttp# Quote Link to comment
trurl Posted January 26, 2016 Share Posted January 26, 2016 I had preclear fail on a 6TB drive once due to memory problems. It would get all the way to the end and then tell me that some of it wasn't zeros. Did it 3 times and finally decided to look elsewhere for the issue. Memtest revealed a bad memory stick. Replaced it and it worked fine the next time. Quote Link to comment
trevisthomas Posted January 27, 2016 Author Share Posted January 27, 2016 That is interesting. I didnt do any kind of mem test on the box that i was using to clear, but now i have the drive in place in what i intend to be the final hardware (which has been memtested) but this box has alerts turned on and, um, check this out: unRAID device sdg SMART health [187]: 26-01-2016 18:22 Warning [TOWER] - reported uncorrect is 10 ST5000DM000-1FK178_W4J04WV6 (sdg) That message popped up in an orange box. This drive may be bad. Quote Link to comment
spants Posted January 27, 2016 Share Posted January 27, 2016 I had a problem using ssh to preclear larger drives - the ssh session disconnects after a time. I now use the Screen command to make a persistent session. Quote Link to comment
trevisthomas Posted January 27, 2016 Author Share Posted January 27, 2016 I'm using the script with the v6 plugin to avoid ssh terminal issues. From the little bit of googling that i did yesterday it sounds like that type of SMART error is a warning sign that the drive wont be with us much longer. I went ahead and got a new one. No use building the new system with a flaky drive. Quote Link to comment
trevisthomas Posted January 28, 2016 Author Share Posted January 28, 2016 Ok, so i had two of these drives. I'm trying to clear the second one and it's having trouble too. I'm starting to wonder now if i'm hitting some weird compatibility issue. It was doing a preclear which seemed to be going fine, but when i went to check status on the plugin i saw that this drive had disappeared. Under the main tab if i scroll down to unassigned devices it's there. The drive is reporting that it is spun down but in the details page it shows it's size as User capacity: 600,332,565,813,390,450 bytes [600 PB] (It should be 5TB) The drives came out of a pair of external segate usb cages. If i click on Disk Log Information from the unRaid main tab, it's just spewing errors. A taste of the errors: Some of these lines are in yellow Jan 27 11:48:42 TheCouncil kernel: ata7: hard resetting link Jan 27 11:48:52 TheCouncil kernel: ata7: softreset failed (1st FIS failed) Jan 27 11:48:52 TheCouncil kernel: ata7: hard resetting link Jan 27 11:49:02 TheCouncil kernel: ata7: softreset failed (1st FIS failed) Jan 27 11:49:02 TheCouncil kernel: ata7: hard resetting link Jan 27 11:49:37 TheCouncil kernel: ata7: softreset failed (1st FIS failed) Jan 27 11:49:37 TheCouncil kernel: ata7: limiting SATA link speed to 3.0 Gbps Jan 27 11:49:37 TheCouncil kernel: ata7: hard resetting link Jan 27 11:49:43 TheCouncil kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jan 27 11:49:43 TheCouncil kernel: ata7.00: link online but device misclassified Jan 27 11:49:48 TheCouncil kernel: ata7.00: qc timeout (cmd 0xec) Jan 27 11:49:48 TheCouncil kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4) Jan 27 11:49:48 TheCouncil kernel: ata7.00: revalidation failed (errno=-5) Jan 27 11:49:48 TheCouncil kernel: ata7: hard resetting link Jan 27 11:49:58 TheCouncil kernel: ata7: softreset failed (1st FIS failed) Jan 27 11:49:58 TheCouncil kernel: ata7: hard resetting link Jan 27 11:50:08 TheCouncil kernel: ata7: softreset failed (1st FIS failed) Jan 27 11:50:08 TheCouncil kernel: ata7: hard resetting link Jan 27 11:50:43 TheCouncil kernel: ata7: softreset failed (1st FIS failed) Jan 27 11:50:43 TheCouncil kernel: ata7: limiting SATA link speed to 1.5 Gbps Jan 27 11:50:43 TheCouncil kernel: ata7: hard resetting link Jan 27 11:50:48 TheCouncil kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 27 11:50:48 TheCouncil kernel: ata7.00: link online but device misclassified Jan 27 11:50:58 TheCouncil kernel: ata7.00: qc timeout (cmd 0xec) These are all in red: Jan 27 11:53:43 TheCouncil kernel: sd 7:0:0:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 bb 43 f9 68 00 00 02 00 00 00 Jan 27 11:53:43 TheCouncil kernel: blk_update_request: I/O error, dev sdf, sector 3141794152 Jan 27 11:53:43 TheCouncil kernel: Buffer I/O error on dev sdf, logical block 392724269, lost async page write Jan 27 11:53:43 TheCouncil kernel: Buffer I/O error on dev sdf, logical block 392724270, lost async page write Jan 27 11:53:43 TheCouncil kernel: Buffer I/O error on dev sdf, logical block 392724271, lost async page write Jan 27 11:53:43 TheCouncil kernel: Buffer I/O error on dev sdf, logical block 392724272, lost async page write Jan 27 11:53:43 TheCouncil kernel: Buffer I/O error on dev sdf, logical block 392724273, lost async page write Jan 27 11:53:43 TheCouncil kernel: Buffer I/O error on dev sdf, logical block 392724274, lost async page write Quote Link to comment
JorgeB Posted January 28, 2016 Share Posted January 28, 2016 User capacity: 600,332,565,813,390,450 bytes [600 PB] This means the disk dropped offline, power cycle it and do a SMART report. Quote Link to comment
SSD Posted January 28, 2016 Share Posted January 28, 2016 Could be caused by a bad or loose Sata cable or power connection. Quote Link to comment
trevisthomas Posted January 28, 2016 Author Share Posted January 28, 2016 User capacity: 600,332,565,813,390,450 bytes [600 PB] This means the disk dropped offline, power cycle it and do a SMART report. Ah, that makes sense. That also explains why I can't see the drive anywhere else after the failure. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.