DizRD

I had two parity drives and bought a larger drive to upgrade parity and move the old parity drive to a data drive... Adding the new parity drive seems to fail but doesn't report obvious errors after starting the array (but it does report error count 41 for the drive). Smart status comes back fine for the drive. Recently updated to Unraid 7.0.1 RC1. Checking to see if there is something different I should be doing or if the drive is trash. deathstar-diagnostics-20250428-1826.zip

I can try to share the file, but It since I only have 3 aps, it might be just better to start over and hope the same thing doesn't happen until I can get it backed up. I copied that unf file out, there were none in the autobackup folder. What's the best way to reset it to scratch so I can start over through unraid?

I didn't have a chance to make any backups, but I do see -rw-r--r-- 1 docker docker 26688 Mar 17 17:10 8.5.6.unf -rw-r--r-- 1 docker docker 4256 Feb 26 17:34 8.5.6_default.unf in var/backup of the volume path, but I haven't be able to access the ui since Feb 26, so I have no idea if either is valid, I'm tempted to just wipe and try again. I May try to restore that "8.5.6.unf" to a new install unless someone says not to.

I have the Extra Param as 8G and the other mem settings at their default. I have alot of ram so I'm happy to increase it if you think that will help. when I start the container, there is a brief moment it will show the login in the webui before it crashes, so I think the networking is alright. It isn't using any VPN. I do use Adguard home for DNS resolution and block all attempts to talk to DNS servers on the internet. but that hasn't changed since it was working so I'm unsure.

Hi All, Just recently started to use this unifi controller. Since it uses so many common ports on my unraid, I thought I'd try to create an extra ip on my unraid br0 to run the controller from. It worked great, but has recently stopped working. The UI isn't responding. we had a power outage that briefly impacted the access points but not the controller server. The only error in the log:

My unraid server lost power two times consecutively the other night... and I've have some performance issues since then.. Slow access, etc. I noticed the system was cycling between trying to run parity check and run mover over and over. I disabled mover, ran parity check, took the array offiline then ran btrfs --readonly on one of the cache drives.. (/dev/sde) it reported multiple btrfs errors, so I had to run --repait as well. I smart checked the drive and it seems fine, but I'm seeing alot of IO errors in the syslog it looks like. Mover runs now and doesn't pause, but it doesn't seem to ever complete and I stop seeing it in the logs after a point in time. I'm not sure if the files that were on that cache drive seem to have issues, I can't tell if it's just file level corruption for those files or if the drive is failing, so I thought I'd get some other eyes on it for opinions, below is some of the log weirdness, That's not filtered on my part.: Jul 1 10:32:57 deathstar move: file: //..g/... Jul 1 10:32:57 deathstar move: move_object: //..g/... File exists Jul 1 10:32:58 deathstar move: skip: /mnt/cache/postgres/global/1262 Jul 1 10:32:59 deathstar move: skip: /mnt/cache/postgres/global/6100 Jul 1 10:33:00 deathstar move: file: //..t/... ### [PREVIOUS LINE REPEATED 4 TIMES] ### Jul 1 10:33:03 deathstar emhttpd: read SMART /dev/sdu Jul 1 10:33:03 deathstar move: file: //..d/... Jul 1 10:33:04 deathstar move: file: //..0/... Jul 1 10:33:05 deathstar move: file: //..t/... Jul 1 10:33:05 deathstar move: file: //..k/... Jul 1 10:33:06 deathstar move: file: //..f/... Jul 1 10:33:06 deathstar move: skip: /mnt/unprotectedcache/ebooks/.config/openbox/autostart Jul 1 10:33:06 deathstar root: Specified filename //..e/... does not exist. Jul 1 10:33:06 deathstar move: file: //..e/... Jul 1 10:33:06 deathstar move: move_object: //..e/... No such file or directory deathstar-diagnostics-20230701-1500.zip

Just to confirm before I try it... So how would I make sure mover doesn't try to move the contents on the unencrypted directory to various disks? Set the share to cache only?

So I have an gocryptfs folder I'd like to mount on Unraid.. Is it a bad idea/no-no to mount the gocryptfs "drive" /mnt/user/somedir? If it's a bad idea, where should I mount it? /mnt/somedir feels weird now after getting used to /mnt/user/somedir

