https://www.reddit.com/r/unRAID/comments/1m1ttue/unraid_lost_internet_connection_now_wont_boot/

This is my post on reddit. Essentially i noticed some of my containers that i have reverse proxied weren't available online. I started digging and am now at the point where i restored my flash drive from a backup from unraid connect. It will boot into gui mode (it would only boot to safe gui mode before restoring the backup) but now i get unable to connect to the localhost. My Unifi UDM Pro can see the server on the LAN, but there is zero traffic moving up or down.

I've attached my syslog from the last boot before restoring the drive.

Before restoring the drive, if i were to let it boot normally, it'd get stuck on the line update_services: queue new job 3, wait for 20s

I let it sit there for over an hour and nothing happened.

Thanks for any ideas!

syslog

Please post the diagnostics.

So i think i've narrowed it down to an issue with my LAN card. I have local access to the server, but it won't connect to the internet. I'm not sure what I did...

Luckily I have my gaming rig that I haven't used in a year so I fired it up and everything seems to work fine. I just need to move my HDD's over and rebuild everything.

Question: My disk management file looks like this

Disk Assignments
Disk: parity Device: WDC_WD100EMAZ-00WJTA0_XXXXXXXXXX Status: DISK_OK
Disk: disk1 Device: WDC_WD100EMAZ-00WJTA0_XXXXXXXXXX Status: DISK_OK
Disk: disk2 Device: Status: DISK_NP
Disk: disk3 Device: WDC_WD60EFAX-68JH4N1_WD-XXXXXXXXXX Status: DISK_OK
Disk: disk4 Device: HGST_HDN724040ALE640_XXXXXXXXXX Status: DISK_OK
Disk: disk5 Device: Status: DISK_NP
Disk: disk6 Device: WDC_WD100EDAZ-11F3RA0_XXXXXXXXXX Status: DISK_OK
Disk: disk7 Device: Status: DISK_NP
Disk: disk8 Device: Status: DISK_NP
Disk: disk9 Device: Status: DISK_NP
Disk: disk10 Device: Status: DISK_NP
Disk: disk11 Device: Status: DISK_NP
Disk: disk12 Device: Status: DISK_NP
Disk: disk13 Device: Status: DISK_NP
Disk: disk14 Device: Status: DISK_NP
Disk: disk15 Device: Status: DISK_NP
Disk: disk16 Device: Status: DISK_NP
Disk: disk17 Device: Status: DISK_NP
Disk: disk18 Device: Status: DISK_NP
Disk: disk19 Device: Status: DISK_NP
Disk: disk20 Device: Status: DISK_NP
Disk: disk21 Device: Status: DISK_NP
Disk: disk22 Device: Status: DISK_NP
Disk: parity2 Device: Status: DISK_NP_DSBL
Disk: cache Device: Samsung_SSD_980_PRO_1TB_XXXXXXXXXX Status: DISK_OK
Disk: plex_cache Device: WDC_WDS100T2G0A-00JH30_XXXXXXXXXX Status: DISK_OK
Disk: flash Device: Cruzer_Fit Status: DISK_OK

when I recreated the flash drive i copied over form a backup from the config folder:
DISK_ASSIGNMENTS.txt

Plus.key
and from config/plugins i copied over:
entire dockerMan folder

I have screen shots of everything else and wanted as stock a system as i could get without having to rebuild it all. In my tinkering i found that when i went to assign the parity drive, it was going to clear it, then start over. Since that is going to happen anyway, can i assign my disks in a more logical/new order? Or will my shares get all jacked up?
I know this is kind of a wacky way to start over, but I don't want to lose my shares and docker configs. Since the HDD's are fine, would this be an ok approach? is there a better way?

Thanks again!!

You can move the data disks to different slots, and since you don't have a parity2, you can still check "parity is alçready valid" to avoid a sync and keep the array protected, though it's good to then run a correcting check.

3 minutes ago, JorgeB said:

You can move the data disks to different slots, and since you don't have a parity2, you can still check "parity is alçready valid" to avoid a sync and keep the array protected, though it's good to then run a correcting check.

awesome thanks!