dlandon

Don't know.

I tried that in the binhex docker container and it failed. It's not working. It should have worked. Unraid will create the file system. You should be able to use clear disk anytime to remove the partitions. After you preclear a disk it is ready to add to the array. You don't need to format the disk first. You can add it to the array whether or not you use the clear disk. You have something out of the ordinary happening in your system. The -z didn't work, and then you were able to clear the disk. Doesn't make sense why it would work then.

You can add it directly to the array after a preclear. The preclear signature tells Unraid it is cleared and Unraid will format it for you.

Go back to the binhex preclear and do: preclear_binhex.sh -z /dev/sdf That should remove the preclear signature and the partition.

Which script did you use to preclear the disk?

The clear all partitions didn't work. At a command line do this command and let me know if there are any errors: /sbin/wipefs -a /dev/sdf Please confirm that /dev/sdf is the coreect disk to remove all partitions.

UD uses parted to remove a partition, but it fails on partitions that don't have a file system. I've removed the 'X' for a partition if it does not contain a file system. You then have to use the clear all paritions to remove the partition. This is fixed in the next release. I tested the clear all partitions and it worked for me, so there is a situation specific to your system. After you perfrm the steps I've asked for above, I can see where there might be a problem in your situation.

Do the following: Go to the UD settings and set the 'Debug Log Level' to 'Udev and Hotplug'. Click on the 'Clear Disk' icon. Post diagnostics. Go back to UD settings and set the 'Debug Log Level' back to none.

Post your diagnostics.

Your unassigned devices tab is missing. Try uninstalling and reinstalling the ud plugin. If that doesn’t work, reboot.

The two disks showing in ud without a file system would be parity.

Update again. You ran into an error condition I didn't cover.

I'll have a fix soon.

Ok, i'll release a fix for the php warning today. I turned on php warnings so I could find and fix any that came up. Some of them like this one havehyugh been a bit rough to track down.

Thanks for turning on the debug log. It looks as if the lock file isn't getting written to the /tmp/ file system or is getting removed before the unlink(). I can stop the unlink() warning, but the file really should be there. Let me do some more testing. Can you post your diagnostics zip file so I can have a look?

Does it happen once i a while or a lot?

After you preclear a drive, you need to delete the log by clicking on the red X on the preclear status line. You can then format the drive. The partition created by preclear is not a mountable partition because it does not have a file system.

This can also happen if the disk is removed before it is unmounted, and then re-inserted into the server. Click on the edit settings (three gears icon) and turn off the 'Share' switch.

