27 minutes ago, dlandon said:

I am going to look into a configurable option in UD that will default to not using the preclear background task that is causing this problem.  It could be turned on to help with preclear issues, but would then potentially cause this problem.  I will see if this is feasible and makes sense.

I think that would be great. Really like using the preclear plugin instead of a screen session since it gives me notifications.

1 hour ago, wgstarks said:

I think that would be great. Really like using the preclear plugin instead of a screen session since it gives me notifications.

Update UD and see if the problem is solved.

3 hours ago, dlandon said:

Update UD and see if the problem is solved.

I won't have a drive to preclear for a few more days, but updated UD and tested with the previous drive that was giving issues. It IS NOT disappearing like it was so looks like that part of the problem is corrected.

Thanks

On 8/30/2017 at 10:01 AM, dabl said:

My latest preclear of a Western Digital 8 TB WDC_WD80EFAX got stuck at post read 94%

 

I'm using Preclear Disks 2017.07.10, Unassigned Devices 2017.07.09c and unRAID 6.3.5

 

Attached are the logs. 

 

I had a similar failure with a WD 8TB Parity WDC_WD80EFZX using an earlier version of the plugin.

 

I noted back in July that based on several similar posts the WDC_WD80 seemed problematic with the preclear plugin.  I don't know if there have been any posts noting success with the plugin and these drives since.

 

My last successfull preclear was on a Seagate Archive 8 TB ST8000AS0002 using Preclear Disks 2017.07.05c, Unassigned Devices 2017.07.04a and unRAID 6.3.3

 

Also please note the below previous recent posts reporting similar behavior with HGST 4TB and 8TB as well as a Hitachi HDS5C4040ALE630 4TB.

 

13-AUG-2017 Vibe HGST 4TB

13-AUG-2017 JarDo Hitachi HDS5C4040ALE630 4TB

16-AUG-2017 bbcorn88 8TB HGST

 

raid_01-diagnostics-20170830-0912.zip

RAID_01-preclear.disk-20170830-0859.zip

 

I also just had an 8TB WD Red get stuck on cycle 2's post read at 95%, pegging a CPU core at 100%. I used gfjardim-0.8.9-beta.

 

Is there no known fix for this? A little frustrating to see all these posts go back months but no definitive script updates or answers.

 

Thanks everyone for the help.

I'm sorry, I'm new to this whole scene.  Just added a used 2TB drive to my array for more storage and this is the first drive I've used pre-clear on.  Would any of you mind taking a look at the logs to confirm I'm good to go?  Everything came back as passed, but wanted to be sure.  If you need anything else, let me know.

 

Thank you in advance.

preclear_report_W340A8TT_2017.09.07_08.50.19.txt

ST2000DM001-1CH164_W340A8TT-20170907-1449.txt

I am also having issues with this plugin using the included script on an 8tb samsung ST8000DM004 with the CPU pegged at 100% and stuck at 49% pre-read

Hi all.  Just skimming through this huge thread, but am I to understand that the Preclear app located on the unRaid app market is not functioning correctly in unRaid 6.3?  I have just built a new server and am using brand new drives, but cannot get the Preclear app to recognize them, it simply states that there are no unassigned devices.  I tried to assign, the unassigned to see if that would fix it, but still "no unassigned devices".  When I assign them unRaid asks to format the drives, so I know they are being seen by the server.   Any suggestions?

Not sure what the app market is, but I would recommend you install Community Applications and then search it for the Unassigned Devices plugin. I believe this is what the Preclear plugin is looking for.

1 hour ago, wgstarks said:

Not sure what the app market is, but I would recommend you install Community Applications and then search it for the Unassigned Devices plugin. I believe this is what the Preclear plugin is looking for.

Sorry, I meant the Community Applications (not Apps Market).  I believe that I have installed this as well.  I did just notice that I have a Preclear icon next to the Unassigned devices that appears on the MAIN tab, but when I clicked it I did not see any progress or other indication that it is doing anything.  Also even though I am seeing the drives on the Unassigned Devices section of the MAIN tab, I still do not see any drives when I launch the Preclear App.

Have you ever assigned any disks to the array? I think there was an issue where it would check to make sure you weren't trying to clear an array disk, but if there were never any assigned the check failed.

On 08/09/2017 at 9:11 AM, falloutboy12 said:

I am also having issues with this plugin using the included script on an 8tb samsung ST8000DM004 with the CPU pegged at 100% and stuck at 49% pre-read

 

I couldn't find the root of this problem, but the next update will support resuming the preclear instance if you stop it or reboot your server.

Uninstalling and reinstalling the Preclear app fixed my issue (not sure what happened before).  Thanks for the suggestions.

On 04/09/2017 at 0:05 AM, capone said:

I have two "dismissed" reports that just won't send... does anyone else have the same issue? I've been trying to send them over the last few days/week... and they just won't send... all the other reports I've generated from different precleared disks have been sent.

 

I've attached screenshots of the syslog (my IP removed)...and the "sending statistics" screen...

 

Nothing else happens...it just sits there... and never sends...

 

 

 

 

I'll remove TOR from Statistics. The hassle is greater than the benefits.

On 30/08/2017 at 11:01 AM, dabl said:

My latest preclear of a Western Digital 8 TB WDC_WD80EFAX got stuck at post read 94%

 

I'm using Preclear Disks 2017.07.10, Unassigned Devices 2017.07.09c and unRAID 6.3.5

 

Attached are the logs. 

 

I had a similar failure with a WD 8TB Parity WDC_WD80EFZX using an earlier version of the plugin.

 

I noted back in July that based on several similar posts the WDC_WD80 seemed problematic with the preclear plugin.  I don't know if there have been any posts noting success with the plugin and these drives since.

 

My last successfull preclear was on a Seagate Archive 8 TB ST8000AS0002 using Preclear Disks 2017.07.05c, Unassigned Devices 2017.07.04a and unRAID 6.3.3

 

Also please note the below previous recent posts reporting similar behavior with HGST 4TB and 8TB as well as a Hitachi HDS5C4040ALE630 4TB.

 

13-AUG-2017 Vibe HGST 4TB

13-AUG-2017 JarDo Hitachi HDS5C4040ALE630 4TB

16-AUG-2017 bbcorn88 8TB HGST

 

raid_01-diagnostics-20170830-0912.zip

RAID_01-preclear.disk-20170830-0859.zip

 

 

Looking at the submitted reports, I counted 162 reports of successful preclears on these drives. It's an intermittent bug that the next version will hopefully fix.

Update:

###2017.09.16
- Fix: detect dd hang and restart it
- Add: resume stopped preclear session

Enviado de meu SM-G955F usando Tapatalk

Thanks to your reports, I just found a bug in the recently introduced 0.9.2-beta version of the script. It prevented the recent "resume" feature from working.

An update is available.

Am I the only one getting:

 

Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339

 

If I install the Preclear plugin -- this happens and fills up my logs.

 

When I remove it, it goes away.   If it matters, I've included that "rc.diskinfo" file.  (I have no clue what I am looking at)

 

I am running: preclear plugin  -  2017.09.22a  (just re-installed it)

rc.diskinfo.txt

12 hours ago, chuck23322 said:

Am I the only one getting:

 

Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339
Sep 22 18:27:11 unraid rc.diskinfo[32461]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 339

 

If I install the Preclear plugin -- this happens and fills up my logs.

 

When I remove it, it goes away.   If it matters, I've included that "rc.diskinfo" file.  (I have no clue what I am looking at)

 

I am running: preclear plugin  -  2017.09.22a  (just re-installed it)

rc.diskinfo.txt

 

Hi, just updated. Please let me know if it got fixed.

I just updated the plugin to the 9.23 version and I still get the same error

Sep 23 08:26:51 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update preclear.disk.plg
Sep 23 08:26:51 Tower root: plugin: creating: /boot/config/plugins/preclear.disk/preclear.disk-2017.09.23.txz - downloading from URL https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/archive/preclear.disk-2017.09.23.txz
Sep 23 08:26:51 Tower root: plugin: creating: /boot/config/plugins/preclear.disk/preclear.disk-2017.09.23.md5 - downloading from URL https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/archive/preclear.disk-2017.09.23.md5
Sep 23 08:26:51 Tower root: plugin: skipping: /boot/readvz already exists
Sep 23 08:26:51 Tower root: plugin: setting: /boot/readvz - mode to 755
Sep 23 08:26:51 Tower root: plugin: running: anonymous
Sep 23 08:26:55 Tower root: plugin: running: anonymous
Sep 23 08:26:55 Tower rc.diskinfo[14054]: killing daemon with PID [10972]
Sep 23 08:26:56 Tower rc.diskinfo[14070]: process started. To terminate it, type: rc.diskinfo --quit
Sep 23 08:26:56 Tower rc.diskinfo[14073]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 341
Sep 23 08:26:56 Tower rc.diskinfo[14073]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 341
Sep 23 08:26:56 Tower rc.diskinfo[14073]: PHP Warning: strpos(): Empty needle in /etc/rc.d/rc.diskinfo on line 341

If I uninstall the plugin the entries go away

 

14 hours ago, gfjardim said:

 

Hi, just updated. Please let me know if it got fixed.

 

I've installed the update -- and the errors persist -- goes away when I uninstall the Preclear plugin.

15 hours ago, chuck23322 said:

 

I've installed the update -- and the errors persist -- goes away when I uninstall the Preclear plugin.

 

Which version of unRAID are you running?

 

