Preclear plugin


Recommended Posts

27 minutes ago, trurl said:

Testing RAM in another machine won't diagnose problems with your RAM slots or other things that may be related to how that RAM actually works on your machine.

I ran MemTest for 2 days (back in January) before I even booted into unRAID for the first time, so when I started having stability issues memory never even crossed my mind.  I'm trying to avoid having my system down for several days, but if it can't be avoided then I guess I must...  

 

Things have been rock solid with just the 2 sticks so I'm kinda avoidin pokin the bear. 

Link to comment

Quite a lot of motherboards have trouble clocking RAM at the maximum advertised speeds when all slots are used.    Therefore you can easily get the situation where the system is stable under any 2 of your RAM sticks but then has stability issues when all 4 are plugged in simultaneously.

Link to comment

Okay,

 

So I tried pre-clearing the drive again, and it failed *again* in a different spot:

 

Apr 06 17:10:47 preclear_disk_WCJ2NAHF_10954: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 3 --cycles 1 --no-prompt /dev/sda
Apr 06 17:10:47 preclear_disk_WCJ2NAHF_10954: Preclear Disk Version: 1.0.21
Apr 06 17:10:48 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T. info type: default
Apr 06 17:10:48 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T. attrs type: default
Apr 06 17:10:48 preclear_disk_WCJ2NAHF_10954: Disk size: 5000981077504
Apr 06 17:10:48 preclear_disk_WCJ2NAHF_10954: Disk blocks: 1220942645
Apr 06 17:10:48 preclear_disk_WCJ2NAHF_10954: Blocks (512 bytes): 9767541167
Apr 06 17:10:48 preclear_disk_WCJ2NAHF_10954: Block size: 4096
Apr 06 17:10:48 preclear_disk_WCJ2NAHF_10954: Start sector: 684071734
Apr 06 17:10:51 preclear_disk_WCJ2NAHF_10954: Pre-read: pre-read verification started (1/5)....
Apr 06 17:10:52 preclear_disk_WCJ2NAHF_10954: Pre-Read: dd if=/dev/sda of=/dev/null bs=2097152 skip=0 count=5000981077504 conv=noerror iflag=nocache,count_bytes,skip_bytes
Apr 06 18:15:27 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 10% read @ 130 MB/s
Apr 06 19:21:15 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 20% read @ 129 MB/s
Apr 06 20:29:42 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 30% read @ 108 MB/s
Apr 06 21:41:38 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 40% read @ 115 MB/s
Apr 06 22:57:57 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 50% read @ 105 MB/s
Apr 07 00:19:23 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 60% read @ 90 MB/s
Apr 07 01:47:16 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 70% read @ 95 MB/s
Apr 07 03:23:45 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 80% read @ 81 MB/s
Apr 07 05:13:06 preclear_disk_WCJ2NAHF_10954: Pre-Read: progress - 90% read @ 69 MB/s
Apr 07 07:19:53 preclear_disk_WCJ2NAHF_10954: Pre-Read: dd - read 5000981077504 of 5000981077504 (0).
Apr 07 07:19:53 preclear_disk_WCJ2NAHF_10954: Pre-Read: elapsed time - 14:08:59
Apr 07 07:19:53 preclear_disk_WCJ2NAHF_10954: Pre-Read: dd exit code - 0
Apr 07 07:19:54 preclear_disk_WCJ2NAHF_10954: Pre-read: pre-read verification completed!
Apr 07 07:19:54 preclear_disk_WCJ2NAHF_10954: Zeroing: zeroing the disk started (1/5)....
Apr 07 07:19:54 preclear_disk_WCJ2NAHF_10954: Zeroing: emptying the MBR.
Apr 07 07:19:54 preclear_disk_WCJ2NAHF_10954: Zeroing: dd if=/dev/zero of=/dev/sda bs=2097152 seek=2097152 count=5000978980352 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Apr 07 07:19:54 preclear_disk_WCJ2NAHF_10954: Zeroing: dd pid [2492]
Apr 07 08:19:40 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 10% zeroed @ 144 MB/s
Apr 07 09:21:05 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 20% zeroed @ 138 MB/s
Apr 07 10:24:35 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 30% zeroed @ 133 MB/s
Apr 07 11:31:07 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 40% zeroed @ 119 MB/s
Apr 07 12:40:58 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 50% zeroed @ 115 MB/s
Apr 07 13:55:18 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 60% zeroed @ 114 MB/s
Apr 07 15:15:26 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 70% zeroed @ 101 MB/s
Apr 07 16:42:54 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 80% zeroed @ 93 MB/s
Apr 07 18:21:10 preclear_disk_WCJ2NAHF_10954: Zeroing: progress - 90% zeroed @ 79 MB/s
Apr 07 20:16:37 preclear_disk_WCJ2NAHF_10954: Zeroing: dd - wrote 5000981077504 of 5000981077504 (0).
Apr 07 20:16:37 preclear_disk_WCJ2NAHF_10954: Zeroing: elapsed time - 12:56:40
Apr 07 20:16:37 preclear_disk_WCJ2NAHF_10954: Zeroing: dd exit code - 0
Apr 07 20:16:37 preclear_disk_WCJ2NAHF_10954: Zeroing: zeroing the disk completed!
Apr 07 20:16:38 preclear_disk_WCJ2NAHF_10954: Signature: writing signature:    0   0   2   0   0 255 255 255   1   0   0   0 255 255 255 255
Apr 07 20:16:38 preclear_disk_WCJ2NAHF_10954: Signature: verifying unRAID's signature on the MBR ...
Apr 07 20:16:38 preclear_disk_WCJ2NAHF_10954: Signature: Unraid preclear signature is valid!
Apr 07 20:16:39 preclear_disk_WCJ2NAHF_10954: Post-Read: post-read verification started (1/5)....
Apr 07 20:16:39 preclear_disk_WCJ2NAHF_10954: Post-Read: verifying the beginning of the disk.
Apr 07 20:16:39 preclear_disk_WCJ2NAHF_10954: Post-Read: cmp /tmp/.preclear/sda/fifo /dev/zero
Apr 07 20:16:39 preclear_disk_WCJ2NAHF_10954: Post-Read: dd if=/dev/sda of=/tmp/.preclear/sda/fifo count=2096640 skip=512 iflag=nocache,count_bytes,skip_bytes
Apr 07 20:16:40 preclear_disk_WCJ2NAHF_10954: Post-Read: verifying the rest of the disk.
Apr 07 20:16:40 preclear_disk_WCJ2NAHF_10954: Post-Read: cmp /tmp/.preclear/sda/fifo /dev/zero
Apr 07 20:16:40 preclear_disk_WCJ2NAHF_10954: Post-Read: dd if=/dev/sda of=/tmp/.preclear/sda/fifo bs=2097152 skip=2097152 count=5000978980352 iflag=nocache,count_bytes,skip_bytes
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: cmp command failed - disk not zeroed
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd - read 14092861440 of 5000981077504 (4986888216064).
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: elapsed time - 0:01:51
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd command failed, exit code [141].
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 1027+0 records in
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 1026+0 records out
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 2151677952 bytes (2.2 GB, 2.0 GiB) copied, 16.452 s, 131 MB/s
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 1474+0 records in
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 1473+0 records out
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 3089104896 bytes (3.1 GB, 2.9 GiB) copied, 23.5275 s, 131 MB/s
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 1920+0 records in
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 1919+0 records out
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 4024434688 bytes (4.0 GB, 3.7 GiB) copied, 30.6582 s, 131 MB/s
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 2435+0 records in
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 2434+0 records out
Apr 07 20:18:33 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 5104467968 bytes (5.1 GB, 4.8 GiB) copied, 38.9401 s, 131 MB/s
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 3030+0 records in
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 3029+0 records out
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 6352273408 bytes (6.4 GB, 5.9 GiB) copied, 48.3416 s, 131 MB/s
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 3700+0 records in
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 3699+0 records out
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 7757365248 bytes (7.8 GB, 7.2 GiB) copied, 58.9051 s, 132 MB/s
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 4437+0 records in
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 4436+0 records out
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 9302966272 bytes (9.3 GB, 8.7 GiB) copied, 70.546 s, 132 MB/s
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 5251+0 records in
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 5250+0 records out
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 11010048000 bytes (11 GB, 10 GiB) copied, 83.2843 s, 132 MB/s
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 6035+0 records in
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 6034+0 records out
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 12654215168 bytes (13 GB, 12 GiB) copied, 96.0797 s, 132 MB/s
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 6720+0 records in
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 6719+0 records out
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: dd output: 14090764288 bytes (14 GB, 13 GiB) copied, 107.935 s, 131 MB/s
Apr 07 20:18:34 preclear_disk_WCJ2NAHF_10954: Post-Read: post-read verification failed!
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: Error:
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.:
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: ATTRIBUTE                INITIAL  NOW  STATUS
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: Reallocated_Sector_Ct    0        0    -
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: Power_On_Hours           28       56   Up 28
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: SATA_Downshift_Count     0        0    -
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: End-to-End_Error         0        0    -
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: Reported_Uncorrect       0        0    -
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: Airflow_Temperature_Cel  33       39   Up 6
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: Current_Pending_Sector   0        0    -
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: Offline_Uncorrectable    0        0    -
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: UDMA_CRC_Error_Count     0        0    -
Apr 07 20:18:35 preclear_disk_WCJ2NAHF_10954: S.M.A.R.T.: SMART overall-health self-assessment test result: PASSED
Apr 07 20:18:36 preclear_disk_WCJ2NAHF_10954: error encountered, exiting...

 

