Jump to content

So small question about a NAS I am thinking of building (After losing a action for a 8 core 16 thread server... ;-; ).

 

Would a Pentium (G4500 or G4400) and 4gb's of ram be able to look after 2 4TB WD Red HDD in raid 1?

 

Wow this was old as heck, Need to update this signature!
Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/
Share on other sites

Link to post
Share on other sites

Just now, sunil6512 said:

My NAS is running 8TB raid 0 on an Intel atom CPU and 4GB ram just fine. If you want to run a Plex server on it then get a better CPU.

Don't know what a Plex Server is :/

I was just gona get unraid and pray to god I get it right first time.

Wow this was old as heck, Need to update this signature!
Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7536368
Share on other sites

Link to post
Share on other sites

Just now, SerialAceTU1 said:

Generally NASes require less powerful processors and less RAM than a consumer-oriented computer.

Also depends on how many HDDs you have in the NAS

 

 

 

 

I will be adding more hard drives after a while. Was thinking about 100 Terabytes or so... Na jk might go to like 16TB (4x4 HDDS in raid 1)

Wow this was old as heck, Need to update this signature!
Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7536425
Share on other sites

Link to post
Share on other sites

13 hours ago, Marshall212 said:

I will be adding more hard drives after a while. Was thinking about 100 Terabytes or so... Na jk might go to like 16TB (4x4 HDDS in raid 1)

RAID1 is mirror. If you have 4 x 4TB drives you will have 4TB (3.6TB formatted) space with 3 hot-spare drives - meaning you can lose up to 3 drives

If you run a RAID1+0 then you'll have a mirrored stripe giving you 8TB (7.2TB formatted) space - and will give you 1 hot-spare drive on each stripe meaning you can lose 2 of the *right* drives

The most popular for 4 disks would be a RAID5, giving you 12TB (10.9TB formatted) space, with 1 parity drive - meaning you can lose 1 drive, replace it and the array will rebuild from parity across the remaining drives.

Spoiler

Desktop: Ryzen9 5950X | ASUS ROG Crosshair VIII Hero (Wifi) | EVGA RTX 3080Ti FTW3 | 32GB (2x16GB) Corsair Dominator Platinum RGB Pro 3600Mhz | EKWB EK-AIO 360D-RGB | EKWB EK-Vardar RGB Fans | 1TB Samsung 980 Pro, 4TB Samsung 980 Pro | Corsair 5000D Airflow | Corsair HX850 Platinum PSU | Asus ROG 42" OLED PG42UQ + LG 32" 32GK850G Monitor | Roccat Vulcan TKL Pro Keyboard | Logitech G Pro X Superlight  | MicroLab Solo 7C Speakers | Audio-Technica ATH-M50xBT2 LE Headphones | TC-Helicon GoXLR | Audio-Technica AT2035 | LTT Desk Mat | XBOX-X Controller | Windows 11 Pro

 

Spoiler

Server: Fractal Design Define R6 | Ryzen 3950x | ASRock X570 Taichi | Asus RTX 4060 Dual OC | 64GB (4x16GB) Corsair Vengeance LPX 3000Mhz | Corsair RM850v2 PSU | Fractal S36 Triple AIO + 4 Additional Venturi 120mm Fans | 8 x 20TB Seagate Exos X22 | 4 x 16TB Seagate Exos X18 | 3 x 2TB Samsung 970 Evo Plus NVMe | LSI 9211-8i HBA

 

Spoiler

NAS: Innovision 4U 24-bay chassis (12GB MiniHD SGIO Backplane) | Intel Core i9-10980xe | EVGA X299 FTW-K | EVGA RTX 2080Ti Super FTW3 | 128GB (8x16GB) Corsair Vengeance LPX 3200Mhz | DEEPCOOL PN1000M PSU| Noctua NH-D12L Chromax Black | 16 x 16TB Seagate Exos X18 | 2 x 2TB Samsung 990 Pro | 2 x 2TB Intel U.2 P4510 | LSI 9305-24i HBA

 

Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7539194
Share on other sites

Link to post
Share on other sites

7 hours ago, Jarsky said:

RAID1 is mirror. If you have 4 x 4TB drives you will have 4TB (3.6TB formatted) space with 3 hot-spare drives - meaning you can lose up to 3 drives

If you run a RAID1+0 then you'll have a mirrored stripe giving you 8TB (7.2TB formatted) space - and will give you 1 hot-spare drive on each stripe meaning you can lose 2 of the *right* drives

