Driconis

+1 for not being able to access webui. SSH and console are working and webui was last accessed normally about 24 hours ago. Tried shutting down and restoring a backup with no luck. My docker containers seem to be working normally and the storage seems to be working normally. It seems to be an issue with MyUnraid as I keep getting redirected to the MyUnraid URL even when I type in the servers local address.

Finally able to upgrade from rc3 without any issues. Thanks!

I noticed that as well. I did doublecheck before updating to ensure that it was pulling rc6. I would like to try manually building the flash and copying my config but I'm a little short on time right now. I'm going to have to wait a couple of days before I have time for that. If I try that and get a better outcome I will let you know. Edit: I couldn't resist. I used another flash drive and the Unraid USB creation tool to put a copy of plain vanilla rc6 without copying the configs to it. I figured this would be as close as possible to a new install. Results were pretty much the same. Took diagnostics and It shows 'ixgbe' is out of tree and the link keeps going up and down. If I can think of anything else to try I will post it here. I hope you find this useful! diagnostics-20220505-1722.zip

Unsuccessfully attempted to upgrade once again from rc3. System appears to boot normally, but after booting it appears as if the array does not start. No drive activity and the WebGUI and SSH is not accessible. I can log in via command line on connected monitor and keyboard. Was previously not able to upgrade to rc4 and rc5 as well. System is a Supermicro A2SDi-8C+-HLN4F with 64 GB with 4 Disk data array and SSD cache drive. A quick read through the diagnostics indicates that the ethernet is still dropping in and out. Two other flash drives give the same result. Went for a hail mary and tried disabling IPMI as I had a hunch it might be interfering but no luck there as well. diagnostics-20220505-1729.zip

Nice catch! I compared this with diagnostics I pulled after restoring rc3 and this definitely is not happening on rc3. It's my understanding that those of us running SuperMicro A2SDi series motherboards were unable to successfully install rc4 due to ethernet issues with the newer kernel. The issues with rc4 were so severe that I was not even able to log in via command line, all I could determine was that the ethernet never connected to the network at all. It would seem that there are still some remaining issues to be worked out with this. I guess I will stand pat for now and hopefully the next release will work out better. Thanks again.

Agreed. I was previously unaware that diagnostics can be run from the command line. I have temporarily reinstalled rc5 and attached the file to my original post.

Unsuccessfully attempted to upgrade from rc3. System appears to boot normally, but after booting it appears as if the array does not start. No drive activity and the WebGUI and SSH is not accessible. I can log in via command line on connected monitor and keyboard. Was previously not able to upgrade to rc4 as well. System is a Supermicro A2SDi-8C+-HLN4F with 64 GB with 4 Disk data array and SSD cache drive. Tried updating to the latest bios, manually building the flash drive and copying the config folder, as well as 2 other flash drives with the same result. Was able to restore my rc3 flash backup to the original flash drive with no issues. diagnostics-20220428-1714.zip