Jump to content

Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

dlandon

By dlandon
in Plugin Support

Recommended Posts

Recommended

Posted by dlandon,

If you are seeing unexplained disk or remote share activity, it may be due to cache dirs caching all folders.  For those of you using the Cache Dirs plugin, you need to specify folders to be included so UD mounted disks and shares do not get included automatically.  This can also apply to pool disks.  It's really the best practice to specify the included folders so you control what is actually being cached.
Recommended by Squid

0 reactions

Go to this post
Recommended

Posted by dlandon,

New release of UD.  The changes are: - Add ability to spin down a disk by sdX.  You don't have to spin down disks by name= any more.  This is still available for spinning down a disk from a User Script because you won't know the correct sdX as it changes on reboot. - Add the ability to detach a disk when a UD script is finished using 'rc.unassigned'.  This detaches the disk from Unraid and should provide a potentially safer way to remove a USB device.  Applies to USB disks only. -
Recommended by SpencerJ
  • Upvote
  • Like

2 reactions

Go to this post
Recommended

Posted by dlandon,

There is a new feature in UD to help with plugins that need a mount point folder.  UD now creates a mount folder '/mnt/addons'.  This folder should be used to mount your plugin devices to prevent FCP warnings and keep your mounts separated from UD.  It is recommended you switch to this new folder for your addon and custom mounts.  You are welcome to leave the mounts at '/mnt/disks' or '/mnt/remotes'.  Things will still work, but if you request support for UD issues, you will be asked to remove t

UD is now creating a mount point folder for plugins and addons

Recommended by dlandon

0 reactions

Go to this post
Recommended

Posted by dlandon,

The recent changes to the way UD checks for remote servers being online were done to eliminate the inappropriate way UD was managing remote server names trying to get around local DNS name lookup issues.  The way it works now is using several methods to lookup server names after an IP address is found to have an open SMB or NFS port when searching for servers.  Nmblookup and avahi are used to find the names.  The issue comes when UD tries to verify the server is online with the servername and no
Recommended by dlandon

0 reactions

Go to this post
  • Replies 10.8k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

dlandon
dlandon

It's that self healing feature I built into UD.  It just fixes itself.

dlandon
dlandon

New release of UD.  Changes: When changing the mount point (which is also the share name), the mount point is checked for a duplicate of a user share or another UD device.  Samba cannot handle

dlandon
dlandon

Major new release of UD: "Where are the switches?"  The "Pass Through", "Read Only", "Automount", and "Share" switches have been moved to a new Edit Settings dialog.  This is also where the sc

Posted Images

dlandon Veteran

dlandon

Posted
  • Author
Posted
2 minutes ago, Splash said:

s there an option to set the mounting attributes? Eg remove ,default_permissions,noatime etc

No.

 

I'm trying to understand what the backup software is having trouble with so I can potentially change the mount parameters.  It looks to be with the atime and not mtime.

 

Mount the disk manually with this command line and see if the backup software works without the warning: 

/sbin/mount -t 'ntfs' -o rw,relatime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdm1' '/mnt/disks/Primary'

 

Note the 'relatime' option.

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
2 minutes ago, Splash said:

Any thoughts on adding the option to modify the mount attributes?

This is not a good idea and will lead to more support as most users will not fully understand what the mount options do.  I'm going to change the 'noatime,nodiratime' to 'relatime'.  This should solve your backup software issues.

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
6 minutes ago, dopeytree said:

Is it possible to build in a feature to hide any more than 5 'historical devices'?

 

I'm reluctant to 'remove' them as I may want to re-use a certain disk in future.

There is a switch at the top of the UD page to hide all Historical Devices.  I encourage you to use that.

Link to comment
resentedpoet Noob

resentedpoet

Posted
Posted

Hi everyone, 

 

I recently discovered and started using Unassigned Devices to mount my other unraid server's NAS volume as a remove share for Jellyfin. Everything was working fine until I had to shutdown and reboot my servers and now UD is won't mount my network share stating it is unavailable; and the mount button is greyed out and I cannot even try to click to mount it. 

 

What am I doing wrong? At first I thought it was because my remote share server started up later than the server that has UD installed on it but when I rebooted that server again thinking it would autoconnect after startup; it didn't. 

 

image.thumb.png.917dd80129657ccb4cca967f07072689.png

 

- Cheers,

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
4 minutes ago, resentedpoet said:

Hi everyone, 

 

I recently discovered and started using Unassigned Devices to mount my other unraid server's NAS volume as a remove share for Jellyfin. Everything was working fine until I had to shutdown and reboot my servers and now UD is won't mount my network share stating it is unavailable; and the mount button is greyed out and I cannot even try to click to mount it. 

 