The most popular for 4 disks would be a RAID5, giving you 12TB (10.9TB formatted) space, with 1 parity drive - meaning you can lose 1 drive, replace it and the array will rebuild from parity across the remaining drives.

While you are generally correct, you are using the term "hot-spare" incorrectly. 

 

A hot spare drive or hot standby drive is powered and connected to the array, but does not hold any data. If the controller detects a drive failure, it immediately switches from the failed drive to the hot spare and begins an array rebuild.

Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7541048
Share on other sites

Link to post
Share on other sites

Well yeah, I was using it in a term that makes sense for a fellow kiwi  :P

Spoiler

Desktop: Ryzen9 5950X | ASUS ROG Crosshair VIII Hero (Wifi) | EVGA RTX 3080Ti FTW3 | 32GB (2x16GB) Corsair Dominator Platinum RGB Pro 3600Mhz | EKWB EK-AIO 360D-RGB | EKWB EK-Vardar RGB Fans | 1TB Samsung 980 Pro, 4TB Samsung 980 Pro | Corsair 5000D Airflow | Corsair HX850 Platinum PSU | Asus ROG 42" OLED PG42UQ + LG 32" 32GK850G Monitor | Roccat Vulcan TKL Pro Keyboard | Logitech G Pro X Superlight  | MicroLab Solo 7C Speakers | Audio-Technica ATH-M50xBT2 LE Headphones | TC-Helicon GoXLR | Audio-Technica AT2035 | LTT Desk Mat | XBOX-X Controller | Windows 11 Pro

 

Spoiler

Server: Fractal Design Define R6 | Ryzen 3950x | ASRock X570 Taichi | Asus RTX 4060 Dual OC | 64GB (4x16GB) Corsair Vengeance LPX 3000Mhz | Corsair RM850v2 PSU | Fractal S36 Triple AIO + 4 Additional Venturi 120mm Fans | 8 x 20TB Seagate Exos X22 | 4 x 16TB Seagate Exos X18 | 3 x 2TB Samsung 970 Evo Plus NVMe | LSI 9211-8i HBA

 

Spoiler

NAS: Innovision 4U 24-bay chassis (12GB MiniHD SGIO Backplane) | Intel Core i9-10980xe | EVGA X299 FTW-K | EVGA RTX 2080Ti Super FTW3 | 128GB (8x16GB) Corsair Vengeance LPX 3200Mhz | DEEPCOOL PN1000M PSU| Noctua NH-D12L Chromax Black | 16 x 16TB Seagate Exos X18 | 2 x 2TB Samsung 990 Pro | 2 x 2TB Intel U.2 P4510 | LSI 9305-24i HBA

 

Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7541082
Share on other sites

Link to post
Share on other sites

15 hours ago, Jarsky said:

*snip*

 

6 hours ago, beavo451 said:

*snip*

Yea I'm not expert on raids so you kinda lost me.

Lets see what Google says because what you said just bounced off me like a tennis ball...

 

EDIT: (Talking about Raid 5) So what I see is that the drives have a partial copy each other? like raid 0? When one drive fails the other 3 drives can rebuild the information to a new drive but its also acts like raid 1 because all 4 drives can have the same info. Allowing Read and Write to be quick and simple... Yea if I got that wrong there holy crap I need to do more research on RAID...

Wow this was old as heck, Need to update this signature!
Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7544480
Share on other sites

Link to post
Share on other sites

1 hour ago, Marshall212 said:

 

Yea I'm not expert on raids so you kinda lost me.

Lets see what Google says because what you said just bounced off me like a tennis ball...

 

EDIT: (Talking about Raid 5) So what I see is that the drives have a partial copy each other? like raid 0? When one drive fails the other 3 drives can rebuild the information to a new drive but its also acts like raid 1 because all 4 drives can have the same info. Allowing Read and Write to be quick and simple... Yea if I got that wrong there holy crap I need to do more research on RAID...

Ok, I will make this very basic and simplified with analogies.

 

Firstly, how data is stored:

 

Normally, data is stored in "blocks". So, a file is made up of bits (and subsequently bytes) of data. This data is grouped into blocks to be stored on media (like a hard drive).

 

So, think of data like sand. You build a sand castle and you want to store that sand castle (saving a file). You take that sand castle (a file), break it down and put it in a bunch of little, tupperware containers (blocks), and you put the containers in your closet (hard drive). If you want to look/play/work (opening the file) with the sand castle (file), you take the containers (blocks) out of the closet (hard drive), and reassemble the sand into a sand castle.

 

