will25u said:
Going into this, I was familiar with Linux by name only. Boy did I get a wake up call. I have been using PCs since WIN3.1 so I am familiar with DOS. But Linux(Raspbian) is a totally different beast. I am catching on though.
Throw away the mouse and learn the command line. It is a different world but it is also a powerful and elegant way of getting things done. It does take some time to master.
Quote:
As of last night, I fully have everything up an running. SAB, Sonarr, Radarr, Plex, PiHole, and shared out my two HDDs. Running all that and with Sab downloading a file, I am hitting about ~65% Memory Usage, and my load sits ~2.5. Now tell me if I am reading the load right? I should be good on the load since < 4 (Load 4 / 4 cores) should be OK? I know you don't want to run flat out at 4 or more on the load, correct? But 2.5 should be OK?
If you are sitting at 2.5 while idle I might be a little concerned. There are some big differences between an ARM architecture vs a modern Intel PC. An Intel PC with a quad core processor would give you 8 virtual 32 bit cores. The Pi memory speed is 1/4 as fast, you have a USB 2.0 interface to your disk, and a 100mb network interface. Those load numbers basically represent wait states or threads waiting to access memory, disk, network...etc. That could be a problem when you basically try to turn a Pi into a server...it's I/O interfaces are too slow.
As for memory, that is hard to quantify on linux because the kernel will run large caches in memory (even when idle) that will be quickly disposed when it needs it. Raspbian doesn't use a swap space either which is good and bad. If the kernel has to free memory that would normally be swapped out to disk then it becomes a double whammy and the system could really slow to a crawl or even crash. But I think the I/O is where your real bottleneck will be felt.
Quote:
I am using this as my external USB HDD enclosure. ORICO 5 bay All I did was share the two HDD that I have in there now. Which I shared SAMBA and my Windows boxes can see correctly. What is the disk corruption you are talking about(Like I said, new to linux)?
First of all, I want to state that I hate Samba, it is a necessary evil perpetrated by MS's internal policies of basically not playing well with others. It is a perfect example of MS SW bloat and, it seems to me, I spend more time tweaking Samba than anything else that just simply works out of the box.
You should really test that functionality by doing multiple simultaneous transfers of large files. Maybe you get lucky and it just works. Samba likes to utilize jumbo network frames and it depends on the network interface drivers as to how well that will work well on a Pi. But again, I/O speed could become a bottleneck.
IMHO, file sharing may be too much for the PI. A much more robust solution would be to build or buy a dedicated NAS and mount whatever files the Pi needs using NFS. NFS is the native *NIX network file system and it's both fast and lightweight compared to Samba.
My question about disk corruption was in reference to JBOD. I am not familiar with that but I read a little about it and it sounds a lot like LVM (Logical Volume Management). With LVM you create one file system that can span multiple disks of various sizes. If one of those disks becomes corrupted however, you lose the entire file system,
similar to losing a HDD with RAID 0. That is only a concern if you are worried about file integrity. If you have a robust backup solution then that may not be a concern.
Quote:
I usually only SSH into the box, hardly ever use the GUI, which I think I could turn off? And configure/use all the apps through another PC.
I would dump the GUI, X windows has always been a memory pig.
