Jump to content

jpowell8672

Members
  • Content Count

    258
  • Joined

Community Reputation

42 Good

About jpowell8672

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Remove Unraid USB drive then connect to Windows PC and backup drive contents to PC. Then do fresh install of Unraid version you want on USB drive and copy the Config folder from your PC backup to the Unraid USB drive you just made. Plug USB back into your Unraid box and boot.
  2. Can't you just do the backup without using snapshot feature? I could but would rather not take down my outside network with pfsense vm going down during backup.
  3. I changed the backup location in vm backup settings to /mnt/cache/ by accident I was up long time tired made mistake of not changing in vm instead. pfsense does not natively support qemu-guest-agent at the moment, will snapshots still work ok?
  4. I had snapshots enabled and it broke my pfsense vm and had to manually restore. Going to disable vm backup plugin for now and wait for you to work out the bugs. Thanks @JTok
  5. 2020-01-05 07:00 information: Windows 10 can be found on the system. attempting backup. 2020-01-05 07:00 information: creating local Windows 10.xml to work with during backup. 2020-01-05 07:00 information: /mnt/cache/backup/Windows 10 exists. continuing. 2020-01-05 07:00 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. Windows 10 is running. can_backup_vm set to y. 2020-01-05 07:00 information: actually_copy_files is 1. 2020-01-05 07:00 information: can_backup_vm flag is y. starting backup of Windows 10 configuration, nvram, and vdisk(s). sending incremental file list Windows 10.xml sent 7,392 bytes received 35 bytes 14,854.00 bytes/sec total size is 7,292 speedup is 0.98 2020-01-05 07:00 information: copy of Windows 10.xml to /mnt/cache/backup/Windows 10/20200105_0700_Windows 10.xml complete. sending incremental file list 6d8d5b31-ae31-9fdc-f498-fa9c73b2221a_VARS-pure-efi.fd sent 131,241 bytes received 35 bytes 262,552.00 bytes/sec total size is 131,072 speedup is 1.00 2020-01-05 07:00 information: copy of /etc/libvirt/qemu/nvram/6d8d5b31-ae31-9fdc-f498-fa9c73b2221a_VARS-pure-efi.fd to /mnt/cache/backup/Windows 10/20200105_0700_6d8d5b31-ae31-9fdc-f498-fa9c73b2221a_VARS-pure-efi.fd complete. 2020-01-05 07:00 information: extension for /mnt/user/isos/Win10_1903_V1_English_x64.iso on Windows 10 was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 information: extension for /mnt/user/isos/virtio-win-0.1.160-1.iso on Windows 10 was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 information: the extensions of the vdisks that were backed up are . 2020-01-05 07:00 information: vm_state is running. vm_original_state is running. not starting Windows 10. 2020-01-05 07:00 information: backup of Windows 10 to /mnt/cache/backup/Windows 10 completed. 2020-01-05 07:00 information: number of days to keep backups set to indefinitely. 2020-01-05 07:00 information: cleaning out backups over 3 in location /mnt/cache/backup/Windows 10/ 2020-01-05 07:00 information: did not find any config files to remove. 2020-01-05 07:00 information: did not find any nvram files to remove. /tmp/vmbackup/scripts/user-script.sh: line 2809: 😞 command not found 2020-01-05 07:00 information: did not find any image files to remove. 2020-01-05 07:00 information: removing local Windows 10.xml. removed 'Windows 10.xml' 2020-01-05 07:00 information: pfsense can be found on the system. attempting backup. 2020-01-05 07:00 information: creating local pfsense.xml to work with during backup. 2020-01-05 07:00 information: /mnt/cache/backup/pfsense exists. continuing. 2020-01-05 07:00 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. pfsense is running. can_backup_vm set to y. 2020-01-05 07:00 information: actually_copy_files is 1. 2020-01-05 07:00 information: can_backup_vm flag is y. starting backup of pfsense configuration, nvram, and vdisk(s). sending incremental file list pfsense.xml sent 7,574 bytes received 35 bytes 15,218.00 bytes/sec total size is 7,477 speedup is 0.98 2020-01-05 07:00 information: copy of pfsense.xml to /mnt/cache/backup/pfsense/20200105_0700_pfsense.xml complete. sending incremental file list 7ee726f1-17c6-3496-d3a2-cb1916f748eb_VARS-pure-efi.fd sent 131,240 bytes received 35 bytes 262,550.00 bytes/sec total size is 131,072 speedup is 1.00 2020-01-05 07:00 information: copy of /etc/libvirt/qemu/nvram/7ee726f1-17c6-3496-d3a2-cb1916f748eb_VARS-pure-efi.fd to /mnt/cache/backup/pfsense/20200105_0700_7ee726f1-17c6-3496-d3a2-cb1916f748eb_VARS-pure-efi.fd complete. 2020-01-05 07:00 information: extension for /mnt/user/isos/pfSense-CE-2.4.4-RELEASE-p3-amd64.iso on pfsense was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 failure: extension for /mnt/user/domains/pfsense/vdisk1.snap on pfsense is the same as the snapshot extension snap. disk will always be skipped. this usually means that the disk path in the config was not changed from /mnt/user. if disk path is correct, then try changing snapshot_extension or vdisk extension. 2020-01-05 07:00 information: extension for /mnt/user/domains/pfsense/vdisk1.snap on pfsense was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 information: the extensions of the vdisks that were backed up are . 2020-01-05 07:00 information: vm_state is running. vm_original_state is running. not starting pfsense. 2020-01-05 07:00 information: backup of pfsense to /mnt/cache/backup/pfsense completed. 2020-01-05 07:00 information: number of days to keep backups set to indefinitely. 2020-01-05 07:00 information: cleaning out backups over 3 in location /mnt/cache/backup/pfsense/ 2020-01-05 07:00 information: did not find any config files to remove. 2020-01-05 07:00 information: did not find any nvram files to remove. /tmp/vmbackup/scripts/user-script.sh: line 2809: 😞 command not found 2020-01-05 07:00 information: did not find any image files to remove. 2020-01-05 07:00 information: removing local pfsense.xml. removed 'pfsense.xml' 2020-01-05 07:00 information: finished attempt to backup Windows 10, pfsense to /mnt/cache/backup. 2020-01-05 07:00 information: cleaning out logs over 1. 2020-01-05 07:00 information: removed '/mnt/cache/backup/logs/20200103_0819_unraid-vmbackup.log'. 2020-01-05 07:00 information: cleaning out error logs over 10. find: '/mnt/cache/backup/logs/*unraid-vmbackup_error.log': No such file or directory 2020-01-05 07:00 information: did not find any error log files to remove. 2020-01-05 07:00 warning: errors found. creating error log file. sending incremental file list 20200105_0700_unraid-vmbackup.log sent 8,049 bytes received 35 bytes 5,389.33 bytes/sec total size is 7,930 speedup is 0.98 2020-01-05 07:00 Stop logging to log file. 2020-01-05 07:00 Stop logging to error log file. 2020-01-05 07:00:02 Removed: /tmp/vmbackup/scripts/user-script.sh 2020-01-05 07:00:02 Removed: /tmp/vmbackup/scripts/user-script.pid
  6. I got a notification of a failed error from vm backup when it tried to do a backup from a set schedule. When going to vm backup in settings this error is shown at the top of vm backup settings tab right above basic settings.
  7. Warning: parse_ini_file(/boot/config/plugins/vmbackup/vdisk-list.txt): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(501) : eval()'d code on line 55
  8. The one thing I like about Unraid the most is the community which they have created that helps anyone & everyone! I would most like to see added to Unraid in 2020 is the support for an all SSD array pool and if it is still to early for that then a Unraid version with the Nvidia driver by Unraid.
  9. Upgraded from 6.7.2 to 6.8 with only one problem, the pfsense vm hang issue described here: I was able to fix with @bastl workaround. Thanks
  10. I also had this problem when upgrading to 6.8 and used your emulate a Intel Skylake CPU on my Threadripper as a workaround for now until this issue gets resolved. Thank You
  11. No the person was named: findingdeals and I just looked he does not have any more at the moment. Your best bet is to look for used server pulls from someone with 100% positive feedback and you should be OK.
  12. Linux kernel We started 6.8 development and initial testing using Linux 5.x kernel. However there remains an issue when VM's and Docker containers using static IP addresses are both running on the same host network interface. This issue does not occur with the 4.19 kernel. We are still studying this issue and plan to address it in the Unraid 4.19 release. Typo above, I'm sure you meant Unraid 6.9 release.
  13. Thank you so much for all your past and future hard work, I very much appreciate it 👍