16 minutes ago, sentient-russ said:

This could be the catalyst here.

All that UD change does is to include '/mnt/remotes/' as a destination in the File Manager so files can be copied or moved to a UD remote share.

 

The issue with the '.LOCAL' in the device name was fixed a long time ago and you would have seen the issue months ago if you were keeping UD up to date.

I’m certain I updated all of my plugins when I upgraded to 7.0 which was released in the beginning of January.  My TLD is not set to local, I was using .local as an example.  All I know is that all my remote shares said that their configs were invalid and removing the .TLD from the share tags solved the issue.  I can’t log into my server without a banner asking me to update UD which I always do.  Not sure where this is going.  Have a good one.

The bold assumption that I haven't been updating my plugins irritated me, so I dug into my server and sure enough I have the CA Auto Update app installed from day one with daily 2am checks....

 

I am not sure when "a long time ago" is, but I dug up an old diag from December 2024 on the server with dates and plugin versions.  Everything was working as expected then, and yesterday morning before making the changes I explain below ( I run plexamp for music every morning on my way to work which depends on the music remote share (nfs) that also had a broken config after recent updates/changes )...

 

All of that aside, I had this issue.  I corrected it without deleting my shares and wanted to share that info on here for anyone experiencing the same problem while bringing attention to the issue to you as the maintainer.

 

I am not blaming the UD plugin, as I also made other changes.  I recently enabled IPv6, and installed the Limetech Unraid Patch plugin.  I am using an Active Directory Domain configured in the SMB settings, it was active ( "Joined" ) at the time of the issue. 

 

