Preclear plugin


Recommended Posts

ErrorWarningSystemArrayLogin


DOWNLOAD


Feb 18 15:44:36 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --cycles 1 --skip-preread --skip-postread --no-prompt /dev/sdk
Feb 18 15:44:36 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Preclear Disk Version: 1.0.12
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: S.M.A.R.T. info type: -d scsi
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Disk size: 4000787030016
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Disk blocks: 7814037168
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Blocks (512 bytes): 7814037168
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Block size: 512
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Start sector: 0
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: readlink: missing operand
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Try 'readlink --help' for more information.
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: readlink: missing operand
Feb 18 15:44:39 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Try 'readlink --help' for more information.
Feb 18 15:44:41 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: emptying the MBR.
Feb 18 15:44:41 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: dd if=/dev/zero of=/dev/sdk bs=2097152 seek=2097152 count=4000784932864 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes
Feb 18 15:44:41 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: dd pid [11998]
Feb 18 16:22:10 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 10% zeroed
Feb 18 17:02:06 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 20% zeroed
Feb 18 17:43:04 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 30% zeroed
Feb 18 18:26:33 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 40% zeroed
Feb 18 19:11:22 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 50% zeroed
Feb 18 19:58:19 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 60% zeroed
Feb 18 20:30:21 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: dd[11998]: Pausing (sync command issued)
Feb 18 20:32:25 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: dd[11998]: resumed
Feb 18 20:47:59 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 70% zeroed
Feb 18 21:41:48 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 80% zeroed
Feb 18 22:42:38 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: progress - 90% zeroed
Feb 18 23:53:05 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: dd - wrote 4000787030016 of 4000787030016.
Feb 18 23:53:06 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Zeroing: dd exit code - 0
Feb 18 23:56:55 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: Writing signature: 0 0 2 0 0 255 255 255 1 0 0 0 255 255 255 255
Feb 18 23:56:58 preclear_disk_Z1Z6Y0KM0000R5191JBJ_10484: cat: /tmp/.preclear/sdk/smart_error: No such file or directory

looks like it worked.

 

Link to comment

Just finished pre-clearing 2 disks and go this error on the final output

 

cat: /tmp/.preclear/sdq/smart_error: No such file or directory found

 

It shows me the first graphic of the successful run with the steps 1-5 but then the area it supposed to show the change in smart data shows that

 

Edit:

Just realized these were SAS disks not SATA not sure if that would affect the outcome, i noticed SAS disks seem to have different smart data than SATA disks

 

 

Edited by mikefallen
Link to comment

