dlandon

It's too complicated and confusing for an edge case use that will not be an issue with 6.12 because your ZFS Pools will be moved to Unraid Pools. You should assign alias disk names to organize the disks. As I suggested, name them "Zpool1", "Zpool2", etc and they will show at the bottom of the list because UD sorts the disks based on the device (alias) name. Actual UD disks will be at the top. A reboot will not change the alias disk names and disks will not show a different order.

The issue with hiding the disks is the ability to un-hide them. How could one do that? If they are hidden from UD, how do you access the disk to un-hide it? You have several options: Turn on the "Disable Mount Button" and the mount buttons will be disabled. Set an alias disk name that will sort and move them in your list of UD devices to make it easier to understand. Start all your alias disk names with "Z" and they will show up at the bottom of the UD list. Maybe do something line "Zpool1", "Zpool2", etc. Turn on the "Passed Through" switch so the mount button will show "Passed" and UD will not allow operations on the disks. Wait for 6.12 with native ZFS support and your disk pools will not be shown as UD disks.

Samba is failing: Feb 18 16:51:03 Server4U smbd[25677]: [2023/02/18 16:51:03.061854, 0] ../../lib/util/become_daemon.c:119(exit_daemon) Feb 18 16:51:03 Server4U smbd[25677]: exit_daemon: daemon failed to start: smbd can not open secrets.tdb, error code 13 Feb 18 16:51:03 Server4U root: /usr/sbin/nmbd -D Post the output of this command: testparm -s What is this in your go file? cp /boot/custom/docker-shell/usr/local/bin

Try turning off Multi-Channel.

You should check or replace the cable before you get rid of the drive.

Doesn't look like it is settable in the driver from the link you showed me.

Doesn't look like it.

How are you connecting the drive? If Linux does not recognize the drive, UD won't see it. I'd ask you to post diagnostics, but there is no value in that unless the disk is not being recognized when you run diagnostics.

No. As long as your appdata is intact. You will have to reconfigure the docker xml since it is stored on the flash.

You can re-install the Docker apps. You have to shut down the server. Don't take the USB out while the server is running! A Windows PC has a file system check you can run once the USB is installed in the PC. Not sure what tools a Mac will have.

Not necessarily if there is a file corruption. What changed in your configuration since January 6th?

Your unclean shutdown probably caused a corruption on the flash drive if everything was working before that. I was hoping it was as simple as redoing the SMB settings. Try this: Take your flash to a PC and perform a file system check. Fix any errors that show up. Restore the flash drive contents from a backup.

Do the following: Stop the array. Confirm and force an update to your SMB Settings. You can force an update by making a change and reverting it back then apply. Start the array.

The commands on the remote server are timing out. This implies a network or remote share issue. Post diagnostics.

No. The recycle bin plugin makes the necessary adjustements when it's updated.

Remove and reseat the nvme drive.

There is a fix in the latest samba release that will be included in Unraid 6.12. Until that is released, add the following to your SMB Extras file: logging = 0

The issue is with the disabling of the delete 'X'. I'll have a look.

I didn't ask you to attach a disk, I only asked if you click on the three gears if the 'Attach' button shows up. I'm looking to see if the detection of a disk in this situation has a problem, or if UD needs to change how it detects this situation. Booting the server should clear the status of a deteched disk. So let's try once more. If you click on the three gears does the 'Attach' button show up?

If you click on the three gears of one of those Historical devices, does the 'Attach' button show?

Looks like you have a lot of disks in that situation. Aren't you interested in removing all of those? Looks pretty messy. I can't reproduce your issue The only way the disk will show as being able to re-attach (delete 'X' disabled) is if you detached the disk in UD. After your next reboot, those disks will show an enabled delete icon.

I've updated recycle bin to fix this issue, but over the last few days GitHub has been slow in posting the updates, so it may take a while.

All your Historical devices except sdv can be deleted.

I need to complete screen shot of Historical devices.