Here is the new samba_shares.conf after I changed the share tags from [//GUMBY.KNET/immich] -> [//GUMBY/immich], etc. and left the ip="GUMBY.KNET" and everything else under the tags alone:

 

Here is the TLD settings under Managment which has been the same for years:

 

And here is a current listing of servers when adding a new remote share under UD and clicking Search:

 

I am unsure why some are listed as .local as they all have their TLD set to knet, maybe mDNS is taking priority, maybe with recently enabling IPv6 Unraid is trying to query the IPv6 DNS which does not have the servers hostname registered under the knet domain for its IPv6 address.

 

If I am doing something stupid please correct me but please don't assume I haven't updated and write this off as that.  I hope this information helps, as that was the intention of the original post to begin with - I had already rectified the issue and wanted to post it up here as I did not see any recent posts about this problem and have had everything up to date DAILY ( I don't want to play server admin every day, I just want my servers to run and hop on to fix anything that breaks with updates to my network or from auto updates )

 

If you decide there may be something going on outside of operator error and need more diagnostic info let me know and I will gladly post it.

There a few tennents I need to mention:

• UD does not make any changes to config files unless user initiated.
• No changes in the latest version of UD would have caused this.
• Changes were made to UD last year to clean up server names entered by users that caused issues in the tags.  A server name entered such as "SERVER.LOCAL" would cause issues in the tag.  The ".LOCAL" was removed from the server name in the tag, but left in the "ip" field of the config file so the lookup of the server name would be successful.
• Changes were made then to indicate an invalid configuration, so a user could tell there was a problem and take action to correct.
• Part of the reason for the change to indicate an invalid configuration was that users were modifying the config file to try to address a problem with name resolution that has been corrected in UD.
• Back then the invalid configuration came up a lot when that message was added.

These are the ways the invalid configuration can occur:

• Updating from a very old version of UD to the latest version.
• Restoring an older samba_mount.cfg file with the incorrect tags.
• Incorrect user modifications to the samba_mount.cfg file.

Since you did not post a diagnostics, I (incorrectly) assumed you updated from an older version of UD because that is normally how this happens.

 

Just as a heads up, the "Local TLD" when blank defaults to "LOCAL".  In your case, you should set it to "KNET".

 

Appologies if I offended you, but I am not fond of posts that encourage manually editing config files as mistakes made can create user problems and support issues to be addressed.

That clears things up a bit, thank you.  
 

I’m still confused at to why I still had config files with the domain extension in the tags and why it was just now an issue when it hasn’t been one in past.  I have had auto plugin updates enabled, if anything this should have come up prior or been corrected by a past update if I’m understanding you correctly.  I have not restored any back ups of the file, nor have I edited it.  This is strange.

 

 You also mention setting TLD to KNET, mine is set to “knet” already unless caps matters here.  
 

This is the first time I have updated the configuration files directly, everything else I have done in the UI for the reasons you mention.  The only reason I did it this way was to preserve the individual login credentials to each share as I don’t have all of the passwords saved and I didn’t want to take the time to go into the other servers and reset several passwords.  
 

I will add that this server has been in service for many years (4-6). and these shares were set up at least a year ago.  Maybe something has fallen through the cracks.

 

I plan to restructure my network and change up my NAS systems and take advantage of AD Domain for my share users/passwords between machines eventually. when I do I will absolutely wipe the remote shares from the UI and provision them fresh from the UI, this was a stop gap as it came up when I didn’t have the time to fix unexpected issues seemingly unrelated to the immediate changes I made.

 

Thank you for the info, I will be sure to post my diag next time to avoid confusion.

Edited February 15, 20251 yr by sentient-russ

2 minutes ago, sentient-russ said:

I’m still confused at to why I still had config files with the domain extension in the tags and why it was just now an issue when it hasn’t been one in past.  I have had auto plugin updates enabled, if anything this should have come up prior or been corrected by a past update if I’m understanding you correctly.

UD used to add the local tld to the tag.  Yes, based on what you've said this should have come up last year from an update to UD.

 

3 minutes ago, sentient-russ said:

 You also mention setting TLD to KNET, mine is set to “knet” already unless caps matters here.  

Caps don't matter.  I thought you said somewhere that your local tld was blank.

I sometimes notice that the auto-mount from my external encrypted USB hard disk does not work. The system log then shows the following although I just have one usb drive connected to the server:

 

Feb 16 13:40:22 smartserver kernel: usb 2-1: new SuperSpeed USB device number 7 using xhci_hcd
Feb 16 13:40:22 smartserver kernel: usb-storage 2-1:1.0: USB Mass Storage device detected
Feb 16 13:40:22 smartserver kernel: scsi host10: usb-storage 2-1:1.0
Feb 16 13:40:23 smartserver kernel: scsi 10:0:0:0: Direct-Access     WD       Elements 25A3    1030 PQ: 0 ANSI: 6
Feb 16 13:40:23 smartserver kernel: sd 10:0:0:0: Attached scsi generic sg5 type 0
Feb 16 13:40:23 smartserver kernel: sd 10:0:0:0: [sdg] Spinning up disk...
Feb 16 13:40:42 smartserver kernel: ...................ready
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] 15627986944 512-byte logical blocks: (8.00 TB/7.28 TiB)
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] 4096-byte physical blocks
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Write Protect is off
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Mode Sense: 47 00 10 08
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] No Caching mode page found
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Assuming drive cache: write through
Feb 16 13:40:42 smartserver kernel: sdg: sdg1
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Attached SCSI disk
Feb 16 13:40:44 smartserver unassigned.devices: Mounting partition 'sdg1' at mountpoint '/mnt/disks/WD_Elements_25A3'...
Feb 16 13:40:44 smartserver unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Feb 16 13:40:44 smartserver unassigned.devices: luksOpen result: Device WD_Elements_25A3 already exists.
Feb 16 13:40:44 smartserver unassigned.devices: Partition 'WD Elements_25A3' cannot be mounted.
Feb 16 13:40:44 smartserver emhttpd: online: WD_Elements_25A3_56444A5244454B4B-0:0 (sdg) 512 15627986944
Feb 16 13:40:44 smartserver emhttpd: read SMART /dev/sdg

 

However after this happend, I can mount it manually without any problems or switch it off and on again and then the auto-mount works again in most cases

 

Feb 16 13:42:36 smartserver unassigned.devices: Mounting partition 'sdg1' at mountpoint '/mnt/disks/WD_Elements_25A3'...
Feb 16 13:42:36 smartserver unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Feb 16 13:42:39 smartserver unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/mapper/WD_Elements_25A3' '/mnt/disks/WD_Elements_25A3'
Feb 16 13:42:39 smartserver kernel: XFS (dm-5): Mounting V5 Filesystem f4d2d3da-164f-403b-9b1e-9ef13ee04ad1
Feb 16 13:42:40 smartserver kernel: XFS (dm-5): Ending clean mount
Feb 16 13:42:40 smartserver kernel: xfs filesystem being mounted at /mnt/disks/WD_Elements_25A3 supports timestamps until 2038-01-19 (0x7fffffff)
Feb 16 13:42:40 smartserver unassigned.devices: Successfully mounted '/dev/mapper/WD_Elements_25A3' on '/mnt/disks/WD_Elements_25A3'.
Feb 16 13:42:40 smartserver unassigned.devices: Adding SMB share 'WD_Elements_25A3'.

 