This time it failed at ~14GB post-read, as opposed to around 27 GB last time... suggesting to me it's likely not the drive, but rather something else (like a RAM issue you suggested).  I'd expect it to fail around the same area if I had bad sectors...

Link to comment
35 minutes ago, heyitsjel said:

This time it failed at ~14GB post-read, as opposed to around 27 GB last time... suggesting to me it's likely not the drive, but rather something else (like a RAM issue you suggested).  I'd expect it to fail around the same area if I had bad sectors...

I agree.

Link to comment

***Update***  It seems /var/log was full, after expanding /var/log and a reboot, preclear is displaying correctly.  We'll see if that also corrects the issue with preclear status once it completes. 

_____________________________________________________________________

 

I precleared a drive last week, which appeared to finish without error, but it was unable to upload the stats and afterward, the drive did not show as being precleared.   I've updated to 6.9.2 with version 2021.03.18 of preclear.  I decided to go ahead and run another preclear on the drive.   Now, the preview and log are acting odd, scrolling continuously.   Let me know if you'd like a diagnostics post or anything else.

 

tput: unknown terminal "screen"
tput: unknown terminal "screen"
tput: unknown terminal "screen"
tput: unknown terminal "screen"

unRAID Server Preclear of disk 35504A5642525646
Cycle 1 of 1, partition start on sector 64.


