UncleStu

Similar to thin provisioning? So basically, not all of the space is allocated at once. That makes sense. However I moved all my VM's to the array and all that was left on my nvme cache was appdata and system files. And there is still that 160 GB delta between df and du and the Calculated space.

For the last 6+ months, my nvme cache drive has been slowly filling up. The last 4 weeks or so it has been pretty flat at ~58%. I built a new VM to replace an existing VM so I expected the cache drive to fill up some. The existing VM was 500 GB and the new VM is 300 GB. What was odd is that when I deleted the 500 GB VM, the new used space on the nvme cache was 67%. I wasn't expecting a ~10% increase when ultimately swapping in a smaller VM. I decided to move all my VMs into the array in hopes that there was something stuck or (no pun intended) cached in there. With no domains on my nvme cache, it is showing 33% in use. When I look at the disk usage for /mnt/nvme_cache, I only see 142G compared to 305G used with Disk Free. Compute space shows 151G in use. Where is this extra 160G sitting? I've tried Balancing and I scrubbed a few days before I built the new VM, but I don't know where to look next. unraid-diagnostics-20221123-1337.zip

Looking forward to the upgrade. Lots of great new features. I've been bit running RC code before so I'm hoping for the general release soon

Thx for looking at it. I don't shut down my systems too often. For now, when I eventually need to, I'll just make sure to shut down my unraid first.

Shutdown my Synology. All the syno share status dots turned grey. Told the array to stop. My remote unraid went to an UNMOUNTING state. A minute later, the first syno mount did too. Let it sit here for a couple of minutes, collected diag file ending in 1724. Powered the syno back up. As soon as the NAS was online, the NFS share dots turned green and they all changed to show MOUNT. My remote unraid went back to showing UNMOUNT. Collected another diag file ending in 1730 Remounted the shares Started my array unraid-diagnostics-20220409-1724.zip unraid-diagnostics-20220409-1730.zip

My rsync only runs between midnight and 8 AM. Interesting that there are additional log entries at 10 PM. I'm open to suggestions if there is a better way to push a duplicate copy of specific directories between A and B. I want to retain my file structure and purge out anything that no longer exists locally. This is my cmd line. rsync -hlrtv --progress --partial --append --delete-after --stop-at 08:00 /mnt/user/source/ /mnt/remotes/dest/ Come to think of it. The IP you show in the logs is my Synology. It does a rsync push to the unraid. Perhaps those are all the spam log entries you are noticing. Again, open to a better method if there is one. Good to know. I'm on the edge of my seat waiting for 6.10 to go GA, and not be RC. The shutdown was last week. I'll shutdown my Syno and get a new diagnostic while trying to stop the array.

Sorry. Added to my previous post.

I know this is an older post I'm circling back on, but I think there may still be an issue. I have a Synology NAS that I have created NFS mount points to from unRAID via UD. I had a planned power outage last week and I shut down my Syno first. When I went to stop the array on my unraid, it hung there with the dancing bars. UD was showing my top Synology NFS mount as "UNMOUNTING". It also showed all the points as offline. (No green dot) It remained like this for 5 minutes or so until I powered on my Synology. At which point everything unmounted and the array stopped. unraid-diagnostics-20220409-1306.zip

I have 2 unRAID servers. One locally and one remote. I use Wireguard between the two and Unassigned Devices to create a mount point from my local to remote server. I started getting read errors on a disk at the remote location so I powered it off so someone local could look at a few things for me. Shortly after the power off, I lost WebUI access to my local unRAID. Everything else worked, SSH, dockers, shares, etc. In looking at my syslog, there were repeated attempts to connect to my remote mount point. As soon as I had the remote unRAID powered on, my WebUI access was restored. This all leads to a few questions/thoughts/comments. I love Unassigned Devices, but is there a better way? The reason I say this is that I also have mount points from unraid to my Synology. If I power off my Synology before I unmount the shares, my unraid server fails to stop the array until the Synology is back online. (I recently tested this as I had a planned power outage and was shutting things down beforehand.) OK. I guess I really only had one question. Is there a better method to creating remote mounts that when the remote/external server(s) is offline my local unraid continues to run normally. My Synology mounts are for Plex backups and a music share. My remote unRAID mount is to push backups offsite via a rsync script. I would prefer to have full local functionality if either my remote server or Syno were off.

Can you set them to pass through and spin up a virtual Windows machine that can read them? Or do you by chance have an external enclosure that you can put them into and read them off your machine? My initial thought was the Windows Mirror as well, but you have proven that wrong. Aside from putting them into another Windows system and transferring the data that way, the only additional thing I can think of is taking a 4TB USB drive back to your original home and transferring the data to this USB drive. Preferable formatted in something that UD and Windows will like. One more thought, if the mirror pair is identical, you could try converting one to basic and leave the other one alone. And if you are really concerned about data loss and have a spare drive laying around, you could play with the conversion on that spare drive and see if UD could read it.

