23 minutes ago, rosskinard said:

I've added the SMB shares to UD on the Unraid box...and when adding them I can query the list of shares, etc. But when I click the MOUNT button, it errors out:

That's generally an issue with credentials.  Try not to use special characters in the password. 

 

24 minutes ago, rosskinard said:

Should there be a credentials file created at the /tmp/unassigned.devices/credentials_PrimaryRAID location?

As soon as the mount is completed, that file is removed because the user and password are in plain text.  After mounting the remote share, the credentials are no longer needed.

37 minutes ago, dlandon said:

That's generally an issue with credentials.  Try not to use special characters in the password. 

 

There are no special characters in the password. Just upper/lower/numbers. Sorry, should have specified that.

 

I tried different user credentials with a super simple password and it fails too.

 

Also tried Allow "EVERYONE" read/write access.

Restarting both file sharing and the machine itself (Mac Pro)

 

Connecting to the shares on my MacBook Pro and my Windows 11 gaming PC works fine.

 

That being said, my Ubuntu machine doesn't want to connect to the shares either. I had never tried from it, but doesn't seem like Linux wants to talk to the Mac Pro's SMB sharing fully.

 

My LibreELEC/Kodi system will browse the SMB shares when added though.

 

Any ideas?

 

Thanks

Ross

I just enabled NFS on the Mac Pro (duh) and those mounts work just fine with UD. Since it's a temporary thing, it's not important. As long as I can get through the next few weeks while I purchase a few 10TB drives and move everything.

 

been getting these errors since the last update. not exactly sure what is causing.

2 hours ago, iilied said:

been getting these errors since the last update. not exactly sure what is causing.

It's a new idea I had that apparently needs some more work.  I've just released an update that will stop the messages.

may a question about auto mounting smb shares since 6.10, seems here UAD tries to mount and gives up after a reboot

 

ug 28 06:23:00 AlsServer emhttpd: nothing to sync
Aug 28 06:23:00 AlsServer unassigned.devices: Mounting 'Auto Mount' Remote Shares...
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server '192.168.1.45' is offline and share '//ALSBATH/internal' cannot be mounted.
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server '192.168.1.25' is offline and share '//ALSSLEEP/internal' cannot be mounted.
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server 'VUDUO4KSE' is offline and share '//VUDUO4KSE/harddisk' cannot be mounted.
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server 'VUDUO4KSE' is offline and share '//VUDUO4KSE/rootfs' cannot be mounted.

 

even the shares are online, so i have to manually mount them in the GUI then which is working just fine.

 

question, any chance to "delay" the mounts as soon network is available to UAD ?

2 hours ago, alturismo said:

may a question about auto mounting smb shares since 6.10, seems here UAD tries to mount and gives up after a reboot

 

ug 28 06:23:00 AlsServer emhttpd: nothing to sync
Aug 28 06:23:00 AlsServer unassigned.devices: Mounting 'Auto Mount' Remote Shares...
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server '192.168.1.45' is offline and share '//ALSBATH/internal' cannot be mounted.
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server '192.168.1.25' is offline and share '//ALSSLEEP/internal' cannot be mounted.
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server 'VUDUO4KSE' is offline and share '//VUDUO4KSE/harddisk' cannot be mounted.
Aug 28 06:23:00 AlsServer unassigned.devices: Remote SMB/NFS server 'VUDUO4KSE' is offline and share '//VUDUO4KSE/rootfs' cannot be mounted.

 

even the shares are online, so i have to manually mount them in the GUI then which is working just fine.

 

question, any chance to "delay" the mounts as soon network is available to UAD ?

Please post your diagnostics.

11 hours ago, dlandon said:

Please post your diagnostics.

thanks for the update, i report back on next reboot, Server currently busy

just want to report some feedback on this awesome plugin.

have one usb to nvme disk attached and the disk log fills up with spinning down commands.

40 minutes ago, TIE Fighter said:

just want to report some feedback on this awesome plugin.

have one usb to nvme disk attached and the disk log fills up with spinning down commands.

That's not enough information.  Please post the diagnostics.

23 minutes ago, dlandon said:

That's not enough information.  Please post the diagnostics.

please find attached diagnostics.

galactica-diagnostics-20210901-1855.zip

6 minutes ago, TIE Fighter said:

please find attached diagnostics.

galactica-diagnostics-20210901-1855.zip 164.31 kB · 0 downloads

You rebooted, so the log doesn't show the spin downs for /dev/sda like you posted.  Looks like you have the spin down set for every 15 minutes.

 

/dev/sda is a WD hard drive (WD60EFRX), so Unraid will spin it down.  It doesn't appear to be a nvme SSD, but the sdX designation can change on reboot so that might not be right.

 

