DeathStar Darth Posted September 4, 2022 Share Posted September 4, 2022 2 hours ago, dlandon said: The diskinfo_log you posted is from the old preclear disk plugin and doesn't apply to the UD Preclear. Post your diagnostics file. thedeathstar-diagnostics-20220904-2037.zip Quote Link to comment
dlandon Posted September 4, 2022 Author Share Posted September 4, 2022 18 minutes ago, DeathStar Darth said: thedeathstar-diagnostics-20220904-2037.zip 271.14 kB · 1 download Looks like a disk problem: Sep 3 11:06:38 Elmo kernel: ata6.00: exception Emask 0x10 SAct 0x1000000 SErr 0x280100 action 0x6 frozen Sep 3 11:06:38 Elmo kernel: ata6.00: irq_stat 0x08000000, interface fatal error Sep 3 11:06:38 Elmo kernel: ata6: SError: { UnrecovData 10B8B BadCRC } Sep 3 11:06:38 Elmo kernel: ata6.00: failed command: READ FPDMA QUEUED Sep 3 11:06:38 Elmo kernel: ata6.00: cmd 60/f8:c0:48:02:00/01:00:00:00:00/40 tag 24 ncq dma 258048 in Sep 3 11:06:38 Elmo kernel: res 50/00:f8:48:02:00/00:01:00:00:00/40 Emask 0x10 (ATA bus error) Sep 3 11:06:38 Elmo kernel: ata6.00: status: { DRDY } Sep 3 11:06:38 Elmo kernel: ata6: hard resetting link Sep 3 11:06:38 Elmo kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 3 11:06:38 Elmo kernel: ata6.00: ATA Identify Device Log not supported ### [PREVIOUS LINE REPEATED 1 TIMES] ### Sep 3 11:06:38 Elmo kernel: ata6.00: configured for UDMA/133 Quote Link to comment
JorgeB Posted September 5, 2022 Share Posted September 5, 2022 11 hours ago, dlandon said: { UnrecovData 10B8B BadCRC } This is usually a bad SATA cable. Quote Link to comment
DeathStar Darth Posted September 5, 2022 Share Posted September 5, 2022 (edited) 16 hours ago, dlandon said: Looks like a disk problem: Sep 3 11:06:38 Elmo kernel: ata6.00: exception Emask 0x10 SAct 0x1000000 SErr 0x280100 action 0x6 frozen Sep 3 11:06:38 Elmo kernel: ata6.00: irq_stat 0x08000000, interface fatal error Sep 3 11:06:38 Elmo kernel: ata6: SError: { UnrecovData 10B8B BadCRC } Sep 3 11:06:38 Elmo kernel: ata6.00: failed command: READ FPDMA QUEUED Sep 3 11:06:38 Elmo kernel: ata6.00: cmd 60/f8:c0:48:02:00/01:00:00:00:00/40 tag 24 ncq dma 258048 in Sep 3 11:06:38 Elmo kernel: res 50/00:f8:48:02:00/00:01:00:00:00/40 Emask 0x10 (ATA bus error) Sep 3 11:06:38 Elmo kernel: ata6.00: status: { DRDY } Sep 3 11:06:38 Elmo kernel: ata6: hard resetting link Sep 3 11:06:38 Elmo kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 3 11:06:38 Elmo kernel: ata6.00: ATA Identify Device Log not supported ### [PREVIOUS LINE REPEATED 1 TIMES] ### Sep 3 11:06:38 Elmo kernel: ata6.00: configured for UDMA/133 Which log/diagnostic is that from? I've searched for "Elmo" and can't locate a file with it in, and the main syslog has no postings at 11:06:38. I've power-downed and reseated the cable to the new drive but get same result on preclear. Not knowing where that log entry pointed out is from, I can't see if it has had any impact there. I can see the difference between the other (old/working) 18tb (same make/model) in the array Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] 4096-byte physical blocks Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Write Protect is off Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Mode Sense: 7f 00 10 08 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 5 14:00:01 TheDeathStar kernel: sdi: sdi1 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Attached SCSI disk Sep 5 14:02:55 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:02:55 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:02:55 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:02:55 TheDeathStar emhttpd: read SMART /dev/sdi Sep 5 14:04:32 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:04:32 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:04:32 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:04:32 TheDeathStar emhttpd: read SMART /dev/sdi Sep 5 14:04:41 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:04:41 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:04:41 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:04:41 TheDeathStar emhttpd: read SMART /dev/sdi and the new one Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] 4096-byte physical blocks Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Write Protect is off Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Mode Sense: 7f 00 10 08 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Attached SCSI disk Sep 5 14:02:55 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:02:55 TheDeathStar emhttpd: read SMART /dev/sdb Sep 5 14:04:32 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:04:32 TheDeathStar emhttpd: read SMART /dev/sdb Sep 5 14:04:41 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:04:41 TheDeathStar emhttpd: read SMART /dev/sdb (Thankyou for you help so far) Edited September 5, 2022 by DeathStar Darth Quote Link to comment
dlandon Posted September 5, 2022 Author Share Posted September 5, 2022 1 hour ago, DeathStar Darth said: Which log/diagnostic is that from? I've searched for "Elmo" and can't locate a file with it in, and the main syslog has no postings at 11:06:38. I think I may have confused your diagnostics with someone else. Quote Link to comment
dlandon Posted September 5, 2022 Author Share Posted September 5, 2022 1 hour ago, DeathStar Darth said: Which log/diagnostic is that from? I've searched for "Elmo" and can't locate a file with it in, and the main syslog has no postings at 11:06:38. I've power-downed and reseated the cable to the new drive but get same result on preclear. Not knowing where that log entry pointed out is from, I can't see if it has had any impact there. I can see the difference between the other (old/working) 18tb (same make/model) in the array Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] 4096-byte physical blocks Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Write Protect is off Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Mode Sense: 7f 00 10 08 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 5 14:00:01 TheDeathStar kernel: sdi: sdi1 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:7:0: [sdi] Attached SCSI disk Sep 5 14:02:55 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:02:55 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:02:55 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:02:55 TheDeathStar emhttpd: read SMART /dev/sdi Sep 5 14:04:32 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:04:32 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:04:32 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:04:32 TheDeathStar emhttpd: read SMART /dev/sdi Sep 5 14:04:41 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH (sdi) 512 35156656128 Sep 5 14:04:41 TheDeathStar kernel: mdcmd (8): import 7 sdi 64 17578328012 0 TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH Sep 5 14:04:41 TheDeathStar kernel: md: import disk7: (sdi) TOSHIBA_MG09ACA18TE_Z1C0A05MFJDH size: 17578328012 Sep 5 14:04:41 TheDeathStar emhttpd: read SMART /dev/sdi and the new one Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB) Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] 4096-byte physical blocks Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Write Protect is off Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Mode Sense: 7f 00 10 08 Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 5 14:00:01 TheDeathStar kernel: sd 8:0:0:0: [sdb] Attached SCSI disk Sep 5 14:02:55 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:02:55 TheDeathStar emhttpd: read SMART /dev/sdb Sep 5 14:04:32 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:04:32 TheDeathStar emhttpd: read SMART /dev/sdb Sep 5 14:04:41 TheDeathStar emhttpd: TOSHIBA_MG09ACA18TE_Z180A014FJDH (sdb) 512 35156656128 Sep 5 14:04:41 TheDeathStar emhttpd: read SMART /dev/sdb (Thankyou for you help so far) You have a huge amount of plugins including Nerd Pack that is loading a lot of packages. I recommend the following steps: Remove the Nerd Pack plugin and reboot. Try a preclear and see it it works properly. Reboot in safe mode and install the UD and UD Preclear packages. You'll need to install CA manually. Instructions are here: Try a preclear and see if it works. Quote Link to comment
DeathStar Darth Posted September 5, 2022 Share Posted September 5, 2022 (edited) 1 hour ago, dlandon said: You have a huge amount of plugins including Nerd Pack that is loading a lot of packages. I recommend the following steps: Remove the Nerd Pack plugin and reboot. Try a preclear and see it it works properly. Reboot in safe mode and install the UD and UD Preclear packages. You'll need to install CA manually. Instructions are here: Try a preclear and see if it works. I removed the Nerd Pack, rebooted and tried a pre-clear again, and observed the same pattern of errors as seen with it present. (note, I again observed intermittent read speeds >0 bytes) I booted in safe mode and set a tail of the syslog going before adding the the CA and UA plugins. I noticed ominous signs on the thumbdrive Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:41 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 58 00 Sep 5 15:34:41 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x80700 phys_seg 88 prio class 0 Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c9 00 00 57 00 Sep 5 15:34:42 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16073 op 0x0:(READ) flags 0x80000 phys_seg 87 prio class 0 Sep 5 15:34:42 TheDeathStar emhttpd: error: get_fs_sizes, 6059: Input/output error (5): statfs: /boot Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:42 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 01 00 Sep 5 15:34:42 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 5 15:34:42 TheDeathStar kernel: FAT-fs (sda1): FAT read failed (blocknr 14024) Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 58 00 Sep 5 15:34:43 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x80700 phys_seg 88 prio class 0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c9 00 00 57 00 Sep 5 15:34:43 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16073 op 0x0:(READ) flags 0x80000 phys_seg 87 prio class 0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:43 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 01 00 Sep 5 15:34:43 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 5 15:34:43 TheDeathStar emhttpd: error: get_fs_sizes, 6059: Input/output error (5): statfs: /boot Sep 5 15:34:43 TheDeathStar kernel: FAT-fs (sda1): FAT read failed (blocknr 14024) Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 58 00 Sep 5 15:34:44 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x80700 phys_seg 88 prio class 0 Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 Sep 5 15:34:44 TheDeathStar kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 3e c8 00 00 01 00 Sep 5 15:34:44 TheDeathStar kernel: blk_update_request: critical medium error, dev sda, sector 16072 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Sep 5 15:34:44 TheDeathStar emhttpd: error: get_fs_sizes, 6059: Input/output error (5): statfs: /boot Sep 5 15:34:44 TheDeathStar kernel: FAT-fs (sda1): FAT read failed (blocknr 14024) Time for a new thumbdrive me thinks... I proceed with the CA/UA install anyway and tried preclear again. This time I don't get the repeating errors (shown in https://forums.unraid.net/topic/120567-unassigned-devices-preclear-a-utility-to-preclear-disks-before-adding-them-to-the-array/?do=findComment&comment=1165650, instead it has just been (seemingly) stuck on /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh --notify 4 --frequen cy 4 --cycles 1 --no-prompt /dev/sdb I have not seen read speed >0 on this attempt. The syslog has recorded the following in that period: Sep 5 15:38:56 TheDeathStar kernel: usb 4-4.4: USB disconnect, device number 4 Sep 5 15:38:56 TheDeathStar kernel: usb 4-4.4: new full-speed USB device number 6 using xhci_hcd Sep 5 15:38:57 TheDeathStar kernel: cdc_acm 4-4.4:1.0: ttyACM0: USB ACM device Sep 5 15:39:00 TheDeathStar kernel: usb 4-4.4: USB disconnect, device number 6 Sep 5 15:39:00 TheDeathStar kernel: usb 4-4.4: new full-speed USB device number 7 using xhci_hcd Sep 5 15:39:00 TheDeathStar kernel: cdc_acm 4-4.4:1.0: ttyACM0: USB ACM device Sep 5 15:39:44 TheDeathStar ntpd[1621]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Sep 5 15:41:58 TheDeathStar emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg Sep 5 15:41:58 TheDeathStar root: plugin: running: anonymous Sep 5 15:41:58 TheDeathStar root: plugin: running: anonymous Sep 5 15:41:58 TheDeathStar root: plugin: skipping: /boot/config/plugins/community.applications/community.applications-2022.07.26-x86_64-1.txz already exists Sep 5 15:41:58 TheDeathStar root: plugin: running: /boot/config/plugins/community.applications/community.applications-2022.07.26-x86_64-1.txz Sep 5 15:41:58 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:31 TheDeathStar emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.php install https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices-2022.09.02.tgz already exists Sep 5 15:42:31 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/start_unassigned_devices - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: setting: /tmp/start_unassigned_devices - mode to 0770 Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices.cfg already exists Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/samba_mount.cfg already exists Sep 5 15:42:31 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/smb-settings.conf - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/config/smb-extra.conf - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/add-smb-extra - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: setting: /tmp/unassigned.devices/add-smb-extra - mode to 0770 Sep 5 15:42:31 TheDeathStar root: plugin: creating: /tmp/unassigned.devices/remove-smb-extra - from INLINE content Sep 5 15:42:31 TheDeathStar root: plugin: setting: /tmp/unassigned.devices/remove-smb-extra - mode to 0770 Sep 5 15:42:31 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:59 TheDeathStar emhttpd: cmd: /usr/local/emhttp/plugins/community.applications/scripts/pluginInstall.php install https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.preclear.plg Sep 5 15:42:59 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:59 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices.preclear/unassigned.devices.preclear-2022.09.02.tgz already exists Sep 5 15:42:59 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices.preclear/tmux-3.1b-x86_64-1.txz already exists Sep 5 15:42:59 TheDeathStar root: plugin: running: /boot/config/plugins/unassigned.devices.preclear/tmux-3.1b-x86_64-1.txz Sep 5 15:42:59 TheDeathStar root: plugin: skipping: /boot/config/plugins/unassigned.devices.preclear/utempter-1.2.0-x86_64-3.txz already exists Sep 5 15:42:59 TheDeathStar root: plugin: running: /boot/config/plugins/unassigned.devices.preclear/utempter-1.2.0-x86_64-3.txz Sep 5 15:42:59 TheDeathStar root: plugin: running: anonymous Sep 5 15:42:59 TheDeathStar root: plugin: running: anonymous Sep 5 15:43:22 TheDeathStar unassigned.devices: PHP Warning: file_get_contents(plugins/dynamix.s3.sleep/Sleep.php): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 66 Sep 5 15:48:43 TheDeathStar unassigned.devices: PHP Warning: file_get_contents(plugins/dynamix.s3.sleep/Sleep.php): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 66 Sep 5 15:48:58 TheDeathStar unassigned.devices: Refreshed Disks and Configuration. Edited September 5, 2022 by DeathStar Darth Quote Link to comment
dlandon Posted September 5, 2022 Author Share Posted September 5, 2022 11 minutes ago, DeathStar Darth said: I have not seen read speed >0 on this attempt. What does the status show - click on the eye. Also download the preclear logs and post here. Quote Link to comment
DeathStar Darth Posted September 5, 2022 Share Posted September 5, 2022 4 hours ago, dlandon said: What does the status show - click on the eye. Also download the preclear logs and post here. THEDEATHSTAR-unassigned.devices.preclear-20220905-2035.zip Quote Link to comment
dlandon Posted September 5, 2022 Author Share Posted September 5, 2022 1 hour ago, DeathStar Darth said: THEDEATHSTAR-unassigned.devices.preclear-20220905-2035.zip 1.13 kB · 0 downloads What is the situation here? Safe mode with UD and UD preclear plugins only installed? Quote Link to comment
DeathStar Darth Posted September 6, 2022 Share Posted September 6, 2022 (edited) On 9/5/2022 at 9:48 PM, dlandon said: What is the situation here? Safe mode with UD and UD preclear plugins only installed? yes, that's correct. I replied late last night whilst away but didn't have my forum login details to hand so it looks like it gets blocked pending a moderator (just in case you see a similar post later). I rebooted in regular (rather than safe) mode, installed the binhex preclear docker, ran that, and it behaved well I forgot to disable the weekly backup and the law of sod being what it is, it was scheduled for early this morning so got interrupted. I restarted it earlier and its 45% of the way through the read cycle....so fingers crossed from here on in. Update 2022-09-08 07:45 BST - still running happily. Fully expect it to complete Update 2022-09-09 13:45 BST - at 94% of stage 10/10 so unless there is final 'gotcha', we look good. Edited September 9, 2022 by DeathStar Darth Update on running status Quote Link to comment
i1mran92 Posted September 17, 2022 Share Posted September 17, 2022 hi. is there a way i can check if a drive has been precleared or not? thank you Quote Link to comment
dlandon Posted September 17, 2022 Author Share Posted September 17, 2022 3 hours ago, i1mran92 said: hi. is there a way i can check if a drive has been precleared or not? thank you Check the Preclear page: Or run a "Verify Signature": Quote Link to comment
i1mran92 Posted September 18, 2022 Share Posted September 18, 2022 On 9/17/2022 at 7:27 PM, dlandon said: Check the Preclear page: Or run a "Verify Signature": after server reboot, it doesnt show the precleared status but the verify signature operation did the trick. thank you! Quote Link to comment
Stubbs Posted September 27, 2022 Share Posted September 27, 2022 If I run a preclear over a USB3 connection to a hard drive, then re-connect the hard drive with a SATA cable, it will retain the Unraid signature, right? And can be added straight to the array? Quote Link to comment
trurl Posted September 27, 2022 Share Posted September 27, 2022 5 minutes ago, Stubbs said: If I run a preclear over a USB3 connection to a hard drive, then re-connect the hard drive with a SATA cable, it will retain the Unraid signature, right? And can be added straight to the array? Might depend on how the USB3 connection is implemented. Many USB enclosures won't even pass SMART data, and some can even affect the apparent size of a disk Quote Link to comment
burnaby_boy Posted November 8, 2022 Share Posted November 8, 2022 I am running Unraid 6.9.2. After uninstalling the old preclear plugin and rebooting the server, I attempted to install the Unassigned Devices Preclear app. When I clicked on the install button a popup appeared saying "Requirements not met - The requirements for this upgrade have not been met on your system". Any ideas as to what this means? Thanks Quote Link to comment
burnaby_boy Posted November 8, 2022 Share Posted November 8, 2022 Sorry, upon further reading, I realized that I neglected to install the Unassigned Devices app in advance of Unassigned Devices Preclear. Quote Link to comment
ThatTallGuy21 Posted November 8, 2022 Share Posted November 8, 2022 (edited) Hello, it's been well over a year since I had a new disk to pre-clear and within the last month or so I upgraded to 6.11.0 from 6.9.2. So, I'm battling being rusty and potentially new changes to the OS. I don't know what I'm missing, if something changed, or if I'm experiencing an issue. I plug my 14TB EasyStore into my server, and it's picked up with the device name name 'Dev 1'. However, regardless of whether I mount or leave it unmounted, I can't get it to display within the Preclear plugin dashboard to kick-off the preclear process. Any tips on things I may be missing? Did anything change after 6.9.2? An old SpaceInvaderOne video I just watched shows that it should just automatically display but that's not happening... Edited November 8, 2022 by ThatTallGuy21 Quote Link to comment
dlandon Posted November 8, 2022 Author Share Posted November 8, 2022 48 minutes ago, ThatTallGuy21 said: Hello, it's been well over a year since I had a new disk to pre-clear and within the last month or so I upgraded to 6.11.0 from 6.9.2. So, I'm battling being rusty and potentially new changes to the OS. I don't know what I'm missing, if something changed, or if I'm experiencing an issue. I plug my 14TB EasyStore into my server, and it's picked up with the device name name 'Dev 1'. However, regardless of whether I mount or leave it unmounted, I can't get it to display within the Preclear plugin dashboard to kick-off the preclear process. Any tips on things I may be missing? Did anything change after 6.9.2? An old SpaceInvaderOne video I just watched shows that it should just automatically display but that's not happening... Remove the partition. Quote Link to comment
ThatTallGuy21 Posted November 8, 2022 Share Posted November 8, 2022 2 minutes ago, dlandon said: Remove the partition. Please excuse my ignorance but I never had to do that before when it was a brand-new drive out of the box. It would just show up. I thought preclear removed everything on the drive (including any partitions)? Quote Link to comment
dlandon Posted November 8, 2022 Author Share Posted November 8, 2022 2 minutes ago, ThatTallGuy21 said: Please excuse my ignorance but I never had to do that before when it was a brand-new drive out of the box. It would just show up. I thought preclear removed everything on the drive (including any partitions)? A protection is built in now to prevent preclearing any disk that has partitions. Go to UD and click the red 'X' next to the serial number and the disk will be cleared. You will need to have the destructive mode turned on before the red 'X' will show. 1 Quote Link to comment
ThatTallGuy21 Posted November 9, 2022 Share Posted November 9, 2022 1 hour ago, dlandon said: A protection is built in now to prevent preclearing any disk that has partitions. Go to UD and click the red 'X' next to the serial number and the disk will be cleared. You will need to have the destructive mode turned on before the red 'X' will show. That did the trick! Thank you! Quote Link to comment
iarp Posted November 9, 2022 Share Posted November 9, 2022 (edited) 6.11.1 with latest plugin versions installed. I'm attempting to preclear a 3TB drive. It's not going to be an array drive, it'll be more of a monthly backup rotation drive. I'm using the preclear as a test. At this point I've attempted to run preclear three (maybe four) times. If I trigger the clearing with the GUI with all default settings on the post-read I get: Nov 08 21:16:13 preclear_disk_WD-WCC7K6PJ0D5Z_786: Post-Read: post-read verification failed! Nov 08 21:16:17 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Error: Nov 08 21:16:17 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Nov 08 21:16:17 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Reallocated_Sector_Ct 0 0 - Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Power_On_Hours 42487 42498 Up 11 Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Temperature_Celsius 22 28 Up 6 Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Reallocated_Event_Count 0 0 - Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Current_Pending_Sector 0 0 - Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Offline_Uncorrectable 0 0 - Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 - Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: S.M.A.R.T.: Nov 08 21:16:18 preclear_disk_WD-WCC7K6PJ0D5Z_786: error encountered, exiting ... I'm not see errors in syslog for the drive. Edited November 10, 2022 by iarp Quote Link to comment
KablammoNick Posted November 21, 2022 Share Posted November 21, 2022 Two new drives, first one failed with "No space left on device"... Second one finished write ok, just doing post-read now. Where to from here? Nov 20 19:10:14 preclear_disk_ZFN408VD_5320: Preclear Disk Version: 1.0.26 Nov 20 19:10:15 preclear_disk_ZFN408VD_5320: Disk size: 4000787030016 Nov 20 19:10:15 preclear_disk_ZFN408VD_5320: Disk blocks: 976754646 Nov 20 19:10:15 preclear_disk_ZFN408VD_5320: Blocks (512 bytes): 7814037168 Nov 20 19:10:15 preclear_disk_ZFN408VD_5320: Block size: 4096 Nov 20 19:10:15 preclear_disk_ZFN408VD_5320: Start sector: 0 Nov 20 19:10:18 preclear_disk_ZFN408VD_5320: Pre-read: pre-read verification started 1 of 5 retries... Nov 20 20:40:37 preclear_disk_ZFN408VD_5320: Pre-Read: progress - 25% read @ 179 MB/s Nov 20 22:20:04 preclear_disk_ZFN408VD_5320: Pre-Read: progress - 50% read @ 161 MB/s Nov 21 00:15:34 preclear_disk_ZFN408VD_5320: Pre-Read: progress - 75% read @ 130 MB/s Nov 21 02:53:10 preclear_disk_ZFN408VD_5320: Pre-Read: elapsed time - 7:42:48 Nov 21 02:53:10 preclear_disk_ZFN408VD_5320: Pre-read: pre-read verification completed! Nov 21 02:53:10 preclear_disk_ZFN408VD_5320: Zeroing: zeroing the disk started 1 of 5 retries... Nov 21 02:53:10 preclear_disk_ZFN408VD_5320: Zeroing: emptying the MBR. Nov 21 04:23:29 preclear_disk_ZFN408VD_5320: Zeroing: progress - 25% zeroed @ 180 MB/s Nov 21 06:02:57 preclear_disk_ZFN408VD_5320: Zeroing: progress - 50% zeroed @ 159 MB/s Nov 21 07:58:46 preclear_disk_ZFN408VD_5320: Zeroing: progress - 75% zeroed @ 129 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd command failed, exit code [1]. Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1871139+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3924062896128 bytes (3.9 TB, 3.6 TiB) copied, 26914.4 s, 146 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1871674+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1871674+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3925184872448 bytes (3.9 TB, 3.6 TiB) copied, 26927.3 s, 146 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872148+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872148+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3926178922496 bytes (3.9 TB, 3.6 TiB) copied, 26940.1 s, 146 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872328+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872328+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3926556409856 bytes (3.9 TB, 3.6 TiB) copied, 26952.9 s, 146 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872388+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872388+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3926682238976 bytes (3.9 TB, 3.6 TiB) copied, 26964.9 s, 146 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872529+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1872529+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3926977937408 bytes (3.9 TB, 3.6 TiB) copied, 26976.4 s, 146 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1879646+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1879646+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3941903368192 bytes (3.9 TB, 3.6 TiB) copied, 26988.4 s, 146 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1888928+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1888928+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3961369133056 bytes (4.0 TB, 3.6 TiB) copied, 27000.6 s, 147 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1898199+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1898199+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3980811829248 bytes (4.0 TB, 3.6 TiB) copied, 27013 s, 147 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: dd: error writing '/dev/sde': No space left on device Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1901419+0 records in Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 1901418+0 records out Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: dd output: 3987562561536 bytes (4.0 TB, 3.6 TiB) copied, 27019.9 s, 148 MB/s Nov 21 10:23:33 preclear_disk_ZFN408VD_5320: Zeroing: zeroing the disk failed! Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Error: Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Reallocated_Sector_Ct 0 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Power_On_Hours 0h+49m+22.573s - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Runtime_Bad_Block 0 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: End-to-End_Error 0 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Reported_Uncorrect 0 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Airflow_Temperature_Cel 37 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Current_Pending_Sector 0 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Offline_Uncorrectable 0 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: UDMA_CRC_Error_Count 0 - Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: S.M.A.R.T.: Nov 21 10:23:36 preclear_disk_ZFN408VD_5320: error encountered, exiting ... midazolam-diagnostics-20221121-1056.zip Quote Link to comment
Recommended Posts
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.