eltonk

As I said, there are no hardware issues. Rolling back the installation to the previous 6.11.5 version fixed the issue. So, if anyone faces this issue, I recommend rolling back the update. Thanks for the support, but I'll wait for the next bug-fixes release before update it again.

Ouch... so, the update process destroyed all my cache data?! I'm pretty sure that the issue is not cables as you suggested... It was working perfectly before the update to version 6.12

draco-diagnostics-20230620-1309.zip Hi @JorgeB Here it is. Thanks

After update Unraid to latest 6.12.0, my MS Windows VM is not starting anymore. I checked the disk permissions, but seems ok. I tried to change the ownership to "nobody" and got the same error (as you can see below). Any help on how to fix this? root@draco:/mnt/cache/domains/Windows 11 VM# ls -la total 50609848 drwxr-xr-x 1 nobody users 20 Mar 30 15:09 ./ drwxrwxrwx 1 nobody users 46 Mar 30 15:09 ../ -rwxrwxrwx 1 root users 68719476736 Jun 20 01:08 vdisk1.img* root@draco:/mnt/cache/domains/Windows 11 VM# chown nobody:users vdisk1.img chown: changing ownership of 'vdisk1.img': Read-only file system root@draco:/mnt/cache/domains/Windows 11 VM# ls -la total 50609848 drwxr-xr-x 1 nobody users 20 Mar 30 15:09 ./ drwxrwxrwx 1 nobody users 46 Mar 30 15:09 ../ -rwxrwxrwx 1 root users 68719476736 Jun 20 01:08 vdisk1.img* root@draco:/mnt/cache/domains/Windows 11 VM#

After update Unraid to latest 6.12.0, my MS Windows VM is not starting anymore. I checked the disk permissions, but seems ok. I tried to change the ownership to "nobody" and got the same error (as you can see below). Any help on how to fix this? root@draco:/mnt/cache/domains/Windows 11 VM# ls -la total 50609848 drwxr-xr-x 1 nobody users 20 Mar 30 15:09 ./ drwxrwxrwx 1 nobody users 46 Mar 30 15:09 ../ -rwxrwxrwx 1 root users 68719476736 Jun 20 01:08 vdisk1.img* root@draco:/mnt/cache/domains/Windows 11 VM# chown nobody:users vdisk1.img chown: changing ownership of 'vdisk1.img': Read-only file system root@draco:/mnt/cache/domains/Windows 11 VM# ls -la total 50609848 drwxr-xr-x 1 nobody users 20 Mar 30 15:09 ./ drwxrwxrwx 1 nobody users 46 Mar 30 15:09 ../ -rwxrwxrwx 1 root users 68719476736 Jun 20 01:08 vdisk1.img* root@draco:/mnt/cache/domains/Windows 11 VM#

Wow! Great news. I'll be testing this in the next days! Many Thanks!

Try this plugin. it woked to me: https://raw.githubusercontent.com/DanITman/unraid-nvidia-vgpu-driver/master/nvidia-vgpu-driver.plg

Same issue here.

So you are saying that we should not trust on the Unraid's top banner telling us to "update" the system because it can be a Malware?! This is a joke, right?

Sorry... This is not true. The release notes shown on web-gui is this one: And again... I do not think that it is wise to not put such an important note, that the release MOST PROBABLY will break your eth connection, in the release notes that 99% of the users will read.... I do not have more time for you. I'm just trying to alert other users about this BAD RELEASE VERSION! But unfortunately, most of the users are not ADVANCED users that always read all the forum posts before clicking on the top button suggested by their Unraid web-gui interface to update to this BAD RELEASE.

I read the changelog.... and there is nothing there saying that your Network cards will not work anymore

Anything that do not work as a "single update click" button, should not be offered in the web-gui to the final users, am I wrong? Or are you saying that Unraid is only for Advanced Users that reads the 1st forum post before click in the button that shows in their web-gui interface?

What has an issue is this VERSION, that do not work for most of the users as far I can see here Please, do a better work next time.

How is possible a company like Unraid, where everyone trust to buy a license of use and store their data, relase such BAD RELEASE?!?!?! I do not have problems with my CAPS! I'm just cannot believe that UNRAID can create such mess with their users!!! HOW DO I ROLLBACK THIS UPDATE?!? Can some one from real support let me know clear how to do this?!?!?!??!

HOW DO I ROLLBACK THIS UPDATE??!?!?

It seems that the network cards are not recognized anymore!!! THIS UPDATE IS NOT GOOD!!!! STOP! DO NOT UPDATE!!!