This is not really a UD issue.

 

You can filter the log messages by installing the Enhanced Log plugin and filtering these messages in the log 'Syslog Filter' tab of Enhanced Log.

1 hour ago, dlandon said:

You rebooted, so the log doesn't show the spin downs for /dev/sda like you posted.  Looks like you have the spin down set for every 15 minutes.

 

/dev/sda is a WD hard drive (WD60EFRX), so Unraid will spin it down.  It doesn't appear to be a nvme SSD, but the sdX designation can change on reboot so that might not be right.

 

This is not really a UD issue.

 

You can filter the log messages by installing the Enhanced Log plugin and filtering these messages in the log 'Syslog Filter' tab of Enhanced Log.

correct the server was rebooted after my first post did not notice the sdX deignation was changed sorry for confusion.

see below

the timer spin down timer set for 15min.

so thats why the disk log is filling up for that particular drive.

so unassigned devices do not exclude ssd/nvme drives like unraid is excluding cache drives from spin down?

 

galactica-diagnostics-20210901-2107.zip

Edited September 1, 20214 yr by TIE Fighter

2 minutes ago, TIE Fighter said:

correct the server was rebooted after my first post did not notice the sdX deignation was changed sorry for confusion.

see below

the timer spin down timer set for 15min.

so unassigned devices do not exclude ssd/nvme drives like unraid is excluding cache drives from spin down?

galactica-diagnostics-20210901-2107.zip 164.93 kB · 0 downloads

You have the disk passed through:

Sep  1 17:22:54 Galactica unassigned.devices: Disk with serial 'SSD_970_EVO_DD5641988390', mountpoint 'Samsung_SSD_970_EVO-part1' is set as passed through.
Sep  1 17:22:54 Galactica unassigned.devices: Disk with serial 'SSD_970_EVO_DD5641988390', mountpoint 'Ny_volym' is set as passed through.

 

UD does not spin down disks.  Those messages come from Unraid spinning down the disk.  Where is the disk passed through to?  Check there.

2 hours ago, dlandon said:

You can filter the log messages by installing the Enhanced Log plugin and filtering these messages in the log 'Syslog Filter' tab of Enhanced Log.

thank you very much for the advice and for another great plugin 🙂

12 minutes ago, dlandon said:

UD does not spin down disks.  Those messages come from Unraid spinning down the disk.  Where is the disk passed through to?  Check there.

passed to a vm as a virtual disk, i'll have a look.

cheers.

Hi,

 

I have problems with my External HD Drive and unassigned plugin in my Unraid Server. I have everything updated, Unraid OS, Unraid unassigned plugin, etc

 

I precleared my external drive and I checked that the disk have errors and everything is fine.

 

When I plug the external HD I can mount and format the disk without problems. The problem is that randonmly Unraid unmount the external disk and I can not mount again (even if i reboot the system I can not mount again the disk).

 

I have checked that the automount option is marked and it is ok.

 

It is very frustanting because I don´t know why Unraid unmount the disk.

 

Thank you in advance an best regards

 

 

9 minutes ago, bonistir said:

problems with my External HD Drive and unassigned plugin

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Here you have.

 

Thank you

tower-diagnostics-20210902-1759.zip

1 hour ago, bonistir said:

Here you have.

 

Thank you

tower-diagnostics-20210902-1759.zip 220.43 kB · 0 downloads

The disk was not unmounted cleanly:

Aug 26 18:03:03 Tower unassigned.devices: Adding disk '/dev/sdf1'...
Aug 26 18:03:03 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'exfat' -o rw,auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdf1' '/mnt/disks/External_HD_Drive'
Aug 26 18:03:04 Tower mount.exfat: volume was not unmounted cleanly
Aug 26 18:03:04 Tower unassigned.devices: Mount of '/dev/sdf1' failed: 'FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option '
Aug 26 18:03:04 Tower unassigned.devices: Partition 'WD Elements_25A3' cannot be mounted.

Click on the check mark next to the mount point and see if it can be fixed.

 

You also have a UPS communications issue:

Aug 26 17:06:39 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:15:51 Tower emhttpd: spinning down /dev/sda
Aug 26 17:16:45 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:16:56 Tower emhttpd: spinning down /dev/sde
Aug 26 17:17:22 Tower emhttpd: spinning down /dev/sdd
Aug 26 17:17:22 Tower emhttpd: spinning down /dev/sdc
Aug 26 17:26:51 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:30:52 Tower emhttpd: spinning down /dev/sda
Aug 26 17:36:57 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:45:53 Tower emhttpd: spinning down /dev/sda
Aug 26 17:47:03 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:51:07 Tower emhttpd: read SMART /dev/sde
Aug 26 17:57:09 Tower apcupsd[5597]: Communications with UPS lost.

