oneskinnydave

Hey All - I had an old version of macinabox running fine but wanted to upgrade OS systems - removed everything (appdata, domains, and custom_ovm files - but getting this weird state after installing OS (Big Sur or any other) - just goes back to an install window with MacOS Base System, OS Installer or Recovery DMG. Is there something I'm missing here? If I click on any of those options it just dumps me to the installer again.

Ok - found a strange bug plowing through the UDMP logs - one port was causing a network loop somehow - to be sure it's all taken care of, I did a full wipe and i'm up and running (so far). Thank you ALL for your helps and ideas - still relatively unsure of how that all happened, but glad you all could put your thoughts in and help me wrap my head around it!

Ok - more weirdness. Got a new NIC card installed - fired up great for a second got an IP via DHCP - was fine for a minute - but then goes back to a self assigned IP address. Gave it a reboot and now I get nothing from any ethernet port. Apart from reinstalling Unraid - what other network setting am I looking at possibly toying with? My unifi network doesn't have any VLANs but should I enable that? I'm going to delete the network config file as well - maybe open it up and see if anything is wrong on there. I also changed my Unraid server name in case something was causing it to be blocked because of the old name showing up.....I'm at a bit of a loss for sure.

I tried a USB linux boot an similar issues - I have an external PCIe on the way to see if that will solve it. Seems odd that it just went out - not sure how common that is on these supermicro boards - but maybe it's just bad luck on my part!

I have tried different cable(s) and also different ports on the motherboard - same result. The router LEDs do show traffic nonstop - and the motherboard interface shows traffic. I have disabled docker and VMs (sorry, I should have said that) and even run just unraid and get the same results.

Ah - good idea - I might actually try the Rpi again and see how that behaves as well. Would that point to an issue with the USB drive or just the unraid install in general? I can get to the GUI load of Unraid just fine - so I didn't know if there is a process where I can just upgrade/fresh install the files on the USB and see if that fixes it! I do have a HA server and plex server running from UNRAID so I'd love to get this thing back online so I can no have to get up and turn off light switches

I'm scratching my head a bit here - updated my old unifi router to a new one, migrated all my setting over and everything was fine for a few days. I plugged in a new Rpi I was tinkering with and my whole network shut down (few APs, switch, etc) - still connected, but all my devices went offline. Unplugged the Rpi - thought that was the issue, but poking around and uplugging/plugging devices it seems my Unraid server is the issue (at least now). I have not changed anything on the server at all - been running flawlessly for a few years - dhcp assigned IP address - nothing static, real basic stuff. But if I plug it in to the network it literally shuts down everything, my client count goes to 0 devices....my unifi router (UDMP) is still reachable by external address - but locally it's gone and so is everything else. If if punch in static IP info I never get the address I save, I get an address on my subnet - but not the one I designate. If I select automatic/DHCP I tend to get a self assigned IP (wacky high IP address) - if I add a fixed IP in the unifi router I get mixed results. Weirdest part is when I get the IP address on my subnet - I get an almost correct MAC address - sometimes I'll get the IP address I specify with the proper MAC address, but it disappears in a few minutes - other times I get 2 address from one LAN port. So strange. Here are a few things I've checked/done: -No ISP router or anything before my UDMP -Kept same network range as before (basic 192.168.1.x) -Made sure no new/strange unifi/firewall settings were set up...I deleted my migrated site and started fresh install of the network setup -new cable (just in case it went bad) and different ethernet ports (I have 4 on my server) -pulled USB flash drive from server, deleted the network config file and had Unraid rebuild it to set to defaults -started in safe mode (both w/GUI and without) - with GUI I can see the self assigned IP address -can't ping any of the addresses that come up when I get one for the server I've been elevated to a level II support for unifi - but wanted to cover my bases....90% sure they'll tell me it's something on UNRAID side of things which kind of makes sense....but also doesn't really make sense (to me at least). Again, this all works fantastic for a few years - but all the sudden it started doing this funky stuff!

Awesome - thanks for the quick reply! So I will just be prompted to extend/purchase once I get this thing fired up again if it has expired?

Hello! I had setup a server using unraid and about 3/4 of the way through my trial - I had an unexpected motherboard issue and am waiting for a replacement/update hardware to come for me to fix. I'm pretty sure my trial ends this week and I won't have the replacement part just yet - will my drive/information still stay intact if my trial expires, and just need to purchase a key as soon as the system restarts? Thanks for your time!

Hey Everyone! I'm tinkering around with my first server build and I think I'm hooked....but I just started getting some MCE errors and I'm just making sure I'm reading them correctly! Mar 27 17:19:04 NASy root: Fix Common Problems: Error: Machine Check Events detected on your server Mar 27 21:00:34 NASy kernel: mce: [Hardware Error]: Machine check events logged Mar 27 21:00:34 NASy kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Mar 27 21:00:34 NASy kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x86b2d8 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c2 socket:1 ha:0 channel_mask:1 rank:0) Mar 27 21:00:45 NASy kernel: mce: [Hardware Error]: Machine check events logged Mar 27 21:00:45 NASy kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Mar 27 21:00:45 NASy kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x86d03a offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c2 socket:1 ha:0 channel_mask:1 rank:0) Mar 27 21:00:47 NASy kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Mar 27 21:00:47 NASy kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x86d398 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c2 socket:1 ha:0 channel_mask:1 rank:0) Mar 27 21:00:47 NASy kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Mar 27 21:00:47 NASy kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x86d428 offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c2 socket:1 ha:0 channel_mask:1 rank:0) Mar 27 22:26:24 NASy kernel: mce: [Hardware Error]: Machine check events logged Mar 27 22:26:24 NASy kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Mar 27 22:26:24 NASy kernel: EDAC MC1: 1 CE memory scrubbing error on CPU_SrcID#1_Ha#0_Chan#0_DIMM#0 (channel:0 slot:0 page:0x86dacd offset:0x0 grain:32 syndrome:0x0 - area:DRAM err_code:0008:00c2 socket:1 ha:0 channel_mask:1 rank:1 I google'd up some of that hot error lines and looks like I could have a bad memory stick - I'm going to shut it down and check bios logs to see if I can identify which one it is. But what I can't tell is what exactly the issue is (or if it's even worth it?). I can't seem to find and "scrubbing" errors online - and it doesn't happen all the time, but It's only logged it twice in the last 2 weeks I've been setting it up. It also seems to be happening as the mover is invoked which seems odd? Is there anything anyone can decipher from the codes as well? I just installed MCElogs to maybe give me more info. Sorry if I haven't provided enough info - this world is a little new to me! Thanks for any light someone could shed on this! nasy-syslog-20200328-1345.zip