Feature Request: I'd like to be able to mount btrfs volumes with the compress option enabled.

1 hour ago, guniv said:

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.

Unraid and UD only mount disks with partitions.  The not 'Partition' means that the disk does not have a partition.  Can you format the virtual disk with a partition?

31 minutes ago, vrytired said:

Feature Request: I'd like to be able to mount btrfs volumes with the compress option enabled.

I'll put it in my feature list and see if it makes sense for the wider user base.

2 hours ago, dlandon said:

Unraid and UD only mount disks with partitions.  The not 'Partition' means that the disk does not have a partition.  Can you format the virtual disk with a partition?

Yeah, formatting worked and the device is still working fine overall. Wanted to make sure I wasn't missing something. Thanks for the fast reply!

Is there a sample script to modify the UD mounting behaviour?
I'm looking at a way to nominate a sub folder, e.g. /mnt/disks/SOME_GROUPING/disk-001 & /mnt/disks/SOME_GROUPING/disk-002

This would allow me to easily pass a group of UD disks into a container, as well as be more dynamic as I add and remove disks over time... as I wouldn't need to change the container volumes each time

9 hours ago, tjb_altf4 said:

Is there a sample script to modify the UD mounting behaviour?
I'm looking at a way to nominate a sub folder, e.g. /mnt/disks/SOME_GROUPING/disk-001 & /mnt/disks/SOME_GROUPING/disk-002

This would allow me to easily pass a group of UD disks into a container, as well as be more dynamic as I add and remove disks over time... as I wouldn't need to change the container volumes each time

If I understand what you are wanting to do, enter 'SOME_GROUPING/disk-001' as the SMB share.

12 hours ago, dlandon said:

If I understand what you are wanting to do, enter 'SOME_GROUPING/disk-001' as the SMB share.

I don't think that's right for what I want to achieve.

If I have 10 local disks in UD, they currently all mount like:
/mnt/disks/disk-001
/mnt/disks/disk-002
/mnt/disks/disk-003
...
/mnt/disks/disk-010

I would like to be able to mount a subset into a different folder, where I can specify the name, e.g. SOME_GROUPING:
/mnt/disks/SOME_GROUPING/disk-001
/mnt/disks/SOME_GROUPING/disk-002
/mnt/disks/SOME_GROUPING/disk-003
/mnt/disks/SOME_GROUPING/disk-004

This would be to allow me to simply pass /mnt/disks/SOME_GROUPING/ into a container

Edited November 23, 20241 yr by tjb_altf4

On 11/22/2024 at 7:28 PM, tjb_altf4 said:

I don't think that's right for what I want to achieve.

If I have 10 local disks in UD, they currently all mount like:
/mnt/disks/disk-001
/mnt/disks/disk-002
/mnt/disks/disk-003
...
/mnt/disks/disk-010

I would like to be able to mount a subset into a different folder, where I can specify the name, e.g. SOME_GROUPING:
/mnt/disks/SOME_GROUPING/disk-001
/mnt/disks/SOME_GROUPING/disk-002
/mnt/disks/SOME_GROUPING/disk-003
/mnt/disks/SOME_GROUPING/disk-004

This would be to allow me to simply pass /mnt/disks/SOME_GROUPING/ into a container

There is currently no way to do that.

On 11/21/2024 at 5:32 PM, dlandon said:

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.

Edit:
In the end i solved it: When adding automatically via "load shares" on UD it adds it as /exports/Cold_backups while actually can only be mounted as /Cold_backups without the /export part. I don't know if it's usual or if It may be a misconfiguration on my part from OMV that lets UD see all the folder tree. I'll fiddle with it in the future, for now at least i can make my backups again. Thank you

A bit late because i don't have time but i just tried and it says the same thing. Now i'll use SMB and maybe by Christmas when i'll have more time  i'll look into it.

Edited November 25, 20241 yr by lory995
Correction

I do have same problem. Also cannot mount NFS share anymore since I updated to Unraid 7.

 

ISSUE below has been resolved:

 

Can anyone think of any reason that the shares of 2 of 4 Unraid systems would stop working?

 

This resolved the issue:

 

• Stopped array on systems not sharing
• Turned OFF SMB
• Started Array
• Stopped Array
• Turned ON SMB
• Started Array

 

