11 minutes ago, dlandon said:

If you assign an IP address to the Container, the port will not interfere with Unraid.

True but then I have to use Allow Host access which I don't want to enable because of other containers.
I already thought about that...

 

But no worries, this was just a question if something is planed.

I just set up a script to mount it.

3 minutes ago, ich777 said:

True but then I have to use Allow Host access which I don't want to enable because of other containers.
I already thought about that...

 

But no worries, this was just a question if something is planed.

I just set up a script to mount it.

I have no plans because of the additional complexity for the user for what seems like a very corner case.

On 11/14/2024 at 5:01 PM, dlandon said:

I don't see anything in the log indicating an issue.  There is a known issue with some browsers in private or incognito mode.  Try a different browser.

 

Also do the following:

• Go to 'Tools->PHP Settings' and enable the php log.  Select 'All Categories'.
• Then go to UD and try to create a script.
• Go back to the 'Tools->PHP Settings' and see if there are any php warnings/errors.  Post any that show up.

Switching from Firefox to Chrome fixed this. Thanks @dlandon

For info - Firefox was not in a Private Tab, so not sure what was causing the issue.

On 11/15/2024 at 5:05 AM, Glycerine said:

Is the layout for UD decided in the plugin or inheriting from elsewhere?  On latest Firefox and safari, noticed the UD items did not have the left margin space other items have (see the difference in attached screenshot between the flash drive menu and UD. Particularly "DEVICE" title and device entry/icons)

I've made a few adjustments that will be in the next release of UD.

On 11/14/2024 at 10:51 PM, tjb_altf4 said:

Came across a visual bug when you have a ton of disks online, if I format (for example) disk sddq, sdd will also show as formatting also (thankfully not a duplicate format).

Haven't tested if this quirk extends to other actions.

The latest release of UD should solve this.

I'm running into some problems with the "Unassigned Devices Settings" where I can't make any changes to the settings...

When I make a change to a setting, and hit "Apply", the setting just goes back to what it was... For instance, when I try to enable "Destructive Mode", after hitting "Apply", it just goes back to "Disabled".  I have the same problem trying to enable "SMB Sharing", etc.

 

31 minutes ago, RGauld said:

I'm running into some problems with the "Unassigned Devices Settings" where I can't make any changes to the settings...

When I make a change to a setting, and hit "Apply", the setting just goes back to what it was... For instance, when I try to enable "Destructive Mode", after hitting "Apply", it just goes back to "Disabled".  I have the same problem trying to enable "SMB Sharing", etc.

 

Update ud.  A new release fixes that.

thank you, that did the trick!

On 11/1/2024 at 1:27 PM, dlandon said:

Keep in mind that Unraid supports NFSv3 and NFSv4.  Your other systems may not.  I think Synology can be configured to support one or the other or both.

 

Problem fixed on Synology!!!

Overview:

NAS mounts failed after the plugin upgrade. Root determination was that one of the three Synology NAS would not respond to a 

> showmount -e {host}

And the plugin was now requiring the response as a health check or something. Other NASs on network were responding.

Resolution: 

On Synology 

Control Panel -> Networking -> General -> Advance Setting -> (uncheck) Reply to ARP request if the target IP address is Identical to a local address configured on the incoming interface.

Turning this option off enabled unRAID to receive a response to the showmount command. Packet traces of the command showed

Problem Troubleshooting 
 

1. Portmap (rpcbind) Lookup

• The command starts by performing a portmap lookup to determine the port associated with the NFS mount daemon on 10.10.10.2.
• Packets 104–114: A connection is established on port 111 (typically used by the rpcbind service), and the client sends a V4 GETADDR call.
• The GETADDR response is received, and then both the client and server initiate a graceful close of the connection, which completes without errors.

2. Connection Attempt to NFS (Port 2049)

• After resolving the mount daemon’s port (likely 2049), the client tries to establish a connection directly to port 2049.
• Packets 284–296: The client and server successfully complete the TCP three-way handshake on port 2049, but soon after, the client sends only a single byte of data (Len=1). This could be a part of the showmount -e command query.
• Following the initial data, the client immediately sends a FIN to terminate the connection.
• The server responds with an ACK, but also sends a duplicate ACK (Packet 291), which may indicate either minor packet reordering or an unexpected early termination.
• Shortly afterward, the server sends a FIN and then a RST (Packets 292–293), suggesting the server is forcefully terminating the session.

3. Repeated Portmap Lookups

