hi, today i tried mounting an HDD via temrinal with:

/usr/local/sbin/rc.unassigned mount /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K0VZ4TVK
sleep 30s

but the drive wan't moutable:

Sep  4 06:43:13 Unraid-1 emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/Backup-to-UD/script 
Sep  4 06:43:14 Unraid-1 unassigned.devices: Mounting partition 'sdd1' at mountpoint '/mnt/disks/WD-WCC7K0VZ4TVK'...
Sep  4 06:43:14 Unraid-1 unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdd1' '/mnt/disks/WD-WCC7K0VZ4TVK'
Sep  4 06:43:21 Unraid-1 kernel: XFS (sdd1): Mounting V5 Filesystem
Sep  4 06:43:21 Unraid-1 kernel: XFS (sdd1): log mount failed
Sep  4 06:43:21 Unraid-1 emhttpd: read SMART /dev/sdd

 

late i tried mounting with the GUI Button and that worked well. i unmounted the drive and tried again the terminal and that also worked now.

 

i report this just for the case. diag is attached.

unraid-1-diagnostics-20230904-0719.zip

Hello,

 

Last week I put together my first build. i was advised to pre-clear all my disks. And so I started the pre-clear on all my 5 disks.

So far one has failed.

 

• What do I do with the one disk? Is it bad for sure? Or should I attempt another pre-clear?

 

 

Edited September 11, 20232 yr by Mave

17 hours ago, Mave said:

Hello,

 

Last week I put together my first build. i was advised to pre-clear all my disks. And so I started the pre-clear on all my 5 disks.

So far one has failed.

 

• What do I do with the one disk? Is it bad for sure? Or should I attempt another pre-clear?

 

 

My biggest question is: Is there such a thing as false positives or not?

I want to take no risks.

If there is such a thing as a false positive, and a second pre-clear will confirm or deny, then I'll run it again.

If there is no such thing as a false positive, I'll toss the disk now.

17 hours ago, Mave said:

Is it bad for sure?

Disk shows a pending sector, which is a bad sign, you can run an extended SMART test to confirm if it's failed.

20 hours ago, JorgeB said:

Disk shows a pending sector, which is a bad sign, you can run an extended SMART test to confirm if it's failed.

Thank you for answering.
A second pre-clear finished without problems...

The pending sector count went back to 0.

Would you use the drive now?

 

Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: ATTRIBUTE             INITIAL NOW   STATUS 
Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: Reallocated_Sector_Ct   0       0     - 
Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: Power_On_Hours          23038   23063 Up 25 
Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: Temperature_Celsius     38      39    Up 1 
Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: Reallocated_Event_Count 0       0     - 
Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: Current_Pending_Sector  1       0     Down 1 
Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: Offline_Uncorrectable   0       0     - 
Sep 12 06:57:43 preclear_disk_WD-WX61DC8HFS00_22733: S.M.A.R.T.: UDMA_CRC_Error_Count    0       0     - 

 

Thanks in advance!

Also: another disk keeps failing the zeroing process. I guess this is also quite alarming?

 

Sep 12 02:12:52 preclear_disk_ZCT0FKZ4_6301: Zeroing: dd output: 3815383+0 records in 
Sep 12 02:12:52 preclear_disk_ZCT0FKZ4_6301: Zeroing: dd output: 3815383+0 records out 
Sep 12 02:12:52 preclear_disk_ZCT0FKZ4_6301: Zeroing: dd output: 8001438089216 bytes (8.0 TB, 7.3 TiB) copied, 166339 s, 48.1 MB/s 
Sep 12 02:12:52 preclear_disk_ZCT0FKZ4_6301: dd process hung at 8001440186368, killing ... 
Sep 12 02:12:52 preclear_disk_ZCT0FKZ4_6301: Zeroing: zeroing the disk started 2 of 5 retries... 
Sep 12 02:12:52 preclear_disk_ZCT0FKZ4_6301: Continuing disk write on byte 8001438089216 
Sep 12 02:20:52 preclear_disk_ZCT0FKZ4_6301: Zeroing: dd output:  
Sep 12 02:20:52 preclear_disk_ZCT0FKZ4_6301: dd process hung at 0, killing ... 
Sep 12 02:20:52 preclear_disk_ZCT0FKZ4_6301: Zeroing: zeroing the disk started 3 of 5 retries... 
Sep 12 02:20:52 preclear_disk_ZCT0FKZ4_6301: Zeroing: emptying the MBR. 

 

