Preclear plugin


Recommended Posts

On 11/14/2019 at 6:04 PM, Nortrek said:

Hi, great app.

I plan to sell my server, so to clear the disk for the next user i plan to zero them out.

Am i correct if the fastest way is to use the "Erase All disk" option, then enable the "Skip Pre-Read" and Skip Post-Read" ?

Is that the fastest way to erase them so nothing can be recovered ?

Edit: my server has 8gb of ram, how many disk can i clear at the same time ?

 

Thank you in advance for the help.

It's the fastest way, yes.

 

You can start as many as you like and let the Preclear Queue handle it for you. Go to Server>Tools>Preclear and set the Queue Limit by pressing the correlated icon:

 

797841096_CapturadeTela2019-11-18as19_24_44.thumb.png.d4c22e7fbb73c214f8abb04aa3002db9.png

Link to comment

Using plugin version 2019.11.22, I just tried to preclear a 10tb and it failed with:

############################################################################################################################
                                         unRAID Server Preclear of disk ZA2XXXXX                                          #
#                                       Cycle 1 of 2, partition start on sector 64.                                        #
#   Step 1 of 5 - Verifying unRAID's Preclear signature:                                                           FAIL    #
#   Step 2 of 5 - Writing unRAID's Preclear signature:                                                          SUCCESS    #
#   Step 3 of 5 - Zeroing the disk:                                                       [14:40:54 @ 189 MB/s] SUCCESS    #
#   Step 4 of 5 - Pre-read verification:                                                  [14:43:57 @ 188 MB/s] SUCCESS    #
############################################################################################################################
#                              Cycle elapsed time: 29:24:54 | Total elapsed time: 29:24:54                                 #
############################################################################################################################

############################################################################################################################
#
#                                        S.M.A.R.T. Status (device type: default)                                         
#   ATTRIBUTE                    INITIAL  STATUS                                                                           #
#   5-Reallocated_Sector_Ct      0        -                                                                                #
#   9-Power_On_Hours             0        -                                                                                #
#   184-End-to-End_Error         0        -                                                                                #
#   187-Reported_Uncorrect       0        -                                                                                #
#   190-Airflow_Temperature_Cel  21       -                                                                                #
#   197-Current_Pending_Sector   0        -                                                                                #
#   198-Offline_Uncorrectable    0        -                                                                                #
#   199-UDMA_CRC_Error_Count     0        -                                                                                #
#
############################################################################################################################
#   SMART overall-health self-assessment test result: PASSED                                                               #
############################################################################################################################

--> FAIL: unRAID's Preclear signature not valid.

Anything useful I can provide?

preclear.disk.log

Link to comment

edit: So I figured out the below is a partition. I tried deleting it using Unassigned Devices in destructive mode, but it didn't remove it. So I removed it using fdisk and confirmed it was no longer showing in the UI. I've tried kicking off another preclear run to see if it makes a difference.


Possibly related? This is the only disk I've ever noticed a 'child' dropdown for in Unassigned Devices. It's a shucked Seagate drive.

2019-11-24 10_10_38-Home_Main.png

Edited by Simon
Link to comment

I apologize for adding to a very long thread already, but I've got a few questions about PreClear and if my observations and assumptions are correct.

 

I bought a pile of used ST9600205SS (600gb SAS) drives to stuff into my second unRaid box (n signature) - mainly built as a place for me to try things out, experiment & learn.  I've been putting them through the preclear plugin and have had troubles.  I had gotten through 14 of them and had 6 failures.  Like this:

 

preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: Pre-Read: dd if=/dev/sde of=/dev/null bs=2097152 skip=0 count=600127266816 conv=notrunc iflag=nocache,count_bytes,skip_bytes Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 Sense Key : 0x3 [current] Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 ASC=0x11 ASCQ=0x0 Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 CDB: opcode=0x28 28 00 44 f3 72 00 00 01 00 00 Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: print_req_error: critical medium error, dev sde, sector 1156805224 Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 Sense Key : 0x3 [current] Nov 23 12:30:40 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 ASC=0x11 ASCQ=0x0 Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 CDB: opcode=0x28 28 00 44 f3 72 68 00 00 08 00 Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: print_req_error: critical medium error, dev sde, sector 1156805224 Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: Buffer I/O error on dev sde, logical block 144600653, async page read Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 Sense Key : 0x3 [current] Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 ASC=0x11 ASCQ=0x0 Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: sd 1:0:3:0: [sde] tag#0 CDB: opcode=0x28 28 00 44 f3 72 68 00 00 08 00 Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: print_req_error: critical medium error, dev sde, sector 1156805224 Nov 23 12:30:41 preclear_disk_6XR15H0Z0000B152HZF7_17906: syslog: Buffer I/O error on dev sde, logical block 144600653, async page read Nov 23 12:30:41

