14 minutes ago, s1l3nce said:

Excellent @dlandon! It works

But after updating, when I rebooted the system, I got this command in console right before it posts the Unraid Version:
 

modprobe: FATAL: Module ntfs3 not found in directory /lib/modules/6.1.74-Unraid

I'm on version 6.12.8, in case that helps.

That's a new feature for Unraid 7.0.  You can ignore that message and I will make a change so it doesn't show.

  

29 minutes ago, dlandon said:

That's a new feature for Unraid 7.0.  You can ignore that message and I will make a change so it doesn't show.

 

Awesome! Thank you so much for your incredible help and interest 🙏😄

 

 

  

5 hours ago, House Of Cards said:

For what it's worth, I have about 20 NFS shares configured, but not automounting.  They are there in case I want to look at the files on the remote server, but every single mount button is greyed out.  That led me here, and I see I'm not alone.

Try the latest UD update. It worked for me so it will probably fix it for you too 👌

Edited October 2, 20241 yr by s1l3nce

On 10/2/2024 at 11:35 AM, dlandon said:

 

Update UD and see if your issues are solved.

Seems to be fixed...  Thank you!

Hi all 

 

I'm having a very odd behavior with NVME external drives connected via USB.

The first time I connect a drive in a USB port it works as expected, the drive shows up in the unassigned list and it can be mounted, but from now on, every time I try to connect that same drive to that same USB port it no longer shows up, no matter how many times I try it or restart the array or server.

If I try it on another USB it works once, and then another port, works once, until I ran out of ports and can't connect the disk any longer. This behavior is not unique to 1 hard drive, I have two external NVME drives, and both behave the same way.

 

The unraid log doesn't show anything at all, and I tried with destructive mode on and off, and to refresh the unassigned disk list as mentioned in this post , no success unfortunately. I also deleted the drive from the historical devices, and same same.

All drives work as expected when connected to a laptop.

 

Anyone else having issues with NVME drives like this?

 

Using Unraid 6.12.6 and both UD plugins up to date.

Edited October 6, 20241 yr by l3gion

2 hours ago, l3gion said:

Hi all 

 

I'm having a very odd behavior with NVME external drives connected via USB.

The first time I connect a drive in a USB port it works as expected, the drive shows up in the unassigned list and it can be mounted, but from now on, every time I try to connect that same drive to that same USB port it no longer shows up, no matter how many times I try it or restart the array or server.

If I try it on another USB it works once, and then another port, works once, until I ran out of ports and can't connect the disk any longer. This behavior is not unique to 1 hard drive, I have two external NVME drives, and both behave the same way.

 

The unraid log doesn't show anything at all, and I tried with destructive mode on and off, and to refresh the unassigned disk list as mentioned in this post , no success unfortunately. I also deleted the drive from the historical devices, and same same.

All drives work as expected when connected to a laptop.

 

Anyone else having issues with NVME drives like this?

 

Using Unraid 6.12.6 and both UD plugins up to date.

Go to a command line and enter the command 'ud_diagnostics', then post the /flash/logs/ud_diagnostics.zip file.  Also post the Unraid diagnostics.

I'm having an interesting issue on 6.12.11 and 6.12.13. I've spent the last two days trying to track down why transfers from SMB/CIFS mounts to my Unraid array (which has no parity) suddenly max out at around 10MB/s (having worked well on previous versions of Unraid). This is despite disk and network benchmarks on both servers showing full to be expected speeds. After trying to rule out any other hardware issues and running tons of different scenarios, I've started playing around with the CIFS mounts themselves.

 

Mounted through UD:

//192.168.0.15/backup /mnt/remotes/192.168.0.15_backup cifs ro,relatime,vers=3.1.1,cache=none,username=rysz,uid=99,forceuid,gid=100,forcegid,addr=192.168.0.15,file_mode=0777,dir_mode=0777,iocharset=utf8,hard,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=10,closetimeo=30 0 0

results in all transfers maxing out at 10MB/s.

 

Self-mounted with UD options, except cache=none:

//192.168.0.15/backup /mnt/remotes/192.168.0.15_backup cifs ro,relatime,vers=3.1.1,cache=strict,username=rysz,uid=99,forceuid,gid=100,forcegid,addr=192.168.0.15,file_mode=0777,dir_mode=0777,iocharset=utf8,hard,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=10,closetimeo=30 0 0

results in all transfers at full expectable speeds around 80-90MB/s.

 

I realize the cache=none flag has been unchanged in UD since 2021...

But were there any SMB changes that could result in this problems I'm having (.. on my hardware) ?

I'd use NFS but the performance on NFS is not ideal at 40MB/s, as opposed to the custom-mounted CIFS.

 

I found this post similar to my issue: https://www.truenas.com/community/threads/slow-samba-performance-with-cache-none-option-on-client.77369/. Which suggests that cache=strict is a sensible setting in regard to oplocks while preserving reasonable performance, and that also seems to be CIFS default since kernel 3.7...

 

6 minutes ago, Rysz said:

 

I realize the cache=none flag has been unchanged in UD since 2021...