You need to get that fixed.

14 hours ago, dlandon said:

The disk was not unmounted cleanly:

Aug 26 18:03:03 Tower unassigned.devices: Adding disk '/dev/sdf1'...
Aug 26 18:03:03 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'exfat' -o rw,auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdf1' '/mnt/disks/External_HD_Drive'
Aug 26 18:03:04 Tower mount.exfat: volume was not unmounted cleanly
Aug 26 18:03:04 Tower unassigned.devices: Mount of '/dev/sdf1' failed: 'FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option '
Aug 26 18:03:04 Tower unassigned.devices: Partition 'WD Elements_25A3' cannot be mounted.

Click on the check mark next to the mount point and see if it can be fixed.

 

You also have a UPS communications issue:

Aug 26 17:06:39 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:15:51 Tower emhttpd: spinning down /dev/sda
Aug 26 17:16:45 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:16:56 Tower emhttpd: spinning down /dev/sde
Aug 26 17:17:22 Tower emhttpd: spinning down /dev/sdd
Aug 26 17:17:22 Tower emhttpd: spinning down /dev/sdc
Aug 26 17:26:51 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:30:52 Tower emhttpd: spinning down /dev/sda
Aug 26 17:36:57 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:45:53 Tower emhttpd: spinning down /dev/sda
Aug 26 17:47:03 Tower apcupsd[5597]: Communications with UPS lost.
Aug 26 17:51:07 Tower emhttpd: read SMART /dev/sde
Aug 26 17:57:09 Tower apcupsd[5597]: Communications with UPS lost.

You need to get that fixed.

 

Thank you for your help!

 

I don´t know where is exactly this check: "click on the check mark next to the mount point and see if it can be fixed." it could be possible that post image capture?

 

Best regards

 

 

1 hour ago, bonistir said:

 

Thank you for your help!

 

I don´t know where is exactly this check: "click on the check mark next to the mount point and see if it can be fixed." it could be possible that post image capture?

 

Best regards

 

 

I don't have access to my servers right now to get a screen shot.  Click on the '+' under the drive and then click on the check mark.

Dear friends,

 

I have 2 (two) SSDs not format /dev/sdc and /dev/sdd, the unraid server recognize both ssds, but only one show in dashboard.

 

[0:0:0:0]disk SanDisk' Cruzer Fit 1.00 /dev/sda 8.00GB

[1:0:0:0]disk ATA ST1000LM024 HN-M 0001 /dev/sdb 1.00TB

[1:0:1:0]disk ATA P4-480 522a /dev/sdc 480GB

[1:0:2:0]disk ATA P4-480 60 /dev/sdd 480GB

[1:0:3:0]disk ATA WDC WDS480G2G0A- 0000 /dev/sde 480GB

[1:0:4:0]disk ATA ST2000DM001-1ER1 CC43 /dev/sdf 2.00TB

[1:0:5:0]disk ATA ST1000DM003-1CH1 CC47 /dev/sdg 1.00TB

[1:0:6:0]disk ATA ST2000DM001-1ER1 CC43 /dev/sdh 2.00TB

[1:0:7:0]disk ATA ST2000DM001-1ER1 CC26 /dev/sdi 2.00TB

[2:0:0:0]disk ATA ST2000DM008-2FR1 0001 /dev/sdj 2.00TB

[3:0:0:0]disk ATA ST2000VX008-2E31 CV12 /dev/sdk 2.00TB

[4:0:0:0]disk ATA ST1000DM003-1CH1 CC47 /dev/sdl 1.00TB

[5:0:0:0]disk ATA ST1000DM003-1CH1 CC47 /dev/sdm 1.00TB

 

 

 Why dont show/dev/sdd ?

 

Thanks

 

Adriano

1 hour ago, Adriano Frare said:

Dear friends,

 

I have 2 (two) SSDs not format /dev/sdc and /dev/sdd, the unraid server recognize both ssds, but only one show in dashboard.

 

[0:0:0:0]disk SanDisk' Cruzer Fit 1.00 /dev/sda 8.00GB

[1:0:0:0]disk ATA ST1000LM024 HN-M 0001 /dev/sdb 1.00TB

[1:0:1:0]disk ATA P4-480 522a /dev/sdc 480GB

[1:0:2:0]disk ATA P4-480 60 /dev/sdd 480GB

[1:0:3:0]disk ATA WDC WDS480G2G0A- 0000 /dev/sde 480GB

[1:0:4:0]disk ATA ST2000DM001-1ER1 CC43 /dev/sdf 2.00TB

