benediktleb

Thanks @JorgeB. I replaced the drive (good time to increase capacity, too!) and the errors and reboots are a goner.

Thank you. I have replaced the SATA cable with a known good cable, no betterment. I also purchased a completely new cable and the errors are not gone (though it has not crashed yet, but the server has only been running for 10 hrs). Here an excerpt from syslog: Also thanks for providing your link. I don't think this relates to my issue, but I will try their method soon regardless. But I think this might be a good time to upgrade to a 1TB cache drive. If the issue still persists then, the motherboard must be faulty. Could the issue (see syslog attached in original post) also be something else? I never checked my syslog in the past so I am unsure whether these were filling the log up for a long time before the crashes started, too.

Hi all, Unfortunately I cannot figure out what is wrong with my system. It worked wonderfully for 3 years but it just started having issues. The syslog is full of storage related errors, some are definitely the cache (sdc) but I am not sure about the rest. What I've done so far: At some point the usb drive would not boot UNRAID anymore, but after replacing all bz files with those from the release, it was back to normal. (I think this is not directly related to my issues) Windows shows the usb drive to have errors, but when I ask it to fix it, it rescans for errors and says it is fine. Ran BTFS diagnostics, all without fault. SMART on the cache indicates at least a few errors, HDDs are fine. Please find attached the anonymised diagnostics from yesterday and also the syslog till crashing of the server. (To this regard: maybe it did not crash? I see logs that one of my access points (the one that my NAS is connected to) claimed the IP address before everything went silent. But then again, the logs show that several times, also during availability of the server. This would, however, explain why sometimes I cannot reach my server and waiting a bit makes it reachable again. In any case, it would be great for you guys to take a loot at my logs and diagnostics. I almost have a new build ready (shopping cart is filling up), but I don't think it should be necessary... Thanks! Best, Benedikt nas-diagnostics-20240224-1421.zip syslog.txt

I updated one of my PhotoPrism dockers yesterday but wanted to wait to update my second docker until I know there's no issues. It seems like the update has been pulled. Both dockers run different versions now and both are "up to date". Let's hope for a fix soon. Thanks ich777 for the great template btw!

Hi tiwing, have you ever figured this out?

Is there any danger/possibility that this would damage dockers? I updated my mariadb docker yesterday and somehow managed to corrupt the database (probably because another docker was still accessing it). Now I'm very cautious as to automatically shutting own dockers.

Thank you! I'll shut others down, first, and then the mariadb docker. Do you use unRAIDs UI to shut it down or do you use the command line of that particular docker?

I updated the docker yesterday and that led to the install being corrupted (couldn't log in anymore, ibdata1 was pretty much fried). I didn't have any mysql backups (which is stupid, I know ;-)) but luckily I also just set up my server last weekend. I didn't lose much I can't quickly recreate. My question becomes: what's the best way of updating this docker? Should I first shut down all the other dockers that use MariaDB before applying the update? I will have /appdata/ backups from now on, but that's of course no solution to an update that causes corruption. Thanks so much ahead. All the best, Benedikt

Hi Marc, just what I needed, thank you so much! I was able to get the docker to boot, although it only worked with leaving server name blank (wouldn't take my server's IP). But that's fine. What I'm having problems with is I think permissions: the WebDAV WebUI (but also when connected through a client) shows no files, but "Container Path: /var/lib/dav" points towards one that is populated with many files and folders. I already ran the Docker Permission tool but that didn't help. Did you run into the same problem by any chance? I'm looking into it now, but wanted to leave this comment here already. Thanks so much again! All the best, Benedikt

Works like a charm. Could have thought of that myself, too, what a simple answer. Thanks so much!

Hi all, thanks for this great plugin. I have WireGuard set up with the peer being "remote access to server". This works well, but I need some help with my configuration. What I want to do: I want to connect all my devices to the NAS using the same IP address, regardless of whether I'm on my local network or not and regardless of whether WireGuard is on (when on local network). Current problem: My unRAID is on 192.169.1.116 (local network). The standard "local tunnel address" was somewhere in the 10.xx.xx.xx range. This created the following problem: I have my NAS connected via samba under 192.169.1.116 (local address). Once I leave the house and I turn on WireGuard, that address cannot be used anymore and I need to add another server using the 10.xx.xx.xx address instead of the 192.169.1.116. That's of course not what I want. So I changed the "local tunnel address" to 192.168.1.116 (and the tunnel to 192.168.1.1/24) which allows me to connect via WireGuard using the "local IP" BUT once I'm back on my local network and WireGuard is still activated, I cannot access the NAS. This makes sense, but I don't know what the solution could be. Question: Can anyone help me with my setup? I want to connect to the NAS using the same IP, regardless of whether I'm on my local network or not (and for when I'm at home, regardless of whether WireGuard is running). Help is much appreciated, thanks so much! All the best, Benedikt

Thank you so much! I know this thread is old, but I'm sure people will eventually have the problem on an Asrock J4125B board, too. Removing the dash worked.