• Packets 297–306: The client repeats the connection to port 111 to perform another V4 GETADDR call, indicating that it’s attempting to re-establish the lookup for NFS service ports.
• This cycle of portmap lookups and brief connections to port 2049 continues (as seen with additional V4 GETADDR calls in Packets 322–326).

 

The Synology NAS that was having the issue has multiple interfaces. Two interfaces are configured for the same subnet (only one active). From Synology's documentation 

https://kb.synology.com/en-ca/DSM/help/DSM/AdminCenter/connection_network_route?version=7

" if you have more than two network interfaces in the same LAN, enabling this option causes network flow on each interface to be transported separately. "

The inactive interface is a built-in 1GE port, with the active interface an expansion card for 10GE

This seems like a Synology BUG, as the second interface is disabled, but the packet reordering was causing the issue.

Hi @dlandon,

 

just ran in to a small challenge. I am using UD to mount a SMB drive from an IoT device with tons of logfiles. With a filebeats container I tail all these logfiles for changes and push them to a graylog. Works nicely with one exception. Every once in a while everything seems is stuck. While on other clients I can mount the SMB path and see updates on the files, when I go to /mnt/remotes etc. the files seem to be stuck on an old version. 

 

I assume this is due to cache=strict and a stupid SMB implementation on the server side. had to tell though. 

 

I manually mounted this with cache=none and the problems went away. I realize that "strict" is the better option in most use cases. Just not in mine. Would it be possible to make this option configurable in what way or the other please? This would greatly help me!

 

So, I have 3 UnRaid systems running 7.0.0 b4. 
 

I am trying to access shares on multiple Macs running Ventura latest.  Using the UnRaid UI>Main>SMB Shares>Add Remote Share

 

Select Windows, select server, username, password, domain=WORKGROUP, select share.  
 

OK that works.  The share shows on UI>Main.  I click mount and it won’t mount.   Log shows errors. 
 

The shares on the Macs are seen by the other Macs.  
 

What am I missing?

 

I did try creating remote shares from another UnRaid box and that works fine.  They will mount and can be browsed. 

8 hours ago, JPHobby said:

Hi @dlandon,

 

just ran in to a small challenge. I am using UD to mount a SMB drive from an IoT device with tons of logfiles. With a filebeats container I tail all these logfiles for changes and push them to a graylog. Works nicely with one exception. Every once in a while everything seems is stuck. While on other clients I can mount the SMB path and see updates on the files, when I go to /mnt/remotes etc. the files seem to be stuck on an old version. 

 

I assume this is due to cache=strict and a stupid SMB implementation on the server side. had to tell though. 

 

I manually mounted this with cache=none and the problems went away. I realize that "strict" is the better option in most use cases. Just not in mine. Would it be possible to make this option configurable in what way or the other please? This would greatly help me!

 

Post ud_diagnostics by going to a command line and entering 'ud_diagnostics' then post the /flash/logs/ud_diagnostics.zip.

7 hours ago, DWomack said:

So, I have 3 UnRaid systems running 7.0.0 b4. 
 

I am trying to access shares on multiple Macs running Ventura latest.  Using the UnRaid UI>Main>SMB Shares>Add Remote Share

 

Select Windows, select server, username, password, domain=WORKGROUP, select share.  
 

OK that works.  The share shows on UI>Main.  I click mount and it won’t mount.   Log shows errors. 
 

The shares on the Macs are seen by the other Macs.  
 

What am I missing?

 

I did try creating remote shares from another UnRaid box and that works fine.  They will mount and can be browsed. 

Post ud_diagnostics by going to a command line and entering 'ud_diagnostics' then post the /flash/logs/ud_diagnostics.zip.

Hi @dlandon, first time i post here but i'll try to be brief

 

I have a problem with NFS - 

