Unassigned Devices Preclear - a utility to preclear disks before adding them to the array


dlandon

Recommended Posts

2 hours ago, dlandon said:

The error message is related to notifications and does not affect the disk preclear.

 

Note: You can stop the preclear at any time, update the plugin, and then start a preclear and select resume.  It will pick back up where it left off.

Great, thanks for the re/assuring and clear information and also for the tip about stopping, updating and resuming the pre/clear session!

Edited by BigFam
Link to comment
2 hours ago, dlandon said:

The error message is related to notifications and does not affect the disk preclear.

 

Note: You can stop the preclear at any time, update the plugin, and then start a preclear and select resume.  It will pick back up where it left off.

I did stop the pre-clear session, updated to 2022-03-05 version and resumed the session. The log view still shows integer error but on a different line in the script. Just for information as I'm very happy with your information that it is for notification only and doesn't affect the actual pre-clear of the disk. Thanks for your work, I just made a small donation for your retirement🙂.

 

 

Mar 06 19:43:31 preclear_disk_71G0A46WFQDH_25290: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 1514: [: : integer expression expected

 

These are the release notes from the installed version:

 

unassigned.devices.preclear

Fix: Integer error in prelcear script.

2022.03.04

Add: Remove libevent (it's included in Unraid) and update utempter package.

Fix: Right justify the preclear results on the status page.

2022.02.27

Initial release.

Edited by BigFam
Link to comment

 

Hey  - just getting started with this and pre-clearing a new 18tb disk and have the following showing up repeatedly in the log. Have I set something up wrong?

 

Mar 10 18:03:44 preclear_disk_X1D0A04PFJDH_19500: cp: cannot create regular file '/boot/preclear_reports/X1D0A04PFJDH.resume.tmp': No such file or directory

Mar 10 18:03:44 preclear_disk_X1D0A04PFJDH_19500: mv: cannot stat '/boot/preclear_reports/X1D0A04PFJDH.resume.tmp': No such file or directory


Appreciate any guidance.

 

Thanks

Edited by matt-uk
formating
Link to comment
On 3/10/2022 at 6:27 PM, trurl said:

I'm guessing your flash drive has disconnected.

 

Attach diagnostics to your NEXT post in this thread.

 

That was happening on an old computer to test Unraid. I have now built a new server, all new and different hardware and have the same issue with this error showing up on the pre-clear log.

 


Mar 11 16:09:33 preclear_disk_81X0A0JYFJDH_10788: cp: cannot create regular file '/boot/preclear_reports/81X0A0JYFJDH.resume.tmp': No such file or directory
Mar 11 16:09:33 preclear_disk_81X0A0JYFJDH_10788: mv: cannot stat '/boot/preclear_reports/81X0A0JYFJDH.resume.tmp': No such file or directory

 

The USB has not been removed or disconnected.

 

Any ideas?

 

Thanks for your help.

Matt

unraid-blue-diagnostics-20220312-0010.zip

Edited by matt-uk
added diagnostics
Link to comment

Hello,

  I am trying to preclear 4 new 16TB Seagate EXOS x16 drives. The read speeds averaged 100 MB/s, but the write speed is a horrible 6 MB/s. I have verified that write-caching is enabled for all drives.

 

image.png.4c4eba05c04151d0b71590f9889cbb94.png

 

Ideas?

Edited by aiden
spelling
Link to comment
16 hours ago, dlandon said:

Look at the disk log and see if there are any log entries relating to disk issues.

 

All the logs look like this...

 

Mar 15 07:12:05 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:12:05 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:14:17 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:14:17 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:16:29 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:16:29 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:18:41 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:18:41 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:20:51 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:20:51 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:23:03 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:23:03 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:25:15 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:25:15 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:27:28 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:27:28 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:29:39 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:29:39 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:31:49 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:31:49 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:34:01 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:34:01 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:36:13 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:36:13 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:38:26 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:38:26 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:40:38 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:40:38 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:42:49 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:42:49 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory

Link to comment
2 hours ago, aiden said:

 

All the logs look like this...

 

Mar 15 07:12:05 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:12:05 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:14:17 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:14:17 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:16:29 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:16:29 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:18:41 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:18:41 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:20:51 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:20:51 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:23:03 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:23:03 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:25:15 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:25:15 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:27:28 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:27:28 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:29:39 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:29:39 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:31:49 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:31:49 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:34:01 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:34:01 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:36:13 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:36:13 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:38:26 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:38:26 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:40:38 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:40:38 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:42:49 preclear_disk_ZL2KAPEB_9509: cp: cannot create regular file '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory Mar 15 07:42:49 preclear_disk_ZL2KAPEB_9509: mv: cannot stat '/boot/preclear_reports/ZL2KAPEB.resume.tmp': No such file or directory

Looks to be an issue with your flash drive.

Link to comment
3 hours ago, dlandon said:

Looks to be an issue with your flash drive.

Right now the script saves a resume status file on the flash drive every two minutes.  This is too much writing to the flash drive.  I'm rewriting the preclear script so the resume status is only saved when the script is paused or stopped.  This will prevent the log messages while the preclear script is running.  They may still show up if the flash drive has an issue when the resume status file is written.

Link to comment
Quote

For a disk to be considered a preclear candidate, it must have one of the following attributes:

An Unassigned disk with no partitions.

An Unassigned disk with a preclear signature and a partition with no file system.

 

IMO - it would have been better to allow any unassigned device, and give redundant warnings about preclearing drives with partitions.

 

Now it's a pain to have to jump thru some hoops in order to preclear a new EasyStore external, because they come with partitions on them and such.

 

For those who see this reply later looking to do the same thing, you can clear the partitions and such from the command line.

 

*** DOUBLE CHECK YOUR DEVICE ASSIGNMENT BEFORE DOING THE BELOW: ***

 

I cleared the filesystem (my easystore was on /dev/sda), by doing:

 

wipefs -a /dev/sda1 (replace sda with whatever device assignment your drive is showing)

Once it shows successful,

wipefs -a /dev/sda (to remove the partitions)

 

The UA preclear will then see the device as available for preclearing

 

I'm not responsible if you wipe the FS/partitions from a drive in your array because you didn't double/triple check ;)

Edited by JasonK
Link to comment
17 minutes ago, JasonK said:

 

IMO - it would have been better to allow any unassigned device, and give redundant warnings about preclearing drives with partitions.

 

Now it's a pain to have to jump thru some hoops in order to preclear a new EasyStore external, because they come with partitions on them and such.

 

For those who see this reply later looking to do the same thing, you can clear the partitions and such from the command line.

 

*** DOUBLE CHECK YOUR DEVICE ASSIGNMENT BEFORE DOING THE BELOW: ***

 

I cleared the filesystem (my easystore was on /dev/sda), by doing:

 

wipefs -a /dev/sda1 (replace sda with whatever device assignment your drive is showing)

Once it shows successful,

wipefs -a /dev/sda (to remove the partitions)

 

The UA preclear will then see the device as available for preclearing

 

I'm not responsible if you wipe the FS/partitions from a drive in your array because you didn't double/triple check ;)