23 hours ago, kennymc.c said:

I sometimes notice that the auto-mount from my external encrypted USB hard disk does not work. The system log then shows the following although I just have one usb drive connected to the server:

 

Feb 16 13:40:22 smartserver kernel: usb 2-1: new SuperSpeed USB device number 7 using xhci_hcd
Feb 16 13:40:22 smartserver kernel: usb-storage 2-1:1.0: USB Mass Storage device detected
Feb 16 13:40:22 smartserver kernel: scsi host10: usb-storage 2-1:1.0
Feb 16 13:40:23 smartserver kernel: scsi 10:0:0:0: Direct-Access     WD       Elements 25A3    1030 PQ: 0 ANSI: 6
Feb 16 13:40:23 smartserver kernel: sd 10:0:0:0: Attached scsi generic sg5 type 0
Feb 16 13:40:23 smartserver kernel: sd 10:0:0:0: [sdg] Spinning up disk...
Feb 16 13:40:42 smartserver kernel: ...................ready
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] 15627986944 512-byte logical blocks: (8.00 TB/7.28 TiB)
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] 4096-byte physical blocks
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Write Protect is off
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Mode Sense: 47 00 10 08
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] No Caching mode page found
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Assuming drive cache: write through
Feb 16 13:40:42 smartserver kernel: sdg: sdg1
Feb 16 13:40:42 smartserver kernel: sd 10:0:0:0: [sdg] Attached SCSI disk
Feb 16 13:40:44 smartserver unassigned.devices: Mounting partition 'sdg1' at mountpoint '/mnt/disks/WD_Elements_25A3'...
Feb 16 13:40:44 smartserver unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Feb 16 13:40:44 smartserver unassigned.devices: luksOpen result: Device WD_Elements_25A3 already exists.
Feb 16 13:40:44 smartserver unassigned.devices: Partition 'WD Elements_25A3' cannot be mounted.
Feb 16 13:40:44 smartserver emhttpd: online: WD_Elements_25A3_56444A5244454B4B-0:0 (sdg) 512 15627986944
Feb 16 13:40:44 smartserver emhttpd: read SMART /dev/sdg

 

However after this happend, I can mount it manually without any problems or switch it off and on again and then the auto-mount works again in most cases

 

Feb 16 13:42:36 smartserver unassigned.devices: Mounting partition 'sdg1' at mountpoint '/mnt/disks/WD_Elements_25A3'...
Feb 16 13:42:36 smartserver unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Feb 16 13:42:39 smartserver unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,relatime '/dev/mapper/WD_Elements_25A3' '/mnt/disks/WD_Elements_25A3'
Feb 16 13:42:39 smartserver kernel: XFS (dm-5): Mounting V5 Filesystem f4d2d3da-164f-403b-9b1e-9ef13ee04ad1
Feb 16 13:42:40 smartserver kernel: XFS (dm-5): Ending clean mount
Feb 16 13:42:40 smartserver kernel: xfs filesystem being mounted at /mnt/disks/WD_Elements_25A3 supports timestamps until 2038-01-19 (0x7fffffff)
Feb 16 13:42:40 smartserver unassigned.devices: Successfully mounted '/dev/mapper/WD_Elements_25A3' on '/mnt/disks/WD_Elements_25A3'.
Feb 16 13:42:40 smartserver unassigned.devices: Adding SMB share 'WD_Elements_25A3'.

 

It appears the disk was not unmounted properly because the luks device was not closed.  When you try to remount the disk, the luks disk is cleaned up with a close and the next attempt (manually) will succeed.  Be sure to unmount the device before removing it with the device script or manually and confirm the disk successfully unmounted.  If it is busy and didn't unmount, that will create this situation.

On 2/12/2025 at 4:39 PM, dlandon said:

UD release to address the following:

• NFS export file not updating after a share edit.
• Shutdown hanging when a remote share is offline.

I think this fixed my issue, i had to restart my camera and nfs settings one time first though but seems good so far, thanks!

6 hours ago, dlandon said:

It appears the disk was not unmounted properly because the luks device was not closed.  When you try to remount the disk, the luks disk is cleaned up with a close and the next attempt (manually) will succeed.  Be sure to unmount the device before removing it with the device script or manually and confirm the disk successfully unmounted.  If it is busy and didn't unmount, that will create this situation.

That's strange because my user script (trigged by cron and not by UDs auto mount) waits 60 seconds for the drive to be unmounted, sends a push message if it takes longer and then waits another 10 seconds until the power plug is toggled. I don't get a push message in these cases. Can this still lead to the above mentioned issues with encrypted drives?

 