Edited September 12, 20232 yr by Mave

 

so pre clearing a new disk and this happened:

 

Sep 13 17:58:12 preclear_disk_22C0T8RD0A001FE2H_9502: Zeroing: zeroing the disk started 1 of 5 retries...
Sep 13 17:58:12 preclear_disk_22C0T8RD0A001FE2H_9502: Zeroing: emptying the MBR.
Sep 13 19:29:11 preclear_disk_22C0T8RD0A001FE2H_9502: 
Sep 13 19:29:11 preclear_disk_22C0T8RD0A001FE2H_9502: malloc: jobs.c:1435: assertion botched
Sep 13 19:29:11 preclear_disk_22C0T8RD0A001FE2H_9502: free: underflow detected; magic8 corrupted
Sep 13 19:29:12 preclear_disk_22C0T8RD0A001FE2H_9502: Aborting.../usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 534: 1694626152 -  : syntax error: operand expected (error token is "-  ")
Sep 13 19:29:12 preclear_disk_22C0T8RD0A001FE2H_9502: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 535: -1694620692 +  : syntax error: operand expected (error token is "+  ")

 

Is the drive bad or did the preclear plugin just mess up?

 

2 hours ago, TrojanHorsePower said:

 

so pre clearing a new disk and this happened:

 

Sep 13 17:58:12 preclear_disk_22C0T8RD0A001FE2H_9502: Zeroing: zeroing the disk started 1 of 5 retries...
Sep 13 17:58:12 preclear_disk_22C0T8RD0A001FE2H_9502: Zeroing: emptying the MBR.
Sep 13 19:29:11 preclear_disk_22C0T8RD0A001FE2H_9502: 
Sep 13 19:29:11 preclear_disk_22C0T8RD0A001FE2H_9502: malloc: jobs.c:1435: assertion botched
Sep 13 19:29:11 preclear_disk_22C0T8RD0A001FE2H_9502: free: underflow detected; magic8 corrupted
Sep 13 19:29:12 preclear_disk_22C0T8RD0A001FE2H_9502: Aborting.../usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 534: 1694626152 -  : syntax error: operand expected (error token is "-  ")
Sep 13 19:29:12 preclear_disk_22C0T8RD0A001FE2H_9502: /usr/local/emhttp/plugins/unassigned.devices.preclear/scripts/preclear_disk.sh: line 535: -1694620692 +  : syntax error: operand expected (error token is "+  ")

 

Is the drive bad or did the preclear plugin just mess up?

 

That looks like a script issue.  I'll have to spend some time on it.  Can you post your diagnostics.  I want to look and see if I can figure out where the 'magic8 corrupted' comes from.

On 9/13/2023 at 10:56 PM, dlandon said:

That looks like a script issue.  I'll have to spend some time on it.  Can you post your diagnostics.  I want to look and see if I can figure out where the 'magic8 corrupted' comes from.

My apologies, did not get a notification about your reply. My diagnostics will probably be useless now, since the script eventually crashed and had to reboot the OS. Have not had a chance to start the pre-clear again and would probably take around more than 24 hours to reach the step I was at unless I skip pre-read.

I have asked around and someone thought it is a memory issue.

hi. been preclearing for the pass 2 days and so far everything seems smooth. just waiting it to finish

 

1 question, i was able to see detail stats before by pressing the eye icon beside the timer. its gone now. is becayse its in that stage and u cant see the stats? or there's some bug

 

 

5 hours ago, i1mran92 said:

1 question, i was able to see detail stats before by pressing the eye icon beside the timer. its gone now. is becayse its in that stage and u cant see the stats? or there's some bug

