MPulse

You can add the community tag to the post arguments and you don't have to worry about paying for the pro version. Of course the community edition doesn't have all the full features as the pro version. Check this site for a comparison: https://www.ntop.org/products/traffic-analysis/ntop/

How do I retain my setting upon restart or reboot. When I restart the docker all my ntopng preferences and settings revert back to their default settings.

Why don't you simply create another user profile in Plex and only make your home videos/pictures visible to that account? Then you can still use your primary Plex account strictly for movies/tv shows, etc? This way the UI remains clean.

Hi everyone, I've done a bit of research and still not 100% sure what kind of SAS/SATA controller I should get. I need to expand my storage so I'm trying to find the best card that is compatible with the latest version of unRAID and doesn't introduce too much latency. I currently have a Gigabyte GA-Z87M-D3H mobo. I'm not currently using any virtualization and likely won't be in the future. From what I can tell from these forums a controller that doesn't have any RAID capabilities is preferred, am I correct? What's the verdict on the SuperMicro AOC-SAS2LP-MV8? Is it compatible with my mobo? Is there a better option in the same price range? I guess a PCIE x8 is preferred over x2 or x4 so it doesn't create a bottleneck for parity sync? Anything else to be on the lookout for? TIA

Yeah, that's what I did. I had to stop the array and even shut down the server to physically remove the old drive and install a new drive. Not really sure what went wrong but I'm pretty certain I did the right procedure. Oh well, good thing I still kept the old drive handy.

Yeah, I have a schedule set to check parity on the first day of every month. Prob best to do another parity check right before making any hard drive changes.

I'm starting over again as you suggested. I reinstalled the old 1TB drive and took the 3TB out. Created a new config and assigned all the drives back to their original slots but left out the parity drive. I started the array and confirmed that all my data was still intact on the 1TB drive. I stopped the array, assigned the parity drive again and started the array. Now it's rebuilding parity from scratch. I'll let this run now for the next few hours then perform a parity check to make sure it's all good. After this is all done, I'll shut the server down again, remove the 1TB drive, re-install the 3TB drive, power-up the server, assign the 3TB drive to the same slot as the old 1TB drive and start the array. This time hopefully it will restore the data back from parity.

Running v6.1.6 I'm prob just using the wrong terminology. After starting the array with the 3TB drive in the same slot as the old 1TB drive, it ran "something" which took a few hours to complete. I assume it was restoring the data on to this new drive.

I removed the old 1TB drive and installed a new 3TB drive and assigned it to the same slot. Then I started the array which automatically invoked a parity which I assume was rebuilding the data from the old 1TB drive onto the new 3TB drive. After that process completed (a few hours), the new drive still shows up as unmountable. I thought that was the correct procedure for replacing a smaller drive with a larger one in the same slot!

Hi all, I was running low on space so I picked up a new 3TB drive and decided to replace it with an existing 1TB drive in the array (disk 3). I cleanly stopped the array and shut the server down. I physically removed the old 1TB drive and installed the new 3TB drive. Once the server booted up I went ahead and added the new drive to the same slot as the old drive and started the array. Once the array started it started to perform a parity rebuild but I also happened to notice that it was telling me I should format this new drive. I ignored this and waited for the parity build to finish which took several hours. I figured after the parity rebuild it would then recover the old data from the 1TB drive and restore it to this new 3TB drive and at the same time I would now have an extra 2TB of space. But now that the parity rebuild is complete the drive is still showing up as unmountable and it still wants me to format this new drive. Why is this happening and what should I do now? I don't want to format it cause I assume I will lose all the data and the parity disk will also be overwritten as well. I still have the old 1TB drive with the data still on it in case I need to reinstall it. What is the correct procedure for replacing as existing smaller drive with a larger drive in the same slot? Old array layout: Parity: 3TB Disk 1: 3TB Disk 2: 3TB Disk 3: 1TB <-- this is the disk that I intended to replace with a new 3TB disk Disk 4: 3TB

So after I hard booted the server the data drive in question that was not being recognized showed a red status indicator. I had to remove and add the drive to the array again and now it's rebuilding it. SMART test passed successfully on the drive, I'm still not certain if my problems are hardware related or software!!! I'm going to check the server again in 24 hours and see if these issues resurface. If they do I will capture the syslog and post it here to see if anyone can see any issues.

Hi all, about two weeks ago I built myself a new Server running unRAID v5.0-rc16c. I'm having an issue where every 24 hours unRAID doesn't recognize one or two of my hard disks. What I notice is that on the main page the hard drive in question hasn't spun down and there are unusually number of high read/writes on this particular disk (but no errors). This is usually the first tell-tale sign that unRAID is no longer able to communicate with this disk. I then try to browse to this disk using a client PC and sure enough it times out. So I then stop the array from the main page then it indicates that this particular disk cannot be found. Next I reboot the server from the webUI and typically the server doesn't come back online on it's own, I even start a contiguous ping from a Windows PC but the server never replies. At this point I know that the server is hung so I have no choice but to go down to the basement and hardboot it. I run my server headless so I may have to attach a monitor to it so that I can see any console messages that appear. I'm not certain at this point if the server is getting hung after the reboot process was initiated from WebUI or if it's getting stuck on POST. The server always comes back online after a hardboot and everything works fine for approx another 24 hours until the same symptoms happen again. At this point I'm not sure if I have hardware issues on my hand or if it has anything to do with the unRAID OS? Has anyone experienced anything like this? My server consists of: ASRock H77 Pro4/MVP MB, Celeron G540 CPU, 4GB RAM, 3 x Seagate Barracuda 7200.14 ST3000DM001 3TB 7200 RPM Drives (1 parity, 2 drives), CORSAIR CX600M PS.

In my instance none of the pages were responding. I was able to stop emhttp from telnet and when I attempted to start it again I would get an error message. I had no other choice but to stop the array, unmount the disks and reboot from my telnet session.

Yes, I am running Simple Features with 4GB RAM.

Thanks, that helped. Found out that emhttp was hung on my server... after reading some other posts it seems that dir cache could be the culprit. I disabled dir cache and will see if it remains stable over the next few days.