I apologize if this has been discussed before. I searched but only found one thing semi close to what I was searching for. And this could be a user education moment for me too. unRAID 6.9.2 UD 2022.01.03 (at the time) UD+ 2021.12.12 A little history: I had a planned power outage in my area, so before the power went out I stopped all my dockers and all but one VM. This VM was server DNS. I also spun down my HDD's as the running VM is on a NVMe drive. Power went out and the UPS estimated 45 minutes of run time. Around the 25 minutes left, I no longer needed that last VM and powered it off. I also initiated a stop to my array. The GUI sat at the dancing bars for 10+ minutes. I refreshed my screen and noticed that UD was trying to unmount the first of four NFS mounts to my Synology NAS. My Synology is on a UPS as well and was still up and running at this point. The NFS mounts are to share disks/directories between my unRAID and Syno NAS. These shares are used for backups and to my Plex docker. Also for backups (off box) and a music share. The music is on my Syno and Plex is on unRAID. I know unRAID UPS cut out before the array stopped as a parity check started when the power was restored. Question(s): Is there a way to force the NFS unmount after a set about of time so I can get my unRAID shutdown quicker? I just learned of the Tunable timeout of 330. Seeing as these are disk shares, is it OK to set this to 0? Would it make a difference during the shutdown of my unRAID? Lastly, the power outage was 4 days ago. Not sure if the diagnostics would yield anything at this point, but happy to collect it if it would have history that far back. TIA

Still getting the same warning message, but rolling back got my WebUI back. TY!

I ran a test backup after the updates to Unassigned Devices and no other changes. The backup completed just fine. The only difference this time was that I powered off my VM manually vs. letting the script do it. I want to test this more as it appeared to copy my previous backup file to the current date and then actually backup the VM to the new dated file as well. It definitely took longer and the logs read funny. I/E: (My recollection of the logs, I don't have access to them at the moment.) Copying backup VMimage_01-31-2020 to VMimage_02-05-2020 started. Copying backup VMimage_01-31-2020 to VMimage_02-05-2020 completed. Copying VMimage to VMimage_02-05-2020 started. Copying VMimage to VMimage_02-05-2020 completed. The good news though is that it finished with no errors.

Sweet. I'm all in for the change. I'll also test my backups again since the update to the Unassigned Devices plugin. I'll also create a new unRAID share and test backing up there. Ideally I would like the VM backups off box though.

I like the cleaner file structure, but would not want to lose the ability to clean up my older backups. Thinking out loud here. Could you take a listing of the folders within the backup directory and convert that to a date or variable to use? Say the backup location is /mnt/user/backups and then the VM Backup app creates dates as directories from there. I know within Linux you can get a listing of files or directories that are older than X days. Is there a way to generate this list on the fly and then purge out old directories that are older than X? Within the app the user can define the value for X.

Settings: Enable Snapshots - No Compress Backups - No Other Settings: Compare files during backup - No Disable delta syncs for backups - No Only use rsync for backups - No Danger Zone: Fall back to standard backups - No Pause VMs instead of shutting down - No

I am getting an error message about the vdisk failing to copy over, yet when I look at the destination location I can see the file there. My backup location set to a NFS mount point on a different NAS and it is successfully mounted via Unassigned Devices. Below is my log for the backup of my domain controller. However I am getting the same error on both VM's when they copy over. My DC is 80 GB and my other VM is 500 GB. Log: 2020-01-30 18:30 information: started attempt to backup DC1, Warden-80_40 to /mnt/disks/192.168.0.107_backup_PCs/unRAID/domains 2020-01-30 18:30 information: DC1 can be found on the system. attempting backup. 2020-01-30 18:30 information: creating local DC1.xml to work with during backup. 2020-01-30 18:30 information: /mnt/disks/192.168.0.107_backup_PCs/unRAID/domains/DC1 does not exist. creating it. 2020-01-30 18:30 information: extension for /mnt/user/isos/virtio-win-0.1.160-1.iso on DC1 was found in vdisks_extensions_to_skip. skipping disk. 2020-01-30 18:30 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2020-01-30 18:30 infomration: DC1 is running. vm desired state is shut off. 2020-01-30 18:30 information: performing 20 30 second cycles waiting for DC1 to shutdown cleanly. 2020-01-30 18:30 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2020-01-30 18:30 information: DC1 is shut off. vm desired state is shut off. can_backup_vm set to y. 2020-01-30 18:30 information: actually_copy_files is 1. 2020-01-30 18:30 information: can_backup_vm flag is y. starting backup of DC1 configuration, nvram, and vdisk(s). 2020-01-30 18:30 information: copy of DC1.xml to /mnt/disks/192.168.0.107_backup_PCs/unRAID/domains/DC1/20200130_1830_DC1.xml complete. 2020-01-30 18:30 information: DC1 does not appear to have an nvram file. skipping. 2020-01-30 18:35 failure: copy of /mnt/user/domains/DC1/vdisk1.img to /mnt/disks/192.168.0.107_backup_PCs/unRAID/domains/DC1/20200130_1830_vdisk1.img failed. 2020-01-30 18:35 information: backup of vdisk1.img vdisk to /mnt/disks/192.168.0.107_backup_PCs/unRAID/domains/DC1/20200130_1830_vdisk1.img complete. 2020-01-30 18:35 information: extension for /mnt/user/isos/virtio-win-0.1.160-1.iso on DC1 was found in vdisks_extensions_to_skip. skipping disk. 2020-01-30 18:35 information: the extensions of the vdisks that were backed up are img. 2020-01-30 18:35 information: vm_state is shut off. vm_original_state is running. starting DC1. 2020-01-30 18:35 information: vm_state is shut off. start_vm_after_backup is 1. starting DC1. 2020-01-30 18:35 information: backup of DC1 to /mnt/disks/192.168.0.107_backup_PCs/unRAID/domains/DC1 completed.