Julex

MY issue was caused by mounting my unassigned disk and using as a pass-through device. Leave drive unmounted if passing unassigned drive through to VM. Lack of knowledge on how unassigned devices work in unraid, led me to believe that drives must be mounted in order for unraid to see them. This is not the case, and in fact causes massive problems, IE unraid failing to see drive partitions after reboot.

Ahh, I thought this whole time, they had to be mounted in order to passthrough. I'll change that and try again. Thanks!

So I've been having issues for quite a while with my main VM setup on my Unraid server. I am passing through a bare metal SSD drive as the primary VM install location, another bare metal drive and 1 Vdisk for storage needs. Both non-primary drives are un-affected by the issue. The issue at hand, is every time I come back to my VM computer setup, the VM is non-functional. I leave server and VM running all day and all night, Sleep and Hibernate are disabled in VM. Cannot VNC client or remote desktop to it. Check Unraid GUI and VM shows running. When I try to restart the VM, files are corrupt and missing and Windows won't boot. Check drive in unnassinged devices and the drive has shown weird issues, one time it said 85mb out of 170mb free, on a 250gb drive, today it shows 75mb free of 250gb... So the drive keeps getting cleared, but how?! How can a drive have all it's files wiped, even while the VM is running.... If I use my VM with a Vdisk, the issue never happens. TLDR: How do I find what keeps clearing my SSD overnight? Checking logs, I can't make out what could be causing issue. Cache Write is off for the bare metal drives, so mover should not be affecting it... This didn't happen before when I imported the drive with a previous install of windows, but it did not like being a VM, so I cleared and started over... For now, I guess I'll stick with just using Vdisks... darkprism-syslog-20181224-0955.zip darkprism-diagnostics-20181224-0957.zip

When running without the GUI, when the server is done loading it will say the Version above your allocated IP Address. With a GUI, it will be located at the top left.

