Hi All -

 

I had a working setup where I had 3 external drives mounted to my server with UD and that were being shared successfully over netowork (SMB and NFS). Something changed and now I can not mount the UD devices on my *nix (Manjaro) machine. I have fully explained the situation here:

 

 

I was directed there to come over here with my question. Any help appreciated as my system is severely handicapped right now.

 

I have a problem, mine remote share mounts are most of the times not shown. only after a reboot of the server then maybe I'm lucky sometimes.

 

is there a fix for this, I already reinstalled the plugin and deleted all files from UD, but still no luck. 

also I've seen an error when changing settings and saving it. 

1.

 

2.

3.

i cannot mount the ud "WD_my_book", because i don't have a mount button. Instead there is a greyed out "Partition" Button. What does it mean ? What i need to mount the usb device ?
Thanks in advance.

my one unraid server running 7.0.1  when you have and ssd shoved in for removable it automaticlly goes  grayed out mount...  if you do a reboot of the computer when you log back in  its still grayed out  not sure whats going on?  any logs tell ya anything

 

and on my main server i found my one 5TB  drive  shows up and sometimes disappears  and i dont see anything in the logs as i also rebooted and sometimes come back  it just hides itself in the historical area.. ill get diagnostics when it happens again

 

 

mitchsserver-diagnostics-20250411-2005.zip

 

Edited April 12, 20251 yr by comet424

1 hour ago, testomat said:

"Partition" Button. What does it mean ?

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

 

Mount Button Indicators

 

Disks

In order to point out to users normal operation and situations that may prevent UD from operating on a disk device properly, the 'Mount' button will show some greyed out text that indicates status on the disk.  If the text shows with the not symbol, the disk is in an error conndition.

• 'MOUNT' or 'UNMOUNT' - when the 'Mount' button shows either of these grayed out, the 'Disable Mount Button' switch is on.  This situation lets UD do auto mount and unmount, but operator actions are not permitted.  Theere are occasions when these indicators are grayed out because of disk drive issues.
• 'PASSED' - This indicates the 'Passed Through' switch is set.  This is used to tell UD that a VM or Docker Container is using the disk and for UD to not manage the disk in any way.
• 'PRECLEAR' - The UD Preclear or binhex Preclear Docker is preclearing the disk.
• 'POOL' - This is used to indicate that a disk is part of a BTRFS pool.
• 'PARTITION' - This will show when a disk is detected that has a file system but no partition.  UD cannot mount a disk in this situation.  If it is a disk introduced to UD that you want to use in UD, you can clear the disk and reformat it for use with UD.
• 'ARRAY' - This indicates that a disk has not been detected by Unraid as an Unassigned Device and UD thinks the disk is a part of the array.  This generally happens when an array disk drops from the array.
• 'UDEV' - UD has detected that the disk format reported by udev does not match the format as reported by lsblk.  This can sometimes be rectified by clicking on the double arrows on the UD UI to refresh the udev data in UD.
• 'REBOOT' - This shows when UD has detected a disk was probably removed before being unmounted and then re-installed.  The best way to clear this up is to reboot.  If this happens because of several disks having the same mount point, unmount the disk with this mount point and change mount points on all disks to be unique.

  

is there a temp fix  to make a drive mountable  so i can copy files to it..  since no fix yet   is there a command line  that i can run that force it to mount  as id like to be able to copy files to a removable hot swap drive  but right now i cant  since its locked me out 

im guessing it lost its partition table..  i found the disk log i guess it lost its ntfs  is reason  its grayed out i guess?

