joebot

if I backed up appdata that should pretty much cover me for my dockers, right? There's also a libvert backup, but I don't have any VMs on this machine. I've confirmed that nothing has changed with my dockers since the last back up. All the plugins reside on the flash drive, right? All my shares are set to either cache "Yes" or "No" with the exception on System Data, which i set to prefer... Since system data is set to prefer and there's nothing in the backup directory for that, does that mean that I will have problems if I wipe the disks and use plugin's restore function?? Is there anything else that I could conceivably have only on my cache disk? I haven't made any transfers to the array in quite some time before the crash.

ok I got the array running without the cache but then I realized that I have a backup of my cache pool because I'm using the automatic backup plugin (CA Auto Backup). is there a way to leverage that to make this easier?

is there something special I need to do to unassign the cache disks? when I change the drop down to "no device" the system complains and grays out the start array button. sorry for being so dense, and thank you so much for your help thus far!

ok. i assume that I can just delete the folder I created on the disk (/mnt/rescue/cachedump) and then parity check will fix it?

ok that helped! now, another important question - how do I mount one of my array drives without messing up parity? I'm asking because I got as far as mounting one of the disks (manually, through CLI, to /mnt/rescue) and added a folder called 'cachedump' before realizing that this might be a terrible idea. did I totally donk up the array? I haven't written to that folder I made on the array disk, but I did create the folder. Also, after starting the array in safe mode, I did not find a /disks folder in /mnt. should I have?

ok will do. also, i just noticed that one of my cpu's is still pegged at 100%. any idea why that might be? I'm still in safe mode, but I have a few plugins loaded.

Im trying to mount the cache pool as prescribed in that link. I have a pool of two ssds. i tried to mount the first disk with: mount -o usebackuproot,ro /dev/sdd1 /x and it returned "Segmentation fault" - what is that all about?! ...so I tried mounting the other drive with: mount -o usebackuproot,ro /dev/sdc1 /x and the cursor simply did a carriage return when I pushed enter and nothing has happened... what does that mean, if anything?

Thanks a ton - I would have never interpreted that as an unmountable cache file system. Do you have any tips to help me spot something like this in the future?

Yeah I'm on the stable branch. Two questions: What in the syslog data tipped you off about the cache filesystem? I totally didn't see that. Considering that my server hard crashed, what were my options for returning to normal operation? Hard reboot seemed like the only option since it was unresponsive...

Anyone have an idea? I'm getting desperate here. I've tried disabling plug ins and then dockers (but not at the same time). Neither try helped.

A few days ago, after making a simple change to my router (probably unrelated, I was testing pi.hole and told my router to use public dns instead of pihole), I looked over at the dash board and noticed that it had frozen. At the time that it froze, all of my CPU indicators were maxed out. I waited for a while, and it didn't come back. None of the disks were being accessed, and seeing as how it was hard-crashed, I figured I better just cycle the power. On reboot (boot to gui, normal mode), the unraid gui environment loaded, but the webserver would not start and none of my server's services were operational. I can reboot into safe mode and see the webui just fine. I have verified that the server is connecting to the network (it pings just fine, and ifconfig reports the correct network configuration). I really need help figuring this out, as all my home automations are down and it's making the wife angry. Facts recap: server hung during normal operation (pegged CPUS, no disk access, webui crashed) server will boot to normal mode, but the webui does not function server will boot to safe mode with functional webui server has no problem talking to the network I don't know what I'm doing Wife is mad A few other interesting things: When booted to normal mode (webui doesn't work), I can see that one of the cpu cores is pegged at 100%. I have no idea why. Upon trying to access the webui from a different computer (while booted into normal mode), SYSLOG reports "rcu: INFO: rcu_bh self-detected stall on CPU" I have attached a syslog (starts with enabling logging to flash booted to safe mode, followed by a reboot to normal mode, followed by me fruitlessly trying to safely shut the server down again) and my diagnostics file. Please help!! Thanks! syslog skippy-diagnostics-20200927-1553.zip

I couldn't get the xlinix reset to work. I think that might be just for really old devices maybe. Do you think this could somehow be the result of my pihole? Does the radio communicate differently than the other devices for some reason?

no, not in a long time. I'll have to check if my credentials are in the server. the radios don't want to connect to that either, but I haven't really tried to connect to it. I'll look into disabling it and I'll also try that reset you mentioned. Thanks guys!!

i just noticed that the device doesn't disconnect from the network. It still has an IP and it reports the server's address. However, in the diagnostics menu, it says that it can't connect or ping the servers ports (9000 and the other one). I know that the ports are setup right in the docker and are visible on the network because all my other players can connect just fine. Keep in mind that my SB touch devices are also on wifi and they connect and play just fine, too - so it's not a problem with the AP. It's something specific to the SB radios and their ability to access the ports. also, this is what my AP reports when the radio stops working: Also my AP is on the LTS branch of the ubiquity thingy, hence the older version.

Thanks Jademonkey - here's what my settings panel looks like: Only thing that seems interesting is that the tooltip seems to indicate that I should keep the multicast and broadband filtering option disabled: