Fffrank

It seemed like my apps didn't load their previous configurations -- they are either running as if it's the first time and are initiating setups or they are throwing errors all over the place. Balance is done -- I guess I'll restore my previous appdata and hope that's all that was effected?

Shares came back up on reboot but my appdata and dockers are still hosed. Here's a new diagnostic in case it offers any more insights. hippo-diagnostics-20200407-1208.zip

Yes, the unraid GUI isn't throwing any errors but my appdata is all out of whack and my dockers are mostly broken. Also all of my user shares have disappeared. I do have backups for my appdata but was hoping I could re-add that missing device. I did run a scrub after reading in the btrfs docs that it should be harmless (although now I'm worried I may have caused more harm?) At one point I issued a command that showed me the UUID of the missing device (and it matched one of my removed devices.) I can't remember how I did that but it still seems like those drives should have my data it's just that there is no way that I can see to mount them or re-add them to the pool non-destructively?

hippo-diagnostics-20200407-0849.zip

Was preparing to replace some cache drives and was removing them 1 by 1 and rebalancing. Everything was going fine until I accidentally removed 1 too many and my cache would no longer mount (missing disks.) I figured I could just add a cache drive back and it should rebalance -- but I don't know if I readded the correct one because it never was able to verify again. The last time it spun up successfuly in Unraid there were 4 drives (out of 8 available.) When I removed the #4 is when the problems started. Running btrfs scan shows me an array of (4) drives but that states there is a missing drive. I can mount that pool and run a scrub and it doesn't find any errors but it seems like certain files are unavailable. Any other ideas of what I can try?

So weird -- never seen this before. Seems like the drive controller is completely dead. Plugged it into a USB interface that I have and isn't detected on two different laptops. Unfortunately I don't have a desktop to check it on but it doesn't even spin up or blink when plugged in. I'll call it dead and order a new one. Anyone seen a drive die this way with no SMART warnings or errors -- just decides to die?

Upgraded from 6.8.1 to 6.8.3 -- I do know that my parity drive was displayed green and working fine before the upgrade but I can't for sure say it failed after the upgrade. Did the regular upgrade and a reboot and a couple of weeks later logged in to see a message that there was no parity drive in my array. Checked the physical drives and they have not changed/moved (although I did try swapping which bay my parity drive was in to no effect.) Diagnostics attached. hippo-diagnostics-20200402-1152.zip

There's already a maintained version on their docker hub. Have you tried it? Should be pretty easy to get to work. Looks like all you need to do is map an external port of your choosing to port 80 on the container. https://hub.docker.com/r/shaarli/

Boot order was correct. Switched my flash drive to another USB port and it came right up. No idea what/how that happened.

Really the first issue I've ever had with Unraid. My server updated and rebooted and didn't come back. It's headless so I had to track down a monitor and keyboard to see what was going on. It's not booting from the flash drive any more. It tries to boot from the C drive, fails, tries to boot from the NIC, fails and then restarts. I've pulled the flash drive but not sure best way to proceed to make it bootable again? What might have caused this in the first place?

Is anyone else having trouble with deluge? Looks like it was updated 2-days ago and mine is putting a strangle-hold on my resources. CPUs are all pinned and the system is bogged down. If I kill that docker it goes back to working normally.

I have a really weird issue -- Home Assistant is polling Unifi to see what devices are connected. If my docker daemon restarts or my server restarts, the connection from HA to Unifi-Controller times out. If I manually restart my HA service it connects just fine. I've tried increasing the delay of the HA server to 10m after the Unifi-Controller starts but it still times out when trying to connect. Anyone have any ideas what else I can try? (Posting here because there isn't a support thread for the HA container -- which is likely the problem.)

Upgraded from 6.6.7 without any major issues and only one minor one. The upgrade took all my services offline but then never rebooted. I was able to ssh in and manually reboot and everything came back up fine (so far.)

That's pretty impressive! I'm pulling ~200watts at idle. But that's with 14 HDDs on an HP G8 server w/ dual x5660s and 96gb of RAM. I don't have a smart plug so I can't tell daily usage, but my PDU never seems to spike above ~240w.

Was able to connect to iLo3. It was a bit of a headache as the firmware as at 1.15 which only supported TLS1.0 (which has been dropped from every current web browser.) I finally was able to install Firefox 23 and then enable TLS1.0 and SSL3 in order to connect and update to 1.20 and then 1.90 firmwares. Cool! Next question -- how can I update the system BIOS either remotely or from UnRaid. HPE only makes available RPM packages and Windows packages. Doesn't look like UnRaid can install RPMs. I tried to flash via a Windows VM and it couldn't detect the system. My server is headless so I don't believe I can do it via USB..... thoughts?

Got it -- I'll try this over the weekend. I can watch the DHCP server on my pfsense for a new ethernet assignment (assuming that my server iLo uses DHCP, anyway.)

I've got an HP hba card and an expander. Bios info: <description>BIOS</description> <vendor>HP</vendor> <physid>0</physid> <version>P67</version> <date>08/16/2015</date> I actually have no idea how to login to iLo. Do I need to connect another Ethernet cable?

I've got a HP DL380G7 -- it's up and running and has been relatively trouble free. But last night I rebooted and the fans now won't quiet down. Rebooted again and same issue. I know this is a tricky and probably bios related problem but all my drives are showing in SMART and 25-30C. System temps are all low. System is basically at idle. Thoughts on things I could try to quiet it down? It's in my basement so it doesn't need to be silent.... but it's gone from a negligible amount of noise to an annoying amount.

The umask issue was unrelated. Fixed that and still couldn't connect to the daemon. Rolled back to version 79 (I'm using the aarch64 builds) and it works again. I wish there was a way to flag a docker image as broken.

Recently my deluge instance quit connecting to the daemon. Log is here: https://pastebin.com/F16zrHF7 ./run umask is failing but I'm not sure what that means?