dlandon

I see the problem. I'm trying to figure it out.

It's actually a detached disk, not disabled disk. Post a screen shot of the Historical Devices. Click on the three gears icon of a deteached disk and see it the 'Attach' button shows.

Use the 'Clear Disk' (the red 'X') next to the DIsk ID to clear the disk.

Lookiing itno it now.

Yes. I see no reason to do more.

Yes, but you can specify the number of zeroing passes (called cycles) up to a total of 3 if you want to do more.

One preclear pass is 5 steps. It's indicating what steps are done in the preclear process.

Once you are happy that it is resolved, turn off the debug logging. It could get too chatty.

I've made some changes in UD that might help with this issue, but GitHub is struggling today so it may take quite a while before the update is available. Once you update it, let me know if the issue is fixed. If not post diagnostics again, Leave the debug level set as it is.

Not really. This is the info reported by udev. We don't have any control over that. I don't know what you are doing with that disk, but the partition is a vfat partition and if it's not needed, you could manually remove it. You're best bet would be to reformat the disk and start over.

Do the following: Go to the UD Settings and set "Debug Log Level" to "Udev and Hot Plug". Reboot - Leave the Auto Mount on. Post diagnostics.

Config folder to start. The rest of it if it still has problems. Most likely config corruption.

I would restore the flash from a backup.

Not that I know of, but that's why UD is choking on that udev info.

Give me the output of the following command: /sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p1) There seems to be something in the udev info for this partition that UD is choking on. We need to get the udev info cleaned up a bit so UD doesn't choke on it. I think that UD will recognie the partition once we can clean up the reserved characters that are causing problems.

When you turn on the 'Share' switch, it can take up to two minutes to actually share the disk.

If you make a change to the flash config file, you'll have to click the double arrows icon on the UD page to refresh the ram file that holds the config file. When UD is operating, the configuration file is in ram and copied to the flash drive when a change is made.

The buttons at the top are immediate and you don't need to click 'Save'. That being said, do you have the 'Auto Mount USB Devices?' set to 'Yes'? It sounds as if the configuration file is corrupt. You could look at the /flash/plugins/unassigned.devices/unassigned.devices.cfg with an editor and see if you see anything amiss. The file is fairly easy to read. PM the file to me if you are unsure of what you are looking at. Don't post it on the forum it contains a password seed.

Your Dev 3 device has a partition with no file system. That's why the 'Mount' button is greyed out. You need to get rid of that partition. A disk with a partition and no file system is fairly useless anyway. What do you intend to do with that disk?

One of your devices has some php reserved characters in a field - '~', '!', etc. Post a screen shot of your UD page so we can find the disk giving the problems and see where the characters are showing up.

Have you set that disk to share? Click the three gears ad turn on "Share".

Post your diagnpstics. UD shouldn't take that long to display.

The file activity plugin was designed to help with array spin ups. You can exclude Cache and Pool devices that are normally SSD devices and where appdata should reside. Your Home Assistant appdata should be on a Cache or Pool device if it is not. This plugin is meant to work at the device level, not the share level.

The only thing I can suggest is to manually remove partition 3. The partition has no file system anyway.

You have some zfs residue left on the disk that UD can't remove: Feb 5 21:35:52 Gringotts unassigned.devices: Successfully unmounted 'nvme0n1p1' Feb 5 21:35:52 Gringotts zed[4419]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by ntfs) Feb 5 21:36:04 Gringotts unassigned.devices: Removing all partitions from disk '/dev/nvme0n1'. Feb 5 21:36:04 Gringotts zed[4419]: zed_disk_event: Feb 5 21:36:04 Gringotts zed[4419]: #011class: EC_dev_status Feb 5 21:36:04 Gringotts zed[4419]: #011subclass: dev_dle Feb 5 21:36:04 Gringotts zed[4419]: #011dev_name: /dev/nvme0n1p1 Feb 5 21:36:04 Gringotts zed[4419]: #011path: /devices/pci0000:00/0000:00:01.2/0000:01:00.2/0000:02:00.0/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 Feb 5 21:36:04 Gringotts zed[4419]: #011devid: nvme-CT500P2SSD8_2239E66F2DAD-part1 Feb 5 21:36:04 Gringotts zed[4419]: #011dev_size: 500106788864 Feb 5 21:36:04 Gringotts zed[4419]: #011dev_parent_size: 500107862016 You'll need to do some manual operations and/or remove the zfs master plugin. I don't know enough about how it works to help you other than that.