Kcirtap1423

I'll probably do that just for the sake of completeness. I find it quite odd though that it seems to only be the bios that's detecting any sort of problem. Also like I asked before, if I do find the culprit and run the GPT recovery, will that pose a risk of data loss?

Tried updating the bios also to no effect. Also wanted to know, would using the gpt recovery, if that becomes necessary, pose a risk of data loss if used on one of the data drives? vengeance-diagnostics-20221009-0552.zip

So I'm getting the same error message on startup about a corrupted GPT header, however fdisk doesn't show that any of the drives are having an issue. The only thing that mentions GPT is the Disklabel type, which for all drives is showing as GPT. Looking at the output of gdisk for all the drives I get a message saying "Found valid GPT with protective MBR; using GPT." So as far as I can tell, all signs indicate that there is nothing wrong. Yet I still receive this error. Thoughts?

Does this mean the memory as actually gone bad or could it be caused by error correcting. The ram I'm using is ECC. Would this kind of error show up if the module had to actually correct something, or does this only come up if the memory is actually dead or dying? Also what kind of test should i run to make sure I replaced the correct module?

Fix common problems informed me that an MCE was detected. I'm not familiar with this and it was suggested that I make a post with my diagnostics. Any help on what caused this, fixes, and what to do in the mean time would be appreciated. enterprise-diagnostics-20220422-1747.zip

Just rebooted the server and both addresses did assign a 169 address.

As far as the 169 vs 198, I may have mistyped but also don't remember what the exact number was. Currently both NIC's are set to automatic and been assigned ip on the same subnet as the rest of the devices on the network, 192.168.50.60 and 192.168.50.59 (for the 1Gb and 10Gb respectively). Yes I have an attached keyboard and mouse, currently that's the only way I'm able to make any changes.

So recently my server has been unable to be reached by anything else on the network. It's been working fine for months, but while doing a recent data rebuild it suddenly lost connectivity. I have both its onboard 1Gb NIC and the 10Gb add-in card set to have static IP's. However when I try to access the web gui the connection times out, and no shares are accessible. Unraid Version: 6.9.2 1Gb onboard NIC: Intel® i350 (motherboard is a supermicro X9DR3-F) 10Gb NIC: Asus XG-C100C Things attempted thus far: 1. Swapping cables and ports on the switch - was able to access the webui for about 20 seconds after bootup via the 1gb ip only 2. Changing network setting to ones that I know worked in the past - no effect 3. Attempting to connect with only 1 nic pluged in and the IP's set to automatic - no effect 4. Deleting the network.cfg and network-rules.cfg files and rebooting - same as 1 5. Restarting my router (done multiple times throughout) - no effect Other Notes: 1. When setting the ip assignment to automatic the 10gb nic will get a normal 192.168 address, however the 1gb onboard will get a 198 self assigned address. 2. This is not the first time something like this has happened, but in the I don't recall how i resolved it the last time. This time the problem arose during the data rebuild process, I doubt that would be part of the problem, but figure i should mention it anyway.