Oldbean57

This updated version also fixed the search issue for me, thank-you @Squid (although curiously I had it without having any VPN in use - I wish I had captured logs before updating to 2025.01.12). But now I want a Bodyblade...

Yes that's correct - the drop-down only shows local shares when I look at mine here. The path for remote shares is /mnt/remotes/<name_of_mount_point>/ So, in the Main -> Unassigned Devices section of Unraid, if your SMB/NFS/ISO Mount Point was called Backups, the path to type in to the "Set backup location" box would be /mnt/remotes/Backups/ Hope that helps. (Caveat that I only have SMB remote shares so I've not seen if there is any different format for NFS).

Hi. Yes I've experienced the same. I expect the plugin will need some updates to work with the newer version of PHP in Unraid 7. The plugin developer says they have a lot on at the moment, so I'm not sure when they might have time to do this, but in the meantime it's been working for me to edit: /config/plugins/vmbackup/user.cfg on the Flash Drive for any settings changes, then use the included commands.sh script to write these settings out to the user-script.sh script (in the same folder), so they apply to your backups. This assumes you're just using the default config and not any custom ones. E.g.: cd /usr/local/emhttp/plugins/vmbackup/scripts ./commands.sh update_user_script Since yours is a new server you'll probably also need to create the schedule (cronjob) and this can be done using the update_cron_job parameter on the commands.sh script once you've set the cron variables in user.cfg: cd /usr/local/emhttp/plugins/vmbackup/scripts ./commands.sh update_cron_job Commands.sh can also be used to start a manual backup (as I find that button is not working in the UI at the moment), by using the backup_now parameter: cd /usr/local/emhttp/plugins/vmbackup/scripts ./commands.sh backup_now I don't completely understand the setup and flow between the different components, but this is what I've been able to deduce just to get things running in the meantime, so I hope it helps. Thanks to @JTok for this plugin and the helpful comments in the code. Hopefully the bodging around above won't make them wince too much

Thank-you for your feedback @ChatNoir and @bonienl for the settings tip - that does help. Interestingly, I've found this setting is a little inconsistent in where it applies. For example, it has worked for device names in the Main tab, but not the Dashboard tab. It works in the Shares tab, but not the Shares Settings page. EDIT: I just upgraded to 6.10.0-rc4 (need to test ipvlan vs macvlan for some network-related crashes) and have found that the lower-case "raw" behaviour is now consistent across all tabs, thank-you Thanks, Rich.

Hi, This is just a small cosmetic request, please: I use lower case names for my Pools in Unraid 6.9.2 as I like the consistency with other names such as disk1, disk2 and ease-of-typing when using the terminal. But since they are acronyms such as SSD and TM (Time Machine), they look odd when shown in the UI as Ssd, Tm etc*. I wondered if it would be possible for you to stop auto-capitalising the first letter off Pool names in the UI please, so they show exactly as named? Like I said, just a small thing, but thought I would ask! Many thanks, Rich. (*I know they are acronyms and should be upper case, but this is just my preference for making the terminal approach the consistent one).

Hi, It's funny you say that, before it started working (spoiler alert), the FS type was listed as btrfs in the FS column in UD. It's a SATA M.2 SSD. After I did the manual decrypt with cryptsetup in the Terminal, I thought I would test a mount via the UD GUI, which unfortunately still didn't work (same error). However I noticed that the FS type changed to crypto_LUKS: I wanted to send you a screenshot of the before and after, so rebooted to reset the encryption, but post-reboot the FS type was still crypto_LUKS, not back to btrfs. After entering the array passphrase I then tried a UD mount and it worked! Automount post-reboot also works as expected, so I'm delighted about that. I don't know whether it was the manual one-off cryptsetup or the reboot that resolved it, but all is now well. It might be hard to get to the bottom of it, but if there is anything further you'd be interested to see please do let me know. Thanks for your help, small Paypal retirement contribution incoming Rich.