(I posted this in General originally, not realising it should be here - sorry"!)

I've got a brand-new Toshiba X300 "NAS"  4TB drive that I want to swap-in to replace a 2TB data disk in my array (the Parity drive is already 4TB) but I'm having trouble with the "Preclear" function, accessed by pressing "Start Preclear"  under "Unassigned Devices" on the Main page...

 

As my hardware doesn't have any spare SATA ports, I have the new drive connected to a USB3 "Drive Dock", where the disk plugs into a slot in the top and connects to a SATA connector at the bottom of the slot.  Seems to work fine...

 

 I did a Preclear with the Pre-read set Off (it's a new disk, no SMART problems, zero power-on hours showing when I started using it, so I assumed pre-read was not going to do anything useful).

 

The Zeroing went well, but during Post-Read something happened at some point after 75% - see below for the messages that popped up as it went:

 

=================================================

Preclear on 0123456789000000005: 22-02-2020 09:14
Zeroing started on 0123456789000000005 (sdb)
Zeroing started on 0123456789000000005 (sdb). Cycle 1 of 1.

 

Preclear on 0123456789000000005: 22-02-2020 16:16
Zeroing finished on 0123456789000000005 (sdb)
Zeroing finished on 0123456789000000005 (sdb). Cycle 1 of 1.

 

Preclear on 0123456789000000005: 22-02-2020 16:16
Post-Read started on 0123456789000000005 (sdb)
Post-Read started on 0123456789000000005 (sdb). Cycle 1 of 1.

 

Preclear on 0123456789000000005: 22-02-2020 17:44
Post-Read in progress on 0123456789000000005 (sdb)

 

Post-Read in progress on 0123456789000000005 (sdb): 25% @ 181. Temp: 41 C. Cycle 1 of 1.

Preclear on 0123456789000000005: 22-02-2020 19:21
Post-Read in progress on 0123456789000000005 (sdb)

 

Post-Read in progress on 0123456789000000005 (sdb): 50% @ 165. Temp: 40 C. Cycle 1 of 1.

Preclear on 0123456789000000005: 22-02-2020 21:11
Post-Read in progress on 0123456789000000005 (sdb)

 

Post-Read in progress on 0123456789000000005 (sdb): 75% @ 136. Temp: 39 C. Cycle 1 of 1.

Preclear on 0123456789000000005: 22-02-2020 22:15

 

FAIL! Post-Read 0123456789000000005 (/dev/sdb) failed
FAIL! Post-Read 0123456789000000005 (/dev/sdb) failed

===================================================

What's going on?  The SMART data is still all OK, but the "Format" button doesn't operate, the only thing I can do is to try another Preclear, but given the time it takes I'd like to know why it failed rather than just "trying it again to see what happens"!

 

The log file, from the Preclear starting, is as follows:

============

Feb 22 09:14:14 uServer1 preclear_disk_0123456789000000005[15731]: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 4 --cycles 1 --skip-preread --no-prompt /dev/sdb
Feb 22 09:14:21 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 09:14:21 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 09:14:21 uServer1 preclear_disk_0123456789000000005[15731]: Zeroing: dd if=/dev/zero of=/dev/sdb bs=2097152 seek=2097152 count=4000784932864 conv=notrunc iflag=count_bytes,nocache,fullb

Feb 22 16:16:12 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 16:16:15 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 16:16:18 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: cmp /tmp/.preclear/sdb/fifo /dev/zero
Feb 22 16:16:18 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: dd if=/dev/sdb of=/tmp/.preclear/sdb/fifo count=2096640 skip=512 conv=notrunc iflag=nocache,count_bytes,skip_bytes
Feb 22 16:16:19 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: cmp /tmp/.preclear/sdb/fifo /dev/zero
Feb 22 16:16:20 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: dd if=/dev/sdb of=/tmp/.preclear/sdb/fifo bs=2097152 skip=2097152 count=4000784932864 conv=notrunc iflag=nocache,count_bytes,skip_bytes
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 95 f0 f0 00 00 00 08 00 00 00
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 6810562560
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 95 f0 f8 00 00 00 08 00 00 00
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 6810564608
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 0
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 1860881286
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 672538168
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 7814037167
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 1372338735
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 6810562560
Feb 22 22:15:01 uServer1 kernel: Buffer I/O error on dev sdb, logical block 851320320, async page read
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] No Caching mode page found
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 22:15:03 uServer1 kernel: sdb: sdb1
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 22 22:15:04 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: dd output: dd: error reading '/dev/sdb': Input/output error
Feb 22 22:15:04 uServer1 unassigned.devices: Adding disk '/dev/sdb1'...
Feb 22 22:15:04 uServer1 unassigned.devices: Mount drive command: /sbin/mount -t precleared -o rw,auto,async,noatime,nodiratime '/dev/sdb1' '/mnt/disks/TOSHIBA_HDWQ140'
Feb 22 22:15:04 uServer1 unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/TOSHIBA_HDWQ140: unknown filesystem type 'precleared'.

===================

I have no idea that UNKNOWN (0x2003) means, and it's weird that it suddenly threw errors on apparently random sectors at 22:15:01 - does this suggest anything?

 

Thanks for any help/advice!

 

Cheers,

Howard

 

Link to comment
On 2/24/2020 at 10:04 AM, HDRW said:

(I posted this in General originally, not realising it should be here - sorry"!)

I've got a brand-new Toshiba X300 "NAS"  4TB drive that I want to swap-in to replace a 2TB data disk in my array (the Parity drive is already 4TB) but I'm having trouble with the "Preclear" function, accessed by pressing "Start Preclear"  under "Unassigned Devices" on the Main page...

 

As my hardware doesn't have any spare SATA ports, I have the new drive connected to a USB3 "Drive Dock", where the disk plugs into a slot in the top and connects to a SATA connector at the bottom of the slot.  Seems to work fine...

 

 I did a Preclear with the Pre-read set Off (it's a new disk, no SMART problems, zero power-on hours showing when I started using it, so I assumed pre-read was not going to do anything useful).

 

The Zeroing went well, but during Post-Read something happened at some point after 75% - see below for the messages that popped up as it went:

 

=================================================

Preclear on 0123456789000000005: 22-02-2020 09:14
Zeroing started on 0123456789000000005 (sdb)
Zeroing started on 0123456789000000005 (sdb). Cycle 1 of 1.

 

Preclear on 0123456789000000005: 22-02-2020 16:16
Zeroing finished on 0123456789000000005 (sdb)
Zeroing finished on 0123456789000000005 (sdb). Cycle 1 of 1.

 

Preclear on 0123456789000000005: 22-02-2020 16:16
Post-Read started on 0123456789000000005 (sdb)
Post-Read started on 0123456789000000005 (sdb). Cycle 1 of 1.

 

Preclear on 0123456789000000005: 22-02-2020 17:44
Post-Read in progress on 0123456789000000005 (sdb)

 

Post-Read in progress on 0123456789000000005 (sdb): 25% @ 181. Temp: 41 C. Cycle 1 of 1.

Preclear on 0123456789000000005: 22-02-2020 19:21
Post-Read in progress on 0123456789000000005 (sdb)

 

Post-Read in progress on 0123456789000000005 (sdb): 50% @ 165. Temp: 40 C. Cycle 1 of 1.

Preclear on 0123456789000000005: 22-02-2020 21:11
Post-Read in progress on 0123456789000000005 (sdb)

 

Post-Read in progress on 0123456789000000005 (sdb): 75% @ 136. Temp: 39 C. Cycle 1 of 1.

Preclear on 0123456789000000005: 22-02-2020 22:15

 

FAIL! Post-Read 0123456789000000005 (/dev/sdb) failed
FAIL! Post-Read 0123456789000000005 (/dev/sdb) failed

===================================================

What's going on?  The SMART data is still all OK, but the "Format" button doesn't operate, the only thing I can do is to try another Preclear, but given the time it takes I'd like to know why it failed rather than just "trying it again to see what happens"!

 

The log file, from the Preclear starting, is as follows:

============

Feb 22 09:14:14 uServer1 preclear_disk_0123456789000000005[15731]: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 4 --cycles 1 --skip-preread --no-prompt /dev/sdb
Feb 22 09:14:21 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 09:14:21 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 09:14:21 uServer1 preclear_disk_0123456789000000005[15731]: Zeroing: dd if=/dev/zero of=/dev/sdb bs=2097152 seek=2097152 count=4000784932864 conv=notrunc iflag=count_bytes,nocache,fullb

Feb 22 16:16:12 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 16:16:15 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 16:16:18 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: cmp /tmp/.preclear/sdb/fifo /dev/zero
Feb 22 16:16:18 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: dd if=/dev/sdb of=/tmp/.preclear/sdb/fifo count=2096640 skip=512 conv=notrunc iflag=nocache,count_bytes,skip_bytes
Feb 22 16:16:19 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: cmp /tmp/.preclear/sdb/fifo /dev/zero
Feb 22 16:16:20 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: dd if=/dev/sdb of=/tmp/.preclear/sdb/fifo bs=2097152 skip=2097152 count=4000784932864 conv=notrunc iflag=nocache,count_bytes,skip_bytes
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 95 f0 f0 00 00 00 08 00 00 00
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 6810562560
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
Feb 22 22:15:01 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 95 f0 f8 00 00 00 08 00 00 00
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 6810564608
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 0
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 1860881286
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 672538168
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 7814037167
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 1372338735
Feb 22 22:15:01 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 6810562560
Feb 22 22:15:01 uServer1 kernel: Buffer I/O error on dev sdb, logical block 851320320, async page read
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Write Protect is off
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Mode Sense: 03 00 00 00
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] No Caching mode page found
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 22:15:03 uServer1 kernel: sdb: sdb1
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Feb 22 22:15:03 uServer1 kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Feb 22 22:15:04 uServer1 preclear_disk_0123456789000000005[15731]: Post-Read: dd output: dd: error reading '/dev/sdb': Input/output error
Feb 22 22:15:04 uServer1 unassigned.devices: Adding disk '/dev/sdb1'...
Feb 22 22:15:04 uServer1 unassigned.devices: Mount drive command: /sbin/mount -t precleared -o rw,auto,async,noatime,nodiratime '/dev/sdb1' '/mnt/disks/TOSHIBA_HDWQ140'
Feb 22 22:15:04 uServer1 unassigned.devices: Mount of '/dev/sdb1' failed. Error message: mount: /mnt/disks/TOSHIBA_HDWQ140: unknown filesystem type 'precleared'.

===================

I have no idea that UNKNOWN (0x2003) means, and it's weird that it suddenly threw errors on apparently random sectors at 22:15:01 - does this suggest anything?

 

Thanks for any help/advice!

 

Cheers,

Howard

 

Your hard drive returned input/output errors at Feb 22 22:15:01 and that made the preclear session to fail. This could be the hard drive controller's fault or could be your USB3 dock controller's fault, but I'm confident it's your USB3 dock fault, because hard drives usually present media errors and yours doesn't. Maybe it got hot, who knows.

 

Try replacing it or try to add a small fan toward it.

Link to comment
On 2/21/2020 at 12:12 PM, mikefallen said:

Just finished pre-clearing 2 disks and go this error on the final output

 

cat: /tmp/.preclear/sdq/smart_error: No such file or directory found

 

It shows me the first graphic of the successful run with the steps 1-5 but then the area it supposed to show the change in smart data shows that

 

Edit:

Just realized these were SAS disks not SATA not sure if that would affect the outcome, i noticed SAS disks seem to have different smart data than SATA disks

 

 

If you can run preclear on them again and send me your diagnostics file, I appreciate.

Link to comment
On 2/25/2020 at 4:42 PM, gfjardim said:

Your hard drive returned input/output errors at Feb 22 22:15:01 and that made the preclear session to fail. This could be the hard drive controller's fault or could be your USB3 dock controller's fault, but I'm confident it's your USB3 dock fault, because hard drives usually present media errors and yours doesn't. Maybe it got hot, who knows.

 

Try replacing it or try to add a small fan toward it.

Thanks for your help.  I'm sure it's not a temperature problem - where it is makes this pretty-much impossible!

 

I ran the Preclear again, this time starting with the Erase, which ran OK (taking about 24hrs) and then zeroing.  I last saw the log with less than 10% remaining of the Zeroing, at about 12:00 today.  When I came back for a look this evening, the drive had vanished from the Main screen, so I couldn't get to its own log, but the main log showed this (there wasn't anything before this):

=====================

Feb 26 12:26:19 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
Feb 26 12:26:19 uServer1 kernel: sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 f7 e0 00 00 00 08 00 00 00
Feb 26 12:26:19 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 16244736
Feb 26 12:26:19 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 16242688
Feb 26 12:26:19 uServer1 kernel: Buffer I/O error on dev sdb, logical block 2030336, async page read
Feb 26 12:26:19 uServer1 kernel: print_req_error: I/O error, dev sdb, sector 16242688
Feb 26 12:26:19 uServer1 kernel: Buffer I/O error on dev sdb, logical block 2030336, async page read
Feb 26 12:26:19 uServer1 rc.diskinfo[7387]: SIGHUP received, forcing refresh of disks info.
Feb 26 12:26:19 uServer1 kernel: usb 8-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Feb 26 12:26:19 uServer1 kernel: usb 8-2: language id specifier not provided by device, defaulting to English
Feb 26 12:26:19 uServer1 kernel: usb-storage 8-2:1.0: USB Mass Storage device detected
Feb 26 12:26:19 uServer1 kernel: scsi host1: usb-storage 8-2:1.0
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd - read 8316256256 of 4000787030016.
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd command failed, exit code [1].
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 10+0 records in
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 9+0 records out
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 18874368 bytes (19 MB, 18 MiB) copied, 0.234822 s, 80.4 MB/s
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 1102+0 records in
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 1101+0 records out
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 2308964352 bytes (2.3 GB, 2.2 GiB) copied, 12.1095 s, 191 MB/s
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 2263+0 records in
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 2262+0 records out
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 4743757824 bytes (4.7 GB, 4.4 GiB) copied, 24.7798 s, 191 MB/s
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 3453+0 records in
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 3452+0 records out
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 7239368704 bytes (7.2 GB, 6.7 GiB) copied, 37.7141 s, 192 MB/s
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: dd: error reading '/dev/sdb': Input/output error
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 3964+1 records in
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 3964+1 records out
Feb 26 12:26:21 uServer1 preclear_disk_0123456789000000005[1943]: Post-Read: dd output: 8314159104 bytes (8.3 GB, 7.7 GiB) copied, 43.4195 s, 191 MB/s
Feb 26 12:26:23 uServer1 preclear_disk_0123456789000000005[1943]: error encountered, exiting...
Feb 26 12:26:26 uServer1 kernel: mdcmd (72): spindown 2
Feb 26 12:26:41 uServer1 kernel: usb 8-2: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Feb 26 12:29:58 uServer1 kernel: mdcmd (73): spindown 3
Feb 26 12:37:00 uServer1 kernel: mdcmd (74): spindown 0
Feb 26 13:49:30 uServer1 kernel: mdcmd (75): spindown 0
Feb 26 14:14:41 uServer1 kernel: mdcmd (76): spindown 0
Feb 26 14:14:53 uServer1 kernel: mdcmd (77): spindown 1
Feb 26 19:37:16 uServer1 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdc

=====================

So it looks like the failure occurred at about the end of Zeroing (given the time).

 

I rebooted and the drive reappeared, showing "precleared" but with the Format button inoperative, as before.

So it does look like something is causing the USB/SATA dock to fail, but it got through erasing and only failed at about the same point during Zeroing.  I'm a bit lost for ideas!

 

Cheers,

Howard

Link to comment
28 minutes ago, gfjardim said:

Not about the same time, the first time it ran for about 6 hours, now it only read 8.3GiB.

 

Please send me the output of this command: smartctl -a /dev/sdb

OK, here it is:

 

root@uServer1:~# smartctl -a /dev/sdb
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.98-Unraid] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     TOSHIBA HDWQ140
Serial Number:    X9GBK1LEFBJG
LU WWN Device Id: 5 000039 99bc010c0
Firmware Version: FJ1M
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Feb 26 20:36:29 2020 GMT
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:                (  120) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 455) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       7394
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       2
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       125
 10 Spin_Retry_Count        0x0033   100   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2
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       -       0
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       133
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       28 (Min/Max 11/42)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   100   100   000    Old_age   Always       -       125
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       637
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

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    Completed without error       00%        81         -
# 2  Short offline       Completed without error       00%        44         -

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.

 