I just updated to the latest version 6.10.2 and now the web interface is not coming back! No issues in the screen, but CPU is always close to 0% of usage! I do not recommend the update until others have success as well, or at least until it proves that the update is safe to be done!

It will replace my Parity Disk.

Hello fellows! I kinda regret setting up 3 cycles of the Preclear, given the time that it took to clear a 14TB disk. Can I just cancel the process when the 2nd cycle starts? What could happen if I cancel the process, let's say, during Step 1? Thanks!

Did it work as expected? I'm on the same boat... I need to replace my cache disk to a larger one.

Thank you!!! It solves the problem with my Windows Server 2019!

Hey fellows, I'm trying to backup a Windows 10 VM, but it seems that the VM Backup is not able to shutdown it to perform the backup. ... 2022-01-31 14:36:38 information: skip_vm_shutdown is false. beginning vm shutdown procedure. 2022-01-31 14:36:38 infomration: Windows 10 is running. vm desired state is shut off. Domain Windows 10 is being shutdown 2022-01-31 14:36:38 information: performing 20 30 second cycles waiting for Windows 10 to shutdown cleanly. 2022-01-31 14:36:38 information: cycle 1 of 20: waiting 30 seconds before checking if the vm has entered the desired state. 2022-01-31 14:37:08 information: Windows 10 is running. vm desired state is shut off. ... 2022-01-31 14:46:38 information: Windows 10 is running. vm desired state is shut off. 2022-01-31 14:46:38 failure: Windows 10 is running. vm desired state is shut off. can_backup_vm set to n. 2022-01-31 14:46:38 information: actually_copy_files is 1. 2022-01-31 14:46:38 information: vm_state is running. vm_original_state is running. starting Windows 10. 2022-01-31 14:46:38 warning: vm_state is running. vm_original_state is running. unable to start Windows 10. 2022-01-31 14:46:38 failure: backup of Windows 10 to /mnt/user/backup/domains/Windows 10 failed. 2022-01-31 14:46:38 information: backup of Windows 10 to /mnt/user/backup/domains/Windows 10 completed. 2022-01-31 14:46:38 information: cleaning out backups older than 15 days in location ONLY if newer files exist in /mnt/user/backup/domains/Windows 10/ 2022-01-31 14:46:38 information: did not find any config files to remove. 2022-01-31 14:46:38 information: did not find any nvram files to remove. /tmp/vmbackup/scripts/default/user-script.sh: line 873: ): command not found 2022-01-31 14:46:38 information: did not find any vdisk image files to remove. 2022-01-31 14:46:38 information: did not find any vm log files to remove. 2022-01-31 14:46:38 information: cleaning out backups over 3 in location /mnt/user/backup/domains/Windows 10/ 2022-01-31 14:46:38 information: did not find any config files to remove. 2022-01-31 14:46:38 information: did not find any nvram files to remove. /tmp/vmbackup/scripts/default/user-script.sh: line 895: ): command not found 2022-01-31 14:46:38 information: did not find any vdisk image files to remove. 2022-01-31 14:46:38 information: did not find any vm log files to remove. 2022-01-31 14:46:38 information: removing local Windows 10.xml. removed 'Windows 10.xml' 2022-01-31 14:46:39 information: finished attempt to backup Windows 10 to /mnt/user/backup/domains. 2022-01-31 14:46:39 information: cleaning out logs over 1. 2022-01-31 14:46:39 information: removed '/mnt/user/backup/domains/logs/20220131_0500_unraid-vmbackup.log'. 2022-01-31 14:46:39 information: cleaning out error logs over 10. 2022-01-31 14:46:39 information: did not find any error log files to remove. 2022-01-31 14:46:39 warning: errors found. creating error log file. sending incremental file list 20220131_1436_unraid-vmbackup.log Is there anyway to setup to perform a backup without shutdown the windows? Or a way to properly shutdown it? Thanks!

Hey guys! I'm facing similar issue, but in my case I have an onboard dual NIC that UNRaid is using and I also have a PCIe Dual NIC that I'd like to passthrough to the KVM. The issue is that both NICS (onboard and PCIe) are of the same brand, and by consequence they have the same ID, as you can see in the picture. How could I separate the NICS from the IOMMU group 1? - [14e4:165f] 02:00.0 - [14e4:165f] 02:00.1 Following the video, after the first reboot none of the networks cards work anymore, and the unraid does not have access to internet anymore. Thanks!