cammelspit

For example, I have this when I look at the files. From what I have read, I don't think I am supposed to have all dashes right? This means I don't have permissions to do anything with the files. I think... So it all boils down to the fact that mover somehow dropped my permissions on the files. I just need to know how to allow user nobody to be able to read and write these files again. I think I have some idea what's going on I just don't know how to fix it.

If I were to just hail mary it and make every file owned by that user, what would I do? chown? Sorry for the noob question.

@John_M Ok, I meant I did indeed set them to 'yes', mover, swap drives, set to 'prefer', mover, now it's all broken. @Squid Frankly? I have no idea... I'm still kinda sad right now tho. No idea how hard it will be to get everything just right again if I decided to just toss out my current installs of these dockers and start over. THough, following the procedure in the unraid wiki shouldn't have caused this problem I would have thought. https://wiki.unraid.net/Replace_A_Cache_Drive I just did what this said to do.

AFAIK, the two big ones that aren't working are Let's encrypt and Nextcloud. I have the original SSD but I used the procedure in the unraid manual and I set all those shares to not use the cache, shut off docker and VM engines, invoked mover, swapped the drives, reenabled the use of the cache drive and invoked mover again. So the original drive doesn't have appdata folders on it anymore. Man, what else can I do? Im pretty useless when it comes to a lot of this stuff so setting up nextcloud and let's encrypt in the first place was not by any means an easy thing for me to do and I would prefer to not have to do it all over again. Was my procedure for replacing the SSD wrong? Was there a better way to handle this?

Hey guys, I replaced my cache SSD recently and several of my dockers have stopped working. After some help from the LS.IO guys on discord, we have figured out my permissions for appdata are all messed up. I prolly did something wrong. What's the procedure to redo those permissions so that appdata is accessible normally again?

Hi! I was wondering if I could get a hand figuring out how to fix an issue I am currently having? After an update in the last couple of days, I can no longer access the web UI for my nextcloud. Before, I had the reverse proxy from your let's encrypt docker all working like a champ for several months. I know that MariaDB is also a part of how nextcloud works so I wasn't sure which if the three docker support threads I should have posted to. I'm not so good at Linux in general but from my layman understanding of the logs, it can't find the DB? Perhaps a permissions issue? I just am not skilled enough to know what to do beyond simply reinstalling and setting up everything from scratch which I would prefer to avoid. The let's encrypt log is especially concerning since it's just the same error over and over but I would still have expected nextcloud to work even if the LE docker and reverse proxy didn't. Anyways, here is my servers diagnostics when I first found out it wasn't working a couple days ago. I also JUST replaced my cache drive with a new 1TB Samsung SSD instead of an old as the hills 120GB PNY POS. Anyways, it wasn't working before the switch so I don't think that has anything to do with it. Below I have attached the logs for MariaDB, nextcloud and let's encrypt dockers as well, though the let's encrypt log was taken from AFTER the SSD swap. I really appreciate the assist, thanks in advance! connollyserver-diagnostics-20181125-0802.zip nextcloud log.txt maria log.txt letsencrypt.txt

This is why pfSense and remote access VPNs exist right?

I upgraded late last week, had to do a lot of validation because I was suffering from the Realtek network dropping the issue. Turns out 6.6.5 works perfectly fine and I've been running full tilt, like always. Finally get to enjoy the new UI! 😜

Really? That's it? Of course, it worked... I feel silly now, I probably should have at the very least tested another browser and then when it worked I would have thought to clear the cache. I'll bet I'm not the first nor will I be the last to have problems that are fixed this exact way, right? 👍 Thanks!

Just updated unRAID to 6.6.5 from 6.5.3 and now this is what I get when trying to access the Jdownloader WebUI. Nothing was changed otherwise. I have tried deleting the container and reinstalling it, changing the port to access the UI, the same result. Any other troubleshooting I can do?

So, the file integrity plugin doesn't calculate the hash on write? Interesting... Well, since those two files seem no worse for wear and they seem to be working just fine, I can assume it just had a bad hair day. I should probably not have both file integrity and parity run on the same day though. I was using the file integrity plugin before mainly because I was running unraid without parity at the time, I know it's a bad idea but I didn't have enough drives and was using it to keep an eye out for damaged files. Now, especially with a proper full server offsite backup I probably don't even need it like I did. Though, I do like keeping known good hashes of all my files regardless if the plugin does it or not.

Do I? Maybe I do! I know a parity ran last night because that's the time I have is scheduled so I just assumed that was it. After just checking, you are right about that, I am 100% talking about the file integrity plugin. SHA256 hash key mismatch, /mnt/disk2/NextCloud/appdata_oc4lmul4d44l/appstore/apps.json is corrupted should I just chalk it up to a hiccup while checking that file and maybe just keep an eye on it? Also, sorry, apparently I am still getting used to how this thing works. 😊

