volcs0

Excellent. Thank you for taking a look. I will make the change you suggested. Also, are all of those post disabled / blocked lines concerning? Thanks again for your help.

I didn't make any changes yet based on your suggestion above. It happened again yesterday - around 16:30. Here are the last 1000 lines of the syslog. Thank you for your insights.

That did it. Thanks.

Here is what I have. Thank you. Edit - Does not appear to be listening on port 514.. Is that the problem?

I turned on syslog server (local) with /mnt/user/syslog as the share (cache only). That was two days ago, and nothing has been written to that folder. Are there supposed to be logs written periodically to the folder? How does that work for a kernel panic - when would something get written to syslog? I checked and group/user is correct (nobody/users) and permissions are 777 for the share. Thanks for the advice.

After years and years of stability, I'm now seeing occasional kernel panics during periods of high CPU usage. This is happening more frequently - I've had three this week. I have to physically turn the machine off and on. I'd like to troubleshoot this. I turned on Syslog Server with "local syslog" to a cache-only share. Is this the preferred way to troubleshoot this? In case it helps, I've attached a screenshot of the kernel panic, and I've attached my diagnostics. Thanks. tower-diagnostics-20230828-0750.zip

So, someone on Reddit figured this out. I had to go into the immich_postgres docker and delete the /var/lib/postgresql/data folder. Then when I rebuilt the stack, it recreated the database. Simply deleting the docker didn't matter - somehow the data persisted. Maybe I don't understand the difference between a docker container and a docker volume (likely) Thanks for your help with this. I am learning new stuff every day...

I installed Immich (photo server) using the Docker Compose plug in according to these instructions. Here are the list of dockers it brings up. I decided to wipe the install and start over with some new settings. So, I used the "Compose Down" feature. I tried changing the Postgres password, but when I brought it back up (Compose Up), it wouldn't connect to the database. Changing the password back worked - and all of my picture data / thumbnails were still there - even though I thought I was starting over. I tried to nuke everything - manually deleting the dockers, even going so far as to delete the Docker Compose plugin. But even starting "from scratch" and doing everything over didn't work. When I bring up the dockers (Compose Up) - there it is - the same thumbnails and data from the Postgres database. And yes, I've deleted the Library folder, so the actual pictures are gone. It's just the database that remained. So, I went into the console and manually deleted the Immich database using the DATABASE DROP command. Now, I can't get anything to work again. The Docker Compose plug-in log says that since the database is still there, it doesn't have to re-create it. How on earth can I delete the database? I know I have to delete the share with Postgres, but I don't see how or where to do that. Thanks for the help and advice.

I am logging into my unRAID instance using an SFTP client and moving files over. They are being transferred as user = root and group = root. I'd like them to be nobody:users. How do I do this? Right now, I have to manually fix them after transfer (or use the dockersafe permissions plugin). Thanks for the help.

In 15 years, this is the first time ever my server was completely unresponsive when I tried to log in this morning. I also could not SSH. I had to do a manual shut down and reboot. I'm not sure if the logs will be revealing, but they are attached. For what it's worth, I did a parity drive upgrade last week (larger drive) and then I upgraded one of the drives to a larger one. There were no errors during either procedure. The server has been running fine since (several days). Thanks for any advice. tower-diagnostics-20230710-0826.zip

I just started a parity rebuild, and I don't want to reboot (am 2 hours into a 24-hour rebuild after upgrading to a larger parity disc). Through a series of stupid moves on my part, I killed the Nginx processes and cannot get into the webgui (was doing something unrelated to the parity rebuild). I tried "/etc/rc.d/rc.nginx reload" and "/etc/rc.d/rc.nginx restart", but I get the message, "Nginx is not running." Is there any way to get it up and running without restarting the server? I am tracking the status of the parity rebuild using "cat /var/local/emhttp/var.ini | grep mdResyncPos" so I'll know when it's done. If I can't get the webgui running, it's no big deal - I can wait until tomorrow night and restart the server. I'm using the latest stable version of unRAID. Thanks for the help.

Thanks. I went ahead and ordered a Pro. Thanks for the advice.

My array is at 90%, and I'm pretty maxed out - 8Tb parity 8Tb x 6 4Tb x 2 My plan is to finally upgrade my parity to 12Tb, and swap the parity drive for one of the 4Tb drives. Then I can start buying 12Tb drives - but this will give me some breathing room. Any preference on brand / model for the parity drive? I see that I can spend $175 - $400. I have a WDC_WD80EMAZ in there now - and it's been working great for 5 years or so. I see the Seagate Ironwolf 12TB NAS for $189 and the Pro version for $200. I appreciate any suggestions. Thanks.

Here you go. Thanks. tower-diagnostics-20230205-1913.zip

Check just finished with 4 errors. I ran it as "non correcting." Any other thoughts? Thanks.

I don't think there was a non-clean shutdown since the last check. I did install a new drive - and there was a subsequent parity rebuild of the new drive. I will run another check right now (non-correcting). Thanks.

Parity check just finished with 1757 errors. Attached are the diagnostics. I'd like recommendations on how to troubleshoot and proceed. I don't see any write errors and all drives are XFS. I haven't done any other troubleshooting. The array seems to be working as expected. Thank you for your help. tower-diagnostics-20230202-1142.zip

Did anyone ever sort this out? Does DLNA work in binhex-plexpass? It's not working for me, and this is the last post in this thread about it - with no solution. Thanks.

I just got Xpenology up and running on my unRAID by following these directions. I want to use the Photos app on Synology, but I want to connect to my unRAID photos share (I have 2Tb of photos). How can I do this from the VM and/or Xpenology instance? Thanks.

I set up Wireguard VPN, so I can now connect to my unRAID interface. I can run most of my dockers. But I cannot connect to my sabnzbvpn or any of the containers that route through it (RADARR, SONARR). Maybe this is obvious, but is there a way for me to get to these dockers (for instance, to add something to SONARR)? I know there are ways to add requests to *arrs containers. But I'm specifically asking why I can't access these VPN containers via my Wireguard VPN connection - and if there is anything i can do to fix it. Thanks.

For TubeSync, I'm getting this error repeatedly: Invalid HTTP_HOST header: '127.0.0.1:8080'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. Bad Request: /healthcheck I added 127.0.0.1 to ALLOWED_HOSTS, along with localhost and the IP for my unRAID. Any other fixes? Does this error matter? Thanks.

I've noticed some serious slow downs in copying to and from the array - both to shares as well as disks. I want to desk I/O speed and tried to use the hdparm command via the console. No matter which disk I choose, it just hangs. hdparm -i works. Formatting a new unassigned drive fails. Something is wrong with the array, and I can't sort it out. Diagnostics attached. tower-diagnostics-20220202-1253.zip

I'm on 6.9.2. I'll let the mover run and see what happens. If it still doesn't work, I'll restart the array. Thanks for the advice.

Since I've expanded my cache pool to 2Tb, I've decided to change my Downloads folder from cache-yes to cache-preferred. Will making this change result in files currently in the Downloads share but not on the cache drive being moved to the cache drive? Or does this only apply to newly transferred files? My Downloads folder share is quite large (300gb) right now, and all of it has been moved off of the cache drive to the array. Do I need to invoke some other mechanism to get it all onto the cache drive - or will the mover take care of it once I change the share from cache-yes to cache-preferred? Thanks.

OK. I pulled the drive - sitting here on my desk. Will wait until the rebuild is done (~16 hours). Then will put drive back in and run a pre-clear on it (is this still possible in 6.9?)