2 minutes ago, Squid said:

 

Appears to be

 

You can try the binhex_preclear app instead (which does the identical thing, but is command line only -> he's got a good FAQ on how to do this)

thanks, i just tried the other script that is in the preclear pluging Joe.L - 1.20 and that seems to be working so far, currently doing the pre read. I take it this script does the same thing as the other?

On 12/6/2021 at 2:28 PM, rajk said:

thanks, i just tried the other script that is in the preclear pluging Joe.L - 1.20 and that seems to be working so far, currently doing the pre read. I take it this script does the same thing as the other?

So i  ran the unclear plugin with the Joe. L - 1.20 script and i did not do the pre read only the zeroing and the post read. When completed and i tried to assign the disk to the array unraid is clearing the disk. This never happened when i used the other preclear plugin script, although on those occassions i did do the preread, zeroing and the post read. Does anyone know why unriad is clearing the disk on assignment when its not happened to the other disks i use preclear plugin with before. 

what does current sector pending mean?  it happened in the 1st round of preclear but 0    does it say anything in the diagnostic logs.. is it a bad old drive?

 

backupserver-diagnostics-20211216-0920.zip

A pending sector is one whose contents could not be read reliably.  Can be corrected when the sector is next written, and if not the sector might then be reallocated instead.

oh ok so then it fixed itself above.. as i didnt see no smart errors either.. 

 

learn something new everyday 

 

thanks

Preclear keeps returning "Signature: failed test 1: MBR signature is not valid, byte 3 [00000] != [00170]" on multiple disks that I try. What am I doing wrong?

 

 

Quote

Dec 17 11:13:16 preclear_disk_7PJGPYMC_31025: Disk blocks: 2441609216
Dec 17 11:13:16 preclear_disk_7PJGPYMC_31025: Blocks (512 bytes): 19532873728
Dec 17 11:13:16 preclear_disk_7PJGPYMC_31025: Block size: 4096
Dec 17 11:13:16 preclear_disk_7PJGPYMC_31025: Start sector: 0
Dec 17 11:13:17 preclear_disk_7PJGPYMC_31025: verifying unRAID's signature on the MBR ...
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: Signature: failed test 1: MBR signature is not valid, byte 3 [00000] != [00170]
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: array 'sectors'
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 0 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 1 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 2 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 3 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 4 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 5 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 6 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 7 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 8 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 9 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 10 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 11 -> 00000
Dec 17 11:13:22 preclear_disk_7PJGPYMC_31025: 12 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 13 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 14 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 15 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 16 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 17 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 18 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 19 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: 20 -> 00000
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: fail - Unraid preclear signature invalid!
Dec 17 11:13:23 preclear_disk_7PJGPYMC_31025: error encountered, exiting...

 

2 minutes ago, Giga12 said:

Preclear keeps returning "Signature: failed test 1: MBR signature is not valid, byte 3 [00000] != [00170]" on multiple disks that I try. What am I doing wrong?

Did you actually preclear, or did you just use the option to test the signature?

3 minutes ago, trurl said:

Did you actually preclear, or did you just use the option to test the signature?

 

I was trying to verify the drive but I guess I was doing it wrong.

 

Are the options below the correct ones to use when I get a new drive and want to verify its integrity?

 

13 minutes ago, Giga12 said:

Are the options below the correct ones to use when I get a new drive and want to verify its integrity?

yes

14 minutes ago, Giga12 said:

verify its integrity

In case you don't know, this will take a while, maybe days depending on size of disk.

I just want to confirm that below means the drive is bad, and my only option is to replace it. The pre-read, and zeroing had no issues.

 

Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: dd: warning: partial read (1576960 bytes); suggest iflag=fullblock
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: dd: error reading '/dev/sdp': Input/output error

 

Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1422781+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2983788019712 bytes (3.0 TB, 2.7 TiB) copied, 25062.9 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1423260+0 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1423259+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2984790458368 bytes (3.0 TB, 2.7 TiB) copied, 25075.8 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1423696+0 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1423695+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2985704816640 bytes (3.0 TB, 2.7 TiB) copied, 25087.7 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1424086+0 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1424085+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2986522705920 bytes (3.0 TB, 2.7 TiB) copied, 25099.9 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1424554+0 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1424553+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2987504173056 bytes (3.0 TB, 2.7 TiB) copied, 25112.4 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425025+0 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425024+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2988491931648 bytes (3.0 TB, 2.7 TiB) copied, 25125.2 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425518+0 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425517+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2989525827584 bytes (3.0 TB, 2.7 TiB) copied, 25138.5 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425786+0 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425786+0 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2990089961472 bytes (3.0 TB, 2.7 TiB) copied, 25158.7 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: dd: warning: partial read (1576960 bytes); suggest iflag=fullblock
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: dd: error reading '/dev/sdp': Input/output error
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425786+2 records in
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 1425786+2 records out
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: dd output: 2990092218368 bytes (3.0 TB, 2.7 TiB) copied, 25169.8 s, 119 MB/s
Dec 18 08:35:27 preclear_disk_Z29140NJ00009134VJJ6_31995: Post-Read: post-read verification failed!
Dec 18 08:35:28 preclear_disk_Z29140NJ00009134VJJ6_31995: error encountered, exiting...

 

1 hour ago, Giga12 said:

I just want to confirm that below means the drive is bad, and my only option is to replace it.

No. A SMART report and possibly diagnostics covering that time may be more informative.

5 minutes ago, JonathanM said:

No. A SMART report and possibly diagnostics covering that time may be more informative.

 

Does below help?

 

Dec 18 08:35:24 Tower kernel: blk_update_request: critical medium error, dev sdp, sector 5840027967 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Dec 18 08:35:24 Tower kernel: Buffer I/O error on dev sdp, logical block 730003495, async page read
Dec 18 08:35:27 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Post-Read: dd output: dd: error reading '/dev/sdp': Input/output error

 

Full log

 

Quote

Dec 17 11:29:02 Tower emhttpd: read SMART /dev/sdp
Dec 17 11:31:15 Tower emhttpd: ST33000650SS_Z29140NJ00009134VJJ6_35000c5003503869b (sdp) 512 5860533168
Dec 17 11:31:15 Tower emhttpd: read SMART /dev/sdp
Dec 17 11:45:19 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --no-prompt /dev/sdp
Dec 17 11:45:24 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Pre-Read: dd if=/dev/sdp of=/dev/null bs=2097152 skip=0 count=3000592982016 conv=noerror iflag=nocache,count_bytes,skip_bytes
Dec 17 18:49:24 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Zeroing: dd if=/dev/zero of=/dev/sdp bs=2097152 seek=2097152 count=3000590884864 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Dec 18 01:35:52 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Post-Read: cmp /tmp/.preclear/sdp/fifo /dev/zero
Dec 18 01:35:52 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Post-Read: dd if=/dev/sdp of=/tmp/.preclear/sdp/fifo count=2096640 skip=512 iflag=nocache,count_bytes,skip_bytes
Dec 18 01:35:53 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Post-Read: cmp /tmp/.preclear/sdp/fifo /dev/zero
Dec 18 01:35:53 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Post-Read: dd if=/dev/sdp of=/tmp/.preclear/sdp/fifo bs=2097152 skip=2097152 count=3000590884864 iflag=nocache,count_bytes,skip_bytes
Dec 18 08:23:59 Tower emhttpd: ST33000650SS_Z29140NJ00009134VJJ6_35000c5003503869b (sdp) 512 5860533168
Dec 18 08:24:01 Tower emhttpd: read SMART /dev/sdp
Dec 18 08:35:02 Tower kernel: sd 7:0:14:0: [sdp] tag#2827 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s
Dec 18 08:35:02 Tower kernel: sd 7:0:14:0: [sdp] tag#2827 Sense Key : 0x3 [current] [descriptor]
Dec 18 08:35:02 Tower kernel: sd 7:0:14:0: [sdp] tag#2827 ASC=0x11 ASCQ=0x0
Dec 18 08:35:02 Tower kernel: sd 7:0:14:0: [sdp] tag#2827 CDB: opcode=0x88 88 00 00 00 00 01 5c 17 ba 00 00 00 04 00 00 00
Dec 18 08:35:02 Tower kernel: blk_update_request: critical medium error, dev sdp, sector 5840026638 op 0x0:(READ) flags 0x84700 phys_seg 63 prio class 0
Dec 18 08:35:07 Tower kernel: sd 7:0:14:0: [sdp] tag#2831 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=7s
Dec 18 08:35:07 Tower kernel: sd 7:0:14:0: [sdp] tag#2831 Sense Key : 0x3 [current] [descriptor]
Dec 18 08:35:07 Tower kernel: sd 7:0:14:0: [sdp] tag#2831 ASC=0x11 ASCQ=0x0
Dec 18 08:35:07 Tower kernel: sd 7:0:14:0: [sdp] tag#2831 CDB: opcode=0x88 88 00 00 00 00 01 5c 17 be 00 00 00 04 00 00 00
Dec 18 08:35:07 Tower kernel: blk_update_request: critical medium error, dev sdp, sector 5840027967 op 0x0:(READ) flags 0x84700 phys_seg 25 prio class 0
Dec 18 08:35:07 Tower kernel: sd 7:0:14:0: [sdp] tag#2779 CDB: opcode=0x12 12 00 00 00 fe 00
Dec 18 08:35:10 Tower kernel: sd 7:0:14:0: [sdp] tag#2409 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=9s
Dec 18 08:35:10 Tower kernel: sd 7:0:14:0: [sdp] tag#2409 Sense Key : 0x3 [current] [descriptor]
Dec 18 08:35:10 Tower kernel: sd 7:0:14:0: [sdp] tag#2409 ASC=0x11 ASCQ=0x0
Dec 18 08:35:10 Tower kernel: sd 7:0:14:0: [sdp] tag#2409 CDB: opcode=0x88 88 00 00 00 00 01 5c 17 c4 00 00 00 06 00 00 00
Dec 18 08:35:10 Tower kernel: blk_update_request: critical medium error, dev sdp, sector 5840029296 op 0x0:(READ) flags 0x80700 phys_seg 57 prio class 0
Dec 18 08:35:10 Tower emhttpd: ST33000650SS_Z29140NJ00009134VJJ6_35000c5003503869b (sdp) 512 5860533168
Dec 18 08:35:13 Tower kernel: sd 7:0:14:0: [sdp] tag#3624 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s
Dec 18 08:35:13 Tower kernel: sd 7:0:14:0: [sdp] tag#3624 Sense Key : 0x3 [current] [descriptor]
Dec 18 08:35:13 Tower kernel: sd 7:0:14:0: [sdp] tag#3624 ASC=0x11 ASCQ=0x0
Dec 18 08:35:13 Tower kernel: sd 7:0:14:0: [sdp] tag#3624 CDB: opcode=0x88 88 00 00 00 00 01 5c 17 bc 08 00 00 00 08 00 00
Dec 18 08:35:13 Tower kernel: blk_update_request: critical medium error, dev sdp, sector 5840026638 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Dec 18 08:35:13 Tower kernel: Buffer I/O error on dev sdp, logical block 730003329, async page read
Dec 18 08:35:15 Tower emhttpd: read SMART /dev/sdp
Dec 18 08:35:21 Tower kernel: sd 7:0:14:0: [sdp] tag#2587 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s
Dec 18 08:35:21 Tower kernel: sd 7:0:14:0: [sdp] tag#2587 Sense Key : 0x3 [current] [descriptor]
Dec 18 08:35:21 Tower kernel: sd 7:0:14:0: [sdp] tag#2587 ASC=0x11 ASCQ=0x0
Dec 18 08:35:21 Tower kernel: sd 7:0:14:0: [sdp] tag#2587 CDB: opcode=0x88 88 00 00 00 00 01 5c 17 c1 38 00 00 00 08 00 00
Dec 18 08:35:21 Tower kernel: blk_update_request: critical medium error, dev sdp, sector 5840027967 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Dec 18 08:35:21 Tower kernel: Buffer I/O error on dev sdp, logical block 730003495, async page read
Dec 18 08:35:24 Tower kernel: sd 7:0:14:0: [sdp] tag#1472 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=2s
Dec 18 08:35:24 Tower kernel: sd 7:0:14:0: [sdp] tag#1472 Sense Key : 0x3 [current] [descriptor]
Dec 18 08:35:24 Tower kernel: sd 7:0:14:0: [sdp] tag#1472 ASC=0x11 ASCQ=0x0
Dec 18 08:35:24 Tower kernel: sd 7:0:14:0: [sdp] tag#1472 CDB: opcode=0x88 88 00 00 00 00 01 5c 17 c1 38 00 00 00 08 00 00
Dec 18 08:35:24 Tower kernel: blk_update_request: critical medium error, dev sdp, sector 5840027967 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Dec 18 08:35:24 Tower kernel: Buffer I/O error on dev sdp, logical block 730003495, async page read
Dec 18 08:35:27 Tower preclear_disk_Z29140NJ00009134VJJ6[31995]: Post-Read: dd output: dd: error reading '/dev/sdp': Input/output error

 

Also Smart Report

Quote

=== START OF INFORMATION SECTION ===
Vendor:               SEAGATE
Product:              ST33000650SS
Revision:             0003
Compliance:           SPC-4
User Capacity:        3,000,592,982,016 bytes [3.00 TB]
Logical block size:   512 bytes
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000c5003503869b
Serial number:        Z29140NJ00009134VJJ6
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Sat Dec 18 10:44:28 2021 PST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     31 C
Drive Trip Temperature:        68 C

Manufactured in week 37 of year 2011
Specified cycle count over device lifetime:  10000
Accumulated start-stop cycles:  475
Specified load-unload count over device lifetime:  300000
Accumulated load-unload cycles:  475
Elements in grown defect list: 925

Vendor (Seagate Cache) information
  Blocks sent to initiator = 3243858654
  Blocks received from initiator = 1580171507
  Blocks read from cache and sent to initiator = 9781774
  Number of read and write commands whose size <= segment size = 358814
  Number of read and write commands whose size > segment size = 224

Vendor (Seagate/Hitachi) factory information
  number of hours powered up = 63995.22
  number of minutes until next internal SMART test = 49

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:   4240360522        6         0  4240360528         12       6058.902           6
write:         0        0         0         0          0       3008.327           0
verify:    16882        0         0     16882          0          0.000           0

Non-medium error count:       37

[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
No Self-tests have been logged

 

Edited December 18, 20214 yr by Giga12

2 minutes ago, Giga12 said:

Does below help?

 

2 minutes ago, Giga12 said:

No Self-tests have been logged

Run a long SMART test and then post the results.

5 minutes ago, JonathanM said:

 

Run a long SMART test and then post the results.

 

Running now, to verify that I ran the right command and the only parameter change is --test=long, what I ran was:

smartctl --test=long  /dev/sdp

1 minute ago, Giga12 said:

 

Running now, to verify that I ran the right command and the only parameter change is --test=long, what I ran was:

smartctl --test=long  /dev/sdp

Dunno off the top of my head. I always just click the start button in the GUI for a SMART extended self test, then look at the results in the GUI.

 

Some things require CLI, but I tend not to keep CLI stuff memorized that has a GUI shortcut.

8 minutes ago, JonathanM said:

Dunno off the top of my head. I always just click the start button in the GUI for a SMART extended self test, then look at the results in the GUI.

 

Some things require CLI, but I tend not to keep CLI stuff memorized that has a GUI shortcut.

 Whenever I run it from there, I click Start, it switches the text to "Stop" then goes back to "Start".

 

How do I know its running?

Edited December 18, 20214 yr by Giga12

Just now, Giga12 said:

 Whenever I run it from there, I click Start, it switches the text to another name then goes back to Start.

 

How do I know its running?

It should say that it's running on that same page, along with a % progress.

Just now, JonathanM said:

It should say that it's running on that same page, along with a % progress.

 

Yeah I am not getting that at all. I don't think I have ever gotten it work. The short test doesn't work either.

You may have to disable spindown on the disk to get the test to complete.

3 minutes ago, trurl said:

You may have to disable spindown on the disk to get the test to complete.

 Below is what I am seeing on the current drive. I do not have it as an active disk in my array and my array is stopped.

 

Edited December 18, 20214 yr by Giga12

You want to click the START button next to SMART extended self test

16 minutes ago, trurl said:

You want to click the START button next to SMART extended self test

 

It changes to "Stop", then instantly changes back to "Start" as if it not running. There is no progress or anything.

 

Below are my disk settings. I don't see where spin down is enabled.

 

Edited December 18, 20214 yr by Giga12

15 hours ago, Giga12 said:

The short test doesn't work either.

 

GUI SMART tests don't won't with SAS devices, you'll need to run it manually, but this is not a good sign:

 

Elements in grown defect list: 925

 

You want this to be 0 for a healthy SAS disk.

Good day,

    I just purchased 3 18TB WD HGST's (came with Molex to SATA power adapters to deal with Power Disable) so I can start replacing my 4TB WD Reds.  The goal is to start with my 2 parity drives and then add the third for data (then pull out 4 of the 4TBs) as I am crazy low on space.  My cached drives still have some large movie files on them because no single data drive has enough space for a file of that size to be move to.  I'm using 2 SAS controllers with 8 ports each.  I am using 15 ports (2 parity, 8 data, 2 cache, 3 for docker and VMs) currently and had one port free.  On December 18th I hooked up the first 18TB drive, downloaded the Preclear plugin and kicked it off.  It got through pre-read without issue but this morning I woke up to an email saying zeroing failed.  In Unraid, I can't see the drive in the Dash or in Main but I can see it in Preclear, although it has very little data associated with (see attached).  I'm not new to Unraid but have been lucky with very few problems and this is my first preclear failure.  The logs show Dec 20 05:35:08 "No space left on disk" referencing the 18TB drive at '/dev/sdp'.  I'm at a loss here since I can't see how it's out of space during a preclear, unless the drive loss connectivity during that time and this error is how it manifested the issue.  I have 2 more of these to do and, as we all know, it takes quite some time to complete.  I don't have any smart data since the drives are connected to SAS.  I was thinking of rebooting the server and seeing if the drive shows back up and then using the CLI to pull smart info but I don't want to reboot yet in case I lose logging or anything related to this issue.  I'd appreciate any assistance as to what might be going on with this process or any advice on what next steps to take.  Thank you in advance.

 

Attached are the preclear log .zip, anon diagnostics .zip, and a screenshot of the disk as seen in Preclear currently.

URFS-preclear.disk-20211220-0755.zip urfs-diagnostics-20211220-0754.zip