But were there any SMB changes that could result in this problems I'm having (.. on my hardware) ?

I'd use NFS but the performance on NFS is not ideal at 40MB/s, as opposed to the custom-mounted CIFS.

I don't know of anything that has changed in Samba that would cause your issue with the 'cache' option, but I will investigate.

1 hour ago, Rysz said:

I realize the cache=none flag has been unchanged in UD since 2021...

The 'cache=none' parameter is used to insure consistency in data when multiple clients access the remote share at the same time.  There are other settings we can try, but we will have to be sure we don't sacrifice data consistency for speed.

 

Try the 'cache=strict' setting and see if the speed improves.  This is a middle ground between consistency and performance.

 

Let me know how that goes, and we can look at other options to see which works best for consistency and speed. 

 

EDIT: I learned that the setting for 'cache' is 'strict' when the 'cache=none' is removed.  I'm probably going to remove the 'cache=none' in the next release.  I'll do some testing.

23 minutes ago, dlandon said:

The 'cache=none' parameter is used to insure consistency in data when multiple clients access the remote share at the same time.  There are other settings we can try, but we will have to be sure we don't sacrifice data consistency for speed.

 

Try the 'cache=strict' setting and see if the speed improves.  This is a middle ground between consistency and performance.

 

Let me know how that goes, and we can look at other options to see which works best for consistency and speed. 

 

Thanks for getting back to me!

 

cache=strict is what the CIFS mount defaulted to when mounting it without setting cache=none, so this seems to be the kernel default in the Unraid kernel as well. So cache=strict has resulted in a 8x-10x speed increase from 10MB/s to 80-100MB/s for me, when compared to cache=none, which is equivalent to my maximum network throughput.

 

I have found some more posts on this issue, some dating back years, so this is possibly an issue with certain software/hardware combinations and Samba itself:

• https://ubuntuforums.org/showthread.php?t=2379232
• https://arstechnica.com/civis/threads/poor-samba-performance.1203625/
• https://forum.level1techs.com/t/baffled-by-samba-performance-and-variation-help/144418
• https://www.truenas.com/community/threads/slow-samba-performance-with-cache-none-option-on-client.77369/
• https://gitlab.gnome.org/GNOME/nautilus/-/issues/1973

Interesting is that it doesn't seem related to an increase in iowait, which seems equal with either caching mode.

 

I understand the point about data integrity and consistency. cache=strict, being the kernel default since 3.7, seems to be a relatively safe choice here when considering the amount of time it has been the kernel's default setting (and the - I'm guessing - somewhat common use case of having multiple clients using a Samba mount at the same time). But I'm by no means an expert on mount options or kernel issues...

 

Perhaps a configurable cache setting (strict/none/loose), possibly in combination with cache=strict as default or not, for CIFS mounts would be an idea or acceptable middle-ground for affected users like me? Personally I can patch this in manually on my system, but I'm just thinking into the direction of possibly less IT-experienced users who might run into this too (even if it seems to be a rare occurrence right now). 🙂 

 

On 1/21/2016 at 11:55 AM, dlandon said:

Unassigned Devices Best Practices

 

Here are some best practices I recommend when using unassigned devices.

 

• Don't share devices and SMB/NFS Shares unless necessary and enable SMB Security for user access when you do.
•  

This line makes no sense. Samba shares  on unassigned devices are meant to be shared. Or am I missing something? I find this comment ambiguous and confusing.

37 minutes ago, Vetteman said:

This line makes no sense. Samba shares  on unassigned devices are meant to be shared. Or am I missing something? I find this comment ambiguous and confusing.

Not really.  UD devices are used for all kinds of uses that do not involve sharing the disks with SMB or NFS:

• Backup disk.  I have a UD disk I use for Daily backups of my Unraid server.  I do not want this disk shared on the network.
• Periodic backup of the server to be stored off-site.  I do this Weekly and Monthly.  I do not want these disks shared on the network when installed to make a backup.
• Downloads and temporary processing.  UD disks are used for storing downloads and temporary data that users don't want shared on the network.
• Docker or Plugin data.  I have a security system Docker Container and a UD disk is used to store security camera video.  I do not want this shared on the network.

UD disks are used like an Array Pool device that can be mounted, unmounted, and removed/installed without shutting down the Array like you'd have to do with a Pool device.

 

The comment in the Best Practices is just a reminder that if you don't need to share devices with SMB, don't, and if you do enable user security to limit who has access to the UD disk.  Initially UD was set up to share everything as Public by default.  This was changed to require a user to enable security as needed for security.

Anyone know how to clear this line:

 

 

It says "Historical device is in standby" when i mouse over the green dot, but that device was removed from the system entirely. the remove button isn't enabled and cant be clicked.

9 hours ago, Vetteman said:

Or am I missing something?

What this option does is that remote share that is mounted in unraid gets reshared over samba by unraid as if it was physically on the unraid machine itself - usually not required since whatever else that needed access could connect to the place where it is directly. 

3 hours ago, Faceman said:

Anyone know how to clear this line:

 

 