```

Apr 13 08:05:24 mitchsserver kernel: ata5: SATA max UDMA/133 abar m131072@0xfce80000 port 0xfce80300 irq 52
Apr 13 08:05:24 mitchsserver kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 13 08:05:24 mitchsserver kernel: ata5.00: ATA-11: WDC  WDS100T2B0A-00SM50, 401020WD, max UDMA/133
Apr 13 08:05:24 mitchsserver kernel: ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
Apr 13 08:05:24 mitchsserver kernel: ata5.00: Features: Dev-Sleep
Apr 13 08:05:24 mitchsserver kernel: ata5.00: configured for UDMA/133
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Write Protect is off
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
Apr 13 08:05:24 mitchsserver kernel: sdc: sdc1
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Apr 13 08:07:34 mitchsserver emhttpd: online: WDC_WDS100T2B0A-00SM50_200802A003DE (sdc) 512 1953525168
Apr 13 08:07:37 mitchsserver emhttpd: read SMART /dev/sdc
Apr 13 08:07:59 mitchsserver unassigned.devices: Partition '/dev/sdc1' does not have a file system and cannot be mounted.
Apr 13 08:22:59 mitchsserver emhttpd: spinning down /dev/sdc
Apr 13 09:56:25 mitchsserver emhttpd: read SMART /dev/sdc
Apr 13 10:11:26 mitchsserver emhttpd: spinning down /dev/sdc
Apr 13 17:42:46 mitchsserver emhttpd: spinning up /dev/sdc
Apr 13 17:42:46 mitchsserver emhttpd: read SMART /dev/sdc

```

 

gonna format and see if it fixes itself

 

Greetings,

Is there any chance of making the initial display of historical devices optional? So that it doesn't show by default at startup?

 

Thanks

Toggle this off.

 

On 4/13/2025 at 11:44 PM, comet424 said:

im guessing it lost its partition table..  i found the disk log i guess it lost its ntfs  is reason  its grayed out i guess?

```

Apr 13 08:05:24 mitchsserver kernel: ata5: SATA max UDMA/133 abar m131072@0xfce80000 port 0xfce80300 irq 52
Apr 13 08:05:24 mitchsserver kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Apr 13 08:05:24 mitchsserver kernel: ata5.00: ATA-11: WDC  WDS100T2B0A-00SM50, 401020WD, max UDMA/133
Apr 13 08:05:24 mitchsserver kernel: ata5.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
Apr 13 08:05:24 mitchsserver kernel: ata5.00: Features: Dev-Sleep
Apr 13 08:05:24 mitchsserver kernel: ata5.00: configured for UDMA/133
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Write Protect is off
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
Apr 13 08:05:24 mitchsserver kernel: sdc: sdc1
Apr 13 08:05:24 mitchsserver kernel: sd 5:0:0:0: [sdc] Attached SCSI disk
Apr 13 08:07:34 mitchsserver emhttpd: online: WDC_WDS100T2B0A-00SM50_200802A003DE (sdc) 512 1953525168
Apr 13 08:07:37 mitchsserver emhttpd: read SMART /dev/sdc
Apr 13 08:07:59 mitchsserver unassigned.devices: Partition '/dev/sdc1' does not have a file system and cannot be mounted.
Apr 13 08:22:59 mitchsserver emhttpd: spinning down /dev/sdc
Apr 13 09:56:25 mitchsserver emhttpd: read SMART /dev/sdc
Apr 13 10:11:26 mitchsserver emhttpd: spinning down /dev/sdc
Apr 13 17:42:46 mitchsserver emhttpd: spinning up /dev/sdc
Apr 13 17:42:46 mitchsserver emhttpd: read SMART /dev/sdc

```

 

gonna format and see if it fixes itself

 

 I have this peoblem too

@DanielMayers for me i got it to work i had to re format the drive.. somehow unraid or UD plugin or just a freak of nature the SSD lost its partition  lucky  i didnt have anything on it..  but for me i didnt know  and i do not know if it will loose it again but thats what i found  i had to click the X to clear the disk and re format it..  but unclear how it lost the partition as it is a automount and script i have auto dismounts after copying  so  its not like pulling the drive while its running..  it gets unmounted.. so very confused  but its working again but who knows when or howlong till the next time.. but thats how i was able to get it back to working

i'm on 7.1 rc1 and on UD 2025.04.14, UD plus 2025.02.14, and UD preclear 2025.02.25 and got these errors in syslog, might not be important but hadn't seen them prior that i remember