Step 1 of 4 - Zeroing in progress:
(1% Done)
** Time elapsed: 0:11:33 | Write speed: 206 MB/s | Average speed: 208 MB/s
Cycle elapsed time: 0:11:35 | Total elapsed time: 0:11:35
S.M.A.R.T. Status (device type: default)
ATTRIBUTE                INITIAL  STATUS
Reallocated_Sector_Ct    0        -
Power_On_Hours           142      -
Temperature_Celsius      27       -
Reallocated_Event_Count  0        -
Current_Pending_Sector   0        -
Offline_Uncorrectable    0        -
UDMA_CRC_Error_Count     0        -
SMART overall-health self-assessment test result: PASSED
tput: unknown terminal "screen"
tput: unknown terminal "screen"
tput: unknown terminal "screen"
tput: unknown terminal "screen"
tput: unknown terminal "screen"

 

Thanks for your time!

seine-diagnostics-20210408-1852.zip

Edited by Grrrreg
updating issue, possible resolution
Link to comment

So my issue was not with Preclear, but with my memory (as suggested I think the slower clock speeds with all 4 sticks populated where causing timing issues and corruption resulting in hung processes).  On the 2 sticks at full stock speed, I precleared 5 disks simultaneously without issue.  Thanks for looking and offering up guidance and suggestions. 

Link to comment

Not sure with 100% certainty what the issue was, but I did the following and it seems to have resolved my issue:

 

1) Changed my RAM speed to DDR4 defaults (2400mhz) instead of XMP. 

2) Enabled IOMMU groups & other virtualisation settings I thought were already enabled (or at least partially... strange that they seemed to have set themselves back to being disabled).

3) Updated Unassigned Devices plugin. Pre-clear started to act weird at this point; not recognising the attached USB drive details (eg. manufacturer, firmware etc.). Tried moving USB port and rebooting, but made no difference.

4) Uninstalled and then re-installed pre-clear. Issues with drive recognition seem to have fixed themselves.

 

So far I'm now at ~43% post read :)

 

I'm thinking it's either the RAM or some sort of issue with the previously installed Preclear plugin (eg. corruption).

Link to comment

Hi guys,

I'm brand new to unraid and this is my first server build.  I have an almost new disk (WD Red Plus 8TB) that I have taken out of my DS418 Play that I'm zeroing for use as a parity drive, however it doesn't look like it's reporting stats back into unraid correctly during the zeroing process.

