Elmojo

Members
  • Posts

    62
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Elmojo's Achievements

Rookie

Rookie (2/14)

11

Reputation

  1. Well, I had to do some shenanigans to get everything moved, but I think it's all there and appears to be working. That Dynamix File Manager is great! That feature alone is worth the update to 6.10.3, assuming that nothing else is broken behind the scenes. Thanks for your quick support. Let's call this one solved for now. 👊
  2. Now you tell me! lol I've updated to 6.10.3, installed the File Manager, and am currently moving the appdata folder to the cache. We'll see how to works... Worst case, I have a full back from a few days ago on the array...
  3. Is it? Ok, I'll update and try again. I've been holding off because I heard there were some issues in 6.10.x, and things had been stable here. I didn't want to introduce new problems... lol
  4. That sounds great, but I can't seem to find that plugin... nothing like that shows up when I search 'Dynamix'.
  5. Okay folks, I've messed something up I think. I'm attempting to upgrade my cache drive from a 250GB SSD to a 1TB PCIe NVMe. I followed this video I found, that seemed to be based on the UNRAID docs. I haven't been able to find the current actual documentation, but that this stage I'm afraid that may be irrelevant anyway. I stopped Docker and VM services, set all shares to 'yes' for cache, and ran mover. Nothing much happened, but after a reboot, I was finally able to get it to move everything to the array. Then I shut down, installed the new NVMe drive, and powered back up. I then stopped the array, removed the old cache, and selected the new drive. So far so good. Here's the issue... When I start setting things back to "Prefer" or "Only" for cache, mover throws "no space left on device" errors for Disk1, which is the array drive that it's copying from. This makes no sense, but it's stopping me from getting my appdata, domains, etc... back on the cache drive. I can't do it manually, since Docker is turned off, so I don't have access to my file manager. I'm not much good with the CLI, before you suggest that option. Any suggestions?
  6. Thanks to everyone for all the support! So I think it's obvious that this is a feature many would like to see. Other than our posting here, though, I'm not sure what else we can do to get the attention of the Devs. Hopefully they keep an eye on this area of the forum (what would be the point otherwise?) and will incorporate this feature into a future release. For all us OCD neat freak controlling types, it sure would be nice to be able to balance our dashboards a bit. I mean, even pfSense offers this type of basic UI customization. Just saying.... lol
  7. Please explain what you did, for the benefit of future noobs who may run into the same issue. 😁
  8. Thanks for that script link, I may give it a try on my T420! Please let me know if you get it working on your PE. I have mine running on a fixed level setting, and it's working okay so far, but I eventually intend to move my server to an unmonitored space, and I'd love to have it self-adjust the fan speed as necessary for the local temps.
  9. I've been getting a similar error for a while. I posted about it a page or so back, but we never did get it resolved. Maybe you'll have better success? I'd love to hear the solution. It's really annoying to have those error messages pop up every time it tries to run. In my case, the job errors out, then completes successfully, which is rather confusing, to say the least.
  10. This isn't something we should be expecting to be implemented any time real soon. I mean, it would be nice, but this thread is just the feature request. It means that we're asking the devs "Please can you consider this feature when you get time - please? 😁". As much as this bugs me, and I'd surely love to have it right now, I'm sure they have lots of other, more urgent things on the 'to do' list.
  11. It was suggested way back (by you I believe) that we not use the default job, but create our own jobs. I can't recall why. Maybe it's in the documentation? It's been a while now, and my memory isn't so good these days... lol
  12. I'd be happy to, but I have no idea how to access that file.
  13. So I'm still getting these odd "cannot run" error messages, even though everything seems to be working correctly. Any update on how to make it stop throwing false errors? It's really disconcerting when I open the dashboard, and see an orange warning message. Makes me thing something has gone wrong. lol Here's my complete log file for the job that ran last night... 2022-02-15 02:00:01 Start logging to log file. 2022-02-15 02:00:01 information: send_notifications is 1. notifications will be sent. 2022-02-15 02:00:01 information: only_send_error_notifications is 0. normal notifications will be sent if send_notifications is enabled. 2022-02-15 02:00:01 information: keep_log_file is 1. log files will be kept. 2022-02-15 02:00:01 information: number_of_log_files_to_keep is 1. this is probably a sufficient number of log files to keep. 2022-02-15 02:00:01 information: enable_vm_log_file is 0. vm specific logs will not be created. 2022-02-15 02:00:01 information: backup_all_vms is 1. vms_to_backup will be ignored. all vms will be backed up. 2022-02-15 02:00:01 information: use_snapshots is 0. vms will not be backed up using snapshots. 2022-02-15 02:00:01 information: kill_vm_if_cant_shutdown is 0. vms will not be forced to shutdown if a clean shutdown can not be detected. 2022-02-15 02:00:01 information: set_vm_to_original_state is 1. vms will be set to their original state after backup. 2022-02-15 02:00:01 information: number_of_days_to_keep_backups is 0. backups will be kept indefinitely. be sure to set number_of_backups_to_keep to keep backups storage usage down. 2022-02-15 02:00:01 information: number_of_backups_to_keep is 2. this is probably a sufficient number of backups to keep. 2022-02-15 02:00:01 information: inline_zstd_compress is 1. vdisk images will be inline compressed but will not be compared afterwards or post compressed. 2022-02-15 02:00:01 information: zstd_level is 3. 2022-02-15 02:00:01 information: zstd_threads is 2. 2022-02-15 02:00:01 information: use_snapshots disabled, not adding snapshot_extension to vdisk_extensions_to_skip. 2022-02-15 02:00:01 information: snapshot_fallback is 0. snapshots will fallback to standard backups. 2022-02-15 02:00:01 information: pause_vms is 0. vms will be shutdown for standard backups. 2022-02-15 02:00:01 information: enable_reconstruct_write is 0. reconstruct write will not be enabled by this script. 2022-02-15 02:00:01 information: backup_xml is 1. vms will have their xml configurations backed up. 2022-02-15 02:00:01 information: backup_nvram is 1. vms will have their nvram backed up. 2022-02-15 02:00:01 information: backup_vdisks is 1. vms will have their vdisks backed up. 2022-02-15 02:00:01 information: start_vm_after_backup is 0. vms will not be started following successful backup. 2022-02-15 02:00:01 information: start_vm_after_failure is 0. vms will not be started following an unsuccessful backup. 2022-02-15 02:00:01 information: disable_delta_sync is 0. rsync will be used to perform delta sync backups. 2022-02-15 02:00:01 information: rsync_only is 0. cp will be used when applicable. 2022-02-15 02:00:01 information: actually_copy_files is 1. files will be copied. 2022-02-15 02:00:01 information: clean_shutdown_checks is 20. this is probably a sufficient number of shutdown checks. 2022-02-15 02:00:01 information: seconds_to_wait is 30. this is probably a sufficient number of seconds to wait between shutdown checks. 2022-02-15 02:00:01 information: keep_error_log_file is 1. error log files will be kept. 2022-02-15 02:00:01 information: number_of_error_log_files_to_keep is 10. this is probably a sufficient error number of log files to keep. 2022-02-15 02:00:01 information: started attempt to backup BlueIris Server (W10), Sandbox (W10 ), Windows 11 to /mnt/user/Backup/xVM Backups 2022-02-15 02:00:02 information: BlueIris Server (W10) can be found on the system. attempting backup. 2022-02-15 02:00:02 information: creating local BlueIris Server (W10).xml to work with during backup. 2022-02-15 02:00:02 information: /mnt/user/Backup/xVM Backups/BlueIris Server (W10) exists. continuing. 2022-02-15 02:00:02 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2022-02-15 02:00:02 infomration: BlueIris Server (W10) is running. vm desired state is shut off. 2022-02-15 02:00:03 information: performing 20 30 second cycles waiting for BlueIris Server (W10) to shutdown cleanly. 2022-02-15 02:00:03 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2022-02-15 02:00:33 information: BlueIris Server (W10) is shut off. vm desired state is shut off. can_backup_vm set to y. 2022-02-15 02:00:33 information: actually_copy_files is 1. 2022-02-15 02:00:33 information: can_backup_vm flag is y. starting backup of BlueIris Server (W10) configuration, nvram, and vdisk(s). 2022-02-15 02:00:33 information: copy of BlueIris Server (W10).xml to /mnt/user/Backup/xVM Backups/BlueIris Server (W10)/20220215_0200_BlueIris Server (W10).xml complete. 2022-02-15 02:00:33 information: copy of /etc/libvirt/qemu/nvram/1f335446-855e-7049-961e-043582ac2630_VARS-pure-efi.fd to /mnt/user/Backup/xVM Backups/BlueIris Server (W10)/20220215_0200_1f335446-855e-7049-961e-043582ac2630_VARS-pure-efi.fd complete. 2022-02-15 02:04:54 information: copy of /mnt/cache/domains/Windows 10/vdisk1.img to /mnt/user/Backup/xVM Backups/BlueIris Server (W10)/20220215_0200_vdisk1.img.zst complete. 2022-02-15 02:04:54 information: backup of /mnt/cache/domains/Windows 10/vdisk1.img vdisk to /mnt/user/Backup/xVM Backups/BlueIris Server (W10)/20220215_0200_vdisk1.img.zst complete. 2022-02-15 02:04:54 information: the extensions of the vdisks that were backed up are img. 2022-02-15 02:04:54 information: vm_state is shut off. vm_original_state is running. starting BlueIris Server (W10). 2022-02-15 02:04:55 information: backup of BlueIris Server (W10) to /mnt/user/Backup/xVM Backups/BlueIris Server (W10) completed. 2022-02-15 02:04:55 information: number of days to keep backups set to indefinitely. 2022-02-15 02:04:55 information: cleaning out backups over 2 in location /mnt/user/Backup/xVM Backups/BlueIris Server (W10)/ 2022-02-15 02:04:55 information: removed '/mnt/user/Backup/xVM Backups/BlueIris Server (W10)/20220125_1020_BlueIris Server (W10).xml' config file. 2022-02-15 02:04:55 information: removed '/mnt/user/Backup/xVM Backups/BlueIris Server (W10)/20220125_1020_1f335446-855e-7049-961e-043582ac2630_VARS-pure-efi.fd' nvram file. 2022-02-15 02:04:55 information: removed '/mnt/user/Backup/xVM Backups/BlueIris Server (W10)/20220125_1020_vdisk1.img.zst' vdisk image file. 2022-02-15 02:04:55 information: did not find any vm log files to remove. 2022-02-15 02:04:55 information: removing local BlueIris Server (W10).xml. 2022-02-15 02:04:55 information: Sandbox (W10 ) can be found on the system. attempting backup. 2022-02-15 02:04:55 information: creating local Sandbox (W10 ).xml to work with during backup. 2022-02-15 02:04:55 information: /mnt/user/Backup/xVM Backups/Sandbox (W10 ) exists. continuing. 2022-02-15 02:04:55 information: extension for /mnt/user/isos/ru-en_windows_10_20H2_x86-x64_28in1_HWID-act.iso on Sandbox (W10 ) was found in vdisks_extensions_to_skip. skipping disk. 2022-02-15 02:04:55 information: extension for /mnt/user/isos/virtio-win-0.1.208.iso on Sandbox (W10 ) was found in vdisks_extensions_to_skip. skipping disk. 2022-02-15 02:04:55 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2022-02-15 02:04:55 infomration: Sandbox (W10 ) is running. vm desired state is shut off. 2022-02-15 02:05:55 information: performing 20 30 second cycles waiting for Sandbox (W10 ) to shutdown cleanly. 2022-02-15 02:05:55 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2022-02-15 02:06:25 information: Sandbox (W10 ) is running. vm desired state is shut off. 2022-02-15 02:06:25 information: cycle 2 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2022-02-15 02:06:55 information: Sandbox (W10 ) is shut off. vm desired state is shut off. can_backup_vm set to y. 2022-02-15 02:06:55 information: actually_copy_files is 1. 2022-02-15 02:06:55 information: can_backup_vm flag is y. starting backup of Sandbox (W10 ) configuration, nvram, and vdisk(s). 2022-02-15 02:06:55 information: copy of Sandbox (W10 ).xml to /mnt/user/Backup/xVM Backups/Sandbox (W10 )/20220215_0200_Sandbox (W10 ).xml complete. 2022-02-15 02:06:55 information: copy of /etc/libvirt/qemu/nvram/6eee4b38-2964-616c-20e2-b7ce678ba076_VARS-pure-efi.fd to /mnt/user/Backup/xVM Backups/Sandbox (W10 )/20220215_0200_6eee4b38-2964-616c-20e2-b7ce678ba076_VARS-pure-efi.fd complete. 2022-02-15 02:10:15 information: copy of /mnt/cache/domains/Win10 Sandbox/vdisk1.img to /mnt/user/Backup/xVM Backups/Sandbox (W10 )/20220215_0200_vdisk1.img.zst complete. 2022-02-15 02:10:15 information: backup of /mnt/cache/domains/Win10 Sandbox/vdisk1.img vdisk to /mnt/user/Backup/xVM Backups/Sandbox (W10 )/20220215_0200_vdisk1.img.zst complete. 2022-02-15 02:10:15 information: extension for /mnt/user/isos/ru-en_windows_10_20H2_x86-x64_28in1_HWID-act.iso on Sandbox (W10 ) was found in vdisks_extensions_to_skip. skipping disk. 2022-02-15 02:10:15 information: extension for /mnt/user/isos/virtio-win-0.1.208.iso on Sandbox (W10 ) was found in vdisks_extensions_to_skip. skipping disk. 2022-02-15 02:10:15 information: the extensions of the vdisks that were backed up are img. 2022-02-15 02:10:15 information: vm_state is shut off. vm_original_state is running. starting Sandbox (W10 ). 2022-02-15 02:10:16 information: backup of Sandbox (W10 ) to /mnt/user/Backup/xVM Backups/Sandbox (W10 ) completed. 2022-02-15 02:10:16 information: number of days to keep backups set to indefinitely. 2022-02-15 02:10:16 information: cleaning out backups over 2 in location /mnt/user/Backup/xVM Backups/Sandbox (W10 )/ 2022-02-15 02:10:16 information: removed '/mnt/user/Backup/xVM Backups/Sandbox (W10 )/20220125_1020_Sandbox (W10 ).xml' config file. 2022-02-15 02:10:16 information: removed '/mnt/user/Backup/xVM Backups/Sandbox (W10 )/20220125_1020_6eee4b38-2964-616c-20e2-b7ce678ba076_VARS-pure-efi.fd' nvram file. 2022-02-15 02:10:16 information: removed '/mnt/user/Backup/xVM Backups/Sandbox (W10 )/20220125_1020_vdisk1.img.zst' vdisk image file. 2022-02-15 02:10:16 information: did not find any vm log files to remove. 2022-02-15 02:10:16 information: removing local Sandbox (W10 ).xml. 2022-02-15 02:10:16 information: Windows 11 can be found on the system. attempting backup. 2022-02-15 02:10:16 information: creating local Windows 11.xml to work with during backup. 2022-02-15 02:10:16 information: /mnt/user/Backup/xVM Backups/Windows 11 exists. continuing. 2022-02-15 02:10:16 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2022-02-15 02:10:16 information: Windows 11 is shut off. vm desired state is shut off. can_backup_vm set to y. 2022-02-15 02:10:16 information: actually_copy_files is 1. 2022-02-15 02:10:16 information: can_backup_vm flag is y. starting backup of Windows 11 configuration, nvram, and vdisk(s). 2022-02-15 02:10:16 information: copy of Windows 11.xml to /mnt/user/Backup/xVM Backups/Windows 11/20220215_0200_Windows 11.xml complete. 2022-02-15 02:10:16 information: copy of /etc/libvirt/qemu/nvram/985ce70c-f343-81f3-65e3-94e77b37d0e7_VARS-pure-efi.fd to /mnt/user/Backup/xVM Backups/Windows 11/20220215_0200_985ce70c-f343-81f3-65e3-94e77b37d0e7_VARS-pure-efi.fd complete. 2022-02-15 02:12:43 information: copy of /mnt/user/domains/Windows 11/vdisk1.img to /mnt/user/Backup/xVM Backups/Windows 11/20220215_0200_vdisk1.img.zst complete. 2022-02-15 02:12:43 information: backup of /mnt/user/domains/Windows 11/vdisk1.img vdisk to /mnt/user/Backup/xVM Backups/Windows 11/20220215_0200_vdisk1.img.zst complete. 2022-02-15 02:12:43 information: the extensions of the vdisks that were backed up are img. 2022-02-15 02:12:43 information: vm_state is shut off. vm_original_state is shut off. not starting Windows 11. 2022-02-15 02:12:43 information: backup of Windows 11 to /mnt/user/Backup/xVM Backups/Windows 11 completed. 2022-02-15 02:12:43 information: number of days to keep backups set to indefinitely. 2022-02-15 02:12:43 information: cleaning out backups over 2 in location /mnt/user/Backup/xVM Backups/Windows 11/ 2022-02-15 02:12:44 information: did not find any config files to remove. 2022-02-15 02:12:44 information: did not find any nvram files to remove. 2022-02-15 02:12:44 information: did not find any vdisk image files to remove. 2022-02-15 02:12:44 information: did not find any vm log files to remove. 2022-02-15 02:12:44 information: removing local Windows 11.xml. 2022-02-15 02:12:44 information: finished attempt to backup BlueIris Server (W10), Sandbox (W10 ), Windows 11 to /mnt/user/Backup/xVM Backups. 2022-02-15 02:12:44 information: cleaning out logs over 1. 2022-02-15 02:12:44 information: removed '/mnt/user/Backup/xVM Backups/logs/20220201_0200_unraid-vmbackup.log'. 2022-02-15 02:12:44 information: cleaning out error logs over 10. 2022-02-15 02:12:44 information: did not find any error log files to remove. 2022-02-15 02:12:44 Stop logging to log file. And here's what the message is saying on screen.... For reference, the "default" job is disabled completely, both by selecting Enable Backups? to 'No' and by setting Backup Frequency to 'Disabled'.
  14. That's what this whole thread is about. Welcome to the club.