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


dlandon

5983 posts in this topic Last Reply

Recommended Posts

17 minutes ago, anylettuce said:

is it unassigned devices that allows network shares to be mounted? I had a few then just disappeared. I did update the plugin.

43 minutes ago, dlandon said:

Post diagnostics.

 

 

Link to post
  • Replies 6k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

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

While I appreciate your interest in esthetics, there is more to consider than just 'aligning' disk drive mounts: This disk is mounted without a UD script, it is probably better to put it in th

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

6 hours ago, anylettuce said:

is it unassigned devices that allows network shares to be mounted? I had a few then just disappeared. I did update the plugin.

Ye it is my plugin is up to date, might hold on doing anything with the drives until i update to 6.9

Link to post

I'm on the 6.9. - RC 2 and just read the info Please remove Unassigned Devices first before upgrading to 6.9-rc1 and then re-install via Community Apps.

But i allready updatet to the RC2 without remove/install UD.. can i do this now or is it to late? Sorry for my english and this question..didn't found an answer here.

Link to post
9 hours ago, Olympus_Media said:

They were NTFS, im not bothered about 2 of the drives but one i am. 

 

I can get two of the drives to show in UD but they wont mount and throw that error and the 3rd (the one im bothered about) wont even show up in UD

You are having a lot of USB errors.

Jan  6 00:37:18 Olympus kernel: usb 1-3: device descriptor read/64, error -71
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:19 Olympus kernel: usb 1-3: new high-speed USB device number 4 using xhci_hcd
Jan  6 00:37:19 Olympus kernel: usb 1-3: device descriptor read/64, error -71
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:20 Olympus kernel: usb usb1-port3: attempt power cycle
Jan  6 00:37:20 Olympus kernel: usb 1-3: new high-speed USB device number 5 using xhci_hcd
Jan  6 00:37:25 Olympus kernel: usb 1-3: Device not responding to setup address.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:30 Olympus kernel: usb 1-3: device not accepting address 5, error -71
Jan  6 00:37:31 Olympus kernel: usb 1-3: new high-speed USB device number 6 using xhci_hcd
Jan  6 00:37:36 Olympus kernel: usb 1-3: Device not responding to setup address.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:41 Olympus kernel: usb 1-3: device not accepting address 6, error -71
Jan  6 00:37:41 Olympus kernel: usb usb1-port3: unable to enumerate USB device
Jan  6 00:37:42 Olympus kernel: usb usb1-port5: Cannot enable. Maybe the USB cable is bad?
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:43 Olympus kernel: usb usb1-port5: attempt power cycle
Jan  6 00:37:45 Olympus kernel: usb usb1-port5: Cannot enable. Maybe the USB cable is bad?

 

Link to post
8 hours ago, anylettuce said:

is it unassigned devices that allows network shares to be mounted? I had a few then just disappeared. I did update the plugin.

Yes, but they do not get removed unless you delete them.

Link to post
1 hour ago, Slaytanic said:

I'm on the 6.9. - RC 2 and just read the info Please remove Unassigned Devices first before upgrading to 6.9-rc1 and then re-install via Community Apps.

But i allready updatet to the RC2 without remove/install UD.. can i do this now or is it to late? Sorry for my english and this question..didn't found an answer here.

If you updated UD to the latest version, you are good to go.

Link to post
41 minutes ago, dlandon said:

You are having a lot of USB errors.


Jan  6 00:37:18 Olympus kernel: usb 1-3: device descriptor read/64, error -71
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:19 Olympus kernel: usb 1-3: new high-speed USB device number 4 using xhci_hcd
Jan  6 00:37:19 Olympus kernel: usb 1-3: device descriptor read/64, error -71
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:20 Olympus kernel: usb usb1-port3: attempt power cycle
Jan  6 00:37:20 Olympus kernel: usb 1-3: new high-speed USB device number 5 using xhci_hcd
Jan  6 00:37:25 Olympus kernel: usb 1-3: Device not responding to setup address.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:30 Olympus kernel: usb 1-3: device not accepting address 5, error -71
Jan  6 00:37:31 Olympus kernel: usb 1-3: new high-speed USB device number 6 using xhci_hcd
Jan  6 00:37:36 Olympus kernel: usb 1-3: Device not responding to setup address.
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:41 Olympus kernel: usb 1-3: device not accepting address 6, error -71
Jan  6 00:37:41 Olympus kernel: usb usb1-port3: unable to enumerate USB device
Jan  6 00:37:42 Olympus kernel: usb usb1-port5: Cannot enable. Maybe the USB cable is bad?
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan  6 00:37:43 Olympus kernel: usb usb1-port5: attempt power cycle
Jan  6 00:37:45 Olympus kernel: usb usb1-port5: Cannot enable. Maybe the USB cable is bad?

 

Yes i noticed that was me last night trying to get the drive to show in UD. Any suggestion on what i can do?

Link to post
2 hours ago, dlandon said:
11 hours ago, anylettuce said:

is it unassigned devices that allows network shares to be mounted? I had a few then just disappeared. I did update the plugin.

Yes, but they do not get removed unless you delete them.

I don't even have the option now to mount any network shares.

Link to post

With the recent changes, my remote SMB shares are no longer automounting.  I clicked the edit settings icon and then toggle AUTOMOUNT to on.  This didn't automount the SMB share after a reboot.  I tried adding a new SMB share with automount turned on but that didn't automount after a reboot.  I can manually mount the SMB shares.

 

I also notice that if I place my mouse over the settings icon, it correctly displays that the AUTOMOUNT toggle is on.  But the SHARE toggle is incorrectly displayed as on.

image.png.39fd432a72383f4f35dbf58b493f7139.png

 