The two affected systems started showing up again, along with their shares. Weird? Ya.

 

 

Original issue for reference:

-----------------------------------

All 4 systems should have identical SMB settings and no manual changes have been recently made to any of the systems that I can think of.

 

 

 

Neither UD nor my Mac can see shares on the two systems, FORD and ARTHUR

 

 

4 running Unraid systems, all on 7.0beta4, all with plugins up-to-date.

 

 

Edited November 28, 20241 yr by Espressomatic

On 11/27/2024 at 7:01 AM, chrizzo said:

I do have same problem. Also cannot mount NFS share anymore since I updated to Unraid 7.

 

When you updated Unraid, UD was also updated.  There have been changes in UD that do wome additional checking for remote shares to be on line and ready to mount NFS shares.  Go to Settings->Unassigned Devices and then click on the 'Remote Servers' and enter your server name or IP address and click "Test".  You will then see the results of UD testing the remote server.

 

If you need further assistance, post the results from the remote server test.

hi i constantly have issues with SSDs and the hot swapping i always get 

sd 12:0:1:0: [sdl] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK

i cant seem to stop it  i even do spin down  for the sdd before i slide it out..  doesnt matter

and then it leaves it powered on  in the historical  section

how do i fix it so it properly  disconnects from unraid when you unplug it and it wasnt even mounted

 

and then when i re plug that SSD back in then i cant mount it as it will say REBOOT   so  this happens with both SSDS i got there  i swap with my sister

 

tardis-diagnostics-20241128-1331.zip

Edited November 28, 20241 yr by comet424

On 11/28/2024 at 3:40 PM, dlandon said:

When you updated Unraid, UD was also updated.  There have been changes in UD that do wome additional checking for remote shares to be on line and ready to mount NFS shares.  Go to Settings->Unassigned Devices and then click on the 'Remote Servers' and enter your server name or IP address and click "Test".  You will then see the results of UD testing the remote server.

 

If you need further assistance, post the results from the remote server test.

@dlandon
Test seems to be fine:
 

Server '192.168.188.71' responds to a 'ping'
Testing SMB...
Remote server 'SMB' port 445 is open
** Remote Server is online for SMB

Testing NFS...
Remote server 'RPC' port 111 is open
Remote server 'NFS' port 2049 is open
The 'showmount -e' command results:
Export list for 192.168.188.71:
/mnt/HD/HD_a2/ha_backup   *
/mnt/HD/HD_a2/nfs_mycloud *
NFS versions available: 3
** Remote Server is online for NFS

But wen trying to mount one of them I get

Nov 29 21:17:07 Chrizzonet unassigned.devices: NFS mount failed: 'mount.nfs4: Protocol not supported for MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup on /mnt/remotes/MYCLOUDEX2ULTRA_ha_backup'.
Nov 29 21:17:07 Chrizzonet unassigned.devices: Remote Share 'MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup' failed to mount.

12 minutes ago, chrizzo said:

NFS versions available: 3
** Remote Server is online for NFS

Only NFSv3 is supported on your remote server.  Go to the UD Settings and set the "NFS Version to use when Mounting Remote Shares:" to "Auto" so NFSv3 qwill be used.

@dlandon
just tried, also no luck
Nov 29 21:37:45 Chrizzonet unassigned.devices: Mounting Remote Share 'MYCLOUDEX2ULTRA:/mnt/HD/HD_a2/ha_backup'...
Nov 29 21:37:45 Chrizzonet unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,hard,relatime 'MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup' '/mnt/remotes/MYCLOUDEX2ULTRA_ha_backup'
Nov 29 21:37:45 Chrizzonet unassigned.devices: NFS mount failed: 'mount.nfs: Protocol not supported for MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup on /mnt/remotes/MYCLOUDEX2ULTRA_ha_backup'.
Nov 29 21:37:45 Chrizzonet unassigned.devices: Remote Share 'MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup' failed to mount.

I don´t know why... It was running for years now, changed nothing on that WD thing...

2 minutes ago, chrizzo said:

