Preclear plugin

February 12, 20206 yr

Author

1 hour ago, sota said:

Huh... I thought it was just me and being weird with having 5 disks running preclear at once.

I had the same situation with a disk or 2 (I don't remember, there were 18 of them total) that got to the end of phase 1, but never did phases 2 and 3, and at least one of them started over with the preclear.

It was 9 hours to process these 4TB disks. Again it wasn't all of them, just a couple. I didn't take very good notes, i'm sorry.

I tried on 8 different drives, and none of them gave me any errors, but somewhat it happens now and then for some people, and I can't debug if I can't reproduce it. It's frustrating.

Quote

February 12, 20206 yr

35 minutes ago, gfjardim said:

I tried on 8 different drives, and none of them gave me any errors, but somewhat it happens now and then for some people, and I can't debug if I can't reproduce it. It's frustrating.

Tell ya what i can do for you on my end: pretty sure there's at least 2 disks of mine that didn't get tagged as precleared. If you want I'll run them through again at some point. Is there any debug settings I can turn on for you, in case it does it again?

Quote

February 12, 20206 yr

Author

4 minutes ago, sota said:

Tell ya what i can do for you on my end: pretty sure there's at least 2 disks of mine that didn't get tagged as precleared. If you want I'll run them through again at some point. Is there any debug settings I can turn on for you, in case it does it again?

Nothing to do, just send me the logs if it happens.

Quote

February 12, 20206 yr

1 minute ago, gfjardim said:

Nothing to do, just send me the logs if it happens.

Ok. Just the preclear logs? or do you want anything else.

Quote

February 13, 20206 yr

Author

3 minutes ago, sota said:

Ok. Just the preclear logs? or do you want anything else.

You can send me the diagnostics file, you can PM me with it to keep you info more private.

Quote

February 13, 20206 yr

I'll keep it in the back of my mind next time I get a chance.

Quote

February 13, 20206 yr

Most of my drives are all the same, HGST Deskstar 3.0 TB drives. It had no problem with the smaller laptop drives, but had this behavior on all of the larger ones, so it seems like it might be related to the size of the drive. I'm rerunning one of them with the updated plugin and I'll see what happens.

Quote

February 13, 20206 yr

Author

5 minutes ago, cisellis said:

Most of my drives are all the same, HGST Deskstar 3.0 TB drives. It had no problem with the smaller laptop drives, but had this behavior on all of the larger ones, so it seems like it might be related to the size of the drive. I'm rerunning one of them with the updated plugin and I'll see what happens.

Thanks, this will help a lot.

Quote

February 13, 20206 yr

2 hours ago, cisellis said:

Most of my drives are all the same, HGST Deskstar 3.0 TB drives. It had no problem with the smaller laptop drives, but had this behavior on all of the larger ones, so it seems like it might be related to the size of the drive. I'm rerunning one of them with the updated plugin and I'll see what happens.

I having having problems with HGST 10TB SAS drives. 2 keep repeating at 99%. Only 1 finished preclear.

Quote

February 13, 20206 yr

Author

57 minutes ago, swamiforlife said:

I having having problems with HGST 10TB SAS drives. 2 keep repeating at 99%. Only 1 finished preclear.

Send me your diagnostics file.

Quote

February 13, 20206 yr

Quote

Preclear Plugin (2020.02.12): unsupported Unraid version (6.8.2). Please upgrade your OS/plugin or request proper support at the forum support thread.

Just updated the preclear plugin to the latest and now I get this warning at the top of unraid. Should I have not updated?

Quote

February 13, 20206 yr

Author

5 minutes ago, remati said:

Just updated the preclear plugin to the latest and now I get this warning at the top of unraid. Should I have not updated?

If you can, remove it and install it again and send me the output of the installation process.

Quote

February 13, 20206 yr

2 minutes ago, gfjardim said:

If you can, remove it and install it again and send me the output of the installation process.

Quote

plugin: installing: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/preclear.disk.plg
plugin: downloading https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/preclear.disk.plg
plugin: downloading: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/preclear.disk.plg ... done
plugin: downloading: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/archive/preclear.disk-2020.02.12.txz ... done
plugin: downloading: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/archive/preclear.disk-2020.02.12.md5 ... done
tmux version 3.0a is greater or equal than the installed version (3.0a), installing...

+==============================================================================
| Skipping package tmux-3.0a-x86_64-1 (already installed)
+==============================================================================

libevent version 2.1.11 is greater or equal than the installed version (2.1.11), installing...

+==============================================================================
| Skipping package libevent-2.1.11-x86_64-1 (already installed)
+==============================================================================

utempter version 1.1.6 is greater or equal than the installed version (1.1.6), installing...

+==============================================================================
| Skipping package utempter-1.1.6-x86_64-3 (already installed)
+==============================================================================

tmux is not working properly

+==============================================================================
| Installing new package /boot/config/plugins/preclear.disk/preclear.disk-2020.02.12.txz
+==============================================================================

Verifying package preclear.disk-2020.02.12.txz.
Installing package preclear.disk-2020.02.12.txz:
PACKAGE DESCRIPTION:
Package preclear.disk-2020.02.12.txz installed.

-----------------------------------------------------------
preclear.disk has been installed.
Copyright 2015-2020, gfjardim
Version: 2020.02.12
-----------------------------------------------------------

plugin: installed

Updating Support Links

preclear.disk --> http://lime-technology.com/forum/index.php?topic=39985.0

No warning this time. Should I restart the server after this install?

Quote

February 13, 20206 yr

Author

7 minutes ago, remati said:

No warning this time. Should I restart the server after this install?

Please open the web terminal and run this command:

tmux new-session -d -x 140 -y 200 -s "install_test_session" &>/dev/null; echo "Open: $?"; sleep 1; tmux kill-session -t "install_test_session"; echo "Close: $?"

Post here the result, please.

Quote

February 13, 20206 yr

1 minute ago, gfjardim said:
Please open the web terminal and run this command:
tmux new-session -d -x 140 -y 200 -s "install_test_session" &>/dev/null; echo "Open: $?"; sleep 1; tmux kill-session -t "install_test_session"; echo "Close: $?"
Post here the result, please.

root@Tower:~# tmux new-session -d -x 140 -y 200 -s "install_test_session" &>/dev/null; echo "Open: $?"; sleep 1; tmux kill-session -t "install_test_session"; echo "Close: $?"
Open: 1
error creating /tmp/tmux-0 (Permission denied)
Close: 1

Quote

February 13, 20206 yr

Author

4 minutes ago, remati said:


root@Tower:~# tmux new-session -d -x 140 -y 200 -s "install_test_session" &>/dev/null; echo "Open: $?"; sleep 1; tmux kill-session -t "install_test_session"; echo "Close: $?"
Open: 1
error creating /tmp/tmux-0 (Permission denied)
Close: 1

It's a permission error. Something changed your /tmp permissions, and that broke the terminal emulator the plugin uses to run scripts in the background.

Send me the result of this command:

ls -la /tmp

Quote

February 13, 20206 yr

1 minute ago, gfjardim said:
It's a permission error. Something changed your /tmp permissions, and that broke the terminal emulator the plugin uses to run scripts in the background.

Send me the result of this command:
ls -la /tmp

root@Tower:~# ls -la /tmp
total 0
drwxrwxrwt 16 nobody users  320 Feb 13 09:45 ./
drwxr-xr-x 20 root   root   440 Feb 12 12:54 ../
drwxrwxrwt  2 nobody users   40 Feb  2 15:28 .ICE-unix/
drwxrwxrwt  2 nobody users   40 Feb  2 15:28 .X11-unix/
drwxrwxrwx  2 root   root    40 Feb 13 09:29 .preclear/
drwxr-xr-x  3 nobody users   60 Feb  2 23:40 Transcode/
drwxrwxrwx  3 nobody users   60 Feb  2 15:29 ca.backup2/
drwxrwxrwx  3 nobody users   60 Feb 13 09:29 community.applications/
drwxrwxrwx  2 nobody users   60 Feb  2 15:29 emhttp/
drwxrwxrwx  2 nobody users  100 Feb 11 09:55 fix.common.problems/
drwxr-xr-x  4 nobody users   80 Feb  2 15:28 notifications/
drwxr-xr-x  2 nobody users 1220 Feb 13 09:31 plugins/
drwxrwx---  2 nobody users  120 Feb 11 09:45 recycle.bin/
drwx------  2 nobody users   60 Feb  2 15:29 tmux-0/
drwxrwx---  4 nobody users  160 Feb  2 15:29 unassigned.devices/
drwxrwxrwx  5 nobody users  140 Feb  2 15:29 user.scripts/

Only other thing that would be using my /tmp folder that I know about is the Plex docker /tmp to /transcode path map. Would this affect it?

Quote

February 13, 20206 yr

Author

4 minutes ago, remati said:

Only other thing that would be using my /tmp folder that I know about is the Plex docker /tmp to /transcode path map. Would this affect it?

Something changed the ownership of your /tmp folder. Try rebooting your server to see if it fixes it.

Quote

February 13, 20206 yr

Author

My /tmp folder, for example is:

drwxrwxrwt 13 root root     400 Feb 13 14:54 ./
drwxr-xr-x 20 root root     440 Feb 13 00:25 ../
drwxrwxrwt  2 root root      40 Feb 12 14:32 .ICE-unix/
drwxrwxrwt  2 root root      40 Feb 12 14:32 .X11-unix/
drwxrwxrwx  8 root root     280 Feb 13 14:54 .preclear/
drwxrwxrwx  3 root root      60 Feb 12 14:32 ca.turbo/
drwxrwxrwx  3 root root      60 Feb 13 06:42 community.applications/
drwxrwxrwx  2 root root      80 Feb 12 14:33 emhttp/
drwxr-xr-x  2 root root     820 Feb 13 14:26 plugins/
drwxrwx---  2 root root     120 Feb 12 14:34 recycle.bin/
drwx------  2 root root      60 Feb 12 15:18 tmux-0/
drwxrwx---  4 root root     160 Feb 12 14:34 unassigned.devices/
drwxrwxrwx  5 root root     140 Feb 12 14:33 user.scripts/

Quote

February 13, 20206 yr

11 minutes ago, gfjardim said:

My /tmp folder, for example is:


drwxrwxrwt 13 root root     400 Feb 13 14:54 ./
drwxr-xr-x 20 root root     440 Feb 13 00:25 ../
drwxrwxrwt  2 root root      40 Feb 12 14:32 .ICE-unix/
drwxrwxrwt  2 root root      40 Feb 12 14:32 .X11-unix/
drwxrwxrwx  8 root root     280 Feb 13 14:54 .preclear/
drwxrwxrwx  3 root root      60 Feb 12 14:32 ca.turbo/
drwxrwxrwx  3 root root      60 Feb 13 06:42 community.applications/
drwxrwxrwx  2 root root      80 Feb 12 14:33 emhttp/
drwxr-xr-x  2 root root     820 Feb 13 14:26 plugins/
drwxrwx---  2 root root     120 Feb 12 14:34 recycle.bin/
drwx------  2 root root      60 Feb 12 15:18 tmux-0/
drwxrwx---  4 root root     160 Feb 12 14:34 unassigned.devices/
drwxrwxrwx  5 root root     140 Feb 12 14:33 user.scripts/

root@Tower:~# ls -la /tmp
total 0
drwxrwxrwt 15 root root 300 Feb 13 10:03 ./
drwxr-xr-x 20 root root 440 Feb 13 09:57 ../
drwxrwxrwt  2 root root  40 Feb 13 09:57 .ICE-unix/
drwxrwxrwt  2 root root  40 Feb 13 09:57 .X11-unix/
drwxrwxrwx  2 root root  40 Feb 13 09:57 .preclear/
drwxrwxrwx  3 root root  60 Feb 13 09:57 ca.backup2/
drwxrwxrwx  3 root root  60 Feb 13 09:57 community.applications/
drwxrwxrwx  2 root root  60 Feb 13 09:57 emhttp/
drwxrwxrwx  2 root root  40 Feb 13 09:57 fix.common.problems/
drwxr-xr-x  4 root root  80 Feb 13 09:57 notifications/
drwxr-xr-x  2 root root  40 Jan 26 09:28 plugins/
drwxrwx---  2 root root 120 Feb 13 09:58 recycle.bin/
drwx------  2 root root  60 Feb 13 09:57 tmux-0/
drwxrwx---  4 root root 160 Feb 13 09:57 unassigned.devices/
drwxrwxrwx  5 root root 140 Feb 13 09:57 user.scripts/
root@Tower:~# tmux new-session -d -x 140 -y 200 -s "install_test_session" &>/dev/null; echo "Open: $?"; sleep 1; tmux kill-session -t "install_test_session"; echo "Close: $?"
Open: 0
Close: 0

Ok after a restart it seems to be fine now. Tried a plex transcode and then ran the tmux new-session command again. No permission change and no error. Re-installed the preclear plugin and no Tmux error this time. So still not sure why the folder permission changed. I suppose I'll keep an eye out for it. Thanks for the help!

Quote

February 14, 20206 yr

Update on current status. I saw two similar issues previously and wasn't sure if they were the same. Some of the drives seemed to restart over and over, which is the log posted above. Others seemed to get "stuck" at 99% and I didn't pull the logs to find out if they were showing the same thing.

Fast forward to now, the 3.0 TB drive I started a new preclear on (erase and preclear, 1 cycle, no pre-read) has been running for about 24 hours. It went through 25%, 50%, and 75% and sent email/UI status correctly. It looks like it hit 99% status and stopped earlier this AM. The UI under unassigned drives still says 99%, but one more email/UI update fired around 5 AM saying "Erasing started on ..." with no percentage, so it almost feels like it started over. I'm not seeing the same results in the logs yet, they just seem to have stopped:

ErrorWarningSystemArrayLogin


DOWNLOAD


Feb 13 07:17:27 preclear_disk_PK1234P8JHP5PX_17218: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --erase-clear --notify 3 --frequency 4 --cycles 1 --skip-preread --no-prompt /dev/sdk
Feb 13 07:17:27 preclear_disk_PK1234P8JHP5PX_17218: Preclear Disk Version: 1.0.9
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: S.M.A.R.T. info type: default
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: S.M.A.R.T. attrs type: default
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Disk size: 3000592982016
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Disk blocks: 732566646
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Blocks (512 byte): 5860533168
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Block size: 4096
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Start sector: 0
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: openssl enc -aes-256-ctr -pass pass:'******' -nosalt < /dev/zero > /tmp/.preclear/sdk/fifo
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: emptying the MBR.
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd if=/tmp/.preclear/sdk/fifo of=/dev/sdk bs=2097152 seek=2097152 count=3000590884864 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes iflag=fullblock
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd pid [20246]
Feb 13 09:22:08 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 10% erased
Feb 13 11:31:10 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 20% erased
Feb 13 13:38:25 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 30% erased
Feb 13 15:47:32 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 40% erased
Feb 13 17:56:33 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 50% erased
Feb 13 20:05:42 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 60% erased
Feb 13 22:14:59 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 70% erased
Feb 14 00:24:15 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 80% erased
Feb 14 02:33:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 90% erased
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429191+0 records out
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2997230764032 bytes (3.0 TB, 2.7 TiB) copied, 76994.5 s, 38.9 MB/s
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429464+0 records in
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429464+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2997803286528 bytes (3.0 TB, 2.7 TiB) copied, 77009 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429723+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429723+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2998346448896 bytes (3.0 TB, 2.7 TiB) copied, 77023.5 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429999+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429999+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2998925262848 bytes (3.0 TB, 2.7 TiB) copied, 77038.1 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430260+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430260+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2999472619520 bytes (3.0 TB, 2.7 TiB) copied, 77052.6 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430518+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430518+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 3000013684736 bytes (3.0 TB, 2.7 TiB) copied, 77067.1 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430791+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430791+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 3000586207232 bytes (3.0 TB, 2.7 TiB) copied, 77081.6 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: dd process hung at 3000588304384, killing....
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Continuing disk write on byte 3000586207232
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: openssl enc -aes-256-ctr -pass pass:'******' -nosalt < /dev/zero > /tmp/.preclear/sdk/fifo
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd if=/tmp/.preclear/sdk/fifo of=/dev/sdk bs=2097152 seek=3000586207232 count=6774784 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes iflag=fullblock
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd pid [20853]
Feb 14 04:47:11 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd - wrote 3000592982016 of 3000592982016.

Quote

February 14, 20206 yr

Author

13 minutes ago, cisellis said:

Update on current status. I saw two similar issues previously and wasn't sure if they were the same. Some of the drives seemed to restart over and over, which is the log posted above. Others seemed to get "stuck" at 99% and I didn't pull the logs to find out if they were showing the same thing.

Fast forward to now, the 3.0 TB drive I started a new preclear on (erase and preclear, 1 cycle, no pre-read) has been running for about 24 hours. It went through 25%, 50%, and 75% and sent email/UI status correctly. It looks like it hit 99% status and stopped earlier this AM. The UI under unassigned drives still says 99%, but one more email/UI update fired around 5 AM saying "Erasing started on ..." with no percentage, so it almost feels like it started over. I'm not seeing the same results in the logs yet, they just seem to have stopped:


ErrorWarningSystemArrayLogin


DOWNLOAD


Feb 13 07:17:27 preclear_disk_PK1234P8JHP5PX_17218: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --erase-clear --notify 3 --frequency 4 --cycles 1 --skip-preread --no-prompt /dev/sdk
Feb 13 07:17:27 preclear_disk_PK1234P8JHP5PX_17218: Preclear Disk Version: 1.0.9
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: S.M.A.R.T. info type: default
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: S.M.A.R.T. attrs type: default
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Disk size: 3000592982016
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Disk blocks: 732566646
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Blocks (512 byte): 5860533168
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Block size: 4096
Feb 13 07:17:29 preclear_disk_PK1234P8JHP5PX_17218: Start sector: 0
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: openssl enc -aes-256-ctr -pass pass:'******' -nosalt < /dev/zero > /tmp/.preclear/sdk/fifo
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: emptying the MBR.
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd if=/tmp/.preclear/sdk/fifo of=/dev/sdk bs=2097152 seek=2097152 count=3000590884864 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes iflag=fullblock
Feb 13 07:17:35 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd pid [20246]
Feb 13 09:22:08 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 10% erased
Feb 13 11:31:10 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 20% erased
Feb 13 13:38:25 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 30% erased
Feb 13 15:47:32 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 40% erased
Feb 13 17:56:33 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 50% erased
Feb 13 20:05:42 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 60% erased
Feb 13 22:14:59 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 70% erased
Feb 14 00:24:15 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 80% erased
Feb 14 02:33:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: progress - 90% erased
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429191+0 records out
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2997230764032 bytes (3.0 TB, 2.7 TiB) copied, 76994.5 s, 38.9 MB/s
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429464+0 records in
Feb 14 04:45:20 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429464+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2997803286528 bytes (3.0 TB, 2.7 TiB) copied, 77009 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429723+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429723+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2998346448896 bytes (3.0 TB, 2.7 TiB) copied, 77023.5 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429999+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1429999+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2998925262848 bytes (3.0 TB, 2.7 TiB) copied, 77038.1 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430260+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430260+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 2999472619520 bytes (3.0 TB, 2.7 TiB) copied, 77052.6 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430518+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430518+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 3000013684736 bytes (3.0 TB, 2.7 TiB) copied, 77067.1 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430791+0 records in
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 1430791+0 records out
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd output: 3000586207232 bytes (3.0 TB, 2.7 TiB) copied, 77081.6 s, 38.9 MB/s
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: dd process hung at 3000588304384, killing....
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Continuing disk write on byte 3000586207232
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: openssl enc -aes-256-ctr -pass pass:'******' -nosalt < /dev/zero > /tmp/.preclear/sdk/fifo
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd if=/tmp/.preclear/sdk/fifo of=/dev/sdk bs=2097152 seek=3000586207232 count=6774784 conv=notrunc iflag=count_bytes,nocache,fullblock oflag=seek_bytes iflag=fullblock
Feb 14 04:45:21 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd pid [20853]
Feb 14 04:47:11 preclear_disk_PK1234P8JHP5PX_17218: Erasing: dd - wrote 3000592982016 of 3000592982016.

I've located the source of this bug, will release a fix soon.

Quote

February 14, 20206 yr

Awesome! I can rerun it when you push an update.

Quote

February 15, 20206 yr

9 hours ago, cisellis said:

Awesome! I can rerun it when you push an update.

new version was pushed out

#2020.02.14

- Fix: Write/Erase ops hang if display_pid is reused by the system

Quote

February 16, 20206 yr

I was having the same issue on a HGST 3TB SAS drive, getting stuck at 90% and restarting.

It has finished preclear successfully after the update!

Thanks!

Quote

1

Preclear plugin

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

Squid

CHBMB

sureguy

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

Squid

CHBMB

sureguy

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)