So in your use case, you auto mount disks and then don't unmount them manually?

6 hours ago, dlandon said:

So in your use case, you auto mount disks and then don't unmount them manually?

Exactly, the disk is used in various containers (Nextcloud, Emby,...) as a cache, external storage and so on... that don't need redundant storage.

Sure I could also create a third Pool on my Server and use the disk there but I like UD for this usecase more.

 

If you don't integrate this I'm also fine with it, I only thought this might be useful to somebody else too...

This is what I've done:

 

 

Please note that the switch says "Disable Mount Button".  This means both mount and unmount.

 

 

I need to change the text in the tool tip to "DIsable Mount Button:.

6 hours ago, dlandon said:

This is what I've done:

 

 

Please note that the switch says "Disable Mount Button".  This means both mount and unmount.

This looks really good! Exactly what I was looking for.

6 hours ago, dlandon said:

This is what I've done:

 

 

Please note that the switch says "Disable Mount Button".  This means both mount and unmount.

 

 

I need to change the text in the tool tip to "DIsable Mount Button:.

Maybe it should be Buttons (plural)?

14 minutes ago, itimpi said:

Maybe it should be Buttons (plural)?

You mean like mount and unmount buttons or multiple devices buttons?  I consider the mount/unmount to be different modes of the 'mount' button and not necessarily just when iit says 'mount'.

26 minutes ago, ich777 said:

This looks really good! Exactly what I was looking for.

One of the other things I've done is to remove the clear disk and remove partition red X's when the destructive mode is enabled and this switch is on.  I have a Windows disk in my test server and I'm constantly afraid I'll remove a partition or clear the disk as I work with UD trying different things.  This keeps me from screwing up.

Are there official docs for this plugin?  I've mounted a couple of shares on my network, but in plex, those folders appear empty despite the fact they are not.  I did see a message about /mnt/remotes but I don't have that directory in my structure it appears.

 

I'd love some docs to read over.  I'm sure I've just overlooked something.

37 minutes ago, survivalbloke said:

in plex, those folders appear empty despite the fact they are not.  I did see a message about /mnt/remotes but I don't have that directory in my structure it appears.

Sounds like you haven't mapped them into the container 

Hi All,

 

Recently I mapped NFS shares from another Unraid server to use in some dockers on this server. That all seems good and working in dockers like I want.

 

 

However recently I tried doing some rsync of some files from Server 1 to Server 2 using this mapped share. Anyway it didn't seem to like that at all. CPUs were randomly and slowly filling up to 100% and not coming back. To the point it would just crash the Unraid UI or become super unresponsive. These files were old VMWare VMs, so some of the individual files were over 1tb. Not sure if that makes it different?

Anyway, it's are transferring just fine now in windows using UNC paths. After this one is done, i'll try another one in rsync and grab logs. I was seeing RED errors. Just forgot to save them. This was yesterday. Processor is a threadripper with 24 cores and 32 RAM.

Most of the time the server sits at 20% CPU and 40% RAM. But running rsync using those mapped shares and it goes crazy. Actually, I think I also tried in Krusader transfering the same files using the mapped shares again and krusader became unresponsive too and had to kill it.

 

So it crashed transferring like this:

rsync -rtvv /mnt/user/backups/EX1 /mnt/remotes/UR02_backups/EX1 --log-file=/mnt/user/Other/rsynclog.log --progress

I think some of the small files worked.

 

Currently transferring like this (Windows Explorer):

\\192.168.0.5\backups\EX1

\\192.168.0.8\backups\EX1

 

Maybe I have a config wrong somewhere, any ideas on what I should look at first?

Dockers seem OK using them.

 

Cheers

 

 

5 minutes ago, cappapp said:

Maybe I have a config wrong somewhere, any ideas on what I should look at first?

Are you using NFSv3 or NFSv4?

13 minutes ago, dlandon said:

Are you using NFSv3 or NFSv4?

How do I check?

Running UnRaid Version: 6.9.2

You'll be running NFSv3.  Go to the UD settings and you'll see the setting for NFS version.  You'll need 6.10 for NFSv4.

 

If you look at your log you'll probably see a lot of stale file handles.  When that happens, everything stops.  NFSv4 solves this and other issues.  NFSv3 is very troublesome and you shouldn't spend a lot of time trying to sort it out.  It's not worth it and you won't get anywhere.

 

How about using SMB for now?

37 minutes ago, dlandon said:

You'll be running NFSv3.  Go to the UD settings and you'll see the setting for NFS version.  You'll need 6.10 for NFSv4.

 

If you look at your log you'll probably see a lot of stale file handles.  When that happens, everything stops.  NFSv4 solves this and other issues.  NFSv3 is very troublesome and you shouldn't spend a lot of time trying to sort it out.  It's not worth it and you won't get anywhere.

 

How about using SMB for now?

Ah OK. That makes sense. No problem. I can work around this for now and revisit it later.

Funny enough, because the 2nd server is not my primary, it's already 6.10. I probably should keep them at the same version moving forward.

 

Thanks for the update.

I have noticed an error several times now when unmounting devices.

 

After I have unmounted my device cleanly in the main tab, many spin down messages are displayed in the syslog.
According to syslog it tries to spindown the device although it is not connected anymore.

 

