srfnmnk

yeah it was working fine before the upgrade.

?? So what else do I need to copy over (other than user scripts) to ensure I get everything pulled over? Thanks again

Is this process documented anywhere (moving to fresh install and restoring all configs)? I've never done this and am a bit concerned of going down a rabbit hole. For example -- given the above, would my user scripts get pulled over? what about all the plugins and their configs such as backups? If I get partially through the process with a new usb and am missing something, can I just stick the old usb back in the server and go capture whatever I missed?

virtio to sata for the disks does allow the VM to start up I believe I tried all the different network options and none of them actually gave me a network.

Thanks. The issue with even attempting to update the kernel inside the VM is that the network also uses virtio it seems and I can't get that to work either...so no internet. More details on this thread. Appreciate the response.

wow -- well, at least you took it all the way to the end. Good work. Dead cpu core, zoinks, super unlucky.

I'm not convinced it's hardware at all, because when I put a fresh 6.12.4 UnRaid usb stick in there everything works just fine. Eth0 and Eth1 are recognized as eth0 and eth1 and everything works perfectly on this hardware. There's some issue in the OS and I can't seem to figure out where.

After upgrading to 6.12.4 from 6.11.5 my ubuntu VM is no longer able to load the os when using virtio. I switch that to sata and then I can get to the OS via VNC but the virtio network still doesn't seem to work at all. I have tried several different network configs to get it to work but none are working. I am currently back to the way it was prior to the upgrade. VMName: Raichu -- VM settings are contained in the diagnostics bundle. Attaching details pumbaa-diagnostics-20231101-1636.zip

@Archonite -- how did you update the kernel?

Ok @JorgeB -- I have completed the upgrade and I still have the same issue. There is no /boot/config/network-rules.cfg after reboot. If I add it (the one I found on the vanilla usb drive) it gets removed when the server reboots. I'm posting the UI screenshot of my network config and another diagnostics bundle. Notice that the eth0 is grayed out and that eth2 and eth3 are seen as what my old eth0 and eth1 used to be. I have tried deleting the network.cfg file and rebooting as well as going through the ui and resetting network config. Seems like there's an OS level issue and short of purging and rebuilding the OS and trying to get all my configs back to functional...I don't know any other way to repair this. I need some more help. Can we please get more eyes on this to see if we can figure out the root cause and fix the issue? pumbaa-diagnostics-20231101-1636.zip

nvm -- I figured out the issue -- it was crashing because my cpu fan died -- hence overheating and shutting off. replaced fan / heat sync, all is good.

@Lime1028 -- I'm having the same issue, did you ever figure out what the issue was?

I validated and reviewed several backups, hence the delay. Noting that after the subsequent reboot, the network-rules.cfg was gone again and the entire problem repeated. Assuming I can get the server back up and in an operational state, I will attempt the upgrade. I'm still baffled why my /boot/config/network-rules.cfg file keeps disappearing and why my eth0 and eth1 devices keep getting renamed to eth2 and eth3 breaking everything. I have no idea how/why this started occurring or really how to fix it. Just praying that the upgrade resolves the issue.

Hi, my server is seemingly randomly shutting down but I cannot seem to figure out why. The syslogs aren't maintained after a reboot...how can I roll the logs or somehow maintain the syslogs after a reboot? I would be fine with just changing the default syslog name to syslog_<start_time_of_log_file> or something like that so that after reboot the syslog spools out to a new file but I need help figuring out how / best way to do this. Any ideas / thoughts? Thank you.

yeah -- been planning on doing upgrade but haven't had time to validate all backups yet. That has become a much higher priority with this issue and am working on the backup validations as we speak. I will upgrade and let you know. RE: missing network-rules.cfg -- that's crazy that it's gone again. I put it there and it did work but I see it's missing now again too. I don't understand why it keeps getting removed. I can add it back but it seems after reboot it's gone again each time. This is very starnge. That said, my udev/rules.d file still looks correct now...but this is very strange. I will attempt the upgrade and see if this resolves it and report back.

Great news, I was able to use the new flash drive to boot up and get the network-rules.cfg. After moving that to the /boot/config of the old flash -- the eth0 and eth1 were both recognized and the /etc/udev/rules.d/70-persistent-net.rules were also populated correctly. I still have one file that looks strange, the /etc/rc.d/rc.inet1.conf file still has references to eth2 and eth3. I dropped the file and rebooted and those references still pop up. I'm attaching the file for reference. Any idea why these interfaces are still popping up in here? I'm also attaching a post-fix diagnostics bundle. Thanks again for the support rc.inet1.conf pumbaa-diagnostics-20231024-1239.zip

one last question -- If it does "work" with the new flash drive -- would it make sense to just copy over the network-rules.cfg to the original flash drive and then it should work?

and if it doesn't work I should just be able to put my old flash drive back in and boot back to the way it is now, right?

I will try this but I can't have the server down for extended periods of time. If I put in the new flash drive with 6.12.4 and it works -- what should I expect? Will all the configs come back or is that where I need to start restoring from backups? Either way how do I know which files to restore from backup? Is it just the array, pool assignments, docker templates or are there other things? Sorry, I just don't have a mirrored test environment to test this on and am trying to figure out how to get back to limping along like I am now in case things don't go right. Thanks.

would I need to upgrade anything or just add new flash with 6.12.4 directly? Will it keep all my configs with regard to docker / disks / etc?

Please note that I don't have extra boards and nics lying around and even if I did, this board is in a prod server and buried in a rack so popping in a new board / nic is not trivial at all. Furthermore, both NICs are still seen by the mobo and by the OS just not as eth0 (which is a special interface to linux / unraid) hence why I can't seem to just use eth2 / eth3. Any chance we can get some more eyes on this to see if they have a method to troubleshoot it further or resolve the issue? I'm ok with completely resetting the network to default / etc but I just don't know where to go from here without potentially making things worse.

So what are next steps? How can we figure this out?

So I'm clear, to where should it be generated? I don't see it in /boot/config/ and I don't see that it was there in the previous backups I have. What can I do to help us figure out why it's not getting created and/or create / restore one? The 70-persistent-net.rules is being generated each time but the contents of that file are incorrect.

I am on 6.11.5. I did delete network.cfg and reboot, that's how I got to this stage. It did reset my LAN back to DHCP, correct, but I am still getting eth2 and eth3 and no eth0. I also checked my backups and do not see a /boot/config/network-rules.cfg there historically either (from last week when it was working).

After messing around with it for a very long time -- I finally got it back up...somewhat...but eth0 is still not found and the persistent-net.rules are still not showing up correctly. I cannot seem to figure out. I'm limping along with some random new eth2 (which used to be eth1) and a static ip address... I got here by deleting the /boot/config/network.cfg file and rebooting and then just doing whatever it took in UI in settings -> network to get at least 1 interface working (apparently eth2)... Still need to figure out how to get everything back to the way it was and what happened. Appreciate the assistance.