So, I got up this morning and checked the server and I saw two red notifications. Seems that during the monthly scheduled parity check two files failed the check. One of them is a config file for an emulator buried deep in the filesystem, super easy to replace by just installing a new copy of that file. The second one has me slightly worried, it was the apps.json file for nextcloud. Now, last month it worked fine without any errors and so I naturally expected the same this time. Is it possible two of my drives are starting to fail? Is this something that can happen if the files are being written to at the time of the parity check and that caused it? Nextcloud seems to be working just fine and all the apps load and work perfectly. Would you guys consider preemptively replacing these drives? Run a second parity check on those drives? Is there any non-HDD-failure reason why the parity might have gotten a bit mixed up? Everything seems to be working just fine and there are no additional smart errors on the drive either. I am also running a month-long rclone transfer and have been hitting the array a little harder than usual recently, especially while I am sleeping. Again, nothing irreplaceable or important seems to be broken, and I have proper weekly offsite backups of the stuff that isn't super easy to replace. Those rclone transfers are actually backing everything else up right now. This is the first time I have seen a parity check fail so I am honestly not sure what, if anything, I should do about it. Maybe swap out the SATA cables?

You would think I would just try it, I have some rclone transfers going and my unRAID also has my pfSense VM on it so I was hoping someone else would have confirmed it fixed before I go through the rigmarole of upgrading and potentially having to downgrade again. If no one else confirms it, I can probably do the test myself this weekend. I was just hoping this might at least have a good chance to fix it, making it work trying. 😜

Any word from anyone else if the Realtek drop out issue has been solved with this release?

Perfect, thanks!

What you guys are saying is I can edit the name and such for the currently installed docker and then CA will allow me to add it again? Just a clarification.

So, I was wondering... Is there a way that I could easily just install a second copy of a docker that is already installed? I ask for a couple of reasons but mostly I want to set up a second Plex server on the same server and do some experimentation without completely ruining my primary Plex config if I happen to much something up. the option to install from the CA plugin is removed once you already have that docker installed. I know I will have to rename the docker and such and that's not a problem for me. Thanks!

OOoooh, something cool to fiddle with this weekend? YAY! 🤣👍

Instructions would be nice, I have been meaning to do this myself but just haven't gotten around to it and having a proper guide before I start fiddling would be extra great.

Pretty good read actually. I was generally aware of Realtek NICs and but have never seen the need to get an add-in card until I started switching out my networking equipment for pfSense, rewired my whole house with multiple runs of higher quality cabling for future expandability and some better switches. I've just never encountered this kind of problem before, though my Linux experience is limited to an old install I did in the 90s just to play around with it and a dual boot on my main PC I kept for about 6 months before I decided to switch back and forth just to play a game or two was too much hassle. I am pretty convinced this has to be the problem and I will likely be spending some cash on a new NIC. This is for the server that benefits two households so spending a little cash to get it working smoothly and reliably is WELL worth it IMO. Heck, the only reason I have this specific MB is the fact that it was free. 😁 I guess I was just not really so acutely aware of the reasons why everyone always recommends Intel brand NICs for applications like this. If it can reduce my headache by even a little, I'll prolly toss cash at it till it works. 😝

I did the diagnostics thing and I have that ZIP so I will have to chime in and post it for them. My server is using a board with a Realtek NIC built in. I use the Realtek for unRAID and I use my 4 port intel for pfSense, which is my guess as to why the internet kept working despite unRAID itself being inaccessible. I originally did this just to avoid having to fiddle with virtual network adapters and all but now I am happy I did this because it makes my whole setup more robust against this kind of failure. I would bet this is my failure too since obviously, unRAID is still running technically since the VM didn't stop working, only any and all communication going over the Realtek NIC. If this remains stable I may end up just adding in another Intel NIC of either the same kind or maybe get something more advanced and add it to work around the issue. I took your advice BTW and was easily able to copy over the previous folder from my backup of 6.6.0 and copy it over the 6.6.1 previous folder and it reverted perfectly back to 6.5.3. Seems to be working properly at the moment but I will still update if it happens again. I know my first foray into the forums here was not a great one, I'm sure you remember that one, but I do understand. Realtek is just so common I find it a little odd that they are not supported better. I'm just glad that if this were to happen during the middle of the night while my wife is working it wouldn't have interfered with her work as she needs the internet to do it. Gotta celebrate the small victories I guess. 😩 Thanks guys!

Whelp, it just locked up again. The VM is working still for my pfSense, otherwise, I would not be able to write this right now but my pfSense VM is using its own passed through quad port Intel NIC. If there is a patch, why wouldn't it get applied before release? I mean, I haven't the foggiest on how to actually do that so I kind of rely on LT to do that sort of thing for me. Damn, I guess rolling back to 6.5.3 is my only reasonable choice, it's a shame too because I LOVE the new CPU pinning stuff, a LOT.

Thanks for the tip, I'll just back it up and do a proper rollback only if needed. It'll be a couple days before I know if it's properly stable anyways. I'll post back next week and let you know how it went. 👍

And just minutes ago I get the notification that there is now a 6.6.1 update. If I do this update and it doesn't fix my issue, will the option to downgrade to 6.5.3 still be there? I was searching the tools and saw that there is indeed a rollback function but I don't want to do the 6.6.1 if it only keeps the last upgrade in there, which would be 6.6 and that's not quite working for me ATM. You know, I just need to have by bases covered before I do it. I have a backup of my USB and all but that would be a hassle compared to just rolling it back.