Secondly, what is the point of RAID?

 

RAID protects against drive failure so that you don't loose all your information (except for RAID 0). So, say your closet (hard drive) catches on fire and burns down. All the stuff or information in it is destroyed.

 

Thirdly, how does RAID work?

 

So using our sand and sand castle analogy...

 

RAID 0 - Stripes data across all member disks. DOES NOT PROTECT AGAINST DRIVE FAILURE! RAID 0 is normally done to increase performance.

So say you have two closets (two hard drives). You could fill one closet up with stuff until it is full and then use your second closet. Or you can split each container of sand in 2 and put half of a container in each closet at the same time. So, if one closet goes up in flames, you only have a bunch of half containers.

 

RAID 1 - Mirrors data. You have to have an even number of disks for RAID 1. Can withstand (total number of drives - 1) disk failure(s).

Take those same two closets. You put your containers of sand into one closet. At the same time, you magically create an exact copy of each container and put it into the second closet. So, if one closet goes up in flames, you still have one closet of stuff. When you replace the burned up closet (failed hard drive), you automatically start copying each container and putting it into the new closet (rebuild). So, if you have 5 closets, those 5 closets will have exactly the same contents. And because they are all exactly the same, 4 of the closets can go up in flames without data loss.

 

RAID 5 - Data striping + parity block. Requires at least 3 drives. Can withstand 1 drive failure regardless of the number of drives.

So, now you have three closets. Think of the RAID 0 above with two disks. The containers are stored in two closets just like the two disk RAID 0 example above. Now you look at each container of sand and create a sort of blueprint if your will (partiy block. Note: this is not what exactly happens, but for the sake of understanding and the analogy it works). You store this blueprint in the third closet. For each container of sand, you create a blueprint for that container. The blueprint is stored in the third closet. But, for every data block, the location of the blueprint is rotated to another closet. So when one closet goes up in flames, you can calculate what data is missing and recreate the missing data when you replace the failed closet.

 

RAID 6 - Data striping + parity block + another parity block. Requires at least 4 drives. Can withstand 2 drive failures regardless of the number of drives.

Same as RAID 5 as above, but now you are making 2 "blueprints" that are stored on separate drives.

 

Hot Spares:

 

Okay, so your data is protected against drive failure. But, what happens when a drive actually fails? The array rebuilds itself when the failed drive is replaced by the operator. Of course, this takes time. RAID 1 has to recopy the data. RAID 5 and RAID 6 has to recalculate the parity blocks (redraw the blueprints). How much time this takes depends on the size of the drives and the amount of data. During this rebuild time, the performance of the array is degraded and is vulnerable to another disk failure. Say you have a disk failure in a RAID 5. You replace the failed drive and the RAID starts a rebuild. If another drive fails during the rebuild, data is lost because there is not enough information to recreate what was stored. The longer an array is in this degraded/rebuilding stage, the more vulnerable to another disk failure and data loss it becomes.

 

A disk failure can happen at anytime. So if you are running a business and a disk fails on a Friday evening right after everybody leaves, the disk failure won't be discovered until Monday morning if you don't have anybody monitoring it. A hot spare disk is a disk that is connected to the system, but is not an active drive. So when the RAID controller detects a failed disk, it switches to the hot spare disk (as if a person physically replaced the failed disk immediately) and rebuilds the array. Instead of a vulnerability time of the weekend + rebuild time, you just have the rebuild time.

Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7545126
Share on other sites

Link to post
Share on other sites

I have a small unraid server with a i3-550 and 4GB ram (with 6 SATA ports), so your spec would be fine.

If you just use it for raid, it will run on 2GB ram easily. I run a docker with zoneminder recording my security cam, a print redirector to my usb printer and sometimes a Server 2016 test VM in 2GB of ram on top of that, because unRaid can host VM's.

 

For storage I use 2x 3TB drives, giving 3TB storage. If I add one more 3TB, i would have 6TB storage. unRaid uses 1 parity drive, and if any 1 drive fails you don't loose data. The more drives you use, the higher the percentage of the storage is used for storage. Its very suitable for home use and only $59US (trial free for a month).

Even better, if you have 4x 4TB disks, you have 1x parity, 3x data which is 12TB of storage. If you were unlucky enough that both the parity and one data disk failed at the same time, the two remaining disks will have valid files remaining - unRaid does not stripe or split the files across disks to improve performance.

 

 

Edited by Rob_LC
Link to comment
https://linustechtips.com/topic/575900-cpu-and-ram-for-nas/#findComment-7547352
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×