Sigma207

It is an Intel x520 according to this listing. https://www.ebay.com/itm/164448384664

My on-board network controller works fine, but I wanted to upgrade to 10gb/s, so I picked up a SFP+ card. I booted the server back up with ethernet plugged into the motherboard and without plugging anything into the SFP+. Couldnt find it on the network. Eventually decided to plug in a monitor and noticed it say "Device "eth0" does not exist" in the startup text. So then I tried connecting up the SFP+ card and still nothing. Removing the card resolved the issue. Could it just be a faulty card, or is there some setting I need to set?

This was an issue in an older version of unraid. At the time, it was fixed by an addon until an unraid update came out to fix it. I am getting that issue again and the addon does not seem to work this time. Currently running version 6.12.6. Steps I have taken to troubleshoot is disabling my network firewall, and trying different DNS servers. No luck so far and not sure what I should be trying next.

Not sure why I was having an issue with mover tuning since that plugin was disabled, but after removing it and giving it a couple days, that issue has not come back.

I had the plug-in installed, but was disabled. I removed the plug-in to see if that resolves the issue.

Here is the full error code: crond[1401]: failed parsing crontab for user root: /usr/local/sbin/mover.old start 2>/dev/null I don't know if this has anything to do with it, but I recently lost my appdata folder and had to reconfigure a lot of things from scratch. I posted my diagnostics file in case it helps. arceus-diagnostics-20221112-1746.zip

Well, that is unfortunate. Thanks for your help. I went ahead and already reconfigured some of the stuff since I needed to get this back online, so the two SATA devices are already wiped as well. But was hoping to still learn how to recover if this happened in the future. I should just be more vigilant with my backups. Thanks for your help.

That is correct. The other pool member was labeled as nvmeOn1. The screenshot posted is of the old pool before I moved stuff around.. I

Here you go arceus-diagnostics-20221101-1743.zip

Yes, I know RAID is not backup. Everything that is irreplaceable is backed up using the 123 rule. This mistake will just cost me many hours reinstalling containers and recovering from backups. My cache pool consists of two sata SSDs in RAID 1. I have been having an issue where one of the cache drives kept having errors in the log. So, I swapped in a m.2 drive I have and let that run for a bit until I can get around to looking more into it. I found some forum posts that suggest that type of error could be caused by the sata controller on the motherboard. My attempted fix was to use a mini-SAS to 4x sata cable with the extra slot on my LSI card and then immediately swap the "bad" sata SSD into the cache pool. Since it is RAID 1, it should just rebuilt as it did when I swapped in the m.2. Except it didn't. It didn't rebuild because unraid decided to change the ID of drive one (the good one) from sdn to sdc. I didn't notice that at first, so I started up the array. After swapping the drives back to the motherboard sata controller, it went back to sdn. But still shows up as unmountable. Nothing has been formatted. I tried using the new config tool in unraid, but that didn't help either. Any ideas on how to get that data back? I am a noob, so I hope I explained everything well enough and that I am just missing some simple step.

There is nothing that prompted me to open the log. I just did out of curiosity. There is still some relevant information though. I recently replaced both (mirrored) cache drives and moved all data back onto them. Then one of them stopped showing up. I swapped in a hot spare to buy myself some time until I can check it out. It was a loose wire. Reconnected the wire, swapped the drives in the pool so the hot spare is once again a hot spare and good to go. Everything seems to be doing just fine. That is when I open up the logs and see this just endlessly scrolling. Anyone know what is going on here?