umount /mnt/disks/WD_Elements_25A3

while [ "$(mount | grep /mnt/disks/WD_Elements_25A3)" ]
do
 sleep 1
 DOWNCOUNTER=$((DOWNCOUNTER + 1))
   if [ $DOWNCOUNTER -gt 60 ] ; then
	# Send Push message
    exit 1
   fi
done

sleep 10

docker exec fhem perl /opt/fhem/fhem.pl 7072 "set WZ_Plug_HDD off"

 

2 hours ago, kennymc.c said:

Can this still lead to the above mentioned issues with encrypted drives?

Yes, use the UD unmount command and check the return code.  It will be 'success' if it successfully unmounts the drive.  Let UD unmount the disk and do the cleanup.  A luks disk has to be closed as part of the unmount.  If you don't do that you will get the above issue.  Go to the UD page and click on the 'Help' icon and you will see how to use the UD 'rc.unassigned' command.

Is there a way where I can add a comment/description for each unassigned drive?

 

I have a few old 1-2TB drives lying around that I use for unimportant data that doesn't need to be on unRAID. These drives are mounted when needed using a USB dock and then unmounted and undocked after I've used it.

 

At the moment, I differentiate them only by their serial number. I'm hoping that Unassigned Devices can have a field where for each historical unassigned device, where I can put in a comment/description for that drive. E.g. "2023 Archives" or "Need to preclear later" or "2020 Pr0n".

Edited February 20, 20251 yr by Phorte

Hi @dlandon Curious to see if there are any known issues with high IOWait times when moving files from unraid to an external share.

Currently have been batteling my unraid instance becoming completly unresponsive when transfering files from my download client>unraid>bulk storage

 

Ive tried running the download client directly on unraid with that being the worst offender, Currently have the client on another system still being passed through unraid with the issue not as bad but still pinning my cpu at 100% for the entire transfer

Hi all,

 

I've got a second unRAID share mounted to my primary storage server via UD's remote SMB share.

The remote is a backup server, so I have the target's "backup" share mounted on the source at /mnt/remotes/backup.

I can't read or write to this dir from the source. On the target everything is fine.

 

Source array: 6.12.15, target 7.0.0.

All of this hardware has been running fine for several months with no issues. The target was recently reimaged with unRAID from Proxmox.

 

Target syslog shows nothing of note. Source syslog shows lots of:

Feb 20 16:32:25 server kernel: traps: lsof[525] general protection fault ip:1475962a7c6e sp:b96ee9d3b65e2e1d error:0 in libc-2.37.so[14759628f000+169000]

 

As well as:

Feb 20 16:32:02 server kernel: CIFS: VFS: reconnect tcon failed rc = -2 
Feb 20 16:32:04 server kernel: CIFS: VFS: \\BACKUP.LOCAL\backup BAD_NETWORK_NAME: \\BACKUP.LOCAL\backup

 

Diags attached. Anything jumping out? Thanks in advance!

source.zip target.zip

Edited February 20, 20251 yr by -Daedalus

11 hours ago, Phorte said:

Is there a way where I can add a comment/description for each unassigned drive?

 

I have a few old 1-2TB drives lying around that I use for unimportant data that doesn't need to be on unRAID. These drives are mounted when needed using a USB dock and then unmounted and undocked after I've used it.

 

At the moment, I differentiate them only by their serial number. I'm hoping that Unassigned Devices can have a field where for each historical unassigned device, where I can put in a comment/description for that drive. E.g. "2023 Archives" or "Need to preclear later" or "2020 Pr0n".

You can assign a disk alias.  Go to the disk settings (three gears icon) and change the disk name.

11 hours ago, IVIazor said:

Hi @dlandon Curious to see if there are any known issues with high IOWait times when moving files from unraid to an external share.

Currently have been batteling my unraid instance becoming completly unresponsive when transfering files from my download client>unraid>bulk storage

 

Ive tried running the download client directly on unraid with that being the worst offender, Currently have the client on another system still being passed through unraid with the issue not as bad but still pinning my cpu at 100% for the entire transfer

Not that I know of.  I can't help with a downloader as LT does not support downloading.  Other users may be of some help.

Hello everyone. This will be a short summary of the following thread from the German subforum. Maybe someone has an idea if this problem could be related to UD.

 

Briefly about the system:

 

Unraid 7 in a Unifi network with corresponding MACLAN customisation

