hsingh314

I am seeing the errors on my main screen and under the 'main' tab.

So started it up. Was missing all the drives but the ones connected to the MB directly. Saw JorgeB's message and decided to reseat the HBA - and it now seems like things are back to 'normal' but I still have the millions of errors. What should I do about this? Do I do a parity-error check but don't do the write corrections? I have also attached a diag from before starting the array and afterwards below. bishop-diagnostics-20240502-0909.zip bishop-diagnostics-20240502-0913.zip

I just started getting messages this morning from my discord bot that files were missing - hundreds of them. When I woke up I tried to login and my root password wasn't working. Trying to restart the server right now hoping I'll be able to just even login. It had this error: Warning: fread(): Length parameter must be greater than 0 in /usr/local/emhttp/plugins/dynamix/include/.login.php on line 23

Any suggestions of what to do? Did I just lose all my data?

I have 12 drives. I took the diag right after I stopped the parity check cause I freaked out cause it was doing the "write corrections to parity" thing. The system hasn't been rebooted for 24 days.

Parity-check ran as scheduled and started populating millions of errors. What does this mean? Did I just lose all my data? I am kinda nervous about this. Thanks! bishop-diagnostics-20240501-1646.zip

Just tried - same issue.

- Removed GPU Top - Blacklisted the i915 driver (just did the echo command thing in the link you sent). - Installed 6.12.10 (only one it would let me). - No webgui - tried /etc/rc.d/rc.nginx-fpm restart & /etc/rc.d/rc.php-fpm restart - Login screen showed up - logged in - blank screen - did diagnostic command through ssh - no array, dockers or vm's will start up. - downgraded back to 6.11.5 I have attached the diagnostic thing from when it was "running" 6.12.10 - I am not sure what to do about the update tower-diagnostics-20240407-1448.zip

Should I also remove Intel GPU Top?

Here is the diag for the current v6.11.5 I am still running. bishop-diagnostics-20240403-1331.zip

Apologies, it kinda hectic. - Ran update assistant (everything said ok) - installed 6.12.8 - no web ui or array working - ran diagnostic but could not get the results through SSH (would crash every time) - downgraded to 6.11.5 - able to get diagnostics (the one posted, from 6.12.8) - array spins up - no VMs work - restart system - All VMs gone, all plug-ins gone, all dockers gone - Communtiy Apps will not install because Unraid is too old - Remake VM and gives error: qemu-system-x86_64: terminating on signal 15 from pid 18676 (/usr/sbin/libvirtd) 2024-03-23 23:57:39.580+0000: shutting down, reason=shutdown - Run update assistant ( everything ok) - install 6.12.8 - same issue, no web ui no array - downgrade back to 6.11.5 - ui and array back. VMs gone - remake VM and gives error : qemu-system-x86_64: terminating on signal 15 from pid 18676 (/usr/sbin/libvirtd) 2024-03-23 23:57:39.580+0000: shutting down, reason=shutdown - that’s all I’ve done so far (besides questioning my life decisions).

I tried recreating the VM and no matter I do I get this error: qemu-system-x86_64: terminating on signal 15 from pid 18676 (/usr/sbin/libvirtd) 2024-03-23 23:57:39.580+0000: shutting down, reason=shutdown

So I had to install 6.11.5 just to be able to get the diagnostics zip file. Unfortunately it seems like alot is gone (can't even install Community Applications plugin to get apps). Also all my VM's are gone. tower-diagnostics-20240323-1901.zip

I tried to downgrade to 6.11.5 which broke everything. Dockers, passthrough, VM's disappeared. So I tried to update back to 6.12.8 .... I am extremely regretting upgrading from 6.12.6 to 6.12.8 and it will not let me downgrade to 6.12.6. I still cannot get ssh to download the diagnostics file. Nothing is working and now I am worried that all my data might have been lost just by pushing the button to upgrade.

Safe mode did the same thing - trying to figure out the diagnostics. I see it on the server through ssh cli - but don't know how to get it on my computer.

Hi, I updated to 6.12.8 (as from I read it was ok to update, but maybe I didn't read enough). I cannot access the webui. I cannot access the array and have no way to get the diagnostic zip file. I did do the suggested solution here: But to no avail. I am not sure what to do. Was working fine for 90+ days without a reboot straight before this update. Any suggestions?

Could having PCIe ACS override set to enabled cause this issue?

Hi, I keep getting my VM crashing and it goes into a 'pause' mode. I checked the logs and keep getting the same error. I think it has something to do with my GPU as the ID of the error corresponds to the GPU I am passing through (Tesla P4). Has anyone else encounter this before? Any suggestions on what to do next? 2023-08-05T22:35:43.826885Z qemu-system-x86_64: vfio_err_notifier_handler(0000:09:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest Thanks!

Thats fair.

Welp! that sucks. Maybe it's worth indicating that in the documentation as it says that all xeon E3 v6 cpus would work, but I believe all the v6's has this gpu. Well... onwards and upwards... I'll try to figure something else out. Thanks!

I tried using this to passthrough my Intel iGPU to my VM while still being able to use it for a container. However, when I opened it, it said my system wasn't compatible even though my CPU is a E3-1245v6. The dialogue said I should download my diagnostics (attached) and post here..... so here I am.... I tried using this to passthrough my Intel iGPU to my VM while still being able to use it for a container. However, when I opened it, it said my system wasn't compatible even though my CPU is a E3-1245v6. The dialogue said I should download my diagnostics (attached) and post here..... so here I am.... bishop-diagnostics-20230804-1824.zip

Ok, I figured it out. I just typed in exactly what you had, not realizing that was the output of the .conf file & I had to edit the .conf file to have those parameters (lol - I am dumb). I got it work, or at least Unraid to detect the card. Thanks!

Ugh - I am not sure what I am doing wrong. Also I do have intel gpu top installed but the a380 doesn't show up there either.

So I updated to 6.12 (yay) - but the driver still doesn't see the a380? Is there something else I need to do. I've seen people mention 'probing' but I am not sure how to do that.

Cool, I'll wait. Thank you.