That seemed like an abnormally high failure rate to me, so I stopped and took a look at what I was doing.  I had been hot-swapping the drives and kicking off the preclear with a queue allowing two simultaneous preclears.  I have seen Unassigned Devices get confused about what actual physical drive it was referencing before and the log for the preclear above was actually refering to a drive that wasn't even in the system at the time.  (by serial #)  I *think* this is what was happening to preclear.  Lesson learned.  Hot-Swap BAD.

 

I pulled the drives and did a power cycle of the machine.  Waited for unRaid to fully boot, inserted the drives.  Kicked off preclear with the same parameters, with 2 simultaneous preclears.  This cleared up the above problem, but now preclear itself was giving me fits - it got stuck in a "zeroing" loop after the first successful preclear and moving down the queue.  Meaning it'd zero a drive, pause and another drive would zero, then it'd go back to the first drive and zero it again.  And again.

 

So, now I'm rebooting between preclear sessions and have a max simultaneous preclear queue of 1.  This appears to have resolved the issues.  I'm not sure what I'm doing wrong, I feel fairly confident this hardware should be able to do more than one preclear at a time, but it works now...

 

(this is with PreClear 2019.11.22 - basically a new system with fresh plugins and apps installed)

Link to comment

I've just had a similar error to Simon above. A new "shucked" WD 6tb drive.

Unassigned devices shows:

image.png.60448e4a63afb8648127f0e368e7de25.png

Near the end of the preclear log I see these lines:

Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: sd 3:0:0:0: [sdc] Attached SCSI disk
Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: WDC_WD60EDAZ-11U78B0_WD-WX21D690LD9T (sdc) 512 11721045168
Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: excluded disks=sda sda2 sdb sdc sdf
Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 4 --cycles 1 --no-prompt /dev/sdc
Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: Disk /dev/sdc is a SSD, disabling head stress test.

Note that the disk is not an SSD.

Only thing I can think of is that during the zeroing run I added a USB drive to the server (an old drive in the donor USB case). That seemed to pause the zeroing whilst it formatted, but is working as a UD attached disk.

Preclear logs attached.

 

What do I do now. I was going to use it as a replacement parity disk, but wanted to give it a try out. Is it unreasonable to just go ahead and swap it with the existing parity?

 

Thanks,

Jon.

 

TOWER-preclear.disk-20191124-1934.zip

  • Like 1
Link to comment
8 hours ago, Gico said:

+1 for "Invalid unRAID`s MBR signature" on a (WD) shucked drive.

Appreciate you effort gfjardim.

same. fresh install, 3 fresh 10TB WD elements drives failed preclear the night before last, (unshucked, running the tests over USB with a fan on the stack of drives) and now I’m getting email notifications that they’re starting to fail it again with clear SMART reports. the failure notification is the same as simon and jsebright’s above (except no confusion about it being an SSD)

 

this time around i ran a single pass with pre-read unchecked (known passed checkpoint) to catch the flags and heres a log of the preclear

preclear_disk_4A454B304544365A_19209.txt

Edited by omORANGE
Link to comment
8 hours ago, Gico said:

+1 for "Invalid unRAID`s MBR signature" on a (WD) shucked drive.

Appreciate you effort gfjardim.

Same here on a new WD Ultrastar 10TB drive.

 

I've tried it twice with the same error.  First time I did the Pre-Read/Post-Read while the second time I just did the Zeroing.

 

############################################################################################################################
#                                                                                                                          #
#                                        unRAID Server Preclear of disk JEXXXX3N                                           #
#                                       Cycle 1 of 1, partition start on sector 64.                                        #
#                                                                                                                          #
#                                                                                                                          #
#   Step 1 of 3 - Verifying unRAID's Preclear signature:                                                           FAIL    #
#   Step 2 of 3 - Writing unRAID's Preclear signature:                                                          SUCCESS    #
#   Step 3 of 3 - Zeroing the disk:                                                       [14:00:50 @ 198 MB/s] SUCCESS    #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
############################################################################################################################
#                              Cycle elapsed time: 14:00:55 | Total elapsed time: 14:00:55                                 #
############################################################################################################################


############################################################################################################################
#                                                                                                                          #
#                                        S.M.A.R.T. Status (device type: default)                                          #
#                                                                                                                          #
#                                                                                                                          #
#   ATTRIBUTE                    INITIAL  STATUS                                                                           #
#   5-Reallocated_Sector_Ct      0        -                                                                                #
#   9-Power_On_Hours             28       -                                                                                #
#   194-Temperature_Celsius      33       -                                                                                #
#   196-Reallocated_Event_Count  0        -                                                                                #
#   197-Current_Pending_Sector   0        -                                                                                #
#   198-Offline_Uncorrectable    0        -                                                                                #
#   199-UDMA_CRC_Error_Count     0        -                                                                                #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
#                                                                                                                          #
############################################################################################################################
#   SMART overall-health self-assessment test result: PASSED                                                               #
############################################################################################################################

