Hi there

 

after adding a couple of drives to my array I seem to have an issue with the time of pre-clear, for some reason its incredably slow, is there any way I can speed this up or should I just wait? 35 days seems like a very long time...

 

I can see that I have some errors on the 3TB drive, but not sure why the 8TB drive is so slow:

 

jupiter-diagnostics-20240418-0922.zip

Edited April 18, 20242 yr by RoyBatty

Do you mean pre-clear (which happens before you add a drive to the array) of Clear which is what Unraid does by default when adding a new drive if it was not previously pre-cleared?   There is a discussion of the difference here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.  In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

 

I am guessing from the diagnostics that you mean Clear on disk4?   If that is the case you are getting lots of write errors and resets on that drive and in the diagnostics and it appears to have gone offline.   I would suspect a cabling issue (power or SATA) but it could be the drive itself but as it is offline we cannot see any SMART information.   You will almost certainly have to power-cycle the server to get that drive back online.

Yes,basicly what Im trying to do is add 2 drives at the same time, but I guess thats whats failing atm.

To give you a perspective of what Im seeing in unraid now:

 

 

Atm Im a bit stuck with deciding what to do, should I cancel the disk clear, stop the array and remove the faulty drive? Would that increase the speed of adding drive 3? 

 

edit: Adding logs from drive4:

 

Apr 18 08:20:00 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 09 ff b9 48 00 00 01 f8 00 00
Apr 18 08:20:00 Jupiter kernel: I/O error, dev sde, sector 167754056 op 0x1:(WRITE) flags 0x0 phys_seg 63 prio class 2
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c0 00 00 00 08 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532928 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c0 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532928 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532864, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c1 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532929 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532865, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c2 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532930 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532866, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c3 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532931 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532867, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c4 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532932 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532868, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c5 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532933 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532869, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c6 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532934 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532870, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c7 00 00 00 01 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532935 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532871, async page read
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Apr 18 09:23:03 Jupiter kernel: sd 2:0:1:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a2 c0 00 00 00 08 00 00
Apr 18 09:23:03 Jupiter kernel: I/O error, dev sde, sector 5860532928 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Apr 18 09:23:03 Jupiter kernel: Buffer I/O error on dev sde1, logical block 5860532864, async page read

Edited April 18, 20242 yr by RoyBatty

1 minute ago, RoyBatty said:

Atm Im a bit stuck with deciding what to do, should I cancel the disk clear, stop the array and remove the faulty drive? Would that increase the speed of adding drive 3? 

I would certainly recommend removing stopping the array as with disk4 playing up it will take forever 😞

 

It is your choice as to whether you want to try and resolve why disk4 is having issues or initially just get disk3 up and running?  It is possible that disk4 just has a cabling issue (power or SATA) and the drive is physically OK.

Hmm, got the array stopped but now my partity drive is disabled, will try a hardware reboot and see if that fixes the issue. edit: Nope, damn, seems like my disk1 died on me during the process.... Cant see it in the bios either....

 

Weird thing is, disk1 smart info reports no errors. Anything I can do about this? 

jupiter-diagnostics-20240418-1021.zip

jupiter-smart-20240418-1027.zip

Edited April 18, 20242 yr by RoyBatty
added diagnostics.

I ended up starting the array without a parity disk and reassigned the disk to the array, so now just need to wait for the rebuild. Oh well, I guess it was time anyways