The 'eye' status icon should always display.  It's probably a Browser issue.  Try clearing the cache or try another Browser.

 

You can go to the UD preclear page at Tools->Preclear Disk or the icon at the bottom of the Unraid webpage to see the status.

2 hours ago, dlandon said:

The 'eye' status icon should always display.  It's probably a Browser issue.  Try clearing the cache or try another Browser.

 

You can go to the UD preclear page at Tools->Preclear Disk or the icon at the bottom of the Unraid webpage to see the status.

 

hmm its still doesnt show 'eye' icon. clear cached. tried multiple browser, edge and chrome. even in the preclear settings page

 

 

2 hours ago, i1mran92 said:

hmm its still doesnt show 'eye' icon. clear cached. tried multiple browser, edge and chrome. even in the preclear settings page

What version of Unraid?  It's also possible that a plugin is interferring with UD Preclear.

17 hours ago, dlandon said:

What version of Unraid?  It's also possible that a plugin is interferring with UD Preclear.

 

Unraid Version 6.12.4 2023-08-31

 

how do i determine if a plugin is interfering with it?

28 minutes ago, i1mran92 said:

 

Unraid Version 6.12.4 2023-08-31

 

how do i determine if a plugin is interfering with it?

It will probably clear up with a reboot.  To find something interferring with the preclear icons, you'd have to boot in safe mode and add plugins back one at a time to see if one is causing a problem.

2 hours ago, dlandon said:

It will probably clear up with a reboot.  To find something interferring with the preclear icons, you'd have to boot in safe mode and add plugins back one at a time to see if one is causing a problem.

 

i let everything finish then i rebooted.

 

i then verify signature via the preclear plugin and the eye icon came back.

both the 18th hdd successfully precleared.

 

not sure why. but seems ok now.

 

thank you!

41 minutes ago, i1mran92 said:

not sure why. but seems ok now.

I've seen these kinds of issues with the Unraid GUI that are cleared up by a reboot.  Must be Gremlins hiding out somewhere.

Guys, I'm just supremely confused here.

 

I just finished using UD Preclear and everything finished with no errors.

 

So I stopped the array, added the drive, and started the array.

I get the "Unmountable: Unsupoorted partition layout" message next to the drive and my storage has no increased.

 

The instructions say no need to format, and several posts here give conflicting information.

 

If I click the red X next to the drive, it tells me it'll remove the pre-clear signature and Unraid will start the lengthy preclear all over again.

 

I've tried rebooting as well.

 

I thought it was as simple as Preclear > Add to Array but seems I'm missing a step.

 

What am I missing guys?

 

Thank you!

 

Edited October 5, 20232 yr by DevanteWeary

2 minutes ago, DevanteWeary said:

I thought it was as simple as Preclear > Add to Array but seems I'm missing a step.

 

What am I missing guys?

That you need to format the drive after adding to array, you should have the format button available at the bottom with the disk you added in the list on the left.

15 minutes ago, Kilrah said:

That you need to format the drive after adding to array, you should have the format button available at the bottom with the disk you added in the list on the left.

 

Hmmm I don't have any buttons at the bottom of Unraid > Main > Array Devices

 

I do have a button under Unraid > Main > Array Operation called Format that says "will create a file system in all Unmountable disks" and when I click it, gives me the following warning:

 

Format Unmountable disks

Create an empty file system on the disks shown as Unmountable discarding all data currently on the disks and update parity to reflect this. This is typically done when a new disk is added to the array to get it ready for files to be written to it.



**WARNING**

A format is NEVER part of a data recovery or disk rebuild process and if done in such circumstances will normally lead to loss of all data on the disks being formatted.

 

Think I should go ahead and do that one?

 

Sorry, just trying to avoid another 4 day clearing.

Edited October 5, 20232 yr by DevanteWeary

11 minutes ago, DevanteWeary said:

I do have a button under Unraid > Main > Array Operation called Format

That is the one, and yes as long as you've checked on the left of that button that the only unmountable drive listed is the one you just added to the array you go ahead.

