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


Recommended Posts

1 hour ago, Alchemist Zim said:

I see several issues:

Your network is dropping offline:

May 27 21:19:39 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
May 27 21:27:57 TESSERACT webGUI: Successful login user root from 192.168.10.201
May 27 21:30:02 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
May 27 21:38:22 TESSERACT kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Down
May 27 21:38:22 TESSERACT kernel: bond0: (slave eth0): link status definitely down, disabling slave
May 27 21:38:22 TESSERACT kernel: device eth0 left promiscuous mode
May 27 21:38:22 TESSERACT kernel: bond0: now running without any active interface!
May 27 21:38:22 TESSERACT kernel: br0: port 1(bond0) entered disabled state
May 27 21:38:31 TESSERACT kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
May 27 21:38:31 TESSERACT kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex
May 27 21:38:31 TESSERACT kernel: bond0: (slave eth0): making interface the new active one

 

Remove the rootshare from your smb-extra.conf and set up a UD rootshare.  Setting shares in smb-extra.conf can cause problems because settings in smb-extra.conf are supposed to be global settings, not share settings.

Link to comment

removed rootshare from smb-extra.conf, and added via UD rootshare...

i see the network drops on that day, but none for today or any other time i have the drive mounted

could it be that the drive has some internal power off function that is not controllable, which is causing this error.  it seems to happen every 10 minutes

It's a WD My Book 25EE

Jun  2 18:10:31 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:20:54 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:29:54 TESSERACT  emhttpd: spinning down /dev/sda
Jun  2 18:31:16 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:39:36 TESSERACT  emhttpd: spinning down /dev/sdq
Jun  2 18:39:36 TESSERACT  emhttpd: spinning down /dev/sdp
Jun  2 18:40:53 TESSERACT  emhttpd: spinning down /dev/sdd
Jun  2 18:40:55 TESSERACT  emhttpd: spinning down /dev/sde
Jun  2 18:40:55 TESSERACT  emhttpd: spinning down /dev/sdf
Jun  2 18:40:55 TESSERACT  emhttpd: spinning down /dev/sdc
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdm
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdk
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdg
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdn
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdo
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdl
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdi
Jun  2 18:41:39 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:51:53 TESSERACT  emhttpd: spinning down /dev/sdj
Jun  2 18:52:01 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:00:07 TESSERACT  emhttpd: read SMART /dev/sda
Jun  2 19:02:24 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:12:47 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:23:09 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:26:50 TESSERACT  emhttpd: read SMART /dev/sdq
Jun  2 19:27:03 TESSERACT  emhttpd: read SMART /dev/sdp
Jun  2 19:30:08 TESSERACT  emhttpd: spinning down /dev/sda
Jun  2 19:33:32 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:35:07 TESSERACT  emhttpd: read SMART /dev/sda
Jun  2 19:43:54 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:51:42 TESSERACT  emhttpd: read SMART /dev/sdj
Jun  2 19:51:50 TESSERACT  emhttpd: read SMART /dev/sdm
Jun  2 19:52:03 TESSERACT  emhttpd: read SMART /dev/sdd
Jun  2 19:52:03 TESSERACT  emhttpd: read SMART /dev/sdn
Jun  2 19:52:03 TESSERACT  emhttpd: read SMART /dev/sdo
Jun  2 19:52:20 TESSERACT  emhttpd: read SMART /dev/sdf
Jun  2 19:52:27 TESSERACT  emhttpd: read SMART /dev/sdg
Jun  2 19:54:17 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 20:04:40 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 20:05:08 TESSERACT  emhttpd: spinning down /dev/sda

 

Edited by Alchemist Zim
Link to comment
1 hour ago, Alchemist Zim said:

removed rootshare from smb-extra.conf, and added via UD rootshare...

i see the network drops on that day, but none for today or any other time i have the drive mounted

could it be that the drive has some internal power off function that is not controllable, which is causing this error.  it seems to happen every 10 minutes

It's a WD My Book 25EE

