@dlandon with the latest update I got two missing devices but they are both connected:

 

 

If I remove the Devices from the Historical Devices the config from the devices is also removed like:

(This screenshot shows with one device removed from the Historical Devices)

 

 

What's also strange is that if I'm only clicking the slider to show the partitions (slider enabled), which BTW are showing anyways, I get this screen:

 

but the slider in the settings from the disk look like this (seems like this isn't saved):

 

 

I'm on Unraid 6.10.0 and UD is version: 2022.05.17

Look carefully at the serial no (id).  The Historical devices have spaces, the new ud devices have underscore.  This is because ud has changed to using the devs.ini id.  They are the same devices, ud just thinks they are different devices.  Apply your settings to the new found devices and then remove the historical devices.

54 minutes ago, dlandon said:

Apply your settings to the new found devices and then remove the historical devices.

I have done this already twice, here is a screenshot after the removal:

 

Here is a screenshot after applying the new setting (only Passed through was enabled and show Partitions disabled):

 

And here after I've assigned it to the second device:

 

 

If I remove the devices from the Historical Devices and re add it it's the same over and over again.

Should I send you my ini file, haven't looked at it yet...

32 minutes ago, ich777 said:

If I remove the devices from the Historical Devices and re add it it's the same over and over again.

Should I send you my ini file, haven't looked at it yet...

PM this file to me.  Don't post it here as it has some private informatiuon.

 

/flash/config/plugins/unassigned.devices/unassigned.devices.cfg

 

I suspect it may have an issue as I can't reproduce your problem.

2 hours ago, ich777 said:

If I remove the devices from the Historical Devices and re add it it's the same over and over again.

Update UD.  I think I may have found it.

1 hour ago, dlandon said:

Update UD.  I think I may have found it.

Thank you, can confirm everything is working after deleting the drives from Historical Devices and applying the settings again!

loki-diagnostics-20220518-1234.zipHi all, my first time asking for support so not sure I'm in the right thread, I've been having issue with a SMB mount to my nas, I switched to NFS and was good for a while however it now started again. All of my shares are showing 0 bytes and I can't navigate to them as they are disconnected, I included a screeshot and what the log is freaking out about.

May 18 11:57:49 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:57:49 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:57:54 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:57:54 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:58:01 Loki kernel: traps: lsof[1259] general protection fault ip:15532da576ae sp:58c4db2936431bf error:0 in libc-2.33.so[15532da3e000+15e000]


 

Edited May 18, 20224 yr by ailliano
Adding diagnostics

21 minutes ago, ailliano said:

Hi all, my first time asking for support so not sure I'm in the right thread, I've been having issue with a SMB mount to my nas, I switched to NFS and was good for a while however it now started again. All of my shares are showing 0 bytes and I can't navigate to them as they are disconnected, I included a screeshot and what the log is freaking out about.

May 18 11:57:49 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:57:49 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:57:54 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:57:54 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
May 18 11:58:01 Loki kernel: traps: lsof[1259] general protection fault ip:15532da576ae sp:58c4db2936431bf error:0 in libc-2.33.so[15532da3e000+15e000]



 

Post your diagnostics zip file.

Thanks for the reply, I edited my original post.

loki-diagnostics-20220518-1234.zip

Edited May 18, 20224 yr by ailliano

11 minutes ago, ailliano said:

Thanks for the reply, I edited my original post.

loki-diagnostics-20220518-1234.zip 399.02 kB · 0 downloads

 

I see several issues.  You are getting general protection faults:

May 18 11:55:57 Loki kernel: traps: lsof[64428] general protection fault ip:151a2e0966ae sp:6211c4e2f66d19bb error:0 in libc-2.33.so[151a2e07d000+15e000]
May 18 11:56:25 Loki kernel: traps: lsof[68667] general protection fault ip:153589cc46ae sp:311500c92e34b55e error:0 in libc-2.33.so[153589cab000+15e000]
May 18 11:56:46 Loki kernel: traps: lsof[71467] general protection fault ip:154c4cef06ae sp:a6ed2d0bfacb66cb error:0 in libc-2.33.so[154c4ced7000+15e000]
May 18 11:57:10 Loki kernel: traps: lsof[72228] general protection fault ip:14f2dac7a6ae sp:e4e808728812df1a error:0 in libc-2.33.so[14f2dac61000+15e000]
May 18 11:57:33 Loki kernel: traps: lsof[73329] general protection fault ip:1553577dd6ae sp:43c1fa20eae56adb error:0 in libc-2.33.so[1553577c4000+15e000]

I don't know where these gpfs are coming from, but I suspect the preclear disk plugin.

 

Remove the preclear disk plugin.  There is a replacement that works a lot better.  You can install it from CA.

preclear.disk.plg - 2021.04.11  (Up to date)  (Incompatible)

 

These log entries are from the remote server being non-responsive or network issues:

May 18 11:57:34 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/DS918_Unraid' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
### [PREVIOUS LINE REPEATED 1 TIMES] ###
May 18 11:57:39 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/DS918_XXX' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!

 

Thank you for fast reply !
I updated the plugin to the new replacement and rebooted the server, will monitor and see what happens, If the remote server is the issue I'm not sure what's going on, it's a DS918 connected to a switch on same network and never has any problems, I'm not sure what can cause the NAS to stop communicating with unraid and cause shares issues, any suggestions ? 

Since upgrading to unRAID 6.10.0 and the latest version of the UD plugin, my external backup drive (14TB Easystore NTFS) will not mount and run the backup script.  I deleted it from historical devices, plugged it in and configured it again.  No change.

 

Worked great in unRAID 6.9.2 and prior to updating UD.

 

If I plug it in to a WIndows PC, everything appears as it should.

 

 

medianas-diagnostics-20220518-2003.zip

Same issue as @Hoopster - I'm running 6.10-rc4. Updated to Unassigned Devices 2022.05.18 today and I can't access my USB connected Elements that I normally have mounted for backups via the DirSyncPro docker.

 

9 hours ago, Hoopster said:

I deleted it from historical devices, plugged it in and configured it again.  No change.

 

8 hours ago, Goldfire said:

I can't access my USB connected Elements

It looks like you didn't unmount the disk before you physically removed it.  If the mount button shows a not 'Unmount', you'll need to reboot to clear it up.  Don't just pull the disk out and expect it to work when you plug it back in.

 

4 hours ago, dlandon said:

It looks like you didn't unmount the disk before you physically removed it.  If the mount button shows a not 'Unmount', you'll need to reboot to clear it up.  Don't just pull the disk out and expect it to work when you plug it back in.

Yes, I should have caught that.  The configuration of the disk was incorrect in UD after the upgrade.  After mounting it manually, I did in fact unplug it without unmounting and removing from historical devices.  A reboot of the server cleared everything up and it is working properly now.

 

I was so used to just unplugging it after the backup and automatic unmount that I forgot to manually unmount.

 

Thanks for pointing out the obvious as I missed that.  😀

Edited May 19, 20224 yr by Hoopster

Is there a way to disable the update check? If not, a way to at least suppress the banner?

1 hour ago, rpj2 said:

Is there a way to disable the update check? If not, a way to at least suppress the banner?

No.  Just perform the update.  Quick and easy,

13 hours ago, dlandon said:

 

It looks like you didn't unmount the disk before you physically removed it.  If the mount button shows a not 'Unmount', you'll need to reboot to clear it up.  Don't just pull the disk out and expect it to work when you plug it back in.

 

 

To be honest, I don't remember removing the external drive during or after updating the plugin, I did try a few different things that may have included that though. Nevertheless, I had to restart for the stable 6.10 update anyway, so I'll keep this in mind going forward.

 

Thanks.

5 hours ago, dlandon said:

No.  Just perform the update.  Quick and easy,

Nothing else puts up a banner. Especially something that is updated so frequently. Will grab source and take out.

5 hours ago, rpj2 said:

Nothing else puts up a banner

Lots of plugins put up the banner including: CA, File Manager, FCP, Recycle Bin, etc.

 

The changes recently were to fix some issues with the Unraid 6.10 release and changed ids of UD devices.

 

When I see something that causes users issues, I will release an update.  I try not to do a lot of unnecessary updates, but sometimes it's really necessary.

 

The idea behind the banner is so users will keep plugins up to date.  If that is not done, there will be posts about issues that have already been solved because users don't update.

12 hours ago, rpj2 said:

a way to at least suppress the banner?

Click the "X" hides it until the next upgrade.  Why don't you want the version of UD with bugs fixed in it?

 

4 hours ago, dlandon said:

Lots of plugins put up the banner including: CA, File Manager, FCP, Recycle Bin, etc.

 

The changes recently were to fix some issues with the Unraid 6.10 release and changed ids of UD devices.

 

When I see something that causes users issues, I will release an update.  I try not to do a lot of unnecessary updates, but sometimes it's really necessary.

 

The idea behind the banner is so users will keep plugins up to date.  If that is not done, there will be posts about issues that have already been solved because users don't update.

I guess I don't use anything else that shows a banner. No worries, I took it out.

Hey,

 

After my server updated to latest version of Unraid and UD my 2 NAS drives that I had mounted previously no longer mount. I believe this is because the NAS bay is pretty old (and no longer supported as of 2018) and it's SMB version is old.

 

I'm getting the following errors in the system logs when attempting to mount:

 

May 20 17:07:50 Jarvis kernel: CIFS: Attempting to mount \\HULK\Volume_1 May 20 17:07:50 Jarvis kernel: CIFS: VFS: cifs_mount failed w/return code = -112 
May 20 17:07:50 Jarvis unassigned.devices: SMB default protocol mount failed: 'mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '. 
May 20 17:07:50 Jarvis unassigned.devices: Mount SMB share '//HULK/Volume_1' using SMB 3.1.1 protocol. 
May 20 17:07:50 Jarvis unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Volume_1' '//HULK/Volume_1' '/mnt/remotes/HULK_Volume_1'

 

Now my problem is, I have no clue where I can change the SMB version. Earlier posts say there's a force version option in UD settings but that seems to have gone in recent updates. Anyone have any help on how to action what the log is suggesting?

Thank you.

6 minutes ago, jsgilly20 said:

Now my problem is, I have no clue where I can change the SMB version. Earlier posts say there's a force version option in UD settings but that seems to have gone in recent updates. Anyone have any help on how to action what the log is suggesting?

Thank you.

Go to Settings->SMB and enable NetBIOS and UD will use SMB1 if none of the other protocols will mount.

6 minutes ago, dlandon said:

Go to Settings->SMB and enable NetBIOS and UD will use SMB1 if none of the other protocols will mount.

Thanks for the swift reply, unfortunately I already have that option enabled within SMB settings, I've also just restarted the array and saved these settings again and tried again and still no luck.