January 7, 20251 yr Hello, I'm using 6.12.14 Yesterday I swapped out the motherboard and ram in mu unraid server (all drives stayed exactly as is). When I booted initially, everything worked find. System came right up, onboard NIC were identified, disks we assigned appropriately and I began running a parity check. About 3 hours before the parity check finished the NICs stopped being recognized so I could access the web interface (I was able to monitor progress via command line through my KVM). I tried to reboot and had no luck. I rebooted again and this time I noticed at the command line the hostname had changed to Tower. Getting a bit concerned I booted into Safe More with GUI and see a few issues: 1.) the NICs are recognized by the OS, but are showing as not connected 2.) My two cache drives are being recognized but are showing up as unassigned, when I try to assign them to the right cache assignments I'm getting a warning that they are new devices and would be erased if I started the arry 3.) The hostname is stil being listed as "Tower" I'm not sure the best steps to debug from here - I'd like to pull the diagnostics, but am not sure how to do so in Safe Mode. Any help would be appreciated.
January 7, 20251 yr Author As a follow-up, I hooked up a USB ethernet adapter and disabled the two onboard NICs and was able to get into the system to download diagnostics, which I have attached below. tower-diagnostics-20250107-0020.zip
January 7, 20251 yr Community Expert Leave the USB NIC consented but re-enable the other NICs and post new diags.
January 8, 20251 yr Author Thanks for the reply. Sorry it took me so long, attached are the diagnostics with onboard NICs enabled. tower-diagnostics-20250107-2200.zip
January 8, 20251 yr Community Expert Flash drive as some lost files: -rw------- 1 root root 16384 Jan 1 1980 FSCK0000.REC -rw------- 1 root root 16384 Jan 1 1980 FSCK0001.REC -rw------- 1 root root 16384 Jan 1 1980 FSCK0002.REC -rw------- 1 root root 16384 Jan 1 1980 FSCK0003.REC -rw------- 1 root root 16384 Jan 1 1980 FSCK0004.REC This likely explains the name change and cache getting unassigned, to import the pool, you just need to start the array without any pool devices assigned, then stop the array, re-assign the pool devices as they were, start the array, server name will need to be changed manually, and possibly other settings have reverted to defauts. Regarding the NICs, they appear to be initialized correctly, and no setting should make them show link down, try different cables or switch ports, you can also boot with a new flash drive using a stock install, no key needed, just to confirm the NIC issue is not config related, and it should not be.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.