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

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

Squid

March 12, 20251 yr

Try this. Under the sharing options, check off the user for the Mac to store windows creds in a less secure manner but which gives greater compatibility

Recommended by Squid

December 4, 20205 yr

Author

3 minutes ago, lzl20110 said:

The priority of'At Stopping of Array' does not seem to be high, and UNRAID still crashes

Post at the user scripts forum and see if that is the right point to apply the script. It may be too late in the sequence to do what you want.

Quote

Replies 11.9k
Views 2.1m
Created 10 yr10 yr
Last Reply Jun 26Jun 26

Popular Days

Posted Images

December 4, 20205 yr

1 minute ago, dlandon said:

Post at the user scripts forum and see if that is the right point to apply the script. It may be too late in the sequence to do what you want.

Ok,thank you very much.

Quote

December 4, 20205 yr

Author

1 minute ago, lzl20110 said:

Ok,thank you very much.

What you want is to have your script run before VMs and Dockers are shutdown.

Did you check the log to verify that the remote share unmounted properly?

Quote

December 4, 20205 yr

12 minutes ago, dlandon said:

您想要的是在关闭VM和Docker之前运行脚本。

您是否检查日志以验证远程共享是否已正确卸载？

Dec 4 20:17:33 Tower shutdown[8549]: shutting down for system reboot
Dec 4 20:17:33 Tower init: Switching to runlevel: 6
Dec 4 20:17:33 Tower init: Trying to re-exec init
Dec 4 20:17:34 Tower nginx: 2020/12/04 20:17:34 [alert] 5357#5357: *17132 open socket #22 left in connection 5
Dec 4 20:17:34 Tower nginx: 2020/12/04 20:17:34 [alert] 5357#5357: aborting
Dec 4 20:17:36 Tower kernel: mdcmd (37): nocheck cancel
Dec 4 20:17:37 Tower emhttpd: Spinning up all drives...
Dec 4 20:17:37 Tower kernel: mdcmd (38): spinup 1
Dec 4 20:17:38 Tower emhttpd: Stopping services...
Dec 4 20:17:38 Tower emhttpd: shcmd (270): /etc/rc.d/rc.libvirt stop
Dec 4 20:17:38 Tower root: Domain bef7c4dc-a168-460a-7902-cc1d6c9e8434 is being shutdown
Dec 4 20:17:38 Tower root:
Dec 4 20:19:09 Tower root: Waiting on VMs to shutdown..........................................................................................
Dec 4 20:19:09 Tower root: The following VMs are still running, forcing shutdown: DS3617
Dec 4 20:19:09 Tower kernel: sdc: sdc1 sdc2 sdc3
Dec 4 20:19:09 Tower kernel: sdd: sdd1 sdd2 sdd3
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'WDC_WD80EZAZ-11TDBA0_2YGU43JD', mountpoint 'WDC_WD80EZAZ-11TDBA0_2YGU43JD' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdc'.
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'TOSHIBA_MD04ABA400V_2814KSICFMYB', mountpoint 'TOSHIBA_MD04ABA400V_2814KSICFMYB-part2' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'TOSHIBA_MD04ABA400V_2814KSICFMYB', mountpoint 'TOSHIBA_MD04ABA400V_2814KSICFMYB' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdd'.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'WDC_WD80EZAZ-11TDBA0_2YGU43JD', mountpoint 'WDC_WD80EZAZ-11TDBA0_2YGU43JD-part2' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'WDC_WD80EZAZ-11TDBA0_2YGU43JD', mountpoint 'DiskStation:2' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdc'.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Dec 4 20:19:09 Tower root: Domain bef7c4dc-a168-460a-7902-cc1d6c9e8434 destroyed
Dec 4 20:19:09 Tower root:
Dec 4 20:19:09 Tower unassigned.devices: Disk with serial 'TOSHIBA_MD04ABA400V_2814KSICFMYB', mountpoint 'DiskStation:3' is not set to auto mount and will not be mounted.
Dec 4 20:19:09 Tower unassigned.devices: Issue spin down timer for device '/dev/sdd'.
Dec 4 20:19:11 Tower root: Stopping libvirtd...
Dec 4 20:19:11 Tower dnsmasq[5380]: exiting on receipt of SIGTERM
Dec 4 20:19:11 Tower kernel: device virbr0-nic left promiscuous mode
Dec 4 20:19:11 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state
Dec 4 20:19:11 Tower avahi-daemon[4087]: Interface virbr0.IPv4 no longer relevant for mDNS.
Dec 4 20:19:11 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Dec 4 20:19:11 Tower avahi-daemon[4087]: Withdrawing address record for 192.168.122.1 on virbr0.
Dec 4 20:19:11 Tower root: Network 2214f59d-018d-4270-9f9c-550be516a722 destroyed
Dec 4 20:19:11 Tower root:
Dec 4 20:19:15 Tower root: Stopping virtlogd...
Dec 4 20:19:16 Tower root: Stopping virtlockd...
Dec 4 20:19:17 Tower emhttpd: shcmd (271): umount /etc/libvirt
Dec 4 20:19:17 Tower root: Stopping docker_load
Dec 4 20:19:17 Tower emhttpd: shcmd (274): /etc/rc.d/rc.docker stop
Dec 4 20:19:19 Tower kernel: vetha23e6f8: renamed from eth0
Dec 4 20:19:19 Tower kernel: docker0: port 2(vethef2c3d8) entered disabled state
Dec 4 20:19:19 Tower avahi-daemon[4087]: Interface vethef2c3d8.IPv6 no longer relevant for mDNS.
Dec 4 20:19:19 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface vethef2c3d8.IPv6 with address fe80::903d:1ff:fe0c:fa9.
Dec 4 20:19:19 Tower kernel: docker0: port 2(vethef2c3d8) entered disabled state
Dec 4 20:19:19 Tower kernel: device vethef2c3d8 left promiscuous mode
Dec 4 20:19:19 Tower kernel: docker0: port 2(vethef2c3d8) entered disabled state
Dec 4 20:19:19 Tower avahi-daemon[4087]: Withdrawing address record for fe80::903d:1ff:fe0c:fa9 on vethef2c3d8.
Dec 4 20:19:27 Tower kernel: device br0 left promiscuous mode
Dec 4 20:19:27 Tower kernel: veth6edc14e: renamed from eth0
Dec 4 20:19:29 Tower kernel: veth90823b5: renamed from eth0
Dec 4 20:19:29 Tower kernel: docker0: port 1(veth81d9b4c) entered disabled state
Dec 4 20:19:30 Tower avahi-daemon[4087]: Interface veth81d9b4c.IPv6 no longer relevant for mDNS.
Dec 4 20:19:30 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface veth81d9b4c.IPv6 with address fe80::d8c2:86ff:fedb:92cc.
Dec 4 20:19:30 Tower kernel: docker0: port 1(veth81d9b4c) entered disabled state
Dec 4 20:19:30 Tower kernel: device veth81d9b4c left promiscuous mode
Dec 4 20:19:30 Tower kernel: docker0: port 1(veth81d9b4c) entered disabled state
Dec 4 20:19:30 Tower avahi-daemon[4087]: Withdrawing address record for fe80::d8c2:86ff:fedb:92cc on veth81d9b4c.
Dec 4 20:19:32 Tower root: stopping dockerd ...
Dec 4 20:19:33 Tower root: waiting for docker to die ...
Dec 4 20:19:34 Tower avahi-daemon[4087]: Interface docker0.IPv6 no longer relevant for mDNS.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface docker0.IPv6 with address fe80::42:f1ff:fe93:aac9.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Interface docker0.IPv4 no longer relevant for mDNS.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Withdrawing address record for fe80::42:f1ff:fe93:aac9 on docker0.
Dec 4 20:19:34 Tower avahi-daemon[4087]: Withdrawing address record for 172.17.0.1 on docker0.
Dec 4 20:19:34 Tower emhttpd: shcmd (275): umount /var/lib/docker
Dec 4 20:19:34 Tower Recycle Bin: Stopping Recycle Bin
Dec 4 20:19:34 Tower emhttpd: Stopping Recycle Bin...
Dec 4 20:19:34 Tower unassigned.devices: Unmounting All Devices...
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume2/videos' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/PT' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/downloads' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/关机/script" >/dev/null 2>&1
Dec 4 20:19:35 Tower emhttpd: shcmd (276): /etc/rc.d/rc.samba stop
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with Network is unreachable
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with No such device
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with Network is unreachable
Dec 4 20:19:35 Tower wsdd[13483]: udp_send: Failed to send udp packet with No such device
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Dec 4 20:19:35 Tower wsdd[13483]: Failed to send bye with No such device
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume2/videos' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/PT' is not mounted and cannot be unmounted.
Dec 4 20:19:35 Tower unassigned.devices: Remote SMB/NFS share '192.168.50.3:/volume1/downloads' is not mounted and cannot be unmounted.
Dec 4 20:19:36 Tower emhttpd: shcmd (277): rm -f /etc/avahi/services/smb.service
Dec 4 20:19:36 Tower avahi-daemon[4087]: Files changed, reloading.
Dec 4 20:19:36 Tower avahi-daemon[4087]: Service group file /services/smb.service vanished, removing services.
Dec 4 20:19:36 Tower emhttpd: Stopping mover...
Dec 4 20:19:36 Tower emhttpd: shcmd (279): /usr/local/sbin/mover stop
Dec 4 20:19:36 Tower root: mover: not running
Dec 4 20:19:36 Tower emhttpd: Sync filesystems...
Dec 4 20:19:36 Tower emhttpd: shcmd (280): sync
Dec 4 20:19:36 Tower emhttpd: shcmd (281): umount /mnt/user0
Dec 4 20:19:36 Tower emhttpd: shcmd (282): rmdir /mnt/user0
Dec 4 20:19:36 Tower emhttpd: shcmd (283): umount /mnt/user
Dec 4 20:19:36 Tower emhttpd: shcmd (284): rmdir /mnt/user
Dec 4 20:19:37 Tower emhttpd: shcmd (286): /usr/local/sbin/update_cron
Dec 4 20:19:37 Tower emhttpd: Unmounting disks...
Dec 4 20:19:37 Tower emhttpd: shcmd (287): umount /mnt/disk1
Dec 4 20:19:37 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:37 Tower emhttpd: shcmd (287): exit status: 32
Dec 4 20:19:37 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:42 Tower emhttpd: Unmounting disks...
Dec 4 20:19:42 Tower emhttpd: shcmd (288): umount /mnt/disk1
Dec 4 20:19:42 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:42 Tower emhttpd: shcmd (288): exit status: 32
Dec 4 20:19:42 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:47 Tower emhttpd: Unmounting disks...
Dec 4 20:19:47 Tower emhttpd: shcmd (289): umount /mnt/disk1
Dec 4 20:19:47 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:47 Tower emhttpd: shcmd (289): exit status: 32
Dec 4 20:19:47 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:52 Tower emhttpd: Unmounting disks...
Dec 4 20:19:52 Tower emhttpd: shcmd (290): umount /mnt/disk1
Dec 4 20:19:52 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:52 Tower emhttpd: shcmd (290): exit status: 32
Dec 4 20:19:52 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:19:57 Tower emhttpd: Unmounting disks...
Dec 4 20:19:57 Tower emhttpd: shcmd (291): umount /mnt/disk1
Dec 4 20:19:57 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:19:57 Tower emhttpd: shcmd (291): exit status: 32
Dec 4 20:19:57 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:20:02 Tower emhttpd: Unmounting disks...
Dec 4 20:20:02 Tower emhttpd: shcmd (292): umount /mnt/disk1
Dec 4 20:20:02 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:20:02 Tower emhttpd: shcmd (292): exit status: 32
Dec 4 20:20:02 Tower emhttpd: Retry unmounting disk share(s)...
Dec 4 20:20:06 Tower root: Status of all loop devices
Dec 4 20:20:06 Tower root: /dev/loop1: [2049]:4 (/boot/bzfirmware)
Dec 4 20:20:06 Tower root: /dev/loop2: [2305]:268435585 (/mnt/disk1/system/docker/docker.img)
Dec 4 20:20:06 Tower root: /dev/loop0: [2049]:3 (/boot/bzmodules)
Dec 4 20:20:06 Tower root: Active pids left on /mnt/*
Dec 4 20:20:06 Tower root: USER PID ACCESS COMMAND
Dec 4 20:20:06 Tower root: /mnt/disk1: root kernel mount /mnt/disk1
Dec 4 20:20:06 Tower root: /mnt/disks: root kernel mount /mnt/disks
Dec 4 20:20:06 Tower root: Active pids left on /dev/md*
Dec 4 20:20:06 Tower root: USER PID ACCESS COMMAND
Dec 4 20:20:06 Tower root: /dev/md1: root kernel mount /mnt/disk1
Dec 4 20:20:06 Tower root: Generating diagnostics...
Dec 4 20:20:07 Tower emhttpd: Unmounting disks...
Dec 4 20:20:07 Tower emhttpd: shcmd (293): umount /mnt/disk1
Dec 4 20:20:07 Tower root: umount: /mnt/disk1: target is busy.
Dec 4 20:20:07 Tower emhttpd: shcmd (293): exit status: 32
Dec 4 20:20:07 Tower emhttpd: Retry unmounting disk share(s)...

I'm very sorry, I don't understand these, I can only send it to you

Quote

December 4, 20205 yr

8 hours ago, dlandon said:

Your disk issues are probably a cable problem and that is why you don't see anything in the SMART report.

I now located the corresponding disk and changed cable and sata controller port. Message persists on reboot. I hope now it could be a controller issue. Should I post this in the forum? 😬

Of course that doesnt belong to this topic.

Edited December 4, 20205 yr by sauerm

Quote

December 4, 20205 yr

Author

1 minute ago, sauerm said:

I now located the corresponding disk and changed cable and sata controller port. Message persists on reboot. I hope now it could be a controller issue. Should I post this in the forum? 😬

I'll tag @JorgeB about this. He is the disk and controller expert.

Quote

December 4, 20205 yr

Thank you once more
glad here are so many experts willing to help new members.

Im really careful within this new topic so I really appreciate your support 👍

EDIT: Searched a bit and now guessing it would be a controller error
(reffering to this thread )

Edited December 4, 20205 yr by sauerm

Quote

December 4, 20205 yr

Author

New release 2020.112.04. One major feature is that starting with 6. Beta 38 (this was an internal test version), UD disk temperatures and disk spin down is handled by Unraid. The spin down delay of UD disks is now set by the Settings->DIsk Settings->Default Spin Down Delay. The disk temperature thresholds are set just the same as with an array disk. Versions earlier that 6.9 Beta 38 will have the spin down delay set by UD.

Release Notes:

All versions
- Issue with samba config file when a remote share has parenthesis in the share name. The mount was not shared properly because of the parenthesis in the share name.
- Php errors when UD disks, samba shares, or iso shares configuration parsing fails and an array is not created.

Legacy Unraid
- The 'Spin Down Disks?' setting in the UD settings was not being used.
- Encrypted disks not checked properly for spin down status.

Startig with Unraid 6.9 Beta 38
- Unraid will manage temperature monitoring and spin down control.
- You can view and change disk attributes (temperature thresholds) per disk.
- Mount remote shares at /mnt/remotes with symlinks in /mnt/disks for backwards compatibility.

- Number of reads and writes per disk are displayed. Earlier versions will show all zeros.

If you map remote shares in VMs or Docker Containers, symlinks to the remote shares at /mnt/remotes are created at /mnt/disks so you shouldn't have to make any changes to your mappings. One word of caution though is you may have to map a share and be sure there is a trialing '/'. If you mapped /mnt/disks/RemoteShare, you may need to change it to /mnt/disks/RemoteShare/ so the symlink will appear as a directory and not a file. This is dependent on how the VM or Docker treats the mapping.

Edited December 5, 20205 yr by dlandon

Quote

December 4, 20205 yr

10 hours ago, dlandon said:

Post at the user scripts forum and see if that is the right point to apply the script. It may be too late in the sequence to do what you want.

It runs at stopping_svcs

Quote

December 4, 20205 yr

8 minutes ago, dlandon said:

The disk temperature thresholds are set just the same as with an array disk.

👍👍👍🎉🎉🎉🎉

Quote

December 4, 20205 yr

Author

3 minutes ago, Squid said:

It runs at stopping_svcs

Is there an event in user scripts that will run a script before the VMs and Dockers are stopped?

Edited December 4, 20205 yr by dlandon

Quote

December 4, 20205 yr

User scripts only supports disks_mounted and stopping_svcs For anything else the user would have to create the appropriate folder in /usr/local/..... and toss the script in there either via go or user script at array start (one time)

Quote

December 4, 20205 yr

Author

1 minute ago, Squid said:

User scripts only supports disks_mounted and stopping_svcs For anything else the user would have to create the appropriate folder in /usr/local/..... and toss the script in there either via go or user script at array start (one time)

Yea, I suspected that. That's too late for what he wants to do.

Quote

December 4, 20205 yr

It is on the never ending bucket list to have it support any event.

Quote

December 5, 20205 yr

2 hours ago, dlandon said:

- Mount remote shares at /mnt/remotes with symlinks in /mnt/disks for backwards compatibility.

Maybe add an option to not create the symlink for those that don't need the backwards compatibility. Not a big deal but it bothers my OCD seeing redundant folders. 🤪

Quote

December 5, 20205 yr

not sure what is going on but existing SMB mounts are mounting with just some directory listings - showing 1.5mb in the disk space bar and files are not appearing - after the latest update.

Edited December 5, 20205 yr by cferra

Quote

December 5, 20205 yr

Author

7 minutes ago, cferra said:

not sure what is going on but existing SMB mounts are mounting with just some directory listings - showing 1.5mb in the disk space bar and files are not appearing - after the latest update.

I need more information. What version of Unraid? Where are you seeing the directory listings and files not appearing? Show a screen shot.

Quote

December 5, 20205 yr

sure its unraid 6.9.0-beta 35 - there are folders in the directories, i had to recreate the shares with different names on the windows server shares for them to appear, but I can not for the synology shares that I am trying to also connect to.

This worked on the previous version.

Edited December 5, 20205 yr by cferra

Quote

December 5, 20205 yr

is there a way to roll back to the last version?

Quote

December 5, 20205 yr

Author

6 minutes ago, cferra said:

sure its unraid 6.9.0-beta 35 - there are folders in the directories, i had to recreate the shares with different names on the windows server shares for them to appear, but I can not for the synology shares that I am trying to also connect to.

This worked on the previous version.

Unmount the share and then remount it. It is browsing the symlink at /mnt/disks. The actual mount point is at /mnt/remotes

Quote

December 5, 20205 yr

Author

Just now, cferra said:

is there a way to roll back to the last version?

No.

Quote

December 5, 20205 yr

it will not let me unmount -

I get this error..

Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Mount SMB share '//MEDIAVAULT/Media' using SMB default protocol.
Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Media' '//MEDIAVAULT/Media' '/mnt/remotes/MEDIAVAULT_Media'
Dec 4 22:28:30 FERRANTEAPP1 kernel: CIFS: Attempting to mount //MEDIAVAULT/Media
Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Successfully mounted '//MEDIAVAULT/Media' on '/mnt/remotes/MEDIAVAULT_Media'.
Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Adding SMB share 'MEDIAVAULT_Media'.
Dec 4 22:28:38 FERRANTEAPP1 unassigned.devices: Removing Remote SMB/NFS share '//MEDIAVAULT/Media'...
Dec 4 22:28:38 FERRANTEAPP1 unassigned.devices: Unmounting Remote SMB/NFS Share '//MEDIAVAULT/Media'...
Dec 4 22:28:38 FERRANTEAPP1 unassigned.devices: Cannot unmount '//MEDIAVAULT/Media'. UD did not mount the device.

I also recreated the mounts inside the ui and it did not work - still get the same thing.

Quote

December 5, 20205 yr

Author

1 minute ago, cferra said:

it will not let me unmount -

I get this error..

Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Mount SMB share '//MEDIAVAULT/Media' using SMB default protocol.
Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Media' '//MEDIAVAULT/Media' '/mnt/remotes/MEDIAVAULT_Media'
Dec 4 22:28:30 FERRANTEAPP1 kernel: CIFS: Attempting to mount //MEDIAVAULT/Media
Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Successfully mounted '//MEDIAVAULT/Media' on '/mnt/remotes/MEDIAVAULT_Media'.
Dec 4 22:28:30 FERRANTEAPP1 unassigned.devices: Adding SMB share 'MEDIAVAULT_Media'.
Dec 4 22:28:38 FERRANTEAPP1 unassigned.devices: Removing Remote SMB/NFS share '//MEDIAVAULT/Media'...
Dec 4 22:28:38 FERRANTEAPP1 unassigned.devices: Unmounting Remote SMB/NFS Share '//MEDIAVAULT/Media'...
Dec 4 22:28:38 FERRANTEAPP1 unassigned.devices: Cannot unmount '//MEDIAVAULT/Media'. UD did not mount the device.

I also recreated the mounts inside the ui and it did not work - still get the same thing.

Reboot the server.

Quote

December 5, 20205 yr

did - same thing.. it will auto mount - not work properly and then will not let me unmount, i have to stop auto mount to be able to remove it.

i mean I'll try it again.

Edited December 5, 20205 yr by cferra

Quote

December 5, 20205 yr

Author

1 minute ago, cferra said:

did - same thing.. it will auto mount - not work properly and then will not let me unmount, i have to stop auto mount to be able to remove it.

i mean I'll try it again.

Post diagnostics.

Quote

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.

Followers

Go to topic listing

Replies 11.9k
Views 2.1m
Created 10 yr10 yr
Last Reply Jun 26Jun 26

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

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

dlandon

dlandon

dlandon

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

dlandon

dlandon

dlandon

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)