image.png.1bfd572c064083513d7037e7f4ae309d.png

ajax-diagnostics-20210106-0925.zip

Link to post
1 hour ago, niwmik said:

With the recent changes, my remote SMB shares are no longer automounting.  I clicked the edit settings icon and then toggle AUTOMOUNT to on.  This didn't automount the SMB share after a reboot.  I tried adding a new SMB share with automount turned on but that didn't automount after a reboot.  I can manually mount the SMB shares.

 

I also notice that if I place my mouse over the settings icon, it correctly displays that the AUTOMOUNT toggle is on.  But the SHARE toggle is incorrectly displayed as on.

image.png.39fd432a72383f4f35dbf58b493f7139.png

 

image.png.1bfd572c064083513d7037e7f4ae309d.png

ajax-diagnostics-20210106-0925.zip 72.44 kB · 0 downloads

Your network is not available:

Jan  6 09:15:07 Ajax unassigned.devices: Cannot 'Auto Mount' Remote Shares.  Network not available!

UD waits for 30 seconds after the array has started to wait for the network to be available before mounting remote shares.  Apparently it is taking longer than that on your system.

 

The shares switch issue will be fixed in the next release.

Link to post
On 12/4/2020 at 5:11 AM, dlandon said:

I am releasing a new version of UD today that should stop those php errors.

 

What I meant was take the USB flash drive to a Windows computer and check the file system using Windows.

After you last update everything seemed to be working fine.  Today however I noticed drive was not accessible again.  When checking the log I see this.

36241426_Screenshot2021-01-07at10_40_16PM.thumb.png.7f334eacf9bddf93032bbd1862e1d5e4.png

Link to post
6 hours ago, jluna said:

After you last update everything seemed to be working fine.  Today however I noticed drive was not accessible again.  When checking the log I see this.

36241426_Screenshot2021-01-07at10_40_16PM.thumb.png.7f334eacf9bddf93032bbd1862e1d5e4.png

Those errors are caused by a config file problem.  Post diagnostics.

Link to post

I am very new to unraid, so this might be the incorrect place but I was having an issue using UD to mount a Windows share into unraid.

I am running version 6.8.3 of unraid, btw, with the latest version of UD (2021.01.01).

 

I was able to successfully add a remote SMB share with the required credentials and navigated to the correct shares and confirmed the share. The Mount button is enabled, but when I click it, nothing happens. The error message in the system log is as follows:

Jan 8 13:09:39 Tower kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Jan 8 13:09:39 Tower kernel: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jan 8 13:09:39 Tower kernel: CIFS VFS: Send error in SessSetup = -13
Jan 8 13:09:39 Tower kernel: CIFS VFS: cifs_mount failed w/return code = -13

 

I have gone in and changed the smb-extra conf file, even the /etc/samba/smb.conf file to add min protocol = SMB2 but none of that worked.

Am I missing something?

 

 

Link to post
1 hour ago, dbzeag said:

I am very new to unraid, so this might be the incorrect place but I was having an issue using UD to mount a Windows share into unraid.

I am running version 6.8.3 of unraid, btw, with the latest version of UD (2021.01.01).

 

I was able to successfully add a remote SMB share with the required credentials and navigated to the correct shares and confirmed the share. The Mount button is enabled, but when I click it, nothing happens. The error message in the system log is as follows:

Jan 8 13:09:39 Tower kernel: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
Jan 8 13:09:39 Tower kernel: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jan 8 13:09:39 Tower kernel: CIFS VFS: Send error in SessSetup = -13
Jan 8 13:09:39 Tower kernel: CIFS VFS: cifs_mount failed w/return code = -13

 

I have gone in and changed the smb-extra conf file, even the /etc/samba/smb.conf file to add min protocol = SMB2 but none of that worked.

Am I missing something?

 

 

That looks like a credentials issue.  Do you use any special characters in the credentials?

Link to post
15 minutes ago, dlandon said:

That looks like a credentials issue.  Do you use any special characters in the credentials?

I do have a ^ character in the password. It is successful logging in to list the shares.

Link to post
53 minutes ago, dlandon said:

That looks like a credentials issue.  Do you use any special characters in the credentials?

Even with a different account that does not have unusual characters is still having an issue.

Link to post
Quote

 

Hi, I'm having problems getting an external SSD to mount using UD and UD+.

 

The drive is formatted using Apple's APFS file system. The EFI partition mounts however, the APFS partition will not.  I've played with UD settings selecting Legacy Mount Point Compatibility? to on and off with no help. I've also checked my Docker settings for binhex-krusader and RW/slave is selected. Having said all that, I can see from my web GUI that the APFS volume is not mounted.

 

I've spent a fair bit of time googling for a fix to no avail, any help appreciated.

 

tower-diagnostics-20210109-1104.zip drives.pdf

Link to post
3 hours ago, Kevlar75 said:

The drive is formatted using Apple's APFS file system.

I am not sure if UD supports this - I have only seen references to HFS+ in its description.

Link to post
35 minutes ago, itimpi said:

I am not sure if UD supports this - I have only seen references to HFS+ in its description.

Correct, UD (and almost every other OS/addon out there) has little or no support for APFS. Blame it on Apple as it's apparently quite the paperwork headache to get approval to develop utilities that support APFS.

Edited by AgentXXL
Link to post

Hi all,

 

Firstly thanks for all the great work with this plugin.

I am setting up spare SSD for my Plex appdata as an unassigned disk rather than through the cache drive appdata.

 

What is the lightning bolt symbol next to the drive name? I don't think I have seen this until recently....?

 

Just want to ensure it is setup correctly before transferring all the Plex data.

Screenshot 2021-01-11 155643.jpg

Link to post

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.