You have a lot of call traces. This goes on and on I also see a lot of the myservers messages like at the top of this snipet. Someone that knows more about how to interpret this would be better to help you. Feb 22 01:41:23 Proto flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Feb 22 01:42:23 Proto flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Feb 22 01:43:23 Proto flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Feb 22 01:44:10 Proto kernel: rcu: INFO: rcu_sched self-detected stall on CPU Feb 22 01:44:10 Proto kernel: rcu: #01118-....: (16260291 ticks this GP) idle=e52/1/0x4000000000000000 softirq=26144979/26144982 fqs=4053314 Feb 22 01:44:10 Proto kernel: #011(t=16260292 jiffies g=129526613 q=14094513) Feb 22 01:44:10 Proto kernel: NMI backtrace for cpu 18 Feb 22 01:44:10 Proto kernel: CPU: 18 PID: 1458 Comm: sensors Tainted: P O 5.14.15-Unraid #1 Feb 22 01:44:10 Proto kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X99 Extreme4, BIOS P3.80 04/06/2018 Feb 22 01:44:10 Proto kernel: Call Trace: Feb 22 01:44:10 Proto kernel: <IRQ> Feb 22 01:44:10 Proto kernel: dump_stack_lvl+0x46/0x5a Feb 22 01:44:10 Proto kernel: ? lapic_can_unplug_cpu+0x93/0x93 Feb 22 01:44:10 Proto kernel: nmi_cpu_backtrace+0x7d/0x8f Feb 22 01:44:10 Proto kernel: nmi_trigger_cpumask_backtrace+0x56/0xd3 Feb 22 01:44:10 Proto kernel: rcu_dump_cpu_stacks+0xc3/0xea Feb 22 01:44:10 Proto kernel: rcu_sched_clock_irq+0x22e/0x608 Feb 22 01:44:10 Proto kernel: ? trigger_load_balance+0x204/0x28a Feb 22 01:44:10 Proto kernel: ? tick_sched_do_timer+0x3e/0x3e Feb 22 01:44:10 Proto kernel: update_process_times+0x8c/0xab Feb 22 01:44:10 Proto kernel: tick_sched_timer+0x38/0x65 Feb 22 01:44:10 Proto kernel: __hrtimer_run_queues+0xfa/0x18a Feb 22 01:44:10 Proto kernel: hrtimer_interrupt+0x92/0x160 Feb 22 01:44:10 Proto kernel: __sysvec_apic_timer_interrupt+0x99/0xdb Feb 22 01:44:10 Proto kernel: sysvec_apic_timer_interrupt+0x61/0x7d Feb 22 01:44:10 Proto kernel: </IRQ> Feb 22 01:44:10 Proto kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Feb 22 01:44:10 Proto kernel: RIP: 0010:smp_call_function_single+0xca/0xf7 Feb 22 01:44:10 Proto kernel: Code: 50 08 80 e2 01 74 04 f3 90 eb f4 83 48 08 01 4d 89 77 10 4c 89 fe 44 89 e7 4d 89 6f 18 e8 a2 fe ff ff 85 db 74 0d 41 8b 57 08 <80> e2 01 74 04 f3 90 eb f3 48 8b 54 24 38 65 48 2b 14 25 28 00 00 Feb 22 01:44:10 Proto kernel: RSP: 0018:ffffc90020fa7cc0 EFLAGS: 00000202 Feb 22 01:44:10 Proto kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 Feb 22 01:44:10 Proto kernel: RDX: 0000000000000011 RSI: ffffc90020fa7cc0 RDI: 0000000000000009 Feb 22 01:44:10 Proto kernel: RBP: ffffc90020fa7d28 R08: 0000000000000009 R09: ffff88810bd56180 Feb 22 01:44:10 Proto kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000009 Feb 22 01:44:10 Proto kernel: R13: ffffc90020fa7d38 R14: ffffffff813e5fa1 R15: ffffc90020fa7cc0 Feb 22 01:44:10 Proto kernel: ? pldmfw_flash_image+0x7fe/0x7fe Feb 22 01:44:10 Proto kernel: ? pldmfw_flash_image+0x7fe/0x7fe Feb 22 01:44:10 Proto kernel: rdmsr_on_cpu+0x48/0x71 Feb 22 01:44:10 Proto kernel: show_temp+0x68/0xc3 [coretemp] Feb 22 01:44:10 Proto kernel: dev_attr_show+0x20/0x42 Feb 22 01:44:10 Proto kernel: sysfs_kf_seq_show+0x75/0xc0 Feb 22 01:44:10 Proto kernel: seq_read_iter+0x156/0x347 Feb 22 01:44:10 Proto kernel: new_sync_read+0x7c/0xaf Feb 22 01:44:10 Proto kernel: vfs_read+0xc6/0x108 Feb 22 01:44:10 Proto kernel: ksys_read+0x76/0xbe Feb 22 01:44:10 Proto kernel: do_syscall_64+0x83/0xa5 Feb 22 01:44:10 Proto kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Feb 22 01:44:10 Proto kernel: RIP: 0033:0x146f4ac243ce

This generally happens when a device is not recognized by Unraid as unassigned. You can tell because the device designation is sda and not 'Dev X'. Try clicking on the double arrows on the upper right hand part of the UD screen and see if that fixes it. There is a bug in UD that may be causing this that is fixed in the next release.

This is UD issuing a standby command to the disk. If the disk does not respect this standby command, then it will not spin down. On Unraid versions earlier that 6.9, there is no direct spin down issued to the disk. The best way to handle this is to upgrade to 6.9. You may find that your disks still won't spin down. Some older USB disks will not spin down at all.

UD informs Unraid whenever a device is hotplugged and Unraid re-organizes unassigned devices. What you did by cliicking on the double arrows was to initiate that hotplug manully that UD didn't do. This will be fixed in the next release.

Click on the double arrows in the upper right corner of the UD page and see if it clears it up.

Are you on the latest version of UD? Can you post your diagnostics zip?

You'll be running NFSv3. Go to the UD settings and you'll see the setting for NFS version. You'll need 6.10 for NFSv4. If you look at your log you'll probably see a lot of stale file handles. When that happens, everything stops. NFSv4 solves this and other issues. NFSv3 is very troublesome and you shouldn't spend a lot of time trying to sort it out. It's not worth it and you won't get anywhere. How about using SMB for now?