64 GB RAM

2x NICs, one is called DMZ but does not lead to a DMZ (to avoid any panic)

1 array. XFS, with parity

Various pools, both ZFS and XFS

various Docker

Nvidia GPU for Emby, Tdarr and Immich

 

Backup:

 

Daily automatic backup to external USB HDD via Mgutt script of the most important data

Once a week automatically encrypted on NAS off-site and in the cloud via duplicacy of the most important data

Always, if deemed necessary, manual backup of the entire array to internal NAS via duplicacy

 

Mods of the Go File:

 

Auto Unlock Array

RAM disc for Docker json/log files v1.6 for 7.0.0 (also used for Emby, if transcode required) (no longer used, even if still available in Diagnostics)

 

Adjustments since update to V7:

• fastusr Fix
• Overlay2 Docker Storage Driver including re-import of all Docker
• Permit exclusive shares and adjust the Docker and mappings from formerly Diskshare Appdata (mnt/cache/appdata) back to mnt/user/appdata

 

Since the update to V7 no problems have occurred so far. Now I've been trying to run a manual backup to the internal NAS via Duplicacy again for a few days (the first time under Unraid 7, as it is only triggered manually every few months). This runs for a while without any problems, then Unraid starts to become very sluggish and sometimes stops responding. When you get back to the WebUI at some point, you can see that it is constantly reading from the USB stick.

 

My understanding of Unraid tells me that something is cluttering up my RAM and Unraid has to keep reloading the OS from the stick into RAM. But so far I have not been able to find out what is causing this problem. Since it only occurs during the backup, I have checked the docker mappings in general and especially Duplicacy several times, but cannot find any errors - I don't want to rule out my own operational blindness or incompetence at this point.

 

For more information, please refer to the pinned thread, where you can also find the diagnostics. Thank you.

Edited February 21, 20251 yr by Gorosch

3 minutes ago, Gorosch said:

When you get back to the WebUI at some point, you can see that it is constantly reading from the USB stick.

 

Try this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

1 hour ago, JorgeB said:

 

Try this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

 

 

1 hour ago, Gorosch said:

 

Adjustments since update to V7:

• fastusr Fix
• Overlay2 Docker Storage Driver including re-import of all Docker
• Permit exclusive shares and adjust the Docker and mappings from formerly Diskshare Appdata (mnt/cache/appdata) back to mnt/user/appdata

 

 

 

Thanks, but its allready done.

may as additional note as we tried some stuff to resolve

 

- using the UAD mount as target (smb) ending up with his result.

 

- using the UAD mount as target (nfs) seems to be ok.

 

so i recomended to post this here as @dlandon may has an idea what could cause this behaviour with an UAD mount using smb to target and may "caching" locally too much as i went out of ideas

I'm having an issue with implementing a script to run at the time of mounting an external disk.

 

FIX: User error, need to click "default" button in lower left to be able to enter script

 

Unraid version:  7.0.0

UAD plugin version: 2025.02.14

UAD+ plugin version: 2025.02.14

 

I'm using the plugin to mount an external USB hard drive, formatted to ext4 and encrypted.  Upon plugin, the disk is auto-mounted and is accessible at /mnt/disks/ZXA0TJLX.  I can read/write to this drive with no issues.

 

When I enter the disk settings to enter the script, the "Device Script" button drops down to a single blank entry which can't be selected.  "Enable Device Script" is set to "Yes" as is "Run Device Script File in the background".  When I paste an entry into the "Device Script Content" area, the "Save" button remains greyed out and I can't save the script.

 

At a bit of a loss here, can anyone help?  Thanks!  

Edited February 23, 20251 yr by pmgeahan
Added fix.

Click "Default" first so it creates an empty script for that device, then you can add your cantents.

That did it! Thank you!

On 2/21/2025 at 10:04 PM, alturismo said:

may as additional note as we tried some stuff to resolve

 

- using the UAD mount as target (smb) ending up with his result.

 

- using the UAD mount as target (nfs) seems to be ok.

 

so i recomended to post this here as @dlandon may has an idea what could cause this behaviour with an UAD mount using smb to target and may "caching" locally too much as i went out of ideas

When looking at the diagnostics, I see the Multichannel feature of SMB is enabled.  That feature requires two NICs and special setup to work properly.  I suggest turning it off and see if it helps.

When I try to change the SMB Sharing type from disabled to another value it does not save. I can make the change to the users access type but am not able to change from disabled. Does anyone have an idea of why this would occur.