Jump to content
We're Hiring! Full Stack Developer ×

(solved) windows 10 VM freeze (unraid freeze)


Recommended Posts

hello. im new here i have an unraid basic licence. and im currently experiencing VMs that freeze. i don't really know why it happens. but in windows if i copy files with speeds over 100Mb/s the pc freezes and i have to hard reset unraid as unraid also froze.

the linux one is also the same issue but unraid doesen't freeze and im able to force the vm to shutdown.

if there is anything i need to give just ask me. as im new to the forums i don't exactly now what to give.

unraid 6.9.0-rc2

edit:
image.thumb.png.0a0ea5c18cd46ada4f9ec446e238f027.png
this is my unraid setup as you might see i only have .m2 ssds. but im thinking of an simular issue with large file transfers causing the issue.
as an game can be 10+ gigs and transfering it from a docker container on array to cache where the VMs are on.

as games can be quickly downloaded from array to cache this might be the issue. the downlonad is on the same machine with the docker. thus the speeds of the ethernet conections are 10G
refrence: 

latest edit:
fmally this time i got some logs to put in this post to help resolve this.


gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3880259584 (dev /dev/md1 sector 7537672)
Feb 4 10:15:01 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3887333376 wanted 266392 found 264345
Feb 4 10:15:01 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3558461440 (dev /dev/md1 sector 6909160)
Feb 4 10:15:01 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3880845312 wanted 266392 found 263034
Feb 4 10:15:01 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3887300608 wanted 266392 found 264345
Feb 4 10:15:01 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3880263680 (dev /dev/md1 sector 7537680)
Feb 4 10:15:01 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3558465536 (dev /dev/md1 sector 6909168)
Feb 4 10:15:01 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 1958494208 wanted 265218 found 263826
Feb 4 10:15:01 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3881566208 wanted 266392 found 263035
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3838689280 wanted 266292 found 263033
Feb 4 10:15:23 gamepc kernel: repair_io_failure: 22 callbacks suppressed
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3838689280 (dev /dev/md1 sector 7456480)
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3838693376 (dev /dev/md1 sector 7456488)
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3838697472 (dev /dev/md1 sector 7456496)
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3838701568 (dev /dev/md1 sector 7456504)
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3844767744 wanted 266297 found 263033
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3844767744 (dev /dev/md1 sector 7468352)
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3844771840 (dev /dev/md1 sector 7468360)
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3844775936 (dev /dev/md1 sector 7468368)
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3844780032 (dev /dev/md1 sector 7468376)
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3888381952 wanted 266392 found 264345
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3888381952 (dev /dev/md1 sector 7553536)
Feb 4 10:15:23 gamepc kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 0 off 3888386048 (dev /dev/md1 sector 7553544)
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3888578560 wanted 266392 found 264345
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3859562496 wanted 266327 found 263034
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3888775168 wanted 266392 found 264345
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3839066112 wanted 266292 found 263033
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3878600704 wanted 266391 found 263034
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3840638976 wanted 266293 found 263033
Feb 4 10:15:23 gamepc kernel: BTRFS error (device nvme0n1p1): parent transid verify failed on 3891347456 wanted 266392 found 264348
Feb 4 10:16:01 gamepc kernel: nvme nvme1: I/O 514 QID 10 timeout, aborting
Feb 4 10:16:01 gamepc kernel: nvme nvme1: I/O 515 QID 10 timeout, aborting
Feb 4 10:16:01 gamepc kernel: nvme nvme1: I/O 516 QID 10 timeout, aborting
Feb 4 10:16:01 gamepc kernel: nvme nvme1: I/O 517 QID 10 timeout, aborting
Feb 4 10:16:01 gamepc kernel: nvme nvme1: I/O 518 QID 10 timeout, aborting
Feb 4 10:16:31 gamepc kernel: nvme nvme1: I/O 514 QID 10 timeout, reset controller
Feb 4 10:17:02 gamepc kernel: nvme nvme1: I/O 17 QID 0 timeout, reset controller
Feb 4 10:17:57 gamepc kernel: mdcmd (36): check correct
Feb 4 10:17:57 gamepc kernel: md: recovery thread: check ...

just a note both m.2 ssds are new and tested before using unraid.
second m.2 dissapeared after enabling and disabling array.

Edited by alexboot
fixed
Link to comment
  • alexboot changed the title to windows 10 VM freeze (unraid freeze)
2 hours ago, JorgeB said:

This means filesystem corruption, likely the result of the NVMe device dropping offline, a scrub might fix it, also see here for better pool monitoring.

i figured as such. i've been experimenting. i tryed using that m.2 as pci passthrogh. and no sucess with an message vfio-pci not ready after flr or something.
the drive im talking about is nvme1n1 its in the second m.2 slot  that my motherboard has (the bios defaulted to Nvme raid mode for nvme ssd's i disabled that. it did nothing.)
it works if you don't stress it. after that it just disconnects or something.
i downgraded unraid to test if it helped but no. im on the stable release now. (i formatted the drives beforehand in the bios) then i got a promt to format the drives again in unraid so i did.
im on the latest bios version thats out  there.
tommorow ill swap the drives with ethother. as it doesen't happen on nvme0n1 only on nvme1n1. (and see if it still happens.)

i hope i find the awnser very soon.

Edited by alexboot
Link to comment
  • alexboot changed the title to (solved) windows 10 VM freeze (unraid freeze)

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...