youngnapoleon

Hey gang, I updated the docker earlier today, & since then, most of my torrents no longer show anything in the Content section? The other tabs (General, Tracker, etc.) all seem to be fine... but in almost all the torrents, Content is completely blank. I've tried different browsers & devices to view the Web UI, I restarted the docker, I restarted the full Unraid system, I've force rechecked, I've added brand new torrents... same deal. The ones showing Content are completely random. They're not from different sites or wildly different sizes or added at certain times... one of the new ones I added today shows, the rest don't. Anyone else come across this, or anyone have any ideas? Thanks :)

I tried the binhex/arch-qbittorrentvpn:5.1.2-1-03, but unfortunately it's a no-go. All the other dockers are fine... any ideas?

It's not just Plex. It's everything. I'm just embarassed about what the other app is though lol. Here's the diags though, friend. & thank you for being a champ.illmatic-diagnostics-20250104-1013.zip

Hey guys, I've restarted my server & my router, but Plex is completely unsuable, it takes like 1 minute to play 1 second. It looks like SHFS is using over 200% of the cpu, so I'm guessing that's it, but maybe not. Any of you brilliant people have any ideas? Or does anyone know the Slackware command to kill SHFS? Google didn't help me much lol

Yeah... I am keenly aware... I'm just kinda tryna work my around it & maybe understand where I went wrong/if it's something I did. But given the original disk still lives, I don't think I've actually lost anything, so I'm just counting my blessings

Here's the latest log if it's of any interest, but I think I'll call it a day. The fs check took around two hours & completed - with a ridiculously long log full of errors. Still at work, but judging by used space, it lost a lot of stuff. But it's all running, I'll run some more diags & keep an eye on things, see if I can get data off the previous drive, etc... & try to swap this out asap because I'm now untrusting haha. Thanks for your help guys, I'm open to any other advice illmatic-diagnostics-20240809-1439.zip

Indeed I did, all I did was remove the -n & kick it off.

Thanks for the explanations. It's still got a few hours to go for the current sync, can try the file system check soon. I forgot to mention in my original post I'd kicked one off yesterday, but when it was taking over an hour with no verbosity for me to understand, I became disheartened & stopped it. I do still have the original disk, so if that can still be loaded as unassigned, I guess a full actual format with the array running would be fine. Guess it'll be another nervous day at work constantly checking the Web gui lol. Thank you both, will update soon!

I can do that, though I worry it will take my system offline for a whole extra day... So, to confirm & out of curiosity: A) my original post doesn't show expected behaviour after a maintenance mode sync? B) even though the the array runs fine while emulated, & the sync presumably builds the disk from scratch, you're concerned it's a recurring xfs error?

I have, for better or worse reboot since the original maintenance mode sync was complete, should I wait for the current one to finish before posting diag? (edit: I've uploaded current diagnostics, but will redo them once the latest sync is finished. Any advice on whether to get new ones right after, or should I start the array proper first?) illmatic-diagnostics-20240808-2357.zip

Hey guys, I'm running the latest stable version of unraid & earlier in the week upgraded my 8tb parity to 18tb. This took awhile, but I ran into no problems. A day after that wrapped up, I swapped out/upgraded a 4tb data drive for that previous 8tb one. I followed the same (I thought) cautious process as I did for the parity. I swapped the drives, went into maintenance mode, then clicked sync after selecting the replacement drive in the appropriate slot. 8tb data build was a lot quicker than 18tb parity build lol. Then I stopped array & started in normal mode, but the new drive, despite no errors etc in the sync & no problem with any of the previous drives, said it was unmountable, no fs (though it registers in the gui as xfs, lsblk confirmed no fs via terminal). I was SO close to just ticking the format box & going for it, then was like... Omg did I just nearly clear 4tb of data that parity would then take as gospel & I can't rebuild? I don't see what other option I have though, is it just horribly worded/explained in the gui? I am currently running through another sync & it's rebuilding from parity again in maintenance mode in the meantime. Maybe after this it will just work? Can anyone clarify if something is going wrong with the sync, or if I'm actually expected to 'format' & that it doesn't actually purge the drive of data? Thanks as always, gang (also I'm writing this on my phone, so apologies for less than stellar formatting/everything.)

Hey gang, Without changing anything I can think of, I've recently developed an issue transferring files via SSH. I'm basically trying to move files from a cache share manually to another cache share... but no matter what I try, & even if I set all folders recursively to 0777, it just instantly fails with a very generic error 4 - no space on disk or different FS (same FS, in some instances it's literally the same disk) or already exists, etc... any advice on how I can troubleshoot this? Also, I have a share on a cache pool where I basically dump files from my PC via SSH (this works lol), but then, even using the web GUI file explorer... 'moving' files takes forever. I'm trying to move, say, cache/Share1/* to cache/Share2/*, & I have confirmed the amount of time this takes is based on how large the file is, & I would have thought all it's basically doing is renaming the path? Am I doing something wrong here? I feel like I used to do stuff like this a fair bit & I never had this issue. Also I'm probably just being dumb, but trying to mv/gmv from the terminal fails. Thanks for any advice

I know this is old, but just wanted to thank you because I was really stressing out & this saved me big time. God/Allah/Bob Dylan/all of them bless you.

Yeah, this is a problem for me, too. As I correctly assumed (though desperately tried anyway), creating "DATA_PERM" variable as 770 (as stolen from DeezLoader) didn't help... surely there's a way? For now I'm just setting New Permissions nightly & editing the next day. Did you get this working? Have you tried forcing an update? I know they're making fairly constant changes & I was having some issues even with the non-docker version that I'd intermittently have to reinstall/redownload to fix.

Probably worthless advice, but have you cleared the cache?