pliu

@JorgeB, thanks as you expected But that's like last resovle, in this case, I've already stopped all the VMs, so not big deal.

Thanks, trying that

Not sure why: I got this after disabled the VM Manger, and then trying to re-enable it: Here is the diagnostic file: tower-diagnostics-20250116-2206.zip The reason I am trying to do that is I want to move some VM img file from array to cache, but might break the VM Engine, but I couldn't find any clue from the error message and apparently no error details in the log.

After bit of random changes and got my system back to operation. After play around the cache pool setting I realized that the error might be to do with btrfs by default using RAID for 2 ssd drives, and I removed one to un-assigend a couple of years ago. Somehow the new version of Unraid decided that my cache should still be mirrored so complains that it is not single as I only assigned one ssd to cache pool. I then confirmed the unassigned ssd still have the cache content exactly same as the cache ssd. However after add the un-assigned ssd back the cache pool, I got more errors. I think it might be to do with the order of two ssds in cache pool are not same as I physically moved ssd around before ( I think). But Unraid does not allow me to move the ssds in the cache pool around, complains about missing drives if I just move ssd order around. I then end up remove all ssds from the current cache pool and add another cache pool, and now I have all the cache pool back! Think that's probably enough for the day

Maybe not relate, but that's my first reboot after updated to version 6.12.2, as my Unraid system been up for almost three months. The error message on the Array is: 'Unmountable: Unsupported or no file system' The error message I got is: No sure what's error message is about as the device seem passed btrfsck with no issue. And following this FAQ: I can at least mount it as read-only, didn't try anything further yet, as I don't understand why Unraid cannot just mount the Cache drive as it seems the data is here and the drive is physically fine? Think I am going to manually copy the data and maybe try to restore the data using: Cache files system check is fine: WARNING: filesystem mounted, continuing because of --force [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/nvme1n1p1 UUID: 66969f3d-4d56-4866-bbb0-b26a91821903 found 648195293184 bytes used, no error found total csum bytes: 6924772 total tree bytes: 230391808 total fs tree bytes: 109608960 total extent tree bytes: 110395392 btree space waste bytes: 25295333 file data blocks allocated: 648014184448 referenced 647944634368

Think I've found the issue: Dec 8 08:52:00 Tower kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=vcpu0,mems_allowed=0,global_oom,task_memcg=/machine/qemu-26-Windows10.libvirt-qemu,task=qemu-system-x86,pid=15998,uid=0 Dec 8 08:52:00 Tower kernel: Out of memory: Killed process 15998 (qemu-system-x86) total-vm:18026704kB, anon-rss:12470132kB, file-rss:88kB, shmem-rss:22844kB, UID:0 pgtables:25496kB oom_score_adj:0 Looks like I've over-committed, too many testing VM's running. Kill a couple of extra ones and both the Windows one can started. The mean kernel is ruthless!

It's getting more interesting: I tried to create a fresh Windows 10 VM, and almost exact same issue, I can go as far as the white spinner in the black screen, and as soon as it went into the blue screen ( I think is the initial setup screen for Windows installation) the VNC connection failed, and log showing the exact same entry "2021-12-09 08:06:46.128+0000: shutting down, reason=crashed". Nothing else.

I am using VNC and sometimes I can see Windows starting up, but a few seconds, as different stages of Windows starting up before Windows fully loaded, the VNC connection suddenly dropped out and I lost the connection and the VM shows as "Stopped" The only relevant message I can see from qemu log is: "shutting down, reason=crashed" And here is the full log for today: The only reason I can think of is a power outrage a couple of weeks ago, the Unraid server was shut down and after that I probably never started the Windows VM, but the Unraid server itself seems fine and a couple of Linux VM started as normal. So How do I got more diagnostic information about the reason for the Windows VM cannot start, can I somehow get more log, or the VM into the Windows recover mode?

Thanks for the comment @ghost82, yes you are right, it's just standard procedure of modify Xorg configure file if the default monitor resolution is not show/detected. I pretty much following instructions from this well written article and got it working the first try!

Hi how to get the Linux guest display QHD (2560*1440) resolution. I can get it up to 4k or 2560*1600, but none match my QHD monitors native resolution? I am using Manjaro Xfce. And here is the system information for the guest Linux VM: System: Kernel: 5.10.83-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 root=UUID=62577852-e55e-4ca4-96a2-50c056de9a17 rw quiet resume=UUID=15ff6072-019d-4143-9235-25ea2120d0b0 udev.log_priority=3 Console: pty pts/1 DM: LightDM 1.30.0 Distro: Manjaro Linux base: Arch Linux Machine: Type: Qemu System: QEMU product: Standard PC (Q35 + ICH9, 2009) v: pc-q35-5.1 serial: <superuser required> Chassis: type: 1 v: pc-q35-5.1 serial: <superuser required> Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: rel-1.13.0-48-gd9c812dda519-prebuilt.qemu.org date: 04/01/2014 CPU: Info: Dual Core model: 11th Gen Intel Core i7-11700 bits: 64 type: MT MCP arch: Rocket Lake family: 6 model-id: A7 (167) stepping: 1 microcode: 3C cache: L1: 160 KiB L2: 1024 KiB L3: 16 MiB flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19976 Speed: 2496 MHz min/max: N/A Core speeds (MHz): 1: 2496 2: 2496 3: 2496 4: 2496 Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Red Hat QXL paravirtual graphic card driver: qxl v: kernel bus-ID: 00:01.0 chip-ID: 1b36:0100 class-ID: 0300 Display: server: X.org 1.21.1.1 compositor: xfwm4 driver: loaded: modesetting alternate: fbdev,vesa tty: 142x123 Message: Advanced graphics data unavailable in console. Try -G --display Audio: Message: No device data found. Sound Server-1: JACK v: 1.9.19 running: no Sound Server-2: PulseAudio v: 15.0 running: yes Network: Device-1: Red Hat Virtio network driver: virtio-pci v: 1 modules: virtio_pci port: N/A bus-ID: 01:00.0 chip-ID: 1af4:1041 class-ID: 0200 IF-ID-1: enp1s0 state: up speed: -1 duplex: unknown mac: <filter> Drives: Local Storage: total: 80 GiB used: 17.06 GiB (21.3%) SMART Message: Required tool smartctl not installed. Check --recommends ID-1: /dev/vda maj-min: 254:0 model: N/A size: 80 GiB block-size: physical: 512 B logical: 512 B speed: <unknown> type: N/A serial: N/A scheme: MBR Partition: ID-1: / raw-size: 73.91 GiB size: 72.2 GiB (97.68%) used: 17.06 GiB (23.6%) fs: ext4 dev: /dev/vda1 maj-min: 254:1 Swap: Kernel: swappiness: 60 (default) cache-pressure: 100 (default) ID-1: swap-1 type: partition size: 6.09 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/vda2 maj-min: 254:2 Sensors: Message: No sensor data found. Is lm-sensors configured? Info: Processes: 182 Uptime: 13m wakeups: 0 Memory: 2.77 GiB used: 1.06 GiB (38.2%) Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 Packages: pacman: 976 lib: 285 Shell: Bash v: 5.1.12 running-in: pty pts/1 (SSH) inxi: 3.3.09

Thank @JorgeB, I found that thread as well, and none of those solutions/workaround make sense to me, as I didn't rename my VM (that's the first VM I've setup on the Unraid rig), or change the VM settings in the Xml view. But since you mentioned that thread. I had another look and the Auto change to manul Primary vDisk workaround does seems worth a shot, yet it doesn't make difference for me. The auto VDisk location is actually the right one, and if I change it to 'Manual' and select the path again, I still cannot add the second Unraid share. I guess I could try the Xml view if I want, but looks like there are other users reported that using the Xml view cause the issue to begin with, so I not keen to do that yet. Now I am just Mount the Unraid share via NFS instead, looks it's wokring ok. But surely it's a bug right?

Hi I encountered a strange issue where I cannot add another 'Unraid Share' to my VM in the 'Form view' in the VM setting. When I added the second share, and click the 'UPDATE' button, it will stay at the 'UPDATEING' state and cannot commit the change. It's a fairly new unraid rig as I had it only for abut two months and this is practically my first VM in use. Unraid is version 6.9.2. I also attached diagnostics file just in case it might be needed. tower-diagnostics-20210711-1333.zip