talmania

I'm resigned to the fact that I've probably lost data here but wanted input--- I recently replaced my parity drive (running parity check before and after). Then precleared the old (maybe 2 years old) parity drive. Everything checked out perfectly so I swapped it in for drive 13. During the rebuild at approximately 50% complete, I get a notification that drive 9 has failed. I wake up this AM and sure enough the user shares have dropped off, disk 9 shows millions of errors but its online and the rebuild is about 72% complete and still running. My plan is to let the rebuild complete and then do some troubleshooting (limited) with drive 9. Not sure what else to check except a reboot and perhaps reseating the drive. What I'm really after is does there exist any ability to tell/determine what files were specifically on drive 9? I have all important shares backed up but as 90% plus of my array is media, what I really want to know is what files I lost on that particular drive. Is there anyway of telling this? I use Plex so perhaps there might be an option there but am unsure. Thanks for any and all advice!

This may be my first post on the Unraid forums, but I have been reading and using for years. I am on my second Unraid system built from tips on the "Good Deal's" forum. My current rig is a Natex S2600 dual Xeon with 128 gig with the Intel case/power supply/cooler and drive cages talked about here. I built it about 8 months ago, originally planned on trying to run it as a Hackintosh server. That didn't work so well, so I put Windows 10 on it, but was never happy with it, so went back to trying to get OSX on it again. After wasting a bunch of time on that, I tried a demo of Unraid 6 on it, liked that so much that I moved all of my media off my old Unraid 5 server, and restarted the S2600 as a new Unraid 6 (using my purchased Key) server. Moved all my media, and have totally loved everything since then. I am learning about dockers and virtual machines, and when I mess something up, I can just delete the experimental thing and nobody knows about it. That is the coolest thing about the dockers and VMs. There is enough horsepower that I can spin up a test docker or VM and it does not affect the "production" Plex server. If I have it transcode, the fans will spin up high, but my CPU coolers are passive, so that is pretty much expected. I may try to replace the large Intel fans with Noctua fans to see if there is a difference. Chef Jay Thanks for the feedback on your experience. Much appreciated! For the cost I can't go wrong and have placed an order. I ended up digging into cooling solutions and found the Nocua referenced earlier is to tall for a Norco 4220/4224 so I bought the smaller NH-u9DXi4. If anyone comes across this post with a 4220/4224 the u12 won't fit apparently. Looking forward to the new build!

Hadn't noticed that--thanks! I just found the E5-2670 thread and it appears to be a better mix of price/performance so I'm reviewing that as an option now.

Well after posting a new thread on CPU/Mobo forum looking at a e5 v4 proc and motherboard I find this thread and realize the savings are more than substantial by going a dual e5-2670 route. I'm looking at the natex combo with the intel mobo and wondering for those who are running it are you still happy with the motherboard? I'm not planning on any GPU passthrough or even VM's at this point. But for 308.00 for the combo with mobo (I have tons of pulled DDR3-1600 PC3L-12800R from legacy systems) it seems like an absolute NO brainer! Using a Norco 4220 and the cooling would be my only sticking point (in addition to the PS requirements of the finicky board but I have a couple different models lying around Corsair 850 etc that I hope might work). People that went the Intel S2600 route still happy with it? Did you have to make modifications for cooling? Otherwise I'm looking at the Supermicro or ASRock option and those are more than the combo price alone!

Thanks for the feedback--I sincerely appreciate it! Did you find your SC846 with the SAS2 backplane already or did you buy a separate backplane to replace the SAS version (of which there seem to be a LOT of on ebay).

Thanks for the feedback--how are they on the loudness front? I have my stuff in the garage so its not super important but I don't want to get any louder than I currently am. In looking at the SM846 I see the PS's come in a 900 or 1200w config. Did you replace yours with a consumer model or running stock?

Are you running the latest version (6.2.4) ?? You can now have 2 parity drives, 28 data drives, and 24 cache drives !! ... you may need a bigger chassis :) Thanks gary!! I am running the latest 6.2.4 and I see myself upgrading drives to bigger sizes as opposed to just increasing drive count but it would be nice to be able to have a few open spots for preclearing etc.