Welp, this may explain some more, looking at unassigned devices, my Primary VM drive shows used and free space in MBs, rather than GBs... the log shows Dec 16 11:22:48 DarkPrism kernel: ata1: SATA max UDMA/133 abar m2048@0xe6136000 port 0xe6136100 irq 27 Dec 16 11:22:48 DarkPrism kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Dec 16 11:22:48 DarkPrism kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 16 11:22:48 DarkPrism kernel: ata1.00: disabling queued TRIM support Dec 16 11:22:48 DarkPrism kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 250GB, S1DBNSAF835247V, EXT0DB6Q, max UDMA/133 Dec 16 11:22:48 DarkPrism kernel: ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA Dec 16 11:22:48 DarkPrism kernel: ata1.00: supports DRM functions and may not be fully accessible Dec 16 11:22:48 DarkPrism kernel: ata1.00: disabling queued TRIM support Dec 16 11:22:48 DarkPrism kernel: ata1.00: configured for UDMA/133 Dec 16 11:22:48 DarkPrism kernel: sd 1:0:0:0: [sdh] 488397168 512-byte logical blocks: (250 GB/233 GiB) Dec 16 11:22:48 DarkPrism kernel: sd 1:0:0:0: [sdh] Write Protect is off Dec 16 11:22:48 DarkPrism kernel: sd 1:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Dec 16 11:22:48 DarkPrism kernel: sd 1:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 16 11:22:48 DarkPrism kernel: sdh: sdh1 sdh2 sdh3 sdh4 Dec 16 11:22:48 DarkPrism kernel: sd 1:0:0:0: [sdh] Attached SCSI disk Dec 16 11:23:13 DarkPrism emhttpd: Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V (sdh) 512 488397168 Dec 16 11:23:30 DarkPrism unassigned.devices: Adding disk '/dev/sdh1'... Dec 16 11:23:30 DarkPrism unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh1' '/mnt/disks/Recovery' Dec 16 11:23:30 DarkPrism unassigned.devices: Mount drive ro command: /sbin/mount -t ntfs -ro auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh1' '/mnt/disks/Recovery' Dec 16 11:23:30 DarkPrism unassigned.devices: Adding disk '/dev/sdh2'... Dec 16 11:23:30 DarkPrism unassigned.devices: Mount drive command: /sbin/mount -t vfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh2' '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part2' Dec 16 11:23:30 DarkPrism unassigned.devices: Successfully mounted '/dev/sdh2' on '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part2'. Dec 16 11:23:30 DarkPrism unassigned.devices: Device '/dev/sdh2' script file not found. 'ADD' script not executed. Dec 16 11:23:31 DarkPrism unassigned.devices: Adding disk '/dev/sdh3'... Dec 16 11:23:31 DarkPrism unassigned.devices: No filesystem detected on '/dev/sdh3'. Dec 16 11:23:31 DarkPrism unassigned.devices: Adding disk '/dev/sdh4'... Dec 16 11:23:31 DarkPrism unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh4' '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part4' Dec 16 11:23:31 DarkPrism unassigned.devices: Mount failed with error: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 0: Invalid argument Record 10 has no FILE magic (0x0) Failed to open inode FILE_UpCase: Input/output error Failed to mount '/dev/sdh4': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. Dec 16 11:23:31 DarkPrism unassigned.devices: Mount drive ro command: /sbin/mount -t ntfs -ro auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh4' '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part4' Dec 16 11:23:31 DarkPrism unassigned.devices: Mount of '/dev/sdh4' failed. Error message: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 0: Invalid argument Record 10 has no FILE magic (0x0) Failed to open inode FILE_UpCase: Input/output error Failed to mount '/dev/sdh4': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. Dec 16 11:25:26 DarkPrism unassigned.devices: Device '/dev/sdh2' script file not found. 'REMOVE' script not executed. Dec 16 11:25:26 DarkPrism unassigned.devices: Unmounting '/dev/sdh2'... Dec 16 11:25:26 DarkPrism unassigned.devices: Unmount cmd: /bin/umount '/dev/sdh2' 2>&1 Dec 16 11:25:26 DarkPrism unassigned.devices: Successfully unmounted '/dev/sdh2' Dec 16 11:25:30 DarkPrism unassigned.devices: Adding disk '/dev/sdh1'... Dec 16 11:25:30 DarkPrism unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh1' '/mnt/disks/Recovery' Dec 16 11:25:30 DarkPrism unassigned.devices: Mount drive ro command: /sbin/mount -t ntfs -ro auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh1' '/mnt/disks/Recovery' Dec 16 11:25:30 DarkPrism unassigned.devices: Adding disk '/dev/sdh2'... Dec 16 11:25:30 DarkPrism unassigned.devices: Mount drive command: /sbin/mount -t vfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh2' '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part2' Dec 16 11:25:30 DarkPrism unassigned.devices: Successfully mounted '/dev/sdh2' on '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part2'. Dec 16 11:25:30 DarkPrism unassigned.devices: Device '/dev/sdh2' script file not found. 'ADD' script not executed. Dec 16 11:25:30 DarkPrism unassigned.devices: Adding disk '/dev/sdh3'... Dec 16 11:25:30 DarkPrism unassigned.devices: No filesystem detected on '/dev/sdh3'. Dec 16 11:25:30 DarkPrism unassigned.devices: Adding disk '/dev/sdh4'... Dec 16 11:25:30 DarkPrism unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh4' '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part4' Dec 16 11:25:30 DarkPrism unassigned.devices: Mount failed with error: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 0: Invalid argument Record 10 has no FILE magic (0x0) Failed to open inode FILE_UpCase: Input/output error Failed to mount '/dev/sdh4': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. Dec 16 11:25:30 DarkPrism unassigned.devices: Mount drive ro command: /sbin/mount -t ntfs -ro auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh4' '/mnt/disks/Samsung_SSD_840_EVO_250GB_S1DBNSAF835247V-part4' Dec 16 11:25:30 DarkPrism unassigned.devices: Mount of '/dev/sdh4' failed. Error message: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 0: Invalid argument Record 10 has no FILE magic (0x0) Failed to open inode FILE_UpCase: Input/output error Failed to mount '/dev/sdh4': Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details.

I'm running a Windows 10 VM on Unraid 6.6.0, Primary drive is passed-through. I'm having a couple hiccups, that didn't happen in a previously setup VM. The first issue, after leaving VM running all night, when I come back to it in the morning, there is no response. Screen stays idle, tried tapping keys and mouse strokes, no response. I am unable to connect with splashtop as it says the VM is off. When I go into Unraid/VMs, it's listed as running. Trying to Hibernate comes up with " Domain 'x' could not be suspended. Guest agent is not responding: QEMU guest agent is not connected.", Pausing and Starting, Stop, and Restart appear to do nothing. Force Stop is my only alternative. The question now is, what could be going on? The second one, even with the keyboard check mark passed through from the GUI, when the VM starts, the keyboard does not work. I have to go into the Hotplug USB plugin and attach keyboard.