Please don't recommend using the cli.  It is too prone to mistakes and is not a good idea.

 

Install UD+ and then you will be given the opportunity to clear the disks.  A red X will appear next to the serial number you can use to clear the disk.

 

Note: Enable destructive mode in UD settings.

Link to comment
20 minutes ago, zaker said:

I am seeing that the install option is not available to me for this plugin, strangely.  I am running 6.9.2, and am adding a 2nd parity (so it is doing a parity sync/data rebuild).  I guess that is why...?

No.  It is available for 6.9.2.

Link to comment
27 minutes ago, zaker said:

I am seeing that the install option is not available to me for this plugin, strangely.  I am running 6.9.2, and am adding a 2nd parity (so it is doing a parity sync/data rebuild).  I guess that is why...?

 

It has a requirement. You need to have "Unassigned Devices" installed. Then the install will show up on the "Unassigned Devices Preclear".

Link to comment
  • 2 weeks later...

Hi there ! :)

 

I just shuked a new WD 12Tb drive and wanted to preclear it with this new plugin

First, there was no way to have the preclear option show, then i read that the disk must not contain any partition, so i deleted it by the cli.
Now the little preclear icon show on unassigned partition but the preclear fail everytime :/
And if i go on the plugin UI, it doesn't list the WD 12Tb at all :/

 

P.S.: i Tried to use the

wipefs -a /dev/sdl

cli (for my case) but fail again :/

 

Do you have any idea please ?

Thank you ! :)

Edited by AinzOolGown
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.