@dlandon
just tried, also no luck
Nov 29 21:37:45 Chrizzonet unassigned.devices: Mounting Remote Share 'MYCLOUDEX2ULTRA:/mnt/HD/HD_a2/ha_backup'...
Nov 29 21:37:45 Chrizzonet unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,hard,relatime 'MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup' '/mnt/remotes/MYCLOUDEX2ULTRA_ha_backup'
Nov 29 21:37:45 Chrizzonet unassigned.devices: NFS mount failed: 'mount.nfs: Protocol not supported for MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup on /mnt/remotes/MYCLOUDEX2ULTRA_ha_backup'.
Nov 29 21:37:45 Chrizzonet unassigned.devices: Remote Share 'MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup' failed to mount.

I don´t know why... It was running for years now, changed nothing on that WD thing...

Post diagnostics.

4 hours ago, chrizzo said:

@dlandon
just tried, also no luck
Nov 29 21:37:45 Chrizzonet unassigned.devices: Mounting Remote Share 'MYCLOUDEX2ULTRA:/mnt/HD/HD_a2/ha_backup'...
Nov 29 21:37:45 Chrizzonet unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,hard,relatime 'MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup' '/mnt/remotes/MYCLOUDEX2ULTRA_ha_backup'
Nov 29 21:37:45 Chrizzonet unassigned.devices: NFS mount failed: 'mount.nfs: Protocol not supported for MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup on /mnt/remotes/MYCLOUDEX2ULTRA_ha_backup'.
Nov 29 21:37:45 Chrizzonet unassigned.devices: Remote Share 'MYCLOUDEX2ULTRA.LOCAL:/mnt/HD/HD_a2/ha_backup' failed to mount.

I don´t know why... It was running for years now, changed nothing on that WD thing...

Edit the /etc/nfsmount.conf file and remove or comment out the "Nfsvers=4":

#
# Setting this option makes it mandatory the server supports the
# given version. The mount will fail if the given version is 
# not support by the server. 
# limetech - support v4
# Nfsvers=4
Nfsvers=4

then update the nfs configuration:

/etc/rc.d/rc.nfsd reload

then try the mount.

Hey @dlandon thx a lot, that did the trick.
I also changed 'Defaultvers=4' to 'Defaultvers=3'.

 

Thx a lot pal!

4 hours ago, chrizzo said:

I also changed 'Defaultvers=4' to 'Defaultvers=3'.

Not sure this is advisable.   If the remote end supports v4 you probably want to use it.

@dlandon

i used another ssd  and it also keeps it online doest shut it down  when i pull it out of my server

is there something i need to add to my GO file or something so i no longer get those errors and it disconnects properly

 

tardis-diagnostics-20241130-0605.zip

5 hours ago, chrizzo said:

Hey @dlandon thx a lot, that did the trick.
I also changed 'Defaultvers=4' to 'Defaultvers=3'.

 

Thx a lot pal!

The idea with the NFS settings is to have NFS negotiate the version so servers supporting only version 3 will be mounted without specifying the version in the mount command.

 

For proper version 3 and 4 negotiation the settings should be:

Defaultvers=4 so the negotiation will start with NFSv4.

Nfsvers=4 commented out so NFSv3 will also be allowed.

 

In UD the 'Auto' setting in the Unassigned Settings for "NFS Version to use when Mounting Remote Shares" initiates the NFS version negotiation.

 

Setting these this way allows servers supporting v3 and servers supporting v4 to be mounted.  While I appreciate chenging both to v3 seemed to be a good idea for your situation, we want these settings to be applicable to all users so versions do not have to specified in the mount commands.  This also applies to fstab mounts.

1 hour ago, comet424 said:

@dlandon

i used another ssd  and it also keeps it online doest shut it down  when i pull it out of my server

is there something i need to add to my GO file or something so i no longer get those errors and it disconnects properly

 

tardis-diagnostics-20241130-0605.zip 317.21 kB · 0 downloads

I suggest you check your BIOS and be sure it is set properly for hot swapping disks.

@dlandon

just recently updated the bios yesterday  and yes i set them all sata drives to Enabled and Hot Swapable

 

the SSD  is connected to a LSI HBA card though

11 minutes ago, comet424 said:

@dlandon

just recently updated the bios yesterday  and yes i set them all sata drives to Enabled and Hot Swapable

 

the SSD  is connected to a LSI HBA card though

Maybe @JorgeB has some suggestions.