Cheers,

Howard

 

Link to comment

Hi ... Just lost my zero'ing of a WD14TB drive at 99% with the following ....

Mar 1 21:05:16 xtower preclear_disk_39524A374C425943[5720]: Zeroing: dd output: dd: error writing '/dev/sda': No space left on device

Tried to resume the session but it just isnt picking up the device now, seems a strange error message, any ideas?

Edited by superloopy1
Link to comment
15 minutes ago, superloopy1 said:

Hi ... Just lost my zero'ing of a WD14TB drive at 99% with the following ....

Mar 1 21:05:16 xtower preclear_disk_39524A374C425943[5720]: Zeroing: dd output: dd: error writing '/dev/sda': No space left on device

Tried to resume the session but it just isnt picking up the device now, seems a strange error message, any ideas?

Send the diagnostics file.

Link to comment
Just now, gfjardim said:

Yep, USB dropouts. You're not the first this week. If you can test the drive connected directly to a SATA port, we can troubleshoot it.

Got no free sata ports, that's the problem. I've been running preclears constatntly for a couple of weeks now via usb never had an issue, so what's causing this, and at 99% ... aargghh! Once preclared it goes in as an upgrade and outgoing disk goes to backup server.

Edited by superloopy1
Link to comment
4 minutes ago, superloopy1 said:

Got no free sata ports, that's the problem. I've been running preclears constatntly for a couple of weeks now via usb never had an issue, so what's causing this, and at 99% ... aargghh!

All other drives were 14TB? Maybe a loose cable or a power brownout. 

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.