Something weird happened last night.. My unraid server just kind of choked? I noticed some apps started stalling. the major ones running were plex and tdarr. I've recently added filerun to the mix as well and was browsing files at the time it choked with filerun. I tried to stop the apps, but the UI wouldn't let me. I looked at the logs and saw a bunch of: sshfs cache share full messages. I tried to run a diagnostic collection to submit here but it stalled in the middle of generation and then the ui became totally unresponsive.. I switched to ssh and was able to see processes, but most file level activities would fail. I noticed there were thousands of plex healthcheck scripts there were stalled, so I tried to kill them. I noticed too there were alot of libreoffice processes open, I assume from filerun trying to generate metadata about files which I tried to kill. I also stopped the docker service and mover.. at the end of the day, I couldn't restore functionality so I had to reboot from the command line. Any clues on what happened? deathstar-diagnostics-20221219-1034.zip

So yea, I had to figure out what Bonienl was talking about.. Maybe there is a better way, but I had to get a Smart switch that supports vlans, and create a VLAN, attach a network adapter to the VLAN port on the switch and then I attached the relevant docker network to the vlan.. It works.. but it's a pain to setup. Networking in Kubernetes would be easier, but I know that's not officially supported. Ultimately with my time in unraid while I love it as a storage device/internal app server, I wouldn't trust the isolation provided by docker and vlans at the moment for public internet facing apps.. But that's just me as a security person. I'm probably just going to setup a fedora server with kubernetes for any public internet facing apps.

Any other suggestions?

Thanks for the response! Yea it's a 24 bay case, but not all the drive bays are full in front so they don't have even airflow to keep the cool under parity load it seems. I will look into what I can do on that. As for the Docker image file, I'm using Directory layout instead of the default docker image encapsulation.

See attached deathstar-diagnostics-20221009-1909.zip

Hey, My Unraid server lost power, there was some corruption on my XFS drives, and then I was advised to update to the latest unraid version. I'm using a directory for docker instead of the default docker image. I tried docker image prune -a but it doesn't seem to make a difference. Somewhere along the way a number of app/containers were removed. When I try to reinstall them, I get the following errors: docker run -d --name='Postgres12.5' --net='netlan' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="deathstar" -e HOST_CONTAINERNAME="Postgres12.5" -e 'POSTGRES_PASSWORD'='***' -e 'POSTGRES_USER'='dsmreadme' -e 'POSTGRES_DB'='dsmrdb' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/Flight777/unraid_justworks_templates/main/images/postgres/Postgresql_elephant.png' -p '5432:5432/tcp' -v '/mnt/user/postgres':'/var/lib/postgresql/data':'rw' 'postgres:12.5-alpine' a4a539f6a3aa5a3919852d623b360bb5365fa5ffcbb83cd9f6eecc9925a09759 docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "docker-entrypoint.sh": executable file not found in $PATH: unknown. The command failed. ---trying a bulk reinstall results in this: Starting binhex-krusader binhex-krusader failed to start. You should install it by itself to fix the errors Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/tini": stat /usr/bin/tini: no such file or directory: unknown Error: failed to start containers: binhex-krusader Starting cyberchef Starting dupeGuru dupeGuru failed to start. You should install it by itself to fix the errors Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/init": stat /init: no such file or directory: unknown Error: failed to start containers: dupeGuru Starting joplin joplin failed to start. You should install it by itself to fix the errors Error response from daemon: unable to find user joplin: no matching entries in passwd file Error: failed to start containers: joplin

Hey, My Unraid server lost power, there was some corruption on my XFS drives, and then I was advised to update to the latest unraid version. Somewhere along the way the postgres app/container was removed. When I try to reinstall it, I get the following error: docker run -d --name='Postgres12.5' --net='netlan' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="deathstar" -e HOST_CONTAINERNAME="Postgres12.5" -e 'POSTGRES_PASSWORD'='***' -e 'POSTGRES_USER'='dsmreadme' -e 'POSTGRES_DB'='dsmrdb' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/Flight777/unraid_justworks_templates/main/images/postgres/Postgresql_elephant.png' -p '5432:5432/tcp' -v '/mnt/user/postgres':'/var/lib/postgresql/data':'rw' 'postgres:12.5-alpine' a4a539f6a3aa5a3919852d623b360bb5365fa5ffcbb83cd9f6eecc9925a09759 docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "docker-entrypoint.sh": executable file not found in $PATH: unknown. The command failed.