I've already cleared 2 shucked 8TB WD Elements and they reported stats fine, and I'm sure temp ad writes were being displyed correctly when this one started.  Is this just a visual bug or something more suspect?

This drive is plugged directly into the MB sata, the previous 2 are plugged into an LSI 9211-8i HBA.

Thanks!

 

image.thumb.png.8acc38c9ae7e72c81b1536510717d2ad.png

image.png.e3c117032737a4043f99fb649cbe1628.png

Link to comment
1 hour ago, GarethRR said:

I'm brand new to unraid and this is my first server build.  I have an almost new disk (WD Red Plus 8TB) that I have taken out of my DS418 Play that I'm zeroing for use as a parity drive, however it doesn't look like it's reporting stats back into unraid correctly during the zeroing process.

I've already cleared 2 shucked 8TB WD Elements and they reported stats fine, and I'm sure temp ad writes were being displyed correctly when this one started.  Is this just a visual bug or something more suspect?

This drive is plugged directly into the MB sata, the previous 2 are plugged into an LSI 9211-8i HBA.

If this pre-clear is still in progress, can you please share your smart data from Main > Drive Name > Download next to Download SMART Report? Alternatively this is also in diagnostics.zip. You should be able to see the smart data on this screen too. As long as the smart data is visible there (and not wildly inaccurate) it's not an issue with your drive. 

ie. 

1422771940_ScreenShot2021-04-13at8_01_48pm.thumb.png.8efa37a298a320d614692ad5f3ee7643.png

223442474_ScreenShot2021-04-13at8_03_09pm.thumb.png.d891801e3b2d35f742aa4a385606b9e6.png

Edited by lnxd
  • Like 1
Link to comment
Hi guys,
I'm brand new to unraid and this is my first server build.  I have an almost new disk (WD Red Plus 8TB) that I have taken out of my DS418 Play that I'm zeroing for use as a parity drive, however it doesn't look like it's reporting stats back into unraid correctly during the zeroing process.
I've already cleared 2 shucked 8TB WD Elements and they reported stats fine, and I'm sure temp ad writes were being displyed correctly when this one started.  Is this just a visual bug or something more suspect?
This drive is plugged directly into the MB sata, the previous 2 are plugged into an LSI 9211-8i HBA.
Thanks!
 
image.thumb.png.8acc38c9ae7e72c81b1536510717d2ad.png
image.png.e3c117032737a4043f99fb649cbe1628.png
This is not a problem with Preclear itself, but with Unraid and the mechanism it uses to track unassigned drives usage. Let's see if@dlandon have a clue of that's going on here.

Enviado de meu SM-G985F usando o Tapatalk

  • Like 2
Link to comment
26 minutes ago, lnxd said:

If this pre-clear is still in progress, can you please share your smart data from Main > Drive Name > Download Report? Alternatively this is also in diagnostics.zip. You should be able to see the smart data on this screen too. As long as the smart data is visible there (and not wildly inaccurate) it's not an issue with your drive. 

 

The pre-clear is still in progress, now onto the post-read.  The disk is not in the array, it's unassigned devices and the disk info label is not clickable. 

 

image.png.6f926b851259b6b16426ca0383f3a2d2.png

 

Pre-clear preview as currently stands below

image.png.b686594d7f71f1edaacc7c9156ca5782.png

 

Disk log

image.thumb.png.4e7f0ede343aca95c18526ca239ac870.png

 

diskinfo_log also attached, which shows lots of entries where SMART info is not being found.

Should I pause the pre-clear to run a SMART test?  No SMART info seems to be available below.  I'm also sure I added the, manufacture and purchase date and warranty period information to the disk yesterday, parhaps when pre-clear was already in progress.

 

image.thumb.png.aa0b8299b0ed24e4c93fb617df45da35.png

diskinfo_log.txt

Edited by GarethRR
  • Like 1
Link to comment
2 minutes ago, GarethRR said:

The pre-clear is still in progress, now onto the post-read.  The disk is not in the array, it's unassigned devices and the disk info label is not clickable. 


Those logs line up with what @gfjardim said above, and I think they're spot on. If I was you I'd let the preclear finish and then confirm that the SMART data is valid after that. Definitely keep an eye on the current temperature data afterwards and make sure it updates as expected, as that is one of the more frequently updated SMART data points, and one that the system likely relies on. You can monitor it for a while before you add it to your array of course, but I think your drive is fine. 

 

 

  • Like 1
Link to comment
51 minutes ago, gfjardim said:

This is not a problem with Preclear itself, but with Unraid and the mechanism it uses to track unassigned drives usage. Let's see if@dlandon have a clue of that's going on here.

Starting with 6.9, Unraid is controlling UD disk spin down.  Because preclear activity is not being tracked as disk activity, Unraid sets the disk as spun down.  It's really not spun down, but Unraid thinks it is.  When this happens, UD does not get the temp, or r/w stats for the disk from Unraid to display.  It's really only a visual thing and doesn't affect the preclear operation.

 

There is currently no plan to change this.

  • Like 1
Link to comment
8 minutes ago, dlandon said:

Starting with 6.9, Unraid is controlling UD disk spin down.  Because preclear activity is not being tracked as disk activity, Unraid sets the disk as spun down.  It's really not spun down, but Unraid thinks it is.  When this happens, UD does not get the temp, or r/w stats for the disk from Unraid to display.  It's really only a visual thing and doesn't affect the preclear operation.

 

There is currently no plan to change this.

 

Thanks for answering this so promptly. Is there anything that Preclear can change to show Unraid that the disk is currently working?

Link to comment
9 hours ago, gfjardim said:

 

Thanks for answering this so promptly. Is there anything that Preclear can change to show Unraid that the disk is currently working?

The only thing I can think of is to bump the disk with a command periodically to have Unraid spin the disk back up.  It's not really spinning the disk back up because it is already spinning, it just makes Unraid think it is spinning again.  I'll PM you the details.

Link to comment

I'm running Preclear as a confidence check on a new 4 TB Western Digital (Red).  It's failing, and, as this is the second brand new 4TB WD drive it has failed on, I'm unsure as to whether it's the drive or the plug-in.  Full disclosure: I'm not an UNRAID power user; I obtained it strictly to turn an old PC of mine into a file server; for which it's been working fine.  This is my first attempt at adding a new drive; I planned on the 4TB becoming my new parity drive and using the 2 TB it replaces for data.   I'm attaching the Preclear log.  Let me know if I'm just unlucky in having purchased 2 bad drives in a row, or if there's something that can be done to get this newest drive working.  Thanks in advance for any help.

preclear_disk_WD-WX42D8058N2A_11243.txt

Link to comment
7 minutes ago, TimFG said:

I'm running Preclear as a confidence check on a new 4 TB Western Digital (Red).  It's failing, and, as this is the second brand new 4TB WD drive it has failed on, I'm unsure as to whether it's the drive or the plug-in.  Full disclosure: I'm not an UNRAID power user; I obtained it strictly to turn an old PC of mine into a file server; for which it's been working fine.  This is my first attempt at adding a new drive; I planned on the 4TB becoming my new parity drive and using the 2 TB it replaces for data.   I'm attaching the Preclear log.  Let me know if I'm just unlucky in having purchased 2 bad drives in a row, or if there's something that can be done to get this newest drive working.  Thanks in advance for any help.

preclear_disk_WD-WX42D8058N2A_11243.txt 320.49 kB · 1 download

 

It may be useful to share diagnostics to allow for better support (unRAID > Tools > Diagnostics) :)

 

You have to be very unlucky to have had 2 bad drives like that. It's worth checking other things at this point.

  1. How are you running preclear and which version it is?
  2. Is this new drive connected to the same storage controller as existing drives? Tried a different cable/port?
  3. Side note: what's the specific model number of the drive? Unlikely to be cause of issue, but if this is a newly purchased drive, I think most recommend the CMR drives (WD Red Plus/Pro) and not the SMR drives. The lower capacity Red drives (e.g. 4TB) come in both flavours; e.g. WD40EFZX (CMR) and WD40EFAX (SMR)

Aside from this issue you're experiencing, I recently went through a similar juggle of drives on an old unRAID server where I replaced my 2TB parity with a larger one and repurposed the old parity as a new data drive. Feel free to message me if you have questions at that stage.

 

Link to comment

Sorry, didn't think about the diagnostics log; it's attached.  The problem drive is SMR apparently (Model Family: Western Digital Red (SMR)).  I had tried switching cables a number of times on the first one, but haven't yet tried on this one.  The drive is attached to a 2 port  storage controller a co-worker had given me.  I'm not sure of the make/model.  I haven't tried plugging the new drive into the other port, which is in use; I'll do that, but, if it works, and it's a port issue, it leaves me without the other drive - not the worst outcome, I guess.  Are there any plug-ins that you know of that are similar to HWiNFO for Windows that can give me a detailed view of the hardware in my box?