After seeing the output of the diagnostics, I decided to have a look for the successful mounting of the HDD from the array to see why that would be any different for /dev/sdd, but I'm not sure if the details of a successful mount are recorded in detail as part of the "unassigned.devices" logging? I was able to see the failed mount, for example: Mar 16 16:57:31 NAS unassigned.devices: Adding disk '/dev/sdj1'... Mar 16 16:57:31 NAS unassigned.devices: Mount drive command: /sbin/mount -t btrfs -o auto,async,noatime,nodiratime '/dev/sdj1' '/mnt/disks/WDC_WDS100T2B0B-00YS70_180481420126' Mar 16 16:57:31 NAS unassigned.devices: Mount of '/dev/sdj1' failed. Error message: mount: /mnt/disks/WDC_WDS100T2B0B-00YS70_180481420126: wrong fs type, bad option, bad superblock on /dev/sdj1, missing codepage or helper program, or other error. Mar 16 16:57:31 NAS unassigned.devices: Partition 'WDC_WDS100T2B0B-00YS70_180481420126' could not be mounted... Looking in the logs at how the encrypted disks in the array are unlocked using "cryptsetup" and then mounted, I replicated this manually via the Terminal for /dev/sdj1 and it mounted successfully, so I have a manual workaround for now from which I can run VMs: root@NAS:/mnt# cryptsetup luksOpen /dev/sdj1 sdj1 Enter passphrase for /dev/sdj1: root@NAS:/mnt# mount -t btrfs -o auto,async,noatime,nodiratime '/dev/mapper/sdj1' '/mnt/disks/test' root@NAS:/mnt# cd /mnt/disks/test root@NAS:/mnt/disks/test# ls root@NAS:/mnt/disks/test# ls -la total 16 drwxrwxrwx 1 nobody users 0 Mar 16 16:50 ./ drwxrwxrwx 3 nobody users 60 Mar 16 20:27 ../ root@NAS:/mnt/disks/test# However it would be great to be able to use Unassigned Devices to have this happen automatically using the same passphrase as entered to start the array after each boot, then all will be mounted and ready for the VM services to start. I think the key is to work out why /dev/sdd mounted using the array passphrase but /dev/sdj will not. Thanks for your help, Rich.

Hi, thanks for getting back to me already. Diagnostics file attached. Thanks, Rich. nas-diagnostics-20180316-1903.zip

Hello, New unRAID user here. I've been having a lot of fun setting my new server up having come from a Synology background. I'm pretty much there, but do have one question about mounting an encrypted unassigned device that I'd appreciate some help with please. My array consists of 6 x HDDs, 2 x SSDs for cache and I have just added a final single M.2 SSD which I intend to use as a standalone unassigned device for virtual disk images. The main reason for being standalone is that I see that SSDs are not yet supported as part of the array and it's much higher capacity than the 2 x SSDs working as cache so wouldn't be fully utilised. I would very much prefer to have the M.2 SSD encrypted in the same way as the other disks in the system (all BTRFS encrypted). I read this statement in the plugin info... An encrypted array disk can be mounted in UD with the following restrictions: The array disk passphrase has to be defined. You cannot enter the passphrase for the disk in UD. An array encrypted disk cannot be created with UD. The disk can only be mounted if the current array passphrase is the same as the UD encrypted disk. Note: There has to be at least one encrypted disk in the array. ... and thought I'd been pretty clever in adding the M.2 SSD temporarily to the array so it was formatted as "BTRFS encrypted" using the same array passphrase, then removing it (shrinking the array) so I could then mount it via UD as per the above. When I try and mount it however, I see this error message in the logs: Mar 16 17:23:51 NAS unassigned.devices: Mount of '/dev/sdj1' failed. Error message: mount: /mnt/disks/WDC_WDS100T2B0B-00YS70_180481420126: wrong fs type, bad option, bad superblock on /dev/sdj1, missing codepage or helper program, or other error. I thought perhaps there was an issue with using BTRFS encrypted, but if I remove another HDD of the same format from the array, it mounts without error in UD, so UD is using the array passphrase OK. The M.2 SSD will also add back in to the array without needing to be reformatted, suggesting the file system is OK. Any suggestions appreciated thank-you. Rich.