23 minutes ago, jcofer555 said:

 

35 minutes ago, trurl said:

 

thanks made post on the release thread

I have created a ROOT SMB share with UD, and have set read-only access to a single user in the UD settings page.  On every single reboot, the user permissions are set back to No Access.   I checked /boot/config/plugins/unassigned.devices/unassigned.devices.cfg and see smb_backups="read-only" at the end of the file, but all smb_ lines disappear on reboot.

 

How can I make the user access stick across reboots?

 

unRAID 7.0.1

UD 2025.04.14 

 

I am confused Grok is telling me that I can mount rclone drives to unassigned devices, is this possible? If so how? I dont seem to have that option in my GUI:

You need to mount via the (presumably) rclone plugin

I have been using UD with tail scale on my main machine and a remote machine to use Duplicati for years without issue until recently. The share is supposed to auto mount but it does not. When I click mount I get an error and in the syslog I get the following. I am on 7.0.0 and have been since before this. Any idea? Nothing turning up for that error code I can find. 

 

Apr 26 15:05:46 WOLF kernel: CIFS: VFS: cifs_mount failed w/return code = -95
Apr 26 15:05:46 WOLF unassigned.devices: SMB mount failed: 'mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)'.
Apr 26 15:05:46 WOLF unassigned.devices: Remote Share '//xxx.xx.xx.111/offsitebackup' failed to mount.

 

7.1.0 rc3 with unassigned devices version 2025.04.14 installed the add pool and add subpool popup screens don't display text correctly like shown in the screenshots. i have attached diagnostics as well

tower-diagnostics-20250426-1506.zip

Originally posted in NFS section, before I found this thread

==============================================

  On 1/22/2025 at 5:17 PM, dlandon said:

It is rcommended that you use the Unassigned Devices Plugin (UD) to manage remote NFS shares.  If you use fstab, you have to be sure to set up the mount parameters correctly to maintain a robust connection.  UD is optimized to manage the remote connection for robustness, and when the Unraid array is started and stopped.

==============================================

I used to create scripts back in the early 6.x days such as

mkdir /mnt/tower3disk1 
mount -t nfs tower3:/mnt/disk1/ /mnt/tower3disk1 
rsync -av --stats --progress /mnt/disk1/ /mnt/tower3disk1/

 

Today the mount part of the script fails either with server name or with IP address.  I used your UD to NFS mount the share on the other server and was able to rsyc as per the example above.  Is there a way to access the UD mounting via script so that unattended backups can still be done?  (use case is for a backup server that isn't running most of the time)

Edited May 6, 20251 yr by tr0910

Hello i have upgraded to the latest 7.1.2 , somehow the plugin doesnt want to mount my 8tb xfs disk that i have for downloading torrents , i dont know if this issue has been reported but rolling back seem to have fixed the issue for now. 

16 minutes ago, shremi said:

Hello i have upgraded to the latest 7.1.2 , somehow the plugin doesnt want to mount my 8tb xfs disk that i have for downloading torrents , i dont know if this issue has been reported but rolling back seem to have fixed the issue for now. 

Do you see the mount button? If not, post the output from

wipefs /dev/sdX

Replace X with the correct disk, and this must be from 7.1, since it may be different with previous kernels, and note that it won't wipe anything as written.

Hi Guys,

I have mounted a few SMB Shares served by my old QNAP NAS. The shares are visible in remotes, I can browse them without issue.
Now I wanted to make those mount points available to a docker container.
But I can't see the remotes "folder" in the path selection UI. What am I missing? Just used my sonarr docker for demonstation purposes. It is the same across all my containers, no matter if they are privileged or not. The remotes are not shown in my containers path selection UI.

21 minutes ago, RcTomcat said:

The remotes are not shown in my containers path selection UI.

What unraid version? There was an issue with that a few versions ago that's been fixed.

Also for such mounts make sure to click the Edit button and switch the access mode to the "slave" version.  

Thank you for your reply. Version is 7.0.0 2025-01-09.
I can't seem to find the slave access mode, could you point me in the right direction please?