Jun  2 18:10:31 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:20:54 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:29:54 TESSERACT  emhttpd: spinning down /dev/sda
Jun  2 18:31:16 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:39:36 TESSERACT  emhttpd: spinning down /dev/sdq
Jun  2 18:39:36 TESSERACT  emhttpd: spinning down /dev/sdp
Jun  2 18:40:53 TESSERACT  emhttpd: spinning down /dev/sdd
Jun  2 18:40:55 TESSERACT  emhttpd: spinning down /dev/sde
Jun  2 18:40:55 TESSERACT  emhttpd: spinning down /dev/sdf
Jun  2 18:40:55 TESSERACT  emhttpd: spinning down /dev/sdc
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdm
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdk
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdg
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdn
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdo
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdl
Jun  2 18:40:57 TESSERACT  emhttpd: spinning down /dev/sdi
Jun  2 18:41:39 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 18:51:53 TESSERACT  emhttpd: spinning down /dev/sdj
Jun  2 18:52:01 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:00:07 TESSERACT  emhttpd: read SMART /dev/sda
Jun  2 19:02:24 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:12:47 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:23:09 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:26:50 TESSERACT  emhttpd: read SMART /dev/sdq
Jun  2 19:27:03 TESSERACT  emhttpd: read SMART /dev/sdp
Jun  2 19:30:08 TESSERACT  emhttpd: spinning down /dev/sda
Jun  2 19:33:32 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:35:07 TESSERACT  emhttpd: read SMART /dev/sda
Jun  2 19:43:54 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 19:51:42 TESSERACT  emhttpd: read SMART /dev/sdj
Jun  2 19:51:50 TESSERACT  emhttpd: read SMART /dev/sdm
Jun  2 19:52:03 TESSERACT  emhttpd: read SMART /dev/sdd
Jun  2 19:52:03 TESSERACT  emhttpd: read SMART /dev/sdn
Jun  2 19:52:03 TESSERACT  emhttpd: read SMART /dev/sdo
Jun  2 19:52:20 TESSERACT  emhttpd: read SMART /dev/sdf
Jun  2 19:52:27 TESSERACT  emhttpd: read SMART /dev/sdg
Jun  2 19:54:17 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 20:04:40 TESSERACT kernel: CIFS: VFS: \\DA-HIVEMIND\Backups (at Grimoire) error -9 on ioctl to get interface list
Jun  2 20:05:08 TESSERACT  emhttpd: spinning down /dev/sda

 

What does the UD page show when this is happening?

Link to comment

First off, apologies if this has been addressed. When I finally found an error to search for that appeared unique, I got no hits in the thread.

 

I would like to mount a micro sd card formatted by the Steam Deck. This would allow me an easy way to read/write to it from my primary, Windows workstation. This use case rules out a reformat as a solution.

 

When I try to mount the partition the plugin processes for a little bit, but when it completes the partition is not mounted and the mount button is still available.

 

Turning on the Udev log I see the following:

Jun  3 11:21:15 finarfin unassigned.devices: Partition found with the following attributes: serial_short='201606271856', device='/dev/sdj1', serial='Generic-_USB3.0_CRW-SD_201606271856-0:2', uuid='0a93b999-b1fa-4f02-ad29-230f6bb55249', part='1', disk='/dev/sdj', label='Generic- USB3.0_CRW-SD', disk_label='', fstype='ext4', mountpoint='/mnt/disks/Generic-_USB3.0_CRW-SD', luks='', pass_through='', mounted='', not_unmounted='', pool='', disable_mount='', target='', size='0', used='0', avail='0', owner='user', read_only='', shared='1', command='', user_command='', command_bg='', prog_name='', logfile=''
Jun  3 11:21:15 finarfin unassigned.devices: Mounting partition 'sdj1' at mountpoint '/mnt/disks/Generic-_USB3.0_CRW-SD'...
Jun  3 11:21:15 finarfin unassigned.devices: Mount cmd: /sbin/mount -t 'ext4' -o rw,noatime,nodiratime,nodev,nosuid '/dev/sdj1' '/mnt/disks/Generic-_USB3.0_CRW-SD'
Jun  3 11:21:15 finarfin kernel: EXT4-fs (sdj1): Filesystem with casefold feature cannot be mounted without CONFIG_UNICODE
Jun  3 11:21:18 finarfin unassigned.devices: Mount of 'sdj1' failed: 'mount: /mnt/disks/Generic-_USB3.0_CRW-SD: wrong fs type, bad option, bad superblock on /dev/sdj1, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call. '
Jun  3 11:21:18 finarfin unassigned.devices: Partition 'Generic- USB3.0_CRW-SD' cannot be mounted.

 

