A couple hours ago I shut down my Unraid server because I was going to be messing with (moving/replacing) the power and network cables respectively. When I started it back up I noticed the Disk Location Plugin had the locations different colors than they were when shut down and My 1 VM hadn't started, Then I noticed that the Dockers hadn't started either. When I click on the docker tab I get a message about "Docker Socket failed to start" (pictures attached). The disk Location plug in when started had a different color scheme from when it was shut down, 1 and 2 are supposed to be array parity (dk. orange/red), 3 should be array data (orange), 13-14 is supposed to be cache (purple). "Fix common problems" says something about the disks being full or read only, but they're not as shown in the other pics. After my main desktop crashed i've been using my array/vm as my main data storage (as well as my Proxmox Backup Directory on my VM), and now with this I can not access ANY of my data.

 

I'd asked on the Facebook page, but didn't get any help, just "Fix your pics", which wasn't helpful.

 

I tried a restart (clean) and when it came back up I got a message about an "unclean restart" (i think was then wording) so It's now doing a parity check, ETA 8hours or so until it's done. with that for some reason I can not access the dashboard from my PC (over the network), just from the server interface monitor. Any question to help you help me, just ask and I'll try to answer to the best of my knowledge, I don't know linux, I've had to use Youtube to get everything setup a couple years ago, alot of which was spaceinvader and ibracorp.

 

Less important: While I had it off I looked to see if I could put my Quadro (p4000) back in but unfortunately there's no way to make it fit in the new chassis I have (2u), with that How do I go about removing it so Unraid doesn't look for it at startup anymore?

 

System:

Unraid 6.10.3
Supermicro x10SRL-F Board

in a Supermicro SC826 Chassis

Array drives in front, Cache drives in rear

Edited October 28, 20241 yr by Eugene D
add system specs

Please post the diagnostics.
 

Here you go. I don't know if it matters much or at all, but I noticed that the time is wrong on the system too (Console GUI)

unraid-diagnostics-20241029-0446.zip

Pool is going read-only, likely due to a device dropping offline in the past:

 

Oct 27 13:14:32 Unraid kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 31150988, rd 879840, flush 2416578, corrupt 0, gen 0

 

Disable docker and VM services so that nothing else gets written to the pool, then reboot and run a correcting scrub and post new diags.

OK, I set both docker and VM Manager to "no" and restarted, upon restarting the colors on Disk Location were kinda back to normal (both cache drives were purple, I think the array ones were correct too, hard to tell) but the time is still off for some reason (again, I don't know if that has any effect on the issue). I then went to the "main" tab and under pools clicked on the "Cache" title and selected the checkbox for "repair corrupted blocks" then clicked Scrub. I'm hoping this was the right one, as I didn't find the word scrub anywhere else I looked. Here is the resulting diagnostic file after.

unraid-diagnostics-20241030-0622.zip

I forgot to ask for the scrub results, were there any uncorrectable errors? You can see the last scrub result in the GUI, above the scrub button.

The scrub results were:
UUID: 26ae09fe-73d8-4cb3-9066-0fa4960759b2

Scrub Started: wed Oct 30 06:14:49 2024

Status: finished

Duration: 0:12:31

Total to Scrub: 253.97GiB

Rate: 346.29MiB/s

Error Summary: verify=9629 csus=4567661

 Corrected: 4577290

 Uncorrectable: 0

 unverified: 0

All errors were corrected, now reboot to clear the logs and re-enable docker and VM services, then post new diags.

Rebooted and re-enabled Docker and VM Services, Dockers started; VM, I didn't try since I removed the associated disks for it (Truenas VM, Set up a bare metal for it since this was down. I may shut it down so I can try and recover the settings from the VM.) My shares (mapped Network Drives) that are on the unraid array didn't re-connect, Web UI still not available. Docker Web UIs also time out.

 

Here is the new Diagnostics.

 

Thank you for all your help and your patience with me only being able to reply around this time of day when I get home from work (working over night this week so sleeping throughout the day and on the road at night)

unraid-diagnostics-20241031-0551.zip

Pool looks OK for now, for later you will want to reset the stats, also in the same link recommend using the script better pool monitoring.

 

Regarding the WebGUI issue, ethtool output on the diags looks strange, the bond is appearing multiple times, try renaming /boot/config/network.cfg and network-rules.cfg to revert back to default DHCP, then reboot and grab new diags.

Sorry for the delay. I went into boot-config and added ".old" to the 2 network files mentioned I then, once scheduled parity check was done, restarted the system. when it started back up I got "missing disk" on one of my cache drives so I replaced it then had to wait for that to rebuild. once it got done doing its thing I went to the network settings tabs and tried to set my static IP back and add my vlan aware tags (also tried specifying IPs on those vlans, It seems pretty self explanatory but for some reason it wouldn't load for me. Do I not put a vlan tag for the host system IP/vlan maybe?!) , while the server was on my "default" vlan it appeared to connect to a mapped share in the UI, once I did the changes and restarted it wouldn't connect again. so I have since deleted the new old network configs and restarted again, I am now able to connect to the web UI (Havn't tried the docker UIs yet) and have since been trying to copy the shares data to another nas just in case before I start messing with the IPs again one at a time. once all this is up and running again I'll have to go through all my dockers and make sure they grab the correct IP, does this network reset change the "Docker network" configured, or is that unaffected?

 

Here is the config I just downloaded after the network reset prior to trying to mess with any of it, while files are copying/moving from it to another nas if it matters.

 

edit: Now that it is connecting to the time servers/internet the time appears to have fixed itself too. Could Unifi have pushed an update that broke my network settings that has worked fine for the year that I've had my network equipment in use, I haven't made ANY changes to the network settings in a good while to make it break.

unraid-diagnostics-20241103-0018.zip

Edited November 3, 20241 yr by Eugene D

If it works in auto/DHCP it suggest you are not configuring it correctly, but that would be a LAN problem, not Unraid.

Any idea why this is at the bottom of the dashboard page? FCP doesn't mention any issues.

Try booting in safe mode to rule out any plugin issues.