Please post the output of this command:

lsblk --version && lsblk -nbP -o name,type,serial

 

34 minutes ago, gfjardim said:

 

Which version of unRAID are you running?

 

Please post the output of this command:

lsblk --version && lsblk -nbP -o name,type,serial

 

 

Hi, I'm at Unraid 6.3.5

 

 

root@unraid:~# lsblk --version && lsblk -nbP -o name,type,serial
lsblk from util-linux 2.28.2
NAME="md11" TYPE="md" SERIAL=""
NAME="sdf" TYPE="disk" SERIAL="K4K7UXVB"
NAME="sdf1" TYPE="part" SERIAL=""
NAME="md8" TYPE="md" SERIAL=""
NAME="sdo" TYPE="disk" SERIAL="5XW1BMCH"
NAME="sdo1" TYPE="part" SERIAL=""
NAME="sdd" TYPE="disk" SERIAL="WD-WMAZA5166243"
NAME="sdd1" TYPE="part" SERIAL=""
NAME="md6" TYPE="md" SERIAL=""
NAME="sdm" TYPE="disk" SERIAL="K4KA796B"
NAME="sdm1" TYPE="part" SERIAL=""
NAME="sdb" TYPE="disk" SERIAL="5YD3YW18"
NAME="sdb1" TYPE="part" SERIAL=""
NAME="md4" TYPE="md" SERIAL=""
NAME="sdk" TYPE="disk" SERIAL="Z1F0MZ6Y"
NAME="sdk1" TYPE="part" SERIAL=""
NAME="md2" TYPE="md" SERIAL=""
NAME="sdi" TYPE="disk" SERIAL="Z1F1ZZRJ"
NAME="sdi1" TYPE="part" SERIAL=""
NAME="sdg" TYPE="disk" SERIAL="5YD5RWGW"
NAME="sdg1" TYPE="part" SERIAL=""
NAME="md9" TYPE="md" SERIAL=""
NAME="fd0" TYPE="disk" SERIAL=""
NAME="md10" TYPE="md" SERIAL=""
NAME="sde" TYPE="disk" SERIAL="WD-WMAWZ0247359"
NAME="sde1" TYPE="part" SERIAL=""
NAME="md7" TYPE="md" SERIAL=""
NAME="loop0" TYPE="loop" SERIAL=""
NAME="sdn" TYPE="disk" SERIAL="S1F0KCZF"
NAME="sdn1" TYPE="part" SERIAL=""
NAME="sdc" TYPE="disk" SERIAL="4C531001540804103384"
NAME="sdc1" TYPE="part" SERIAL=""
NAME="md5" TYPE="md" SERIAL=""
NAME="sdl" TYPE="disk" SERIAL="Z1W1AGJX"
NAME="sdl1" TYPE="part" SERIAL=""
NAME="sda" TYPE="disk" SERIAL="ML0221F30431JD"
NAME="sda1" TYPE="part" SERIAL=""
NAME="md3" TYPE="md" SERIAL=""
NAME="sdj" TYPE="disk" SERIAL="S1F01NX2"
NAME="sdj1" TYPE="part" SERIAL=""
NAME="md1" TYPE="md" SERIAL=""
NAME="sdh" TYPE="disk" SERIAL="Z1F0L360"
NAME="sdh1" TYPE="part" SERIAL=""

 

@chuck23322, do you have a floppy disk installed on your server?

4 minutes ago, gfjardim said:

@chuck23322, do you have a floppy disk installed on your server?

 

No, I don't.   But was looking at syslog, and apparently Unraid thinks I do

 

root@unraid:~# cat /var/log/syslog | grep fd0
Sep 24 09:11:03 unraid kernel: pci 0000:00:11.0: reg 0x18: [io  0xfd00-0xfd07]
Sep 24 09:11:03 unraid kernel: Floppy drive(s): fd0 is 1.44M
Sep 24 09:11:29 unraid kernel: blk_update_request: I/O error, dev fd0, sector 0
Sep 24 09:13:41 unraid kernel: blk_update_request: I/O error, dev fd0, sector 0
Sep 24 09:15:02 unraid kernel: blk_update_request: I/O error, dev fd0, sector 0
root@unraid:~# 

 

Digging further -- checking my motherboard specs - https://www.gigabyte.com/Motherboard/GA-MA770T-UD3-rev-14#sp

 

 

South Bridge: 

1. 1 x IDE connector supporting ATA-133/100/66/33 and up to 2 IDE devices
2. 6 x SATA 3Gb/s connectors supporting up to 6 SATA 3Gb/s devices
3. Support for SATA RAID 0, RAID 1 and RAID 0+1

iTE IT8720 chip:

1. 1 x floppy disk drive connector supporting up to 1 floppy disk drive

@chuck23322, just committed an update. Please let me know if your problem is solved.