It says "Historical device is in standby" when i mouse over the green dot, but that device was removed from the system entirely. the remove button isn't enabled and cant be clicked.

Click on the three gears icon and then click the 'Attach' button.  If the device is actually removed, the attach will time out and the message will go away.

That worked, it then considered the device disconnected and I was able to remove it with the red X.

 

Cheers.

Hi,

 

Is it save to click 'remove' button under 'Historical Unassigned Devices" since the listed devices is part of my array now?

 

1 hour ago, Muhamad Aidil Karim said:

Is it save to click 'remove' button under 'Historical Unassigned Devices" since the listed devices is part of my array now?

 

yes

3 hours ago, alturismo said:

yes

Thanks.

I am experiencing a behavior that was not present before and for the life of me, I can't figure out what.  I have 40 unassigned drives all formatted to XFS.  They are a mixture of SAS and SATA drives (SAS Spindown plug-in installed).  When all drives spin down, almost half of the drives have the "Reboot" grayed out button showing where you normally see the "Mount" / "Unmount" button.  The error log shows UnAssigned Device plug-in trying to mount with the error message saying the drives are already mounted.  The only way to fix this is to umount all the drives from command line and remount using the GUI.  But when the drives spindown, the same problem appears again.  This was never an issue before.  I have tried different backplanes, power supply, cables, drives, renaming the drives.  I can spinddown 39 out of the 40 drives.  As soon as the last drive tried to spindown (doesn't matter which order or what drive), the problem appears.  Anyone seeing this behavior?

 

7 hours ago, timc6896 said:

I am experiencing a behavior that was not present before and for the life of me, I can't figure out what.  I have 40 unassigned drives all formatted to XFS.  They are a mixture of SAS and SATA drives (SAS Spindown plug-in installed).  When all drives spin down, almost half of the drives have the "Reboot" grayed out button showing where you normally see the "Mount" / "Unmount" button.  The error log shows UnAssigned Device plug-in trying to mount with the error message saying the drives are already mounted.  The only way to fix this is to umount all the drives from command line and remount using the GUI.  But when the drives spindown, the same problem appears again.  This was never an issue before.  I have tried different backplanes, power supply, cables, drives, renaming the drives.  I can spinddown 39 out of the 40 drives.  As soon as the last drive tried to spindown (doesn't matter which order or what drive), the problem appears.  Anyone seeing this behavior?

 

Post ud_diagnostics by going to a command line and executing the command 'ud_diagnostics' and then post the '/flash/logs/ud_diagnostics.log file'.  Also post Unraid diagnostics.

So I'm a bit lost and I'm hoping for a little guidance.

 

A friend and I have set up a wireguard tunnel and an NFS share for offsite backups.

 

Server A and Server B are connected VIA wireguard, both servers are able to ping each other. Server B can connect to Server A's NFS share. Server A however cannot connect to Server B's share.

 

I've gone through everything I can think of but I cannot get the "LED" to turn green on Server A's end. Both servers have the same configuration. Both are running 6.12.13 along with the latest current release of 2024.10.02 for the plugin.

 

What's weird is, when going through to mount the NFS share I can see the share if I click the "load shares" button. Kinda lost as what to do next.

 

I can mount a local NFS share I spun up on a laptop for what's it worth.

 

Thanks,

Hey there,

 

i want to mount encrypted disks with UD without saving the passphrase.

I have read here that you should save the passphrase in the UD settings and delete it after mounting.
Unfortunately, I cannot find a way to delete the passphrase in the GUI!
 

It would be nice if after clicking on Mount you would be asked directly for the passphrase. 

 

Thanks

 

1 hour ago, HansOtto said:

Hey there,

 

i want to mount encrypted disks with UD without saving the passphrase.

I have read here that you should save the passphrase in the UD settings and delete it after mounting.
Unfortunately, I cannot find a way to delete the passphrase in the GUI!
 

It would be nice if after clicking on Mount you would be asked directly for the passphrase. 

 

Thanks

 

Go to the settings when the disk is unmounted and save a blank passphrase.  It will then be removed from UD.

2 hours ago, Nomaran said:

So I'm a bit lost and I'm hoping for a little guidance.

 

A friend and I have set up a wireguard tunnel and an NFS share for offsite backups.

 

Server A and Server B are connected VIA wireguard, both servers are able to ping each other. Server B can connect to Server A's NFS share. Server A however cannot connect to Server B's share.

 

I've gone through everything I can think of but I cannot get the "LED" to turn green on Server A's end. Both servers have the same configuration. Both are running 6.12.13 along with the latest current release of 2024.10.02 for the plugin.

 

What's weird is, when going through to mount the NFS share I can see the share if I click the "load shares" button. Kinda lost as what to do next.

 

I can mount a local NFS share I spun up on a laptop for what's it worth.

 

Thanks,

Be sure Server B has NFS enabled.  Try a clean reboot on Server B and see if it will work.

1 hour ago, dlandon said:

Go to the settings when the disk is unmounted and save a blank passphrase.  It will then be removed from UD.

 

Perfect, that is what i was looking for! Thanks for the quick answer.