I've been having tons of recent instability with my system and I believe it's directly related to the really old hardware. I've been running the following config since early 4.x days and I'm ready for an upgrade: Current build: Supermicro X8SIL Xeon x3470 16gb RAM Norco 4220 (thinking about replacing this as well and made thread in the hardware section) Dual Supermicro AOC-SASLP-MV8 50TB total space, 10TB free Dockers: Plex typically 1 stream, rarely 2--MAX of 3 (maybe once in the past 2 years!) Nextcloud LetsEncrypt Crashplan What I value: above all else flexibility. I hate being limited by my technology choices--I'd prefer to over build then fall short. I don't really see this being for KVM or VM's as I have other systems that serve that role but I'd rather build the foundation that way then have to start over. I also value my money and don't want to just throw money at a solution. What I must have: IPMI and the ability to run 2 Plex streams at the same time. What I'm considering: I first started looking at the new 1151 offerings in a e3 series xeon with Skylake but quickly realized I won't have the PCIe slots needed for the flexibility I desire. I'm now focused on the 2011-3 offerings and specifically the following: Supermicro X10DRL-i Xeon e5-1620v4 I'm open to trying other motherboard manufacturers but have had good luck with Supermicro (until now). Does the above config look reasonable? See any deficiencies or shortcomings? Thanks in advance for any and all feedback!!!

My old x3470 and Supermicro X8SIL have been giving me fits and I've decided it's time for an upgrade. Current: Norco 4220 20x drives of various sizes totaling 50TB available with 10TB free. x3470 ~5k passmark Supermicro X8SIL 16gb RAM I currently run a Norco 4220 fully populated with 2 internal SSD's for cache just hanging out internally. Have a lot of room to upgrade the drive sizes (run anywhere from 1.5's to 4tb's for parity) but I'm considering a new chassis that would allow me more than the 20 hot swap bays for preclearing etc. I'm thinking about the Norco 4224 or even a Supermicro SC846 chassis as the foundation for a new build/migration. Doesn't have to be rackmount but I'd like to get at least to 24 bays where I can theoretically max out my unRaid license. Any feedback on the 4224 or supermicro route? Other options I should be considering? Thanks in advance for the advice/opinions!

Link in my sig In what may go down as one of the biggest "OMG" moments in the history of unRAID, I happened to notice on the dashboard screen that 3508 MB of RAM was listed as allocated and 16GB of RAM available. Hmmm...that's odd I thought. Rebooted and checked in BIOS--showed 3gb there. Powered down, reseated memory, still 3gb. Pulled DIMM thinking perhaps I hadn't bought qualified memory and wanted to check DIMM stats. Sure enough it's listed on qualified manufacturers list for my mobo. Rinse repeat--still 3gb. Started poking through the BIOS and there's a check field for qualified CPU and DIMM compatibility. Disabled that option, rebooted and low and behold 16gb. I've been struggling with these random lock ups for at least a month now and at some point perhaps I loaded bios defaults or things reset. But now the UI screams as does docker UI's and scans--it's clear that just between plex and unraid I was running right up against the limit. Sometimes it's the most simple things...hope this is the resolution once and for all. Does that mean you need to memtest the other 13GB? Sent from my LG-H815 using Tapatalk Not sure..I'm certain I've tested it numerous times and can't imagine I wouldn't have noticed if it was only testing 3gb. But based on my recent history who knows...time to test for sure. Had a lockup again last night while transcoding and saw a new error "hangcheck value past margin!" A search against that showed another user had to replace his CPU so Im looking for new hardware at this point.

Link in my sig In what may go down as one of the biggest "OMG" moments in the history of unRAID, I happened to notice on the dashboard screen that 3508 MB of RAM was listed as allocated and 16GB of RAM available. Hmmm...that's odd I thought. Rebooted and checked in BIOS--showed 3gb there. Powered down, reseated memory, still 3gb. Pulled DIMM thinking perhaps I hadn't bought qualified memory and wanted to check DIMM stats. Sure enough it's listed on qualified manufacturers list for my mobo. Rinse repeat--still 3gb. Started poking through the BIOS and there's a check field for qualified CPU and DIMM compatibility. Disabled that option, rebooted and low and behold 16gb. I've been struggling with these random lock ups for at least a month now and at some point perhaps I loaded bios defaults or things reset. But now the UI screams as does docker UI's and scans--it's clear that just between plex and unraid I was running right up against the limit. Sometimes it's the most simple things...hope this is the resolution once and for all.

