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?
 

Try booting in safe mode, note that you can also get the diagnostics for the CLI.

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. 

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. 

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

Edited March 23, 20242 yr by hsingh314

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

9 hours ago, hsingh314 said:

So I had to install 6.11.5 just to be able to get the diagnostics zip file.

Not sure I follow, the diags are from 6.12.8.

 

I do see the Intel 915 driver crashing, try blacklisting the iGPU driver:

https://docs.unraid.net/unraid-os/release-notes/6.10.0#linux-kernel

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). 

Post current diags from v6.11.5, or upgrade back trying what I mentioned above.

Here is the diag for the current v6.11.5 I am still running. 

bishop-diagnostics-20240403-1331.zip

I would try updating again with the iGPU driver blacklisted, and if there are still issues grab the diagnostics from the CLI.

Should I also remove Intel GPU Top?

Not sure if it will load with the driver blacklisted but probably better to remove it.

- 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

Edited April 7, 20242 yr by hsingh314
I think I figured out the vm problem - might be because bitlocker

Try booting v6.12.10 with a new flash drive using a stock Unraid install, no key needed, just to see if it's a config issue.

Just tried - same issue. 

That suggests it's a compatibility issue with the newer kernel, get the diagnostics from that boot