It looks like the casefold feature is the is the root cause of the failure, but I am not familiar with it. A casual google search suggests that CONFIG_UNICODE is a kernel flag that needs to be enabled. Can someone confirm or correct my analysis? Do I need to open an Unraid feature request to address this?

Edited by aburgesser
Link to comment

Hi, Guys:

 

I tried to mount an ISO file from the disk but got nowhere to go. I have the Unassigned plugin installed and I can mount the remote SMB without issue. However when I click "ADD ISO FILE SHARE", a pop up page appeared asking me to choose iso file. I clicked it but got a draw down menu with nothing, as below. 

 

Is there anything I've missed? All disks are started already. 

image.thumb.png.f6235490b739eb4e12d9184139534987.png

Link to comment

hi i know it used to work.. the rootshare  but it wont let me access it.. i used to hardcode it when it booted up  from the spaceinvader video... and then i went the rootshare mount in the ud  page...  

 

and it used to work.. in past it worked on and off.. now it wont.. its mounted...  but i cant access it.. tried share button doesnt help

 

and cant unmount it either... here is a diagnostic... what i need to do to get the root share to work..

 

and i use  root  as rootshare is reserverd or something

 

tardis-diagnostics-20230604-1027.zip

Link to comment
10 minutes ago, comet424 said:

hi i know it used to work.. the rootshare  but it wont let me access it.. i used to hardcode it when it booted up  from the spaceinvader video... and then i went the rootshare mount in the ud  page...  

check the UD settings page, under SMB settings

I had to enable SMB Sharing, and set permissions for my user

the path is not going to be "rootshare" its going to be whatever name you gave it

ex...share named homebase

\\SERVER\homebase - should work

\\SERVER\rootshare - doesn't work

 

Edited by Alchemist Zim
added example
Link to comment
7 hours ago, eddie_bear said:

Hi, Guys:

 

I tried to mount an ISO file from the disk but got nowhere to go. I have the Unassigned plugin installed and I can mount the remote SMB without issue. However when I click "ADD ISO FILE SHARE", a pop up page appeared asking me to choose iso file. I clicked it but got a draw down menu with nothing, as below. 

 

Is there anything I've missed? All disks are started already. 

image.thumb.png.f6235490b739eb4e12d9184139534987.png

ISO files have to be in an isos share.

Link to comment

i used to access it like  \\tardis\root     or \\192.168.0.3\root      now i know it used to work.. and then there was  a while ago it stopped working then worked again now its not working  

i know when i did the old way   you did it hardcoded 

i did  rootshare  and my user name that was linked to the rootshare so i used to do

 

\\tardis\rootshare

\\192.168.0.3\rootshare    

but you can no longer do rootshare its reserved.  so i do root...  but its not allowing it

 

and the diagnastic shows you cant even unmount it  so its stuck 

Link to comment
1 hour ago, comet424 said:

i used to access it like  \\tardis\root     or \\192.168.0.3\root      now i know it used to work.. and then there was  a while ago it stopped working then worked again now its not working  

i know when i did the old way   you did it hardcoded 

i did  rootshare  and my user name that was linked to the rootshare so i used to do

 

\\tardis\rootshare

\\192.168.0.3\rootshare    