cntfile-diagnostics-20210418-1624.zip

Link to comment
12 hours ago, TimFG said:

Sorry, didn't think about the diagnostics log; it's attached.  The problem drive is SMR apparently (Model Family: Western Digital Red (SMR)).  I had tried switching cables a number of times on the first one, but haven't yet tried on this one.  The drive is attached to a 2 port  storage controller a co-worker had given me.  I'm not sure of the make/model.  I haven't tried plugging the new drive into the other port, which is in use; I'll do that, but, if it works, and it's a port issue, it leaves me without the other drive - not the worst outcome, I guess.  Are there any plug-ins that you know of that are similar to HWiNFO for Windows that can give me a detailed view of the hardware in my box?

cntfile-diagnostics-20210418-1624.zip 135.99 kB · 0 downloads

 

Logs show a bad drive and/or a bad controller card. Hard to tell which is the faulty one because of mixed syslog entries. I would try to put the testing disk into another controller's SATA port to eliminate the HBA from the suspect list.

Link to comment
On 4/13/2021 at 12:11 PM, dlandon said:

It's really only a visual thing and doesn't affect the preclear operation.

 

It's more than just cosmetic though. It increments SMART parameters 4, 192 and 193 and momentarily halts throughput. Spin-down is attempted hourly, just before the hour. Otherwise the pre-clear is proceeding well.

 

896509036_ScreenShot2021-04-19at19_01_47.thumb.png.b7260b01f79ab6c749fe42e95af2965e.png

 

179801010_ScreenShot2021-04-19at19_00_37.png.7e6f67e1b9e7d79b5a58ab1e58dc333d.png

 

disk-log.txt

 

 

 

Link to comment

Seeing this is a Preclear thread, I'm going to post my question here about SMART health assessment. 

 

I have a couple of pretty old 2 TB WDEF20RX RED NAS. These have been pretty reliable from my old QNAP NAS, possibly close to 10 years old. They have been lightly used in the Unraid server, those shares don't get use much. Now I'm repurposing these drives as external BU drives using an external USB SATA. 

I've just done preclear to check disc condition and wipe clear, I know, it doesn't wipe it cleanly, but I plan to encrypt the drives anyway using Unraid encrypted (luks). The reason I've done preclear is to make sure they are still ok to use. However I've been getting the following message.

 

 S.M.A.R.T.: ATTRIBUTE                INITIAL  NOW    STATUS
 S.M.A.R.T.: Reallocated_Sector_Ct    0        0      -
 S.M.A.R.T.: Power_On_Hours           44631    44649  Up 18
 S.M.A.R.T.: Temperature_Celsius      32       35     Up 3
 S.M.A.R.T.: Reallocated_Event_Count  0        0      -
 S.M.A.R.T.: Current_Pending_Sector   0        0      -
 S.M.A.R.T.: Offline_Uncorrectable    0        0      -
 S.M.A.R.T.: UDMA_CRC_Error_Count     0        0      -
 S.M.A.R.T.: SMART overall-health self-assessment test result: FAILED!

 

If the message is overall-health self-assessment test result FAILED, how safe is it to use these drives as Back-up drives? I have other backups, these are the third back ups following the 3-2-1 rule.

 

Preclear log attached.

 

Thanks.

Phil

preclear_disk_012345678900000001A_17247.txt

Edited by Rhodius
Link to comment
On 4/19/2021 at 8:55 PM, Rhodius said:

how safe is it to use these drives as Back-up drives?

 

The information you've given doesn't show what's wrong with them. You'd need to look at the full SMART report for that. As to your question, I'd ask how safe is it to use a failed parachute or a failed crash helmet? Better than none, but not much.

Link to comment

A quick question regarding an oddity when preclearing disks, maybe I am missing something very obvious.

After the disks are precleared I leave them in the chassis in case I have a disk failure so that I can throw them at the array quickly whenever needed.

The strange thing is that after a while the disk seems to have a partition on it and I need to preclear again.

What am I missing? UNRAID or unassigned devices seem to be doing something that I don't want by creating a new partition on the disk, is there a way to lock the disk or something?

Thanks for the help

Link to comment
5 hours ago, Hakunamatata said:

The strange thing is that after a while the disk seems to have a partition on it and I need to preclear again.

What am I missing? UNRAID or unassigned devices seem to be doing something that I don't want by creating a new partition on the disk, is there a way to lock the disk or something?

Thanks for the help

 

Never heard of this happening before without the user taking some action.

 

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.