Feb 19 12:49:05 nas emhttpd: spinning down /dev/sde
Feb 19 13:19:06 nas emhttpd: spinning down /dev/sde
Feb 19 13:49:07 nas emhttpd: spinning down /dev/sde
Feb 19 14:19:08 nas emhttpd: spinning down /dev/sde
Feb 19 14:49:09 nas emhttpd: spinning down /dev/sde
Feb 19 15:19:10 nas emhttpd: spinning down /dev/sde
Feb 19 15:49:11 nas emhttpd: spinning down /dev/sde
Feb 19 16:19:12 nas emhttpd: spinning down /dev/sde
Feb 19 16:49:13 nas emhttpd: spinning down /dev/sde
Feb 19 17:19:14 nas emhttpd: spinning down /dev/sde
Feb 19 17:49:15 nas emhttpd: spinning down /dev/sde
Feb 19 18:19:16 nas emhttpd: spinning down /dev/sde
Feb 19 18:49:17 nas emhttpd: spinning down /dev/sde
Feb 19 19:19:18 nas emhttpd: spinning down /dev/sde
Feb 19 19:49:19 nas emhttpd: spinning down /dev/sde
Feb 19 20:19:20 nas emhttpd: spinning down /dev/sde
Feb 19 20:49:21 nas emhttpd: spinning down /dev/sde
Feb 19 21:19:22 nas emhttpd: spinning down /dev/sde
Feb 19 21:49:23 nas emhttpd: spinning down /dev/sde

 

In the "Dashboard" tab the device is marked with status unassigned.

In the "Main" tab, however, the device is no longer visible, since it has already been removed.

 

Does anyone have an idea what this could be?

 

Edited February 21, 20224 yr by Anym001

Are you on the latest version of UD?   Can you post your diagnostics zip?

27 minutes ago, dlandon said:

Are you on the latest version of UD? 

 

Yes I am.

 

27 minutes ago, dlandon said:

Can you post your diagnostics zip?

 

I have sent it to you by PN.

Click on the double arrows in the upper right corner of the UD page and see if it clears it up.

1 hour ago, dlandon said:

Click on the double arrows in the upper right corner of the UD page and see if it clears it up.

Thank you, that helped.

UD informs Unraid whenever a device is hotplugged and Unraid re-organizes unassigned devices.  What you did by cliicking on the double arrows was to initiate that hotplug manully that UD didn't do.

 

This will be fixed in the next release.

On 2/18/2022 at 8:43 PM, trurl said:

Sounds like you haven't mapped them into the container 

That's exactly what I discovered.  I apologize for taking so long to come back to this as I've been overloaded at work.  Once I mapped them to /mnt/remotes (or I should say, once I figured out how to), all was well.  Thanks!

Hi,

 

Can anyone explain the grayed-out "ARRAY" label on my usb drive..

 

I had it plugged into a usb3 port but lsusb -t showed that its was in fact not usb (although marked blue) so i performed (using the unmount button on UD) to unmount it. Nothing wrong there.. The disk was unmounted and could be remounted using UD.

Then I removed the usb-disk and plugged it into a blue usb socketed on the back-plane of the motherboard.. Now lsusb -t shows that it is on a and usb3 hub, but I can no longer mount or unmount it - but it is accessible -

 

 

 

And here is a part of the unraid log:

Feb 22 16:04:35 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 22 16:04:35 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 4f 00 00 00
Feb 22 16:04:35 Tower kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb 22 16:04:35 Tower kernel: sda: sda1
Feb 22 16:04:35 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Feb 22 16:04:35 Tower rc.diskinfo[9404]: SIGHUP received, forcing refresh of disks info.
Feb 22 16:04:37 Tower unassigned.devices: Adding partition 'sda1'...
Feb 22 16:04:37 Tower unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/USB_DISC_4T'...
Feb 22 16:04:37 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'ext4' -o rw,noatime,nodiratime,nodev,nosuid '/dev/sda1' '/mnt/disks/USB_DISC_4T'
Feb 22 16:04:38 Tower kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Feb 22 16:04:38 Tower unassigned.devices: Successfully mounted 'sda1' on '/mnt/disks/USB_DISC_4T'.
Feb 22 16:04:38 Tower unassigned.devices: Adding SMB share 'USB_DISC_4T'.
Feb 22 16:04:54 Tower unassigned.devices: Refreshed Disks and Configuration.
Feb 22 16:04:54 Tower rc.diskinfo[9404]: SIGHUP received, forcing refresh of disks info.

 

 

Don't understand this line tho: "unassigned.devices: Adding SMB share 'USB_DISC_4T'."

 

I can browse the file and directories on it by clicking the label and is also accessable from the terminal.

 

Any idea's ?

 

 

10 minutes ago, sjoerd said:

Any idea's ?

This generally happens when a device is not recognized by Unraid as unassigned.  You can tell because the device designation is sda and not  'Dev X'.  Try clicking on the double arrows on the upper right hand part of the UD screen and see if that fixes it.  There is a bug in UD that may be causing this that is fixed in the next release.

Cannot find Unassigned Devices plugin in Apps tab search. Is it under a different name?

28 minutes ago, nathanarizona said:

Cannot find Unassigned Devices plugin in Apps tab search. Is it under a different name?

No. Post screenshot