What am I doing wrong? At first I thought it was because my remote share server started up later than the server that has UD installed on it but when I rebooted that server again thinking it would autoconnect after startup; it didn't. 

 

image.thumb.png.917dd80129657ccb4cca967f07072689.png

 

- Cheers,

Post diagnostics.

  • Like 1
Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
5 minutes ago, Johann said:

So I keep a pre cleared sata drive connected in my system in case I need to replace a disk. Am I able to prevent it from spinning up by using the detach option and attaching it back when I need it? Thanks!

Yes.  The good thing is it's powered off too.

  • Like 1
Link to comment
hawihoney Proficient

hawihoney

Posted
Posted

Since 6.12.4 (coming from 6.11.5) I do have trouble to copy files over SMB remotes. It doesn't make a difference if I copy from Unraid barebone to Unraid VM or between two Unraid VMs. I always see the following errors and the system stalls. I do have to kill the sessions to free the systems from this.

 

The error (example): 

Tower unassigned.devices: Warning: shell_exec(/bin/df '/mnt/remotes/192.168.178.101_disk1' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10s!

 

Remote SMB is registered like this: 

/usr/local/sbin/rc.unassigned mount //192.168.178.101/disk1

 

On 6.11.5 this was never a problem.

 

Diagnostics attached.

 

Thanks in advance.

 

tower-diagnostics-20230910-1528.zip

Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
11 minutes ago, hawihoney said:

I do have to kill the sessions to free the systems from this.

 

It looks to me that you are pushing your system too much.  You have 22 individual disks mounted on two servers.  44 mounts total and many disks at 100% used: 

//192.168.178.102/disk1   5.5T  5.5T   20G 100% /mnt/remotes/192.168.178.102_disk1
//192.168.178.102/disk2   5.5T  5.5T   10G 100% /mnt/remotes/192.168.178.102_disk2
//192.168.178.102/disk3   5.5T  5.5T   13G 100% /mnt/remotes/192.168.178.102_disk3
//192.168.178.102/disk4   5.5T  5.5T   20G 100% /mnt/remotes/192.168.178.102_disk4
//192.168.178.102/disk5   5.5T  5.5T   22G 100% /mnt/remotes/192.168.178.102_disk5
//192.168.178.102/disk6   5.5T  5.5T   13G 100% /mnt/remotes/192.168.178.102_disk6
//192.168.178.102/disk7   5.5T  5.5T   36G 100% /mnt/remotes/192.168.178.102_disk7
//192.168.178.102/disk8   5.5T  5.5T  9.1G 100% /mnt/remotes/192.168.178.102_disk8
//192.168.178.102/disk9   5.5T  5.5T   13G 100% /mnt/remotes/192.168.178.102_disk9
//192.168.178.102/disk10  5.5T  5.5T   12G 100% /mnt/remotes/192.168.178.102_disk10
//192.168.178.102/disk11  5.5T  5.5T  8.3G 100% /mnt/remotes/192.168.178.102_disk11
//192.168.178.102/disk12  5.5T  5.5T   13G 100% /mnt/remotes/192.168.178.102_disk12
//192.168.178.102/disk13  5.5T  5.5T   30G 100% /mnt/remotes/192.168.178.102_disk13
//192.168.178.102/disk14  5.5T  5.5T   33G 100% /mnt/remotes/192.168.178.102_disk14
//192.168.178.102/disk15  5.5T  5.5T   30G 100% /mnt/remotes/192.168.178.102_disk15
//192.168.178.102/disk16  5.5T  5.5T   13G 100% /mnt/remotes/192.168.178.102_disk16
//192.168.178.102/disk17  5.5T  5.5T   14G 100% /mnt/remotes/192.168.178.102_disk17
//192.168.178.102/disk18  5.5T  5.5T   30G 100% /mnt/remotes/192.168.178.102_disk18
//192.168.178.102/disk19  5.5T  5.5T   11G 100% /mnt/remotes/192.168.178.102_disk19
//192.168.178.102/disk20  5.5T  5.5T   20G 100% /mnt/remotes/192.168.178.102_disk20
//192.168.178.102/disk21  5.5T  5.5T   25G 100% /mnt/remotes/192.168.178.102_disk21
//192.168.178.102/disk22  5.5T  5.5T   17G 100% /mnt/remotes/192.168.178.102_disk22
//192.168.178.101/disk1    17T   17T  206G  99% /mnt/remotes/192.168.178.101_disk1
//192.168.178.101/disk2    17T   16T  458G  98% /mnt/remotes/192.168.178.101_disk2
//192.168.178.101/disk3   5.5T  5.4T  139G  98% /mnt/remotes/192.168.178.101_disk3
//192.168.178.101/disk4    17T   17T   73G 100% /mnt/remotes/192.168.178.101_disk4
//192.168.178.101/disk5    17T   17T   51G 100% /mnt/remotes/192.168.178.101_disk5
//192.168.178.101/disk6    17T   17T  183G  99% /mnt/remotes/192.168.178.101_disk6
//192.168.178.101/disk7    17T   17T  6.7G 100% /mnt/remotes/192.168.178.101_disk7
//192.168.178.101/disk8    17T   17T   17G 100% /mnt/remotes/192.168.178.101_disk8
//192.168.178.101/disk9   5.5T  5.4T   66G  99% /mnt/remotes/192.168.178.101_disk9
//192.168.178.101/disk10   17T   17T  119G 100% /mnt/remotes/192.168.178.101_disk10
//192.168.178.101/disk11   17T   17T   17G 100% /mnt/remotes/192.168.178.101_disk11
//192.168.178.101/disk12  5.5T  5.3T  208G  97% /mnt/remotes/192.168.178.101_disk12
//192.168.178.101/disk13   17T   17T   61G 100% /mnt/remotes/192.168.178.101_disk13
//192.168.178.101/disk14   17T   17T   39G 100% /mnt/remotes/192.168.178.101_disk14
//192.168.178.101/disk15  5.5T  5.5T   16G 100% /mnt/remotes/192.168.178.101_disk15
//192.168.178.101/disk16   17T   17T   15G 100% /mnt/remotes/192.168.178.101_disk16
//192.168.178.101/disk17  5.5T  5.5T   39G 100% /mnt/remotes/192.168.178.101_disk17
//192.168.178.101/disk18  5.5T  5.5T   48G 100% /mnt/remotes/192.168.178.101_disk18
//192.168.178.101/disk19   17T   15T  2.0T  89% /mnt/remotes/192.168.178.101_disk19
//192.168.178.101/disk20   17T  7.3T  9.1T  45% /mnt/remotes/192.168.178.101_disk20
//192.168.178.101/disk21  5.5T  5.4T   64G  99% /mnt/remotes/192.168.178.101_disk21
//192.168.178.101/disk22   17T   17T   69G 100% /mnt/remotes/192.168.178.101_disk22

UD has to do a 'df' on 44 mount points.  All this over a one 1GB NIC (you are only using eth0) using SMB?  Why don't you use root shares instead of mounting each and every disk separately?  That would be one 'df' per server.

 

The 'df' timeout could be extended in UD, but that would just stop the log messages about the command taking too long.

 

You might try the following:

  • Use a Root Share instead of individual disk mounts.
  • Switch to NFS remote shares.  It may be faster and avoid this issue.
  • Cut down on the simultaneous disk mounts.  Only do a few at a time.  Why remote mount all disks?  You can't write to disks that are 100% used.
  • Use both your NICs.  Bond your two NICs using one of the balancing modes - like 'balance-alb' that doesn't require switch configuration.
33 minutes ago, hawihoney said:

The error (example): 

Tower unassigned.devices: Warning: shell_exec(/bin/df '/mnt/remotes/192.168.178.101_disk1' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 10s!

 

This is not the causing the stalling; it is an effect of the system stalling.

Link to comment
OmegaCrit Noob

OmegaCrit

Posted
Posted (edited)

I'm relatively new to Unraid, having started using it just yesterday, so it's possible I made a mistake somewhere. I was using Unassigned Devices to mount some old HDDs and transfer their data. Everything was working fine until I received a notification about a new update. After updating, I've encountered an issue – I can no longer mount the drive I was using just an hour ago.

Where the mount button is typically located, there's now a greyed-out "UDEV" with a crossed-out circle next to it. I'm unsure how to proceed in fixing this problem.

htpc-diagnostics-20230910-1649.zip

Edited by OmegaCrit
Diagnostics
Link to comment
dlandon Veteran

dlandon

Posted
  • Author
Posted
1 minute ago, OmegaCrit said:

I'm relatively new to Unraid, having started using it just yesterday, so it's possible I made a mistake somewhere. I was using Unassigned Devices to mount some old HDDs and transfer their data. Everything was working fine until I received a notification about a new update. After updating, I've encountered an issue – I can no longer mount the drive I was using just an hour ago.

Where the mount button is typically located, there's now a greyed-out "UDEV" with a crossed-out circle next to it. I'm unsure how to proceed in fixing this problem.

Post diagnostics.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing
×
×
  • Create New...