I have an OpenMediaVault server with a single disk for "Cold_backups" ( warm actually but doesn't matter now ) shared trough NFS with the unraidip/32 as only allowed client. It worked (after lots of tries) with unraid 6.x.x but last week i upgraded to the latest intel core ultra 245 so new cpu,mobo, ram from ddr4 to 5 etc. To make it work with my config i had to upgrade to unraid 7 and since i've upgraded the same exact NFS share that i was using for backups automatically (restic via backrest) now doesn't work anymore. 
I know a lot has changed in my server, but technically the hardware shouldn't make a difference and that's why i believe it's a bug with UD and unraid 7. 
The disk "connects" ok, and the little dot is green ( so it sees OMV as online and can communicate with it) but as i click "mount" comes the error of "no file or directory". I tried messing around with options like subtree_check ( shouldn't matter ) or "nohide" yet nothing changed. After all it was already working before.. 

Anyway here are the diagnostics hope it's an easy to solve problem or simply a mess up from my part. 

 

P.S: Thank you for your incredible work!

ud_diagnostics-20241120-111222.zip

Edited November 20, 20241 yr by lory995

14 hours ago, dlandon said:

Post ud_diagnostics by going to a command line and entering 'ud_diagnostics' then post the /flash/logs/ud_diagnostics.zip.

ud_diagnostics-20241120-073645.zip

 

Thank you!

 

Dennis

7 hours ago, lory995 said:

Hi @dlandon, first time i post here but i'll try to be brief

 

I have a problem with NFS - 

I have an OpenMediaVault server with a single disk for "Cold_backups" ( warm actually but doesn't matter now ) shared trough NFS with the unraidip/32 as only allowed client. It worked (after lots of tries) with unraid 6.x.x but last week i upgraded to the latest intel core ultra 245 so new cpu,mobo, ram from ddr4 to 5 etc. To make it work with my config i had to upgrade to unraid 7 and since i've upgraded the same exact NFS share that i was using for backups automatically (restic via backrest) now doesn't work anymore. 
I know a lot has changed in my server, but technically the hardware shouldn't make a difference and that's why i believe it's a bug with UD and unraid 7. 
The disk "connects" ok, and the little dot is green ( so it sees OMV as online and can communicate with it) but as i click "mount" comes the error of "no file or directory". I tried messing around with options like subtree_check ( shouldn't matter ) or "nohide" yet nothing changed. After all it was already working before.. 

Anyway here are the diagnostics hope it's an easy to solve problem or simply a mess up from my part. 

 

P.S: Thank you for your incredible work!

ud_diagnostics-20241120-111222.zip 47.56 kB · 0 downloads

Several things to look at:

• The remote share is at 'OMV.LOCAL/export/Cold_backups'.  Confirm this is the actual mount point on the OMV server.
• Log in to the NFS server and check the permissions of the /export/Cold_backups directory.
• Check the remote server (OMV) logs.
• Go to the Settings->Unassigned Devices anc click on the 'Remote Servers' tab and enter the OMV.LOCAL server name, then click the 'Test' button.  Look in the results and be sure your Unraid server has access to the /export/Cold_backup share.  Also verify the NFS versions that are supported.  Post the results if you continue to have issues.

3 hours ago, DWomack said:

ud_diagnostics-20241120-073645.zip 43.05 kB · 1 download

 

Thank you!

 

Dennis

It looks like the credentials failed.  Add the remote share back and confirm the credentials.

hi, i want to use a drive i recently decommissioned as an unassigned device, however i can't mount it

 

the error in the drive log is

unassigned.devices: Partition '/dev/sdg1' does not have a file system and cannot be mounted.

 

this makes sense, as i zeroed out this drive in order to remove it from the array

 

how can i format it ? 

39 minutes ago, jbrodriguez said:

hi, i want to use a drive i recently decommissioned as an unassigned device, however i can't mount it

 

the error in the drive log is

unassigned.devices: Partition '/dev/sdg1' does not have a file system and cannot be mounted.

 

this makes sense, as i zeroed out this drive in order to remove it from the array

 

how can i format it ? 

Go to Settings->Unassigned Devices and enable the destructive mode.  Then go to the UD page and click on the red 'X' on that drive and the partition will be removed.  Then you can format the drive.

6 hours ago, dlandon said:

It looks like the credentials failed.  Add the remote share back and confirm the credentials.

I found the problem.  Posting back here so it might help someone else.  
 

The problem was the setup on the Macs.  In File Sharing setup there is an Options button that has to be clicked and SMB access specifically turned on for user(s) creds.  
 

It must be for Windows users, because Apple depreciated AFP and uses SMB between Macs now. 
 

So how did I find it?  I asked Copilot how to set the Mac up to do SMB. 
 

 

Edited November 21, 20241 yr by DWomack
Add screen capture

1 hour ago, dlandon said:

Go to Settings->Unassigned Devices and enable the destructive mode.  Then go to the UD page and click on the red 'X' on that drive and the partition will be removed.  Then you can format the drive.

ty, that did the trick !

 

21 hours ago, dlandon said:

Several things to look at:

• The remote share is at 'OMV.LOCAL/export/Cold_backups'.  Confirm this is the actual mount point on the OMV server.
• Log in to the NFS server and check the permissions of the /export/Cold_backups directory.
• Check the remote server (OMV) logs.
• Go to the Settings->Unassigned Devices anc click on the 'Remote Servers' tab and enter the OMV.LOCAL server name, then click the 'Test' button.  Look in the results and be sure your Unraid server has access to the /export/Cold_backup share.  Also verify the NFS versions that are supported.  Post the results if you continue to have issues.

Thanks for the fast answer, here i report that:

• The remote share is correct
• For testing purposes i removed all restrictions to the nfs share. I tested and mounted correctly the share with another debian distro without problems.
• .
• Nothing appears on system logs but i couldn't find nfs-specific ones ( at least i'm not aware of them )
• Tested with this too. Same results which i attach with another diagnostics. I tested both the troubleshooting section in settings and the normal mounting with the direct ip too and yet same error. 
• * bonus : i deleted all the UD plugins, rm -rf'd them from boot plugin-removed folder and reinstalled everything. Nothing changed.

 

As i've told in the beginning it's reasonable to believe that the problems isn't mine. 1 hour before the hw swapping and softw upgrading everything was working. Then everything was broken and i didn't touch anything. 
Anyway now i think i really uploaded everything i could to diagnose it. I don't know if it's a Unraid 7  or a UD problem but it's a bug.

 

ud_diagnostics-20241121-164117.zip unraid-diagnostics-20241121-1644.zip

Edited November 21, 20241 yr by lory995

On 11/19/2024 at 9:42 AM, JPHobby said:

Hi @dlandon,

 

just ran in to a small challenge. I am using UD to mount a SMB drive from an IoT device with tons of logfiles. With a filebeats container I tail all these logfiles for changes and push them to a graylog. Works nicely with one exception. Every once in a while everything seems is stuck. While on other clients I can mount the SMB path and see updates on the files, when I go to /mnt/remotes etc. the files seem to be stuck on an old version. 

 

I assume this is due to cache=strict and a stupid SMB implementation on the server side. had to tell though. 

 

I manually mounted this with cache=none and the problems went away. I realize that "strict" is the better option in most use cases. Just not in mine. Would it be possible to make this option configurable in what way or the other please? This would greatly help me!

 

The 'cache=strict' is the best option for performance and consistency  If you do a 'sync -f {mountpoint}' when checking for the files on Unraid, this invalidates the cache and the files will then be made current.

 

Adding a cache setting will only complicate UD for a corner use case.

25 minutes ago, lory995 said:

Thanks for the fast answer, here i report that:

• The remote share is correct
• For testing purposes i removed all restrictions to the nfs share. I tested and mounted correctly the share with another debian distro without problems.
• .
• Nothing appears on system logs but i couldn't find nfs-specific ones ( at least i'm not aware of them )
• Tested with this too. Same results which i attach with another diagnostics. I tested both the troubleshooting section in settings and the normal mounting with the direct ip too and yet same error. 
• * bonus : i deleted all the UD plugins, rm -rf'd them from boot plugin-removed folder and reinstalled everything. Nothing changed.

 

As i've told in the beginning it's reasonable to believe that the problems isn't mine. 1 hour before the hw swapping and softw upgrading everything was working. Then everything was broken and i didn't touch anything. 
Anyway now i think i really uploaded everything i could to diagnose it. I don't know if it's a Unraid 7  or a UD problem but it's a bug.

 

ud_diagnostics-20241121-164117.zip 50.7 kB · 0 downloads unraid-diagnostics-20241121-1644.zip 192.83 kB · 0 downloads

This error message is coming from your remote server:

Nov 21 16:32:10 Unraid unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,hard,relatime '10.10.10.6:/export/Cold_backups' '/mnt/remotes/10.10.10.6_Cold_backups'
Nov 21 16:32:10 Unraid unassigned.devices: NFS mount failed: 'mount.nfs: mounting 10.10.10.6:/export/Cold_backups failed, reason given by server: No such file or directory'.

The "No such file or directory' is coming from the remote server.  I don't see anything that UD is doing to cause this reply from the server.

 

Try this mount command at the command line:

mkdir /mnt/remotes/10.10.10.6_Cold_backups
/sbin/mount -t 'nfs4' -o rw,hard,relatime '10.10.10.6:/export/Cold_backups' '/mnt/remotes/10.10.10.6_Cold_backups'

Then try:

/sbin/mount -o rw,hard,relatime '10.10.10.6:/export/Cold_backups' '/mnt/remotes/10.10.10.6_Cold_backups'

Show the output of the 'mount' command if it mounts.

I just added the relatively new NanoKVMs from Sipeed to my two Unraid servers. They have a feature where they can mount a virtual disk. It does show up on both of my systems but I am not able to use it and the plugin isn't giving me any feedback as to why.

 

 

How might I be able to access this virtual disk using this plugin? I don't think formatting the disk is an option.