ducker

I upgraded yesterday from 6.6.1 to 6.9.2 and the only issues I've found so far is a single Win7 vm that starts and brings up a blue screen in Windows. I'm getting a STOP 0x0000001E aswvmm.sys When I upgraded to 6.9.2 all went well via the GUI, I then restarted Unraid and had an issue with my flashdrive booting and had to recreate on another flashdrive so I don't know if this is related or just a coincidence but wanted to share. I was able to copy my config folder from a backup to the new flashdrive. I have another Win7 vm that was the original image that I used to make the vm I'm having issues with now and it still works fine after the upgrade. I don't know if this is upgraded related or not but I'm looking for suggestions to get this vm to successfully boot again.

Thanks Johnnie, for some reason I had it in my head that it would move to another disk after the first disk was 50% full so I expected it to happen at 4tb in this case. The link explains it clearly.

Unraid: 6.5.0 Originally had a single 8tb drive in my array, it sent me a low disk space notice somewhere around 4tb free. Once it got down to 2.5tb free I added a 2tb drive to the array. It still hasn't written any files to the new drive after another 500gb or so written to the 8tb drive which is now about 2tb free. All shares are set to Allocation method: High-Water but nothing is getting written to the new drive....ideas? All Shares are set to Included disks: All Is there something I should change to get unraid to start writing to the newly added 2tb drive?