tr0910 Posted January 30, 2016 Share Posted January 30, 2016 I have some older 3tb drives that are throwing errors. I just precleared it successfully using the preclear plugin, but here is what it dumped I think I should preclear it again just in case. What do you think? (not sure what the errors are in line 842. Boot flash has 12gb free) Warning [KIM] - reported uncorrect is 44 Warning [KIM] - current pending sector is 8 Warning [KIM] - offline uncorrectable is 8 unRAID device sdn SMART health [198]: 29-01-2016 22:35 ST3000DM001-9YN166_W1F0N4JK (sdn) ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdn = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 27C, Elapsed Time: 23:34:33 ========================================================================1.15b == ST3000DM001-9YN166 W1F0N4JK == Disk /dev/sdn has been successfully precleared == with a starting sector of 1 ============================================================================ /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdn /tmp/smart_finish_sdn ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 ok Spin_Up_Time = 92 ok Start_Stop_Count = 97 ok Reallocated_Sector_Ct = 100 ok Seek_Error_Rate = 81 ok Power_On_Hours = 76 ok Spin_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Runtime_Bad_Block = 100 ok End-to-End_Error = 100 ok Reported_Uncorrect = 63 ok Command_Timeout = 100 ok High_Fly_Writes = 84 ok Airflow_Temperature_Cel = 78 ok G-Sense_Error_Rate = 100 ok Power-Off_Retract_Count = 100 ok Load_Cycle_Count = 41 ok Temperature_Celsius = 22 ok Current_Pending_Sector = 100 ok Offline_Uncorrectable = 100 ok UDMA_CRC_Error_Count = 200 ok Head_Flying_Hours = 100 ok Total_LBAs_Written = 100 ok Total_LBAs_Read = 100 ok No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 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. a change of 0 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = /boot/config/plugins/preclear.disk/preclear_disk.sh: line 2298: echo: write error: No space left on device root@Kim:/usr/local/emhttp# Quote Link to comment
tr0910 Posted January 30, 2016 Share Posted January 30, 2016 I have some older 3tb drives that are throwing errors. I just precleared it successfully using the preclear plugin, but here is what it dumped I think I should preclear it again just in case. What do you think? (not sure what the errors are in line 842. First time that has appeared. Boot flash has 12gb free) Warning [KIM] - reported uncorrect is 44 Warning [KIM] - current pending sector is 8 Warning [KIM] - offline uncorrectable is 8 unRAID device sdn SMART health [198]: 29-01-2016 22:35 ST3000DM001-9YN166_W1F0N4JK (sdn) ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdn = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 27C, Elapsed Time: 23:34:33 ========================================================================1.15b == ST3000DM001-9YN166 W1F0N4JK == Disk /dev/sdn has been successfully precleared == with a starting sector of 1 ============================================================================ /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdn /tmp/smart_finish_sdn ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 ok Spin_Up_Time = 92 ok Start_Stop_Count = 97 ok Reallocated_Sector_Ct = 100 ok Seek_Error_Rate = 81 ok Power_On_Hours = 76 ok Spin_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Runtime_Bad_Block = 100 ok End-to-End_Error = 100 ok Reported_Uncorrect = 63 ok Command_Timeout = 100 ok High_Fly_Writes = 84 ok Airflow_Temperature_Cel = 78 ok G-Sense_Error_Rate = 100 ok Power-Off_Retract_Count = 100 ok Load_Cycle_Count = 41 ok Temperature_Celsius = 22 ok Current_Pending_Sector = 100 ok Offline_Uncorrectable = 100 ok UDMA_CRC_Error_Count = 200 ok Head_Flying_Hours = 100 ok Total_LBAs_Written = 100 ok Total_LBAs_Read = 100 ok No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 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. a change of 0 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = /boot/config/plugins/preclear.disk/preclear_disk.sh: line 2298: echo: write error: No space left on device root@Kim:/usr/local/emhttp# Quote Link to comment
trurl Posted January 30, 2016 Share Posted January 30, 2016 ...(not sure what the errors are in line 842. Boot flash has 12gb free)... Take a look on the Dashboard under System Status for the numbers labeled flash : log : docker. Possibly the "no space" device is the log. Quote Link to comment
tr0910 Posted January 30, 2016 Share Posted January 30, 2016 Those 3 numbers are. 21% 3% 21% Log has lots of headroom doesn't it? But the syslog has these interesting errors early this morning relating to this drive being precleared a second time. This would have been at the end of the preread, or the start of the zeroing stage. It is happily marching along zeroing at present. Jan 30 06:04:49 Kim kernel: ata4.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 Jan 30 06:04:49 Kim kernel: ata4.00: irq_stat 0x40000008 Jan 30 06:04:49 Kim kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 30 06:04:49 Kim kernel: ata4.00: cmd 60/00:00:70:38:d7/01:00:5c:01:00/40 tag 0 ncq 131072 in Jan 30 06:04:49 Kim kernel: res 41/40:00:08:39:d7/00:01:5c:01:00/00 Emask 0x409 (media error) <F> Jan 30 06:04:49 Kim kernel: ata4.00: status: { DRDY ERR } Jan 30 06:04:49 Kim kernel: ata4.00: error: { UNC } Jan 30 06:04:49 Kim kernel: ata4.00: configured for UDMA/133 Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 Sense Key : 0x3 [current] [descriptor] Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 ASC=0x11 ASCQ=0x4 Jan 30 06:04:49 Kim kernel: sd 5:0:0:0: [sdn] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5c d7 38 70 00 00 01 00 00 00 Jan 30 06:04:49 Kim kernel: blk_update_request: I/O error, dev sdn, sector 5852576008 Jan 30 06:04:49 Kim kernel: ata4: EH complete Jan 30 06:04:52 Kim kernel: ata4.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x0 Jan 30 06:04:52 Kim kernel: ata4.00: irq_stat 0x40000008 Jan 30 06:04:52 Kim kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 30 06:04:52 Kim kernel: ata4.00: cmd 60/08:18:08:39:d7/00:00:5c:01:00/40 tag 3 ncq 4096 in Jan 30 06:04:52 Kim kernel: res 41/40:08:08:39:d7/00:00:5c:01:00/00 Emask 0x409 (media error) <F> Jan 30 06:04:52 Kim kernel: ata4.00: status: { DRDY ERR } Jan 30 06:04:52 Kim kernel: ata4.00: error: { UNC } Jan 30 06:04:52 Kim kernel: ata4.00: configured for UDMA/133 Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 Sense Key : 0x3 [current] [descriptor] Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 ASC=0x11 ASCQ=0x4 Jan 30 06:04:52 Kim kernel: sd 5:0:0:0: [sdn] tag#3 CDB: opcode=0x88 88 00 00 00 00 01 5c d7 39 08 00 00 00 08 00 00 Jan 30 06:04:52 Kim kernel: blk_update_request: I/O error, dev sdn, sector 5852576008 Jan 30 06:04:52 Kim kernel: Buffer I/O error on dev sdn, logical block 731572001, async page read Jan 30 06:04:52 Kim kernel: ata4: EH complete Jan 30 06:04:55 Kim kernel: ata4.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x0 Jan 30 06:04:55 Kim kernel: ata4.00: irq_stat 0x40000008 Jan 30 06:04:55 Kim kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 30 06:04:55 Kim kernel: ata4.00: cmd 60/08:48:08:39:d7/00:00:5c:01:00/40 tag 9 ncq 4096 in Jan 30 06:04:55 Kim kernel: res 41/40:08:08:39:d7/00:00:5c:01:00/00 Emask 0x409 (media error) <F> Jan 30 06:04:55 Kim kernel: ata4.00: status: { DRDY ERR } Jan 30 06:04:55 Kim kernel: ata4.00: error: { UNC } Jan 30 06:04:55 Kim kernel: ata4.00: configured for UDMA/133 Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 Sense Key : 0x3 [current] [descriptor] Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 ASC=0x11 ASCQ=0x4 Jan 30 06:04:55 Kim kernel: sd 5:0:0:0: [sdn] tag#9 CDB: opcode=0x88 88 00 00 00 00 01 5c d7 39 08 00 00 00 08 00 00 Jan 30 06:04:55 Kim kernel: blk_update_request: I/O error, dev sdn, sector 5852576008 Jan 30 06:04:55 Kim kernel: Buffer I/O error on dev sdn, logical block 731572001, async page read Jan 30 06:04:55 Kim kernel: ata4: EH complete Quote Link to comment
tr0910 Posted January 31, 2016 Share Posted January 31, 2016 Those 3 numbers are. 21% 3% 21% Log has lots of headroom doesn't it? It just finished a second pass of preclear, this time the smart uncorrectable and pending are cleared, but uncorrect has increased to 47. Preclear it a third time, but reboot first to hopefully clear up the run errors?? ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdn = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 27C, Elapsed Time: 23:34:33 ========================================================================1.15b == ST3000DM001-9YN166 W1F0N4JK == Disk /dev/sdn has been successfully precleared == with a starting sector of 1 ============================================================================ /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected /boot/config/plugins/preclear.disk/preclear_disk.sh: line 842: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdn /tmp/smart_finish_sdn ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 ok Spin_Up_Time = 92 ok Start_Stop_Count = 97 ok Reallocated_Sector_Ct = 100 ok Seek_Error_Rate = 81 ok Power_On_Hours = 76 ok Spin_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Runtime_Bad_Block = 100 ok End-to-End_Error = 100 ok Reported_Uncorrect = 63 ok Command_Timeout = 100 ok High_Fly_Writes = 84 ok Airflow_Temperature_Cel = 78 ok G-Sense_Error_Rate = 100 ok Power-Off_Retract_Count = 100 ok Load_Cycle_Count = 41 ok Temperature_Celsius = 22 ok Current_Pending_Sector = 100 ok Offline_Uncorrectable = 100 ok UDMA_CRC_Error_Count = 200 ok Head_Flying_Hours = 100 ok Total_LBAs_Written = 100 ok Total_LBAs_Read = 100 ok No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 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. a change of 0 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = /boot/config/plugins/preclear.disk/preclear_disk.sh: line 2298: echo: write error: No space left on device root@Kim:/usr/local/emhttp# Quote Link to comment
SSD Posted January 31, 2016 Share Posted January 31, 2016 Not sure what that invalid integer in line 842 is. Not normal. Possible post read verify issue. I'd guess cabling issue. But generally, smart attributes are not affected by cabling, except the CRC one. Quote Link to comment
tr0910 Posted February 2, 2016 Share Posted February 2, 2016 Not sure what that invalid integer in line 842 is. Not normal. Possible post read verify issue. I'd guess cabling issue. But generally, smart attributes are not affected by cabling, except the CRC one. Swapped the ports for 2 drives being pre cleared, and they both came through with no issues. I have no clue what that invalid integer error is either, but now it is gone simply by swapping a port. Quote Link to comment
itimpi Posted February 2, 2016 Share Posted February 2, 2016 Not sure what that invalid integer in line 842 is. Not normal. Possible post read verify issue. I'd guess cabling issue. But generally, smart attributes are not affected by cabling, except the CRC one. Swapped the ports for 2 drives being pre cleared, and they both came through with no issues. I have no clue what that invalid integer error is either, but now it is gone simply by swapping a port. I think that you can get errors of that sort if you get read/write errors on the drive you are trying to preclear. The preclear is a bash script so it has limited error handling capability. Quote Link to comment
jeffreywhunter Posted February 12, 2016 Share Posted February 12, 2016 Quoted from: http://lime-technology.com/forum/index.php?topic=39985.450 I never saw anything about this, but clearly it's a script problem. Nothing I could do from my side, I'm afraid. Please post this here to someone help you. Reposting the original issue here as recommended by gfjardim. If you guys have a moment, could you take a look at this related post. Looks like 2 of us have the same problem with the preclear plugin hanging on the boot record. Is there a diagnostic or log we can check? I've looked in the preclear log directory on the flash drive, and there's not entry for this disk. http://lime-technology.com/forum/index.php?topic=46501.msg444428#msg444428 Quote Link to comment
RobJ Posted February 13, 2016 Share Posted February 13, 2016 I don't have any ideas myself, but I do suggest simplifying the process first - try running a simple Preclear from the command line, the old way. Quote Link to comment
jeffreywhunter Posted February 16, 2016 Share Posted February 16, 2016 I don't have any ideas myself, but I do suggest simplifying the process first - try running a simple Preclear from the command line, the old way. I ran the command line preclear and it ran without issues. So must be a script issue? Quote Link to comment
trurl Posted February 16, 2016 Share Posted February 16, 2016 I don't have any ideas myself, but I do suggest simplifying the process first - try running a simple Preclear from the command line, the old way. I ran the command line preclear and it ran without issues. So must be a script issue? The command line is a script. The plugin uses whichever version of the script you set it up to use. Quote Link to comment
jeffreywhunter Posted February 19, 2016 Share Posted February 19, 2016 I don't have any ideas myself, but I do suggest simplifying the process first - try running a simple Preclear from the command line, the old way. I ran the command line preclear and it ran without issues. So must be a script issue? The command line is a script. The plugin uses whichever version of the script you set it up to use. Right. For the command line, I'm using the preclear_disk.sh dated 4/5/2014. For the WebGUI, I installed the preclear_bjp.sh. Duh, I should have used the BJP from the command line instead of what I usually use. Didn't connect the dots. I'll have to give the BJP version a try from the command line next time and see if the problem persists. Quote Link to comment
grither Posted March 1, 2016 Share Posted March 1, 2016 hi all, this is a result of preclear from a new 8tb seagate archive drive... everything look ok? wasn't sure about high fly writes, or Hardware ECC recovered? Disk: /dev/sdh smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.17-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000AS0002-1NA17Z Serial Number: Z840DGAZ LU WWN Device Id: 5 000c50 087ebda8a Firmware Version: AR15 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5980 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Mar 1 11:18:36 2016 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 947) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 110 100 006 Pre-fail Always - 26155608 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 21054474 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 75 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 088 088 000 Old_age Always - 12 190 Airflow_Temperature_Cel 0x0022 065 062 045 Old_age Always - 35 (Min/Max 21/38) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 194 Temperature_Celsius 0x0022 035 040 000 Old_age Always - 35 (0 21 0 0 0) 195 Hardware_ECC_Recovered 0x001a 110 100 000 Old_age Always - 26155608 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 219988224901195 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 15628053216 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 47793036504 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. Quote Link to comment
RobJ Posted March 1, 2016 Share Posted March 1, 2016 hi all, this is a result of preclear from a new 8tb seagate archive drive... everything look ok? wasn't sure about high fly writes, or Hardware ECC recovered? Everything looks good. The high fly writes *might* indicate a marginal mechanical issue some day. For now, it's fine. Quote Link to comment
wolferl99 Posted March 8, 2016 Share Posted March 8, 2016 Hi, following situation. I ran a preclear on a drive over the weekend and I assume it finished sometime last night. This morning we had an extended power outage and the server shutdown and then restarted a couple of hours later. I can't seem to find the preclear reports. It looks like the drive was cleared, as I see this, when I run a preclear -t on it: Pre-Clear unRAID Disk /dev/sdl ################################################################## 1.15 Device Model: ST8000AS0002-1NA17Z Serial Number: Z840DXXX LU WWN Device Id: 5 000c50 087d2caac Firmware Version: AR15 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Disk /dev/sdl: 8001.6 GB, 8001563222016 bytes 255 heads, 63 sectors/track, 972801 cylinders, total 15628053168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdl1 1 4294967295 2147483647+ 0 Empty Partition 1 does not start on physical sector boundary. ######################################################################## ========================================================================1.15 == == DISK /dev/sdl IS PRECLEARED with a GPT Protective MBR == ============================================================================ I ran the preclear script via the gui plugin. I checked /boot/preclear_reports/ but there are no new reports. The last one is from November, the last time I ran a preclear. Am I missing something? Are the logs somewhere else? Should I assume that there were no major problems, when the drive is marked precleared? Here's the current smart report. (running an extended smart report right now) root@tower:/boot# smartctl -a /dev/sdl smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: ST8000AS0002-1NA17Z Serial Number: Z840DXXX LU WWN Device Id: 5 000c50 087d2caac Firmware Version: AR15 User Capacity: 8,001,563,222,016 bytes [8.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5980 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Mar 7 17:22:16 2016 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 951) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 81402960 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 071 060 030 Pre-fail Always - 12772681 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 49 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 65537 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 063 060 045 Old_age Always - 37 (Min/Max 18/37) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 194 Temperature_Celsius 0x0022 037 040 000 Old_age Always - 37 (0 18 0 0 0) 195 Hardware_ECC_Recovered 0x001a 114 099 000 Old_age Always - 81402960 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 69879117905966 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 15628053208 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 17547198660 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 Extended offline Self-test routine in progress 90% 49 - # 2 Short offline Completed without error 00% 48 - 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. root@tower:/boot# Quote Link to comment
Kode Posted March 14, 2016 Share Posted March 14, 2016 I personally would run it again, as I understand it, because unraid runs from RAM, logs don't survive a reboot (or loss of power) so there is no way to tell what the previous preclear indicated, if you really don't want to, you could run a SMART test and if everything in there is OK you will probably be fine, what you wont be able to tell is if there were any changes before the start of the preclear and after which can indicate possible problems. *edit* looking at that smart test there is nothing that stands out to me, but I'm no expert, Current_Pending_Sector and Reallocated_Sector_Ct are 0 though so will probably be ok. Quote Link to comment
Joe L. Posted March 16, 2016 Share Posted March 16, 2016 I personally would run it again, as I understand it, because unraid runs from RAM, logs don't survive a reboot (or loss of power) so there is no way to tell what the previous preclear indicated, if you really don't want to, you could run a SMART test and if everything in there is OK you will probably be fine, what you wont be able to tell is if there were any changes before the start of the preclear and after which can indicate possible problems. *edit* looking at that smart test there is nothing that stands out to me, but I'm no expert, Current_Pending_Sector and Reallocated_Sector_Ct are 0 though so will probably be ok. Actually, the preclear script logs its reports on the flash drive in /boot/preclear_reports You might look there. If the report is not there, then it finished the clearing step, but not the post-read phase to see if it was successfully zeroed. Joe L. Quote Link to comment
Dephcon Posted March 16, 2016 Share Posted March 16, 2016 an issue with 6.2? root@vault15:~# /boot/config/plugins/preclear.disk/preclear_disk.sh /dev/sdb sfdisk: invalid option -- 'R' Usage: sfdisk [options] <dev> [[-N] <part>] sfdisk [options] <command> Quote Link to comment
Mailman74 Posted March 17, 2016 Share Posted March 17, 2016 Looking for some help reading my pre clear results on 2 drives. I am still running preclear on 2 8 tb drives that I will post later. I am attaching the results here if I do not attach correct files let me know, thank you preclear_finish_150718RBF54A1515VYWP_2016-03-14.txt preclear_finish_Z300W5T7_2016-03-17.txt Quote Link to comment
saarg Posted March 17, 2016 Share Posted March 17, 2016 an issue with 6.2? root@vault15:~# /boot/config/plugins/preclear.disk/preclear_disk.sh /dev/sdb sfdisk: invalid option -- 'R' Usage: sfdisk [options] <dev> [[-N] <part>] sfdisk [options] <command> Yes it's an issue running the preclear script on 6.2 as it uses a newer version of sfdisk where the R option is depricated. Quote Link to comment
RobJ Posted March 19, 2016 Share Posted March 19, 2016 Looking for some help reading my pre clear results on 2 drives. I am still running preclear on 2 8 tb drives that I will post later. I am attaching the results here if I do not attach correct files let me know, thank you Both look fine. There's a bit of wear and tear on the Seagate, but not bad for 20000 hours. Quote Link to comment
motorskalle Posted March 23, 2016 Share Posted March 23, 2016 I have seen these near_thresh statuses on a couple of reports in this thread. Do any of you guys know if these values are common for the Seagate Archive drives, anyone that observed them in the array for a while and know if they will get worse? --------------------------------------- Preclear Successful Total time 195:12:12 (USB3 enclosure using the preclear plugin and "normal" script with slower post read, 3 cycles performed) Pre-Read time 19:02:30 (116 MB/s) Zeroing time 20:01:25 (111 MB/s) Post-Read time 40:00:08 (55 MB/s) --------------------------------------- ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdo = cycle 1 of 1, partition start on sector 64 = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 43C, Elapsed Time: 195:12:12 ========================================================================1.15 == ST8000AS0002-1NA17Z Z840EE0V == Disk /dev/sdo has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdo /tmp/smart_finish_sdo ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 100 6 ok 180295208 Seek_Error_Rate = 77 100 30 ok 4346424698 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 57 77 45 near_thresh 43 Temperature_Celsius = 43 23 0 ok 43 Hardware_ECC_Recovered = 118 100 0 ok 180295208 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. Quote Link to comment
JorgeB Posted March 23, 2016 Share Posted March 23, 2016 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 57 77 45 near_thresh 43 For the 1st two the important thing here is that both new and old values are the same, they come near threshold from new, e.g., a single end-to-end error will trigger a SMART failing now. The 3rd attribute is temperature, it will trigger a SMART failure at 45C, after the disk cools down it will show "failed in the past". So all looks good, nothing to worry about. Quote Link to comment
motorskalle Posted March 23, 2016 Share Posted March 23, 2016 Thank you Johnnie! So I interpret it as the drive came with the attributes this way, close to the threshold, from Seagate and just barely passed internal tests for e.g. end-to-end error. 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.