dlandon

Update to the latest version of UD.

This is fixed in the next release.

UD is using lsblk to determine the size of your disk /dev/sda. That disk is a WD My Passport. Does that disk show a zero size in the UD UI? Are you using the disk? Is it working?

You can move files to the recycle bin.

That's not UD. I've never seen that before.

Found something I missed. Try 2022.02.06a.

Latest releaase 2022.02.06 should resolve this issue. Please let me know if it is working now without the log messages.

Keep trying to get the 2022.02.05 version loaded. Once you can get that one, let me now and we'll try again. I'll upload a new package. In the meantime I think I have this problem solved. It is probably related to a change I made to the udev rules a few months ago.. I was trying to solve an issue where UD wss not picking up a disk that had no partitions. The issue is that with the rules I set, udev was churning everytime there was a 'change' on a disk. Basically all the disks were changing on system startup. I guess this annoyed btrfs and it decided it needed to do all that scanning, I need to do some more testing, but I'm not at my test server and I need to test a bunch of hot plugs to be sure it all works out.

The latest version is 05.

We need to try qgain. Remove the plugin and install the latest from CA. Tell me what version it shows and I'll prepare a new test package.

If it still comes up as 04b then change the 05 on the file I gave you to 04b and follow the procedure. I may have gotten ahead of myself this morning.

Remove ud completely. Then reinstall from CA. You'll have the latest. Then follow the procedure I ouined.

The problem with prompting for the password on an encrypted disk is that it cannot always be done from the UI. If a user clicks the mount button on the UI, it may be possible to prompt at that point, but if a disk is auto mounted, it's difficult to prompt for a password because there is a background script doing the mounting and it is not UI aware. That's why the password is a configurable setting, so the mount can happen whether or not the UI is running at the time.

I have an update for you to try. Copy the attached file to /flash/config/plugins/unassigned.devices/. It will overwrite the one already there. Then edit /flash/config/plugins/unassigned.devices.plg and change the version from '2022.01.05' to '2022.01.04. Then go to the Unraid UI and click on 'Plugins' It will say there is an update to UD. Apply that update. Then do your thing and post diagnostics zip file again. unassigned.devices-2022.02.05.tgz

Yes, I got the information I need. I think I see what is happening. I'm reworking the udev events. I have not reviewed them for many years and now that I am deep diving into these events, I see issues. Instead of releasing an update, I'll post an update here for you to install and try. I'm doing some testing now and should have something for you soon.

Thank you. I'll review the log and see what we have.

I believe this is coming from udev events in UD. I've released a new version just now that has the udev rules reworked and I've added some debug logging to track the udev and hotplug activity. What this will do is let me see what event(s) in UD are happening just before the btrfs log messages occur. Please update to the latest version, and then go to the UD settings and set the debug level to '1'. Do whatever you need to do to make the log messages happen and post the diagnostics zip file. This is a very difficult thing to do because I'd have to track down the differences between versions to determine what changed. I can't reproduce the issue. I've tried to force it with no luck, so the next best thing is to get enough information in the log for me to track this down.

When do you think this started? I can look back at my changes and see it there is anything that might cause this.

You can try that, but all UD+ does is install some packages. I'm at a loss why this is happening. You don't have any UD disks, so UD isn't doing anything. Post your latest diagnostics, I want to see where in the startup sequence it is happening.

Update UD and try once more to see if the messages stop.

It happens at bootup when UD is trying to auto mount devices. I'm not sure why that is happening, because UD s not doing anything since you don't have any auto mounted devices. There is one thing I'm doing just before the auto mount that causes some udev action. I'm going to do a little testing and then issue an update to let you try again.

The plugin was not cleaning up properly and left some things behind. I've posted a new recycle.bin.plg. Install the plugin and then remove it and it will clean things up.

Do you have Pool devices in UD? Try removing the UD plugin and see if it stops the messages.

That would explain it.

Update to the latest release of UD and let me know if it solved the problem.