pOpYRaid

Same issue here on unraid 7 beta 2 and an windows 11 pro VM. When i start it again after it's paused, it does'nt work and shows an black screen with VNC. Here are the diagnostics data: mediaserver-diagnostics-20240903-0808.zip Ok, so the VM's are also living on the cache, which is the primary storage:

Thx a lot, also for this change!

Nice, thanks a lot adding the character check! No, I am running just an BTRFS JBOD Array with 2 disks and one parity disk.

Sure, the VM name was "Windows 11 Server (Macrium Site Manager)" (without quotes). The snapshot name was "Vor Windows 11 Upgrade" (without quotes). Maybe it was the bracket's in the KVM name?

@SimonF sorry, didn't know VM Engine is your code Thanks for looking into it.

ok, i fixed it! It was definitely the issue that i used KVM (domain) name with spaces! I will call it a bug, you find articles on the net saying the frontend using libvirt should NOT allow KVM (domain) names with spaces. I fixed it by doing the following: Rename the maschine with the webgui to a name without spaces ("Windows11" in my case) The snapshots seems to be gone and are not shown in webgui That's because the snapshotdb\{domain} folder is not renamed. Maybe that's another bug. I manually renamed it in directory "/etc/libvirt/qemu/snapshotdb/" from "Windows\ 11\ Server\ \(Macrium\ Site\ Manager\)" to "Windows11" (same as KVM name) After pressing F5 in the webgui on the VM tab, snapshots for this machine is shown again Sadly "Block commit" does'nt work, it complains about missing base image Sure, the sanpshotdb has the wrong domain path in it. I dirty/lazy fixed it by coping the new renamed domain folder to the old name. cd /mnt/cache/domains cp -r Windows11 "Windows 11 Server (Macrium Site Manager)" After that the "Block commit" worked Now you have to remove the New domain with "rm -R Windows11". Because the merged disk is at the old path. An than move the new vdisk back to the new KVM/domain name 'mv "Windows 11 Server (Macrium Site Manager)"/ Windows11' !! Attention !! Before you remove anything, be SURE that's the correct directory or make an backup. I have double checked the timestamps of vdisk1.img. And yessss, it boots up! @limetech can you please look into this, this should be fixed for the final v7 release. There are two issues: Don't allow spaces in KVM & snapshot names Also rename the snapshotdb when renaming KVM over webgui and maybe fix the baseimage path inside the db or prevent renaming in the gui when there are snapshots. thx

@SimonFin my case it's empty. It doesn't matter how often i start the commit: Any hint's how i can proceed? Maybe because my VM name and snapshot has spaces in it?

After half an hour my unraid was going to sleep. File are unchanged. Started the commit again, and again the window is empty (as on the first try). Also the file are not changing (size and time stamp). Please help? Where are Log files for the commands launched? thx

Hey guys, running unraid 7 beta 2 and made an snapshot of an windows 10 VM before upgrading to 11. The upgrade went throught, and now i wanted to delete the snapshot and stay on the data the VM now is. After reading threads the "Block commit" function is what i am wanting. Started it, with the VM shutdown. Sadly, the output window is empty, for over 15 minutes now (See picture). The files disk files seems untouched: Any hint's what i can do to merge those vdisk's? Do i have to start the VM to get it merged? (Dont want to mess it up :-) Thank you

I had the same issue. A fix for me was to copy the MSI to C:\Temp and install it from there.

@limetech can you please look into this?

@aqua single files work for me here, really

@jserioyou are right! I have forgotten the issue was just on deleting folders with some files in it. Issue still persists for me, also with 2.8.46 solid explorer. I am so sorry guys for the false alarm! Will contact the dev of solid explorer and ask him how to proceed.

Here are my solid explorer settings: And the unraid settings: Advanced settings (for hardening): #hardening SMB standalone server server min protocol = SMB3_11 client ipc min protocol = SMB3_11 client signing = mandatory server signing = mandatory client ipc signing = mandatory client NTLMv2 auth = yes smb encrypt = required restrict anonymous = 2 null passwords = No raw NTLMv2 auth = no but also without any advanced settings i can delete files without an issue with solid explorer now.

@aqua Interresting! My best advise is to enable debug mode in solid explorer, reproduce the issue and send the report to the dev within the app. Or second: update to unraid 7 beta 2 (which runs flawless for me).

FINALLY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Solid Explorer Dev. fixed that issue on 17.08.2024 with version 2.8.46, see here: https://play.google.com/store/apps/details?id=pl.solidexplorer2 I was in contact with him and sent some logs during reproducing the issue (deletion of an file on unraid on SMB 2/3). Tested it with the new version stating "SMB client improvements" and it works! No more errors! Just wanted you (Solid Explorer) users know.

@tkenn1s thx for clearing things up. my beta 2 of unraid 7 is running samba 4.20.2. No, i have not installed the recycle bin plugin. Any other ideas. It seems to be related to specific android file managers, i am using solid explorer for years and sadly it affects it. Any other hint's i can tighten up security by using SAMB 2/3 with solid explorer?

I have tested it with the beta, sadly the issue is not gone.

thx, that also worked on unraid 7 beta. The nerdtools python3 panda package needed this.

thx, that solved pip for me on unraid 7 beta.

I have tested SMBv2/v3 with v7 beta and the issue still exists.

Because beta version 7 is out now, see here: Is this issue solved? (so i dont have to activate old samba protocoll?) thx

@samsausages thx a lot for this!!!! Any Updates on this script?

+1 for this!

Thanks, will write an user script, use rsync directly and ditch luckyback all together.