2TC

I switched from emilated to host passthrough and now it all works as intended. Thank you very much for the help!

No, not really. I could do either or. I am just used to running it as emulated. And to be frank, I cant say that I have the biggest clue about the pros and cons of the different alternatives.

Thank you for replying, nothing changed in the XML, only changed the version of machine as stated before. When I create a new machine and use the vdisk it works as intended. This VM does not start and throws an error This VM works

Bump

I have a Debian 11 VM that I have had some issues with, so I tried to stop the VM and upgrade the "Machine" from Q35-4.2 to Q35-7.1, thinking this migh solve some issues. When I stopped the VM and changed the value and tried to start it again, I keep getting the following error "Execution error the CPU is incompatible with host CPU: Host CPU does not provide required features: svm" As I understand, svm is related to virtualization for AMD CPUS, I am using an INTEL CPU and the Intel VT-X is enabled in BIOS. I have not update my BIOS or anything. I had not rebooted the computer for over 4 months and after last reboot it all worked as intended. Right now, I updated to the latest version of unraid, 6.12.6 and thought that might solve the problem, it did not. Does anyone have an idea of where to start with this issue? Also, if you want any logs, let me know and I will pull them.

Ah, I assume that is what I mean. When I click the icon on the disk which ways "disk log information". If that is tied to syslog, then yes. Surely syslog gets cleared every reboot, but if it was a read error I would assume it should come up again if there was an issue with the disk.

That is true, I should see them more as statistics overtime than anything else. The error in the disk log is also gone, but I assume that correlate to the error counter changing from 0 to another number. I am currently doing a parity check to see if there will be any errors during that, once it is done and all is good I will redo the smart test to see if that can see anything.

When I boot up my server I get the following error in the output of the screen mv: cannot stat '/usr/local/bin/mover': No such file or directory it is not really an issue, I searched the web and I found this post talking about this and the addon "move tuning plugin", which I assume is "CA Mover Tuning". The post talks about deleting the plugin. Now I do not have an issue with the server not starting, just that the entry is there. I looked at the '/usr/loval/bin/mover' which is a shell script #!/bin/bash PPPID=`ps h -o ppid= $PPID 2>/dev/null` P_COMMAND=`ps h -o %c $PPPID 2>/dev/null` /usr/local/emhttp/plugins/ca.mover.tuning/mover.php $P_COMMAND $1 I looked at the file mentioned, and the mover.php file is where it is supposed to be, seems everything is working as intended, except that I get the error when booting it, surely I could just ignore it. But I rather fix it than leave it there.

Alright, I will ask in the thread. Thanks!

When I boot up my server I get the following error in the output of the screen mv: cannot stat '/usr/local/bin/mover': No such file or directory it is not really an issue, I searched the web and I found this post talking about this and the addon "move tuning plugin", which I assume is "CA Mover Tuning". The post talks about deleting the plugin. Now I do not have an issue with the server not starting, just that the entry is there. I looked at the '/usr/loval/bin/mover' which is a shell script #!/bin/bash PPPID=`ps h -o ppid= $PPID 2>/dev/null` P_COMMAND=`ps h -o %c $PPPID 2>/dev/null` /usr/local/emhttp/plugins/ca.mover.tuning/mover.php $P_COMMAND $1 I looked at the file mentioned, and the mover.php file is where it is supposed to be, seems everything is working as intended, except that I get the error when booting it, surely I could just ignore it. But I rather fix it than leave it there.

Thank you! I will try this and see if it sorts the issue. I have already ordered a spare disk in case it would fail! Will update with result! Edit: After a reboot, no change of cables, there is no report of errors. will run a parity check to be certain, but seems to have sorted the issue. Thank you!

Please see attached diagnostics nas-diagnostics-20230911-1804.zip

Hi, I have some issues with my parity drive, or so I think. My report says the following Notice [NAS] - array health report [FAIL] Parity - ST8000VN0022-2EL112_ZA16XZXN (sdc) - active 40 C (disk has read errors) [NOK] Parity is valid When looking into the logs of the disk, I can see the following Sep 1 14:21:45 nas kernel: ata2.00: exception Emask 0x0 SAct 0x7f000000 SErr 0x0 action 0x0 Sep 1 14:21:45 nas kernel: ata2.00: irq_stat 0x40000008 Sep 1 14:21:45 nas kernel: ata2.00: failed command: READ FPDMA QUEUED Sep 1 14:21:45 nas kernel: ata2.00: cmd 60/40:c0:90:1c:c9/05:00:3b:03:00/40 tag 24 ncq dma 688128 in Sep 1 14:21:45 nas kernel: ata2.00: status: { DRDY SENSE ERR } Sep 1 14:21:45 nas kernel: ata2.00: error: { UNC } Sep 1 14:21:45 nas kernel: ata2.00: configured for UDMA/133 Sep 1 14:21:45 nas kernel: sd 2:0:0:0: [sdc] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Sep 1 14:21:45 nas kernel: sd 2:0:0:0: [sdc] tag#24 Sense Key : 0x3 [current] Sep 1 14:21:45 nas kernel: sd 2:0:0:0: [sdc] tag#24 ASC=0x11 ASCQ=0x4 Sep 1 14:21:45 nas kernel: sd 2:0:0:0: [sdc] tag#24 CDB: opcode=0x88 88 00 00 00 00 03 3b c9 1c 90 00 00 05 40 00 00 Sep 1 14:21:45 nas kernel: I/O error, dev sdc, sector 13887937680 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 0 Sep 1 14:21:45 nas kernel: ata2: EH complete On the Main page, I can see that the Parity have "Errors: 168", while when I check the SMART status for the drive it reads as follows Last SMART test result: Completed without error And the SMART overall-health: says SMART overall-health: Passed Attached is the SMART test result. Let me know if any you need any other details. The ask is, should I replace my drive, or is this another issue? ST8000VN0022-2EL112_ZA16XZXN-20230911-1349.txt