but you can no longer do rootshare its reserved.  so i do root...  but its not allowing it

 

and the diagnastic shows you cant even unmount it  so its stuck 

You mounted it at user.root:

Jun  4 10:23:47 Tardis unassigned.devices: Mounting Remote Share '//TARDIS/mnt/user0'...
Jun  4 10:23:47 Tardis unassigned.devices: Mount ROOT command: /sbin/mount -o rw --bind '/mnt/user0' '/mnt/rootshare/user.root'
Jun  4 10:23:47 Tardis unassigned.devices: Successfully mounted '/mnt/user0' on '/mnt/rootshare/user.root'.

You would access the root share at //TARDIS/user.root.

 

It won't unmount because someone or something is accessing //TARDIS/user.root:

Jun  4 10:26:49 Tardis unassigned.devices: Unmount of 'user0' failed: 'umount: /mnt/rootshare/user.root: target is busy.

It's busy.

Link to comment

Hello:

I encountered the following issue while mounting SMB from 2023.06.02 to 2023.05.06. If there's a Non-ASCII code in the path name, it will be corrupted by safe_name($string,false.'$share_name = true') in UTF-8 coding.

 

For instance:
[//192.168.1.1/文件]
protocol = "SMB"
ip = "192.168.1.1"
path = "文件"
share = "文件"

 

This cannot be correctly mounted.
To correct this, modify the function get_samba_mounts() in lib.php:
Replace $string = safe_name($device, false, true); ==> $string = safe_name($device, false, false);
Replace $mount['share'] = safe_name($mount['share'], false, true) ?? ""; ==> $mount['share'] = safe_name($mount['share'], false, false) ?? "";.

Link to comment
24 minutes ago, andyjy12 said:

Hello:

I encountered the following issue while mounting SMB from 2023.06.02 to 2023.05.06. If there's a Non-ASCII code in the path name, it will be corrupted by safe_name($string,false.'$share_name = true') in UTF-8 coding.

 

For instance:
[//192.168.1.1/文件]
protocol = "SMB"
ip = "192.168.1.1"
path = "文件"
share = "文件"

 

This cannot be correctly mounted.
To correct this, modify the function get_samba_mounts() in lib.php:
Replace $string = safe_name($device, false, true); ==> $string = safe_name($device, false, false);
Replace $mount['share'] = safe_name($mount['share'], false, true) ?? ""; ==> $mount['share'] = safe_name($mount['share'], false, false) ?? "";.

I believe this has been fixed.  Renove the remote share and add it back again.

Link to comment

Hi.

I ran into this problem. There is a shared resource on Windows Server. I mount remote directory in Unraid via plugin, I specify (IP, USER, PASS, DOMEN) directory is mounted and everything is fine. But... If for some reason connection to remote directory disappears (or to remote server) then directory can't be mounted itself and in log it will be like this

 

Jun  4 04:18:22 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:24 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:24 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:24 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:24 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:25 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:25 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:26 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:26 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:27 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:27 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:27 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:27 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:29 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:29 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:29 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:29 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:31 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:31 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:31 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:31 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:32 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:32 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13
Jun  4 04:18:32 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun  4 04:18:32 kernel: CIFS: VFS: \\IP_ADDRESS Send error in SessSetup = -13

 

The only way to solve this is to manually remount the directory.

 

Also. Maybe there is a ready-made script for user-scripts that automatically mounts the directory, makes a backup via rsync and unmounts the directory?

Link to comment
11 hours ago, dlandon said:

ISO files have to be in an isos share.

Why is there that filter? Been annoying me several time to have to copy a file that's already somewhere else to the isos share for no apparent good reason.

Edited by Kilrah
Link to comment
7 hours ago, ScreN said:

 

Also. Maybe there is a ready-made script for user-scripts that automatically mounts the directory, makes a backup via rsync and unmounts the directory?

This is the best way to handle this situation.  Mount the remote share, backup files, then unmount the remote share.  There is no User Script that I know of that will do what you want, but it is not hard.  If you turn on the Help while on the UD page, you can see the commands needed to mount and unmount the remote share.  You can add a script to User Scripts on a cron to run at a specific time, or add the script to the Remote Share in UD that will run when it is mounted.  The script would look something like this:

/usr/local/sbin/rc.unassigned mount source

rsync

/usr/local/sbin/rc.unassigned umount source

 

The source is "//Tower/remote share" for a SMB remote share.

 

The issue you are running into is the downside of remote shares.  Your network and remote server have to be very robust and reliable to maintain the connection.  Both CIFS and NFS have these issues.  There is little recovery that I've found except to unmount and remount the remote share.

  • Like 1
Link to comment
2 hours ago, Kilrah said:

Why is there that filter? Been annoying me several time to have to copy a file that's already somewhere else to the isos share for no apparent good reason.

Historically ISOs are downloaded for use with a VM and are stored in the isos share.  For security reasons, UD limits the ISO selections to the isos share.  I don't think copying an ISO file is that difficult.  The Unraid file browser makes it very easy.

Link to comment

@dlandon  i never mounted it as  user.root

it says add a rootshare name i typed in   "root"  not "user.root"  so how do i erase the user part..

 

and i noticed that for a while too..  when you create root share it adds user on front  why is it doing that?

 

and nothing is using it  its just stuck  i cant unmount it ill have to do a reboot..  and i cant add a 2nd rootshare name as it says  user0 is already being used

Link to comment
2 minutes ago, comet424 said:

it says add a rootshare name i typed in   "root"  not "user.root"  so how do i erase the user part..

When you set up a user share, 'user' or 'user-pool' is added to the mount point to distinguish between all shares and pool devices ('user-pool') and just user shares ('user').  Click on the Mount Point for the share and change the Mount Point to anything you'd like that is not a reserved name.

 

5 minutes ago, comet424 said:

and nothing is using it  its just stuck  i cant unmount it ill have to do a reboot..

When it won't unmount because the share is busy, something is using it.  A PC having the share open in a browser or a terminal having the /mnt/rootshare/user.root open will prevent an unmount.

 

7 minutes ago, comet424 said:

and i cant add a 2nd rootshare name as it says  user0 is already being used

Only one root share for 'user0' is allowed.  The same for 'user'.  Why do you need two?

Link to comment

ah ok.  as i know it used to work  \\tardis\root   but ill do that as i was having issues  mounting the share.. so i deleted it and re added it...  and still couldnt access it   .. ill try renaming it

 

ya nothing access user.root  so reason i dunno why it was stuck..   i did do  like share the root share  so figured that might do it.. as i never knew youd access it as  \\tardis\user.root      all i used to do was \\tardis\root   

so i wonder if the error in the logs locked it

 

as for the 2nd rootshare  i dont need a 2nd..  its just that the Button  "add rootshare"  isnt grayed out after making 1   so i was able to click it and try to make a 2nd one to bypass the root one i couldnt unmount

 

but i was able to change the root name from user.root..  how come they add the user on front?

 

and you couldnt see in my logs its driving me nuts and no one in general forums answered it

 

why do  i get 1000 of these... its making me nuts i making sure all browsers closed gui for unraid.. i check everything but its making me nuts...  i do a clean reboot.. and then a few min after logging in it just starts up  with this  


Jun  5 09:30:40 Tardis nginx: 2023/06/05 09:30:40 [error] 11796#11796: *2130 limiting requests, excess: 20.612 by zone "authlimit", client: 192.168.0.227, server: , request: "PROPFIND /login HTTP/1.1", host: "tardis"

 

tardis-diagnostics-20230605-0931.zip

Link to comment
3 hours ago, comet424 said:

why do  i get 1000 of these... its making me nuts i making sure all browsers closed gui for unraid.. i check everything but its making me nuts...  i do a clean reboot.. and then a few min after logging in it just starts up  with this  

I suggest you post that in the general support section.

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.