moejama

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

moejama's Achievements

Noob

Noob (1/14)

1

Reputation

  1. We should have an easy way to track Power On Hours/Years of RunTime from the Main display. This way you're more aware of how old each drive is in the array more or less at all times. So like the YEARS runtime right there on the Array/Pool Devices screen for each drive like you have for File System or Temp is all I mean. It would just be really cool to see years run time right there on each drive. That should be very easy, the data is there and the main display has plenty of space and I think it's such relevant info to the way ppl use Unraid that it makes sense to be integrated into the Main screen for all the devices. The main factor for lifespan for most storage is power on time, so it's just good info to know at a glance. Personally, I mostly only use the Main display, so also the Health monitors would work better moved to the Main display also. I might make sense to make the Main display a bit more customizable in the long run since it a lot of underused/spread out space. Things like health and Power On Years would be obviously useful, but there's probably room for more and you may as well have more stats on the Main screen or have something like the Array Widget that offers more stats at a glance. Array widget is nice, but it doesn't have terrabyte numbers and it's more compact and just not as useful as the Main screen. I'd rather have more data at glance than Dashboard widgets really. I guess the alternative is make the Dashboard widgets or whatever you call them a lot more customizable, but personally I'd rather just have that info on the main device screen because it seems integral to large array management. Thanks for listening!
  2. I voted snapshots though I must say basic definitions of the features would have helped. The number one improvement everyone should still be asking for is a file explorer than isn't a half ass version of Krusader or Dolphin. It doesn't make sense this far into the project to not have made a good solid GUI based file explorer. Having FOLDER based version is probably all most people need. It's a server mostly for large cheap storage pools. You want features for data management, exploring data, observing data use, monitoring data changes. You want features for backup and file syncing all built in and if not robust at the very least fairly seamless and fool proof. Snapshot makes sense, expanding arrays/drives makes sense for SOME, but probably less ppl than anything like Version. The other BIG weakness of unraid is file sharing to insecure windows desktops. I think building basic client folder syncing in makes the most sense, but it all needs a well polished UI. I didn't buy unraid because I wanted to drop to command line or use Krusader. I bought it as an alternative to getting balls deep in Linux apps, command and scripts because that all takes TIME I don't want to spend. That being the case when it comes time to share a file my natural response is to GET ER DONE and that means a public share or simple SMB password. That's ok, but it could be a lot better in this day and age and it could save untold bits of data from malicious corruption via those super insecure network shares, which are mostly not being used in a direct access fashion anyway. For all the people that just want to put and pull files from Unraid and browse and delete files from shares it makes good logistical sense as a product and consider the likely customer base to build that feature it. OR just look at the threads as to what questions come up the most and add features so the problems don't exist. ;) That's the easy way to do things. Solve the most common problems and call it progress, chances are you've done more good that way than experimental features which benefit small factions of users. NONE of those features seem like things mainstream users are likely to need other than simple easy to use versioning... if that's what snapshot would turn out to mean.
  3. Logging should be improved, there is no reason for logs to simply be deleted because they are in ram. It doesn't matter if you hard crash and can't get that part of the log, at least knowing something can be helpful and having the sever just delete X days of logs because RAM doesn't make the slightest bit of sense. Logs aren't ONLY for crashes anyway, they should be automatically preserved like on pretty much every other server on the planet. I'm kind of amazed nobody bothered to make the logs persistent all these years later. If you build a windows or linux server, you logs don't just auto-delete, so I expect MOST people are not happy to see that happen and often surprised. This is also a very very easy thing to fix and I'm sure would eliminate X amount of posts asking WHERE DID MY LOGS GO per year. I don't have to diagnose Unraid much, but when I do I'd like my logs to not be wiped out by something as simple as a reboot. That is not necessary, not cool, not right, not proper!
  4. I migrated from a Windows 10 server to Unraid 6 back in April. Initial setup wasn't bad, though moving a large library over efficiently and safely did require me to figure out some paths and remember some Linux command line commands which I don't use much. My server hard is just consumer and ASRock - B75M R2.0, Xeon® CPU E3-1230 V2 @ 3.30GHz, 8 Gigs Ram, some passive Geforce video card since it don't have onboard video with the Xeon. This is all just stuff I had laying around. The mobo has like 8 SATA ports so there is no SATA expansion and I think clearly spending more on bigger drives is the best way to deal with that as well as future proofing yourself and just making your life easier. My drives are 5 WD REDs and two old Samsung and WD Green 2 gigs that I threw in for fun, because hey I have parity. I don't have a big need for VMs, so that's more than enough ram for my dockers and file serving needs. If I start using VMs more I will need more ram or even a mobo/platform upgrade. Unfortunately, for me, I was migrating right at a time when Plex was having issues with transcoding inside a docker or something, so that actually wound up taking more time troubleshooting and than the entire rest of the migration project combined. That probably wound up being 30+ hours of troubleshooting because of how the problem cropped up right in the middle of transition so I was not obvious like most problems. I had some problems with the combination of PLEX's transcoding on the cache drive and SabNZB really lagging the server during post processing. I moved Plex transcoding off the cache and just gave it a direct drive assignment, like this /mnt/disk6/transcode/. I also switched the NzbGet which simply points to downloads with cache set to preferred. My lan transfer rates range from 45-120 MB/s depending on what drive and SATA ports I'm pulling from. That's about as good as I can expect without high end hardware. I'm running dockers for Plex, rtorrent connected to VPN with proxify routing Couchpotato and Sonarr as well as working as my home proxy server works great. I don't use the torrent side much, but it works great as a proxiy for my VPN. I used the LinuxServer dockers for most stuff and Binhex for rtorrent. It took some time to figure out that's the easy way to do it, but once I did it only took a couple minutes to setup. It took many hours however, to figure out that was the way to easily get VPN setup and solve any routing complexities. I occasionally use Krusader to manage some content manually, but I don't like it much. That bring up one of the bigger weaknesses of Unraid when it comes to easy management, no built in GUI based file management. I think that would also be nice during migration from one file system to another. I still have some occasional permissions problems where a file will require me to run the permissions fix script in order to my SMB user permissions to allow me to move/delete it. I didn't preclear my drives, I was in a rush and I'm a rebel! Beyond the initial setup and Plex transcoding issue it's been smooth sailing. I'm at 113 days uptime with zero reported errors. The response to the security issues in the general Linux community has been fast. The updates have been painless. Autoupdating dockers and plugins have caused no problems. rtorrrents VPN proxify setup stays connected and working great, so I'm not looking like a endpoint to a bunch of known questionable endpoints reoccurring at predictable intervals anymore. That's nice The interesting part is I'm running the exactly the same hardware that Windows 10 was unstable on, but I also did a full rebuild to a new case (using the same hardware). Perhaps I made something stable in the process of re-assembly or the additional cooling helped a lot, or maybe Windows + Drive Pool just wasn't as stable. I was going to buy a new mobo, but I decided to try a Linux solution to see if that was the problem. I would like a better visual based file explorer that is more fit to the job of managing Unraid because as it stands I'm managing files using SMB. Even web simple based management would be more secure than that because it wouldn't involve cross platform permissions. A well targeted malware might exploit Unraid's reliance on SMB. Considering the power of the Unraid web interface. It's safe to say if someone gets into the web interface, they can wipe you out, so.. I think I would like a web based file explorer that lets you move/delete/rename/maybe change permissions and other basic stuff specifically for Unraid. I'm happy with my investment though. It has made my existing hardware significantly more stable and reduced management time. I could have set this up as a linux distro with dockers, but I prefer the web based nature for the sake of management and a more unified purpose built package. Plus I didn't have to spend weeks testing various drive pool configurations and potentially put my library at greater risk in the process since I don't have a spare server with 15+ TB of space just sitting around. If your time is worth money and you need a file server/appliance that also requires CPU power for transcoding or VMs. I would say Unraid is a pretty solid option. It's proven quite stable on hardware that I didn't even that was all that stable. Performance is consistent. Maintenance is very easy and the level of compartmentalization means it's not only easier to backup and restore, it's simply more resistant to catastrophic corruption. Less monolithic kernels = less change of massive failure, imo. Thanks for the awesome product Unraid Team!
  5. You probably want to use the Appdata Cleanup Plugin, but may also want to go ahead install Dolphin from the Community App plugin (or krusader but it's slightly more complicated) and that will setup a docker that gives you a GUI based file manager via a separate web interface that pops up (hint: everything you care about is mostly under /mnt/user and /mnt/cache, including all your shares). You can also telnet, SSH in or simply install and use the command line tool at the server or the Command Line plugin also located in Community apps, but of course you will have to learn some command line to do that and generally that's something you will have to do with Unraid eventually. If you have not set a root password then you can login as root from the command line or directly from the server just by typing in the username root. You can set a root password in the console by typing passwd when logged in as root and don't forget that password because the webgui will now require it. Appdata is located under /mnt/user/appdata and/or /mnt/cache/appdata if you have a cache drive. Common commands needed are cd for change directory, ls for list directory and 'm -rf to remove an entire folder and contents or just a file, don't point that the wrong folder Also, in Unraid you always login as username root In command line you would type cd /mnt/user/appdata <enter> ls <enter> rm -rf foldername <enter> you can also cd into any directory you can see using the ls command. so you could do: cd mnt cd user cd appdata if you like the scenic route you can go back using cd .. you can use cd / to go to your root or 'C: directory' so you can poke around the file system like that and explore some with those commands Most everything important is located under /mnt/user or /mnt/cache. If you find a docker can't read those, it's because it's not mapped right. In this case though you might considering using the Cleanup Appdata cleanup plugin tool which may do what you want faster and safer.
  6. Since Unraid is based off Linux it helps a lot if you're already a Linux pro or at least have some Linux experience. You have logs to read, that's the key to rapid troubleshooting. As for learning Unraid, master using the forums so you can get the relevant info rapidly instead of hunting and pecking for solutions via trial and error. For new users I would recommend coming up with a goal you want to accomplish with Unraid. Maybe just a simple backup server or maybe a full blown Plex/VM monster. Present your goals to community and let them provide you with a list of apps and perhaps hardware that will fast track you to that goal. You can trial and error your way through it, but you are likely to take 3 times longe , spend more money in the long run, have an inferior setup and wind up asking questions on workarounds for a setup that you didn't plan out well first. That's not the new users fault though, that's Limetechs fault for not having better guides for new users. They probably just like all the attention I HAS FRANDS I think Limetech should just make common roles and the initial dockers/file system setup could be entirely automated. The Plex Downloader role, for instance, could install know working combinations of apps like Plex/Nzbget/DelugeVPN and so on and the new users would all wind up with the same file structures which would make support down the road far easier for everyone. The uses of Unraid aren't that diverse I suspect and really the app store is a lot of copies of the same dockers done slightly differently. That only helps support the idea that most users are using the same apps and pre-configured roles would work perfectly to turn Unraid into a true appliance like solution. As it stands the setup complexity and the fact some dockers don't really work as well as others, it's hard for new user to just know which direction to go. The best you can do on your own is just download the apps with the most stars and hope for the best, but if you ask and get advice first your life will be a lot easier and you setup will probably be more flexible and perform better for what you want it to do, as well as potentially cost less or at least be the right hardware for the job.
  7. Sweet! I had no idea I could route other apps through the built in VPNs of the dockers. I installed DelugeVPN and set Sonarr and Couchpotato to point to locahost:8118 using their WebGUI. That seems to be working in the sense that they can still grab files and pass to Nzbget though I can't really confirm they are going through VPN because I'm too newb at Linux. A couple questions: 1) How would I get Nzbget or jacket through Privoxy. I don't see any proxy setting field? 2) Does Deluge require the proxy settings to the Privoxy or is that built into the VPN container? 3) If the VPN connection drops will apps routed through Privoxy just timeout or will they failover to normal non VPN operation? 4) Is there anyway to check that the traffic is running through VPN or do I just check the log and assume it's working? Thanks again, that saved me tons of time. Here a bit of the log from the DelugeVPN docker. I think it's saying its routing traffic through 172.17.0.9. Is that correct? 2017-05-10 09:07:30,295 DEBG 'start-script' stdout output:default via 172.17.0.1 dev eth0172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.9192.168.1.0/24 via 172.17.0.1 dev eth02017-05-10 09:07:30,295 DEBG 'start-script' stdout output:--------------------2017-05-10 09:07:30,299 DEBG 'start-script' stdout output:[info] iptable_mangle support detected, adding fwmark for tables2017-05-10 09:07:30,314 DEBG 'start-script' stdout output:[info] Docker network defined as 172.17.0.0/162017-05-10 09:07:30,355 DEBG 'start-script' stdout output:[info] iptables defined as follows...--------------------2017-05-10 09:07:30,356 DEBG 'start-script' stdout output:-P INPUT DROP-P FORWARD ACCEPT-P OUTPUT DROP-A INPUT -i tun0 -j ACCEPT-A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT-A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT-A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT-A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT-A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT-A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT-A INPUT -p udp -m udp --sport 53 -j ACCEPT-A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT-A INPUT -i lo -j ACCEPT-A OUTPUT -o tun0 -j ACCEPT-A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT-A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT-A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT-A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT-A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT-A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT-A OUTPUT -p udp -m udp --dport 53 -j ACCEPT-A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT-A OUTPUT -o lo -j ACCEPT
  8. This is my first go at Unraid. I've managed to convert most of my Windows Plex/Sonarr/Couchpotato/Nzbget/rutorrent functionality to Unraid, but I'm still lacking a reasonably easy VPN solution. I'm also working full time and moving to Unraid has taken a lot of hours of work and I'm down to 6 days. Previously I just run PIA VPN client on my Windows install and it was as simple as running the software client and setting it to startup and autoconnect. The goal of VPN is have VPN on all the indexer traffic. I have no need to access Unraid from outside my network. I've read several threads on OpenVPN on Unraid and most seem outdated/for older version of Unraid. I'd like someone to at least point me in the current right direction on VPN because on Unraid it seems like the most complicated part of the setup. I want a solution where my local network can still connect to all those wonderful web interfaces and all the Unraid traffic goes through PIA. I've read about the OpenVPN Client Plugin and I have that installed, but I couldn't find any instructions on how to set it up. I've read about using pfsense and routing all Unraid traffic through that, but again, the documentation seems limited/outdated or just a far over engineered solution for what I should need. So far my only working solution is running PIA through my DDWRT router and using Policy Based Routing withing the DDWRT OpenVPN client to make it only route the Unraid IP, which was surprisingly easy to setup and I still can access Unraid just fine from the rest of the network. The problem is my single core 800 mhz router is maxing out around 6 mbps instead of 120 which it should hit. I don't need max WAN bandwidth on the Unraid server, but I need more than 6 mbps and I don't want a bunch of potential lan latency from maxing out the router. To do that I will have to buy something like a WRT1200 for 140 dollars, which would still be underpowered to hit 100 mbps and I still have to buy the Unraid license. My Unraid experiment is getting a bit expensive. On the other hand a new router wouldn't be the worst thing since my WIFI is kind of weak, but it's not something I had planned to need. Obviously Unraid should just run OpenVPN somehow with all my wonderful Xeon CPU power and the simple policy based routing I used in DDWRT should be very simple to setup via Unraid and far easier to update. I think jumping into Unraid at 6.3 is only a semi ideal time, but a lot of the documentation and perhaps some features are not smoothed out yet. Of course, as a total newbie to Unraid and the community I'm just guessing at that. I'm also considering just building a Linux mergerFS/Snap Raid solution which would give me more flexibility and security, but I like Unraid and if It meets my needs and isn't too much work I'm willing to buy it. Right now with my FCC run by crazy people who think the ISP service I PAY for should have the same 'rights' to spy on me as Google's free data mining fueled services really makes me require VPN. When you consider dockers vs VPN, I think VPN is more important than app compartmentalization. App compartmentalization is mostly a theoretical security measure, we don't really have reports of exploits accomplishing much via our apps, but we have PLENTY of reason to run VPN. ISPs spying and throttling are a known and real problem that impacts hundreds of thousands of people at least, so having an easy to setup VPN option should be a fairly top priority because it's the bigger likely threat. Many people, like me, only have one ISP choice. Is there an easy way to get VPN access to PIA working? I don't need any remote access or VPN access All I want is to hide IP endpoints from the ISP. The encryption isn't even what I'm concerned about. SSL is nice and all, but it does nothing to really hide where all that bandwidth is going. Thanks