[1:0:5:0]disk ATA ST1000DM003-1CH1 CC47 /dev/sdg 1.00TB

[1:0:6:0]disk ATA ST2000DM001-1ER1 CC43 /dev/sdh 2.00TB

[1:0:7:0]disk ATA ST2000DM001-1ER1 CC26 /dev/sdi 2.00TB

[2:0:0:0]disk ATA ST2000DM008-2FR1 0001 /dev/sdj 2.00TB

[3:0:0:0]disk ATA ST2000VX008-2E31 CV12 /dev/sdk 2.00TB

[4:0:0:0]disk ATA ST1000DM003-1CH1 CC47 /dev/sdl 1.00TB

[5:0:0:0]disk ATA ST1000DM003-1CH1 CC47 /dev/sdm 1.00TB

 

 

 Why dont show/dev/sdd ?

 

Thanks

 

Adriano

How do you have the disks connected?

Hello!

 

I'm encountering an issue and I'm in a bit of a pickle.

 

After a data drive swap in my main array and a UD plugin update, I am no longer able to mount certain drives in UD. I have a total of 10 drives in UD. 2 SSDs, 7 pre-existing HDDs, and 1 new HDD. The 2 SSDs and 1 new HDD mount fine, but the 7 pre-existing HDDs no longer mount. When attempting to mount, the log shows:

 

Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] physical block alignment offset: 4096
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 4096-byte physical blocks
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write Protect is off
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Mode Sense: 73 00 00 08
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 6 22:08:32 Tower kernel: sdaa: sdaa1
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Attached SCSI disk
Sep 6 22:08:52 Tower emhttpd: WDC_WUH721818ALE6L4_3WKXN7LJ (sdaa) 512 35156656128
Sep 6 22:08:52 Tower emhttpd: read SMART /dev/sdaa
Sep 6 22:09:56 Tower unassigned.devices: Adding disk '/dev/sdaa1'...
Sep 6 22:09:56 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>'
Sep 6 22:09:56 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. '
Sep 6 22:15:30 Tower unassigned.devices: Adding disk '/dev/sdaa1'...
Sep 6 22:15:30 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>'
Sep 6 22:15:30 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. '
Sep 6 22:18:48 Tower unassigned.devices: Adding disk '/dev/sdaa1'...
Sep 6 22:18:48 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>'
Sep 6 22:18:48 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. '

 

This is the same error show for all 7 of my drives which previously mounted just fine. Anyone have any insight? I really need to get this fixed ASAP as these drives contain data I need to access.

 

I have tried reinstalling the plugin as well as full server restarts, neither seem to help.

Edited September 7, 20214 yr by doubley

4 hours ago, doubley said:

Hello!

 

I'm encountering an issue and I'm in a bit of a pickle.

 

After a data drive swap in my main array and a UD plugin update, I am no longer able to mount certain drives in UD. I have a total of 10 drives in UD. 2 SSDs, 7 pre-existing HDDs, and 1 new HDD. The 2 SSDs and 1 new HDD mount fine, but the 7 pre-existing HDDs no longer mount. When attempting to mount, the log shows:

 

Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] physical block alignment offset: 4096
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] 4096-byte physical blocks
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write Protect is off
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Mode Sense: 73 00 00 08
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 6 22:08:32 Tower kernel: sdaa: sdaa1
Sep 6 22:08:32 Tower kernel: sd 8:0:7:0: [sdaa] Attached SCSI disk
Sep 6 22:08:52 Tower emhttpd: WDC_WUH721818ALE6L4_3WKXN7LJ (sdaa) 512 35156656128
Sep 6 22:08:52 Tower emhttpd: read SMART /dev/sdaa
Sep 6 22:09:56 Tower unassigned.devices: Adding disk '/dev/sdaa1'...
Sep 6 22:09:56 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>'
Sep 6 22:09:56 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. '
Sep 6 22:15:30 Tower unassigned.devices: Adding disk '/dev/sdaa1'...
Sep 6 22:15:30 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>'
Sep 6 22:15:30 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. '
Sep 6 22:18:48 Tower unassigned.devices: Adding disk '/dev/sdaa1'...
Sep 6 22:18:48 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdaa1' '/mnt/disks/<drivename>'
Sep 6 22:18:48 Tower unassigned.devices: Mount of '/dev/sdaa1' failed: 'mount: /mnt/disks/<drivename>: mount point does not exist. '

 

This is the same error show for all 7 of my drives which previously mounted just fine. Anyone have any insight? I really need to get this fixed ASAP as these drives contain data I need to access.

 

I have tried reinstalling the plugin as well as full server restarts, neither seem to help.

Are you out of memory?  Post your diagnostics.