--> FAIL: unRAID's Preclear signature not valid.

 

Edited by jlficken
Link to comment
18 minutes ago, Pascal51882 said:

Same Problem with a 10TB WD Red/My Book over USB. After like 2 days of waiting I got the same error.. 

 

I get same problem also. New array. My 8 2TB drives precleared without issue, but my 4 4TB drives all get this same error (FAIL: unRAID's Preclear signature not valid.). Already tried: swapping cables, connecting to a different HBA card, rerouting power cables, clearing the drives with diskpart on W10 pc, turned off aggressive sata power management etc. no changes. Still fail on all 4TB drives. 

 

Went through extended smart test. All came back clean. Seems to be working fine when I form an array with all the disks. still worries me tho, whether i still have some issue with the drives, cables or the HBAs whether or not to trust the array with current situation.

 

The 2TB drives (WD BLACKS and RE) came from old exsi -server, and 4 TB:s came from old Lenovo NAS. 2 of the 4TB drives are shucked and 2 are non-shucked retail WD RED:s.

 

Other than the size, only thing i can think of is that the 4TB drives were originally GPT -partitioned drives, whereas the 2TB:S were MBR. That shouldnt matter though?

 

Link to comment
1 hour ago, Hurubaw said:

The 2TB drives (WD BLACKS and RE) came from old exsi -server, and 4 TB:s came from old Lenovo NAS. 2 of the 4TB drives are shucked and 2 are non-shucked retail WD RED:s.

 

Could you post the specific model of the HDDs - both the ones failing and the ones completing successfully?

("WD Red" or "WD Black" are marketing names and can point to a bunch of different drive models). You can find the model name as the left part of the "identification" col on the GUI - examples could be WDC_WD4000F9YZ or WDC-WD60EDAZ or HUH721212AL4200. Do not post the serial number, which is typically the rightmost part and should be considered private information).

 

Trying to compare it to my case and perhaps suggest a common theme to the failing drives vs. succeeding ones.

Link to comment
46 minutes ago, doron said:

Could you post the specific model of the HDDs - both the ones failing and the ones completing successfully?

("WD Red" or "WD Black" are marketing names and can point to a bunch of different drive models). You can find the model name as the left part of the "identification" col on the GUI - examples could be WDC_WD4000F9YZ or WDC-WD60EDAZ or HUH721212AL4200. Do not post the serial number, which is typically the rightmost part and should be considered private information).

 

Trying to compare it to my case and perhaps suggest a common theme to the failing drives vs. succeeding ones.

Sure.

 

Passed drives (2TB)

WDC_WD2002FAEX-007BA0

WDC_WD2003FZEX-00Z4SA0

WDC_WD2004FBYZ-01YCBB1

 

Fail drives (4TB)

WDC WD40EFRX-68WT0N0

 

Actually tried also with a 4TB Seagate drive also. Fail on that too, same issue.

ST4000DM004-2CV104

 

One more thing Im noticing now... all 2TB drives are also 7200 drives, the 4TB are all 5400 ones.

 

Looking at the time that the issues started, kinda seems like its an issue with the latest version of preclear. I wonder if I can somehow manually install a previous version of the plugin to that one and give it a go on those drives?

 

EDIT: tried also with 4TB WD GREEN from my mishmatch pile, fail on that one too, same issue.

 

WDC WD40EZRX-00SPEB0

Edited by Hurubaw
Added drive
Link to comment

Looks like I'm having the same issue:

Event: Preclear on xxxxxxxx
Subject: FAIL! Invalid unRAID`s MBR signature on xxxxxxxxx (/dev/sdu)
Description: FAIL! Invalid unRAID`s MBR signature on xxxxxxxxxx (/dev/sdu).
Importance: alert

Invalid unRAID`s MBR signature on xxxxxxxx (/dev/sdu) - Aborted

 

Drive is a 12 TB WD easystore shucked. WDC_WD120EMFZ-11A6JA0

Edited by bobobeastie
removed sn
Link to comment

Thanks @Hurubaw!

... and there goes my hypothesis. The WD40EFRX certainly is not a 4Kn (*), which is what I thought might be a common theme.

36 minutes ago, Hurubaw said:

Looking at the time that the issues started, kinda seems like its an issue with the latest version of preclear. I wonder if I can somehow manually install a previous version of the plugin to that one and give it a go on those drives?

That is for the author to answer authoritatively.

 

(*) 4k native sector size, as opposed to 512e or 512, which both present 512 size sectors, either emulated or native.

Link to comment
29 minutes ago, Simon said:

My 10TB Seagate failed in the same manner again. I'm going to try the Docker preclear and will report back...

If you have the same issue with the docker please post there as well. Might be a general issue with the script (although I doubt it).

Edited by wgstarks
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.