Link in my sig Should have looked there first--apologies. Here it is. I did find another post while searching for the freedesk error that hinted at using /mnt/user instead of the individual folders for my library. Might simplify the go command... root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name="plex" --net="host" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -e "VERSION"="latest" -v "/mnt/user/appdata/plexmediaserver/":"/config":rw -v "/mnt/user/Jason":"/JMovies":rw -v "/mnt/user/Movies":"/Movies":rw -v "/mnt/user/Jason TV/PlexTV/":"/JTV":rw -v "/mnt/user/Television/PlexTV/":"/TV":rw -v "/mnt/user/Photos":"/Photos":rw -v "/mnt/user/Christmas Movies":"/Christmas":rw --cpuset-cpus=0-3 linuxserver/plex 4c3704bfb34c8244fd6c9a848cee7959d4dc76ea9da79a1a3f7c4ec628297f2c

I got no idea. what's your docker run command? I'll see if I can reproduce. Thanks CHBMB! Where would I locate the run command? Getting a bit deeper than I've been before...

I've posted earlier in here about general lockups and I have more info. Off a clean shutdown and reboot of the system I'm seeing the following in my plex container docker log when starting it: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... No update required [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted No update required [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Those last lines will repeat until I kill it. Things I've done to this point in an effort to pinpoint the random lockups (where I can ping host but not SSH or get webgui functionality): Full memtest multiple times and for 24 hours plus runs. Removed and rebuilt docker.img multiple times. Running Plex and only Plex docker. Set CPU variable to only use anywhere from 6 down to 3 cores (out of 8 ). Replaced power supply thinking perhaps not enough on the +12v. I just can't stay stable for more than 24 hours with Plex running. At this point I'm ready to replace my hardware (Xeon x3470 on Supermicro X8SIL so it's pretty old) with new hardware in an effort to resolve these months of hard resets and reboots. I've attached my diagnostics log here in the hope it might shed some light--appreciate any feedback! diagnostics-20170101-1140.zip

I think Nextcloud has changed the setup a little bit from when I last tried. DOH!!! That's what I get for not reading everything in it's entirety! BINGO!! New instructions worked perfectly--thanks CHBMB! Edit: donations link via apps page doesn't work--found it by your main site. Thanks again for all the hard work you guys do--it does not go unnoticed or unappreciated!!

Hey Chuga-- Just wanted to let you know you're not the only one with this issue. I'm in the same boat and I believe something has changed. I had this working several days ago no problems and now I get stuck on the same error as your last post (I had it working then decided to start over yesterday just to clean things up and for learning). Since then no luck getting past the same error you've reported in the post above. I've gone as far as removing everything (including docker.img) and not using templates. I've noticed that when pulling the nextcloud docker from the "apps" tab that the orange helpful notes below each section no longer appear. I've checked in some of the logs (still trying to find out how to get to mariadb syslog!) for nextcloud and there's mention of a 11.0.1 version. My guess is there's been an update as I'm almost certain my previous version was 10.0.2.

Thank you VERY much for this! I was excited to see that previous guaranteed lockup behavior wasn't causing the lockup once I set this parameter. Then all of a sudden after repeated testing it locked up again---looking at the cores from the webgui dashboard page I saw that core 6 was reporting 100% (almost no activity on the other cores) and I had specified Plex to use 0-5....which leads me to the point I had configured Crashplan to use 6&7 and enabled it after extensive testing. So reality is I'm looking at a crashplan issue and would have never arrived there without your assistance. I know I had lockups with Plex being the only active docker previously but with this --cpuset-cpus variable I'm able to avoid having the lockups that plagued me as long as I don't have Crashplan running at the same time. Plex cpu0-5 and nothing else: no lockups Crashplan 6-7 and Plex 0-5: 100% on core6 and lockup Thanks! Maybe you need to let unRAID have a core. I'm guessing I can't assign unRAID a core as per the extra parameters and rather the process would be to just leaving one unassigned is enough correct?

Thank you VERY much for this! I was excited to see that previous guaranteed lockup behavior wasn't causing the lockup once I set this parameter. Then all of a sudden after repeated testing it locked up again---looking at the cores from the webgui dashboard page I saw that core 6 was reporting 100% (almost no activity on the other cores) and I had specified Plex to use 0-5....which leads me to the point I had configured Crashplan to use 6&7 and enabled it after extensive testing. So reality is I'm looking at a crashplan issue and would have never arrived there without your assistance. I know I had lockups with Plex being the only active docker previously but with this --cpuset-cpus variable I'm able to avoid having the lockups that plagued me as long as I don't have Crashplan running at the same time. Plex cpu0-5 and nothing else: no lockups Crashplan 6-7 and Plex 0-5: 100% on core6 and lockup Thanks!

Rebuilt successfully and on my first attempt to scan a Plex library and then navigate WebGui it became unresponsive again. Waited a few minutes then walked away in frustration. Came back maybe 45 minutes later and the webgui acted like nothing had ever gone wrong. Strange...

Very similar to you--legacy Supermicro X7 series motherboard with Xeon, 16GB RAM, dual 256gb SSD cache but I've got about 5k media files across 3 or 4 libraries with just over 20% capacity left on the entire array. I hope so too! I'll report back once the array is rebuilt here in a few days--crossing my fingers but not counting on it solving the problem.

Hi Talmania, I concur. After re-booting my server and doing a complete Parity Check (w/o issues), I've concluded that when Plex initiates, it seems to tie up the Server's resources. Interestingly after completing the Parity Check and reinitializing Plex (incl restart), I had to log out of my Webloc link and back in to find the "Server" (still do occasionally). It then seemed to find all of my movies, so apparently Plex continued to work in the background despite locking up regular access (either that or while it was checking Parity). I've subsequently added several more movies to my sub-directory w/o incident. It would be interesting if others are seeing this pattern. Are you using MakeMKV-RDP and if so have you had problems "ripping blu ray discs"? Dave Nope just using regular Plex. I've found it starts up just fine and then runs through getting metadata from the most recently added films (sometimes requesting same title 4-5 times in logs). It only seems to occur when I do a rescan on a library and then try to use the unraid webgui. That's the trigger I've found--and it's not like my CPU is taxed, memory is close to being fully allocated or the docker.img is anywhere close to being full either. It's happened almost a dozen times at this point with the only solution being a hard powerdown. The only thing I can think of at this point is the fact that one of my drives is showing a SMART issue reported (hasn't been kicked out of pool yet) with reallocated sector count of 9 (threshold 36). I'll be replacing that drive tonight once the parity check (like the 5th or 6th one at this point--cancelled the others).

Interesting reading the past couple of responses here---especially yours Archivist. I've recently had trouble (like the past week or two) with my system as well. I'm finding that with the Plex docker running and doing a directory scan etc it will cause the webui to lock up and the only thing i can do is ping the server. No telnet, webgui, or fileshares. I've been trying different combinations of dockers to see what was causing it and i have it nailed down to plex and plex alone (i only run 3 and one of those is off 80% of the time). Have ran 24-hour plus memtests, reinstalled plex, reinstalled/recreated docker etc. Have run sqlite on the database to check for corruption and it comes back clean. Still more to investigate but it's looking like Plex is the culprit IMO.

Well strange--it completed without any problems. I wonder if it had to possibly due with overheating. All my sensors don't show overheating or any alarms but I had increased my fan speed to 70% (or whatever supermicro calls it) and it completed no problems. Guess I'll continue to watch it.....

Antec Earthwatts 650w. Ea-650 Been running for a few hours now and hasn't failed yet. Neglected to add that I suspected memory but ran memtest for 20+ hours with zero errors/faults.

Install Fix Common Problems plugin then put it into troubleshooting mode, then start a parity check. If / when it crashes, post the latest diagnostics file AND the syslog.txt stored on the flashdrive in /logs Woah--never noticed that plugin before--thanks Squid! Will do!