Edited October 5, 20232 yr by Kilrah

22 minutes ago, Kilrah said:

That is the one, and yes as long as you've checked on the left of that button that the only unmountable drive listed is the one you just added to the array you go ahead.

Worked like a charm. You're the best. 😆

 

Just throwing the steps here for anyone looking for a definitive order:

 

• Use UD Preclear on drive. (could take days)
• Stop Array
• Increase drive number by one.
• Select new drive to fill new slot.
• Start Array.
• Format drive through Array Operations > Format
• Done!

I have never been able to get Preclear to work.  It fails every time regardless of the disc.  I have never bothered to seek help and finally decided to as I am in the process of replacing my parity drives.  Would like to preclear them first.

 

This is the second drive I tried today.  Error as follows.  Any help would be much appreciated.  Unraid Version: 6.12.4

many thanks in advance.

 

Oct 26 16:26:57 preclear_disk_70015084_17575: Preclear Disk Version: 1.0.29
Oct 26 16:26:57 preclear_disk_70015084_17575: Disk size: 8001563222016
Oct 26 16:26:57 preclear_disk_70015084_17575: Disk blocks: 1953506646
Oct 26 16:26:57 preclear_disk_70015084_17575: Blocks (512 bytes): 15628053168
Oct 26 16:26:57 preclear_disk_70015084_17575: Block size: 4096
Oct 26 16:26:57 preclear_disk_70015084_17575: Start sector: 0
Oct 26 16:27:00 preclear_disk_70015084_17575: Pre-read: pre-read verification started 1 of 5 retries...
Oct 26 16:27:04 preclear_disk_70015084_17575: size:         0, available:     0, free: 0%
Oct 26 16:27:04 preclear_disk_70015084_17575: Filesystem     1K-blocks    Used Available Use% Mounted on
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs              32768     408     32360   2% /run
Oct 26 16:27:04 preclear_disk_70015084_17575: /dev/sda1       30028448 1238544  28789904   5% /boot
Oct 26 16:27:04 preclear_disk_70015084_17575: devtmpfs            8192       0      8192   0% /dev
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs           16392372       0  16392372   0% /dev/shm
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs             131072    9764    121308   8% /var/log
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/disks
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/remotes
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/addons
Oct 26 16:27:04 preclear_disk_70015084_17575: tmpfs               1024       0      1024   0% /mnt/rootshare
Oct 26 16:27:04 preclear_disk_70015084_17575: Low memory detected, aborting ...
Oct 26 16:27:04 preclear_disk_70015084_17575: Pre-read: pre-read verification failed!
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Error:
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.:
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: ATTRIBUTE              	INITIAL	NOW	STATUS
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Reallocated_Sector_Ct  	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Power_On_Hours         	1      	1  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Reported_Uncorrect     	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Airflow_Temperature_Cel	38     	38 	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Current_Pending_Sector 	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: Offline_Uncorrectable  	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: UDMA_CRC_Error_Count   	0      	0  	-
Oct 26 16:27:07 preclear_disk_70015084_17575: S.M.A.R.T.: 
Oct 26 16:27:07 preclear_disk_70015084_17575: error encountered, exiting ...

 

 

32 minutes ago, jimeez said:

I have never been able to get Preclear to work.  It fails every time regardless of the disc.  I have never bothered to seek help and finally decided to as I am in the process of replacing my parity drives.  Would like to preclear them first.

Post diagnostics.

33 minutes ago, dlandon said:

Post diagnostics.

Apologies.  Forgot to do that. 

diagnostics-20231026-1730.zip

1 hour ago, jimeez said:

Apologies.  Forgot to do that. 

diagnostics-20231026-1730.zip 155.67 kB · 1 download

Start by going to the cache_dirs settings and only inculding shares that need to be cached.  Normally any share on an SSD pool device doesn't need to be cached by cache_dirs.  Shares like 'isos' don't need to be cached.  Cache_dirs by default will cache everything it finds.  It can be a real memory hog.