Raspberry Pi RAID: the solution for a space-saving and inexpensive NAS?

by Kelvin
Raspberry Pi RAID: the solution for a space-saving and inexpensive NAS?

The Raspberry Pi, a veritable Swiss army knife, is a machine capable of taking on multiple responsibilities. We are looking at the storage case today with the example of a RAID solution which involves both the installation of specific hardware from China and the deployment of a software interface, famous and free OpenMediaVault. Without claiming to be exhaustive, we will try to guide you through the different stages of the process and give you our opinion on its final interest.

Founded by David Braben, Louis Glass, Jack Lang, Pete Lomas, Robert Mullins and Alan Mycroft, the Raspberry Pi foundation recently celebrated its twelfth candle. More important for the simple users than we are, the foundation was especially noticed by marketing a few months ago the Raspberry Pi 4 B, the latest version of its ARM-based single-board nanocomputer as defined by Wikipedia. Thanks to a largely renewed power, more RAM and more efficient inputs / outputs, the Pi 4B raised many hopes with hackers of all stripes. At Clubic, the beast gave us desires for RAID further boosted by the distribution of a kit by AllNet.China.

Raspberry Pi 4 B - Angle


At the heart of our NAS, the Raspberry Pi 4B © Nerces for Clubic

The Raspberry Pi goes to “v4”

As we said in the introduction, the Raspberry Pi 4 Model B has been available for some time. We were also able to offer you a relatively complete test from August 2019, a test that we of course invite you to (re) consult in order to have clearer ideas before going any further . Recall that the Raspberry Pi 4B is the evolution of the basic concept of the Raspberry Pi foundation. A concept holding in a nanocomputer which comes down to a single card. Between the Pi3B + and the Pi4B, the form factor is therefore practically identical. Thus, the motherboard is simply a little bit wider, but the real “visual” differences are more in the connectors and on-board components.

Raspberry Pi 4 Model B Datasheet

  • Processor : Broadcom BCM2711, quad-core 1.5 GHz Cortex-A72 64-bit
  • GPU: Broadcom VideoCore VI 500 MHz
  • RAM: 1 GB, 2 GB or 4 GB of LPDDR4-3200 SDRAM (depending on the model)
  • Network: Gigabit Ethernet and Wi-Fi 802.11b / g / n / ac 2.4 / 5 GHz; Bluetooth 5.0, Bluetooth Low Energy
  • Storage: MicroSD card reader
  • Connections: USB 2.0 (x2), USB 3.0 (x2), Ethernet (RJ45), micro-HDMI (x2), 3.5 mm audio jack, Camera Serial Interface (CSI), Display Serial Interface (DSI) and USB- C (power), General Purpose Input / Output (GPIO) 40 pins
  • Dimensions: “Credit card” format: 88 x 58 x 19 mm, 46 grams
  • Price and availability : already available, at € 39 (equipped with 1 GB) / € 49 (2 GB) / € 59 (4 GB)

At the heart of the Raspberry Pi 4 Model B, there is therefore a Broadcom BCM2711 processor whose name could suggest a decline compared to the BCM2837 which equips the previous generation. In reality, the BCM2711 is distinguished by the presence of four ARM Cortex-A72 cores, much more powerful than the Cortex-A53 of the Pi 3B +. The operating frequency is also improving (+ 100 MHz) at 1.5 GHz. Sufficient “potato” for our Raspberry RAID NAS?

Raspberry RAID without enclosure

Various Raspberry RAID solutions exist. Sometimes it’s a bit “raw”

RAID for network storage

In order to set the scene well, we must now discuss what a RAID solution is and why it is of particular interest in the form of a NAS. The term RAID is an English acronym – Redundant Array of Independant Disks – which means, more or less, “redundant grouping of independent disks”.

There are multiple variants of RAID with significantly different objectives. RAID 0 for example involves splitting data into as many “groups” as there are disks in the RAID 0 stack. The system writes only one group per disk, but does it simultaneously, so we take advantage of much higher speeds than writing all the data on a single disk. On the other hand, as soon as a disk fails, we lose all the data at once: the system is unable to recalculate the missing group or groups from the others still valid.


The three most basic RAID systems organizations seen by LaCie

RAID 1, RAID 5, RAID 6, RAID 10: towards a little security

In contrast to this system, there is RAID 1 which combines two physical hard disks: the data is copied simultaneously on the two units without any user intervention. Imagine that one of the two falls into pass, the system detects it and indicates it so that the replacement can be carried out as soon as possible. This done, the system will – on its own – take care of copying all the data so that the two disks are again identical in content. Here, we therefore favor a certain form of security over performance.

RAID 5 diagram

Parity diagram on a RAID 5 stack © Wikipedia

Halfway there are multiple variants of RAID such as RAID 5, RAID 6 or RAID 10 to name a few. The idea is to offer “the best of both worlds”, but less effective. A RAID 5 stack generally provides better performance than a RAID 1 stack, but is not at the level of a RAID 0 stack. On the other hand, compared to the latter, it provides a certain “protection” of the data. We are resting here on the notion of “parity”. We will not go into details, but there are very good articles on the subject, especially on Wikipedia.

The question of the SIN

Finally, we should mention the question of the SIN, again an English acronym for Network Attached Storage or, in good French, networked storage unit. The purpose of a NAS is to be accessible, on a network, from various client workstations in order to store data for them. It allows centralization of said data and has many “practical” advantages: easier backup, simplified sharing and simultaneous access, lower costs and reduced administration time.

QNAP vs Synology

QNAP and Synology – here opposed by 01net – are two of the leaders of the NAS © 01net

In the case before us today, only some of these benefits come into play. Using a Raspberry Pi 4B to make it a mini-NAS is obviously a financially economical solution given the price of a Raspberry. Another advantage, the extreme compactness of the nanocomputer makes it a particularly compact NAS. Still, such a product should not be able to deliver performance to justify its place in business … To see if it is possible, as we hope to make a NAS “domestically” interesting.

Quad SATA kit datasheet

  • Nature : tower case, Raspberry Pi 4 NAS server
  • Raspberry Pi compatibility: model 4B only
  • RAID support: software, RAID 0/1/5
  • Disk controller: 2x JMicron JMS561
  • Number of ports: 4x SATA, HDD or SSD
  • Maximum capacity: theoretically up to 32 TB
  • Raspberry Pi 4 connection: via GPIO
  • Data transfers: via the 4 USB3.0 ports
  • Ventilation : double, 30 mm (Raspberry Pi) / 40 mm (HDD)
  • Display: OLED screen (IP, charge, storage …)
  • Food : external, via USB-C port (12V / 5A)
  • Dimensions (W / L / H): complete case, 94 x 70 x 173 mm
  • Price and availability : pre-order, 99 €

Sold in spare parts or in bundle called “complete”, the Quad SATA kit is a very compact solution intended to accommodate a Raspberry Pi 4B as well as a maximum of four storage units. It should be noted that technically, nothing prevents from exploiting 3.5 inch discs, but the case as well as the system as a whole are much more thought to accommodate 2.5 inch units, whether HDD or SSD.

Dual / Quad SATA Kit AllNet.China

Sold in spare parts, our Quad SATA kit must first be assembled © AllNet.China

Installation of our RAID solution

If it can be sold as a set presented as “complete”, the Quad SATA kit is actually not quite. First, it obviously does not include the famous Raspberry Pi 4B since it is presented as an accessory in addition to the nanocomputer. You must already go to the cashier and get the Raspberry. Remember that there are three versions of the Pi 4B with the only difference being the amount of on-board RAM. In the case of NAS use, we strongly suggest that you start with the 4 GB version.

Also, don’t forget the keyboard / mouse duo. There, any USB model can do the trick and there is no need to go broke. We even suggest that you only take “troubleshooting” devices, because we will also see how quickly this without this duo will be used for the very first steps of installation / configuration. Finally, don’t forget the HDMI cable – beware the Pi 4B requires micro-HDMI – and a power supply worthy of the name. We have prepared a small insert for this purpose, as things are not as simple as AllNet.China suggests. Finally, we must not forget the inevitable microSD card intended to store the operating system.

The video above illustrates most of the steps required to assemble our small RAID solution. It is pretty well done and, followed step by step, it should allow you to avoid the majority of pitfalls. Things start logically enough with the installation of spacers on the plate which serves as the bottom of the case. Then place the Raspeberry Pi 4B and fix it with the screws provided.

Raspberry RAID mount

Attachment of spacers and Raspberry Pi 4B © Nerces for Clubic

New spacers are to be wedged on the Raspberry: they will serve as an anchor for the heart of the RAID system: the Quad SATA HAT card which will be plugged into the GPIO port of the Raspberry and screwed securely … even if we had to recover two screws out of the four in our reserve: little quack at AllNet.China. Before that, however, you should fix the radiator / fan combo delivered by AllNet.China to keep the Pi 4B cool.

Raspberry RAID mount

Installation of the ventilation of the Pi 4B and the SATA HAT © Nerces card for Clubic

It is interesting to note that said radiator / fan is not powered by the Raspberry Pi. The short cable must actually be connected under the Quad SATA HAT card. This connection should therefore be made before attaching the card to the Pi 4B. It is then possible to set up the Quad SATA HAT: nothing very complicated at this level, just be careful not to force on the pins of the GPIO.

Raspberry RAID mount

Installation of our four SSDs and connection to SATA HAT © Nerces for Clubic

Parallel to this small assembly, it is a question of installing the HDD / SSD by fixing them to the two “walls” of the case. Again, nothing too rocky and AllNet.China delivers all the necessary hardware to install four discs. For the next step, we invite you to take a good look at our photo: the fan / screen card intended to take place at the top of the box must be placed upright. Just put the fan on the side of the HDD / SSD sockets. Second little quirk on the hardware side: we missed two more on our bundle.

Raspberry RAID mount

Final connections for general ventilation and LCD screen © Nerces for Clubic

The last step, connection side, involves the connection of a white cable. The latter is used for nothing less than to power this card “ceiling” of the housing: it is that it takes a little current to turn the fan and provide the energy necessary for the small LCD screen. This done, you can admire the pretty little Raspberry RAID case that you now have in your hands.

Raspberry RAID mount

Screwing and installation of the “external” USB bridge for data transfer. Note the ports a little too deep in the housing: not very practical © Nerces for Clubic

A final step for which we must not hurry. This involves sliding the housing casing. Holes have been arranged so that the connectors of the Pi 4B and the Quad SATA HAT remain available: we slide the casing without moving too much and then, when it touches the metal “basic” plate, we slide it slightly so that the ports are well “in the holes”. Do the opposite and it is the insurance to damage a USB of your Pi 4B … as during our test!

Choice of food

Regulars of the Raspberry Pi will tell you, choosing a power supply for your Pi is not always an easy task … it is even more true in the case of our Rapsberry RAID. Basically, we actually started on the small external brick provided by AllNet.China and officially planned to deliver 45W. Problem, it never wanted to work properly on our guinea pig: the Raspberry Pi 4B systematically displayed the “little flash” so characteristic of under-nourishment.

We had however taken care to retain SSDs rather than HDDs in our system, but even by drastically reducing the number of SSDs (to three then two and even only one), the “little flash” was still in order. In desperation, we used an official Raspberry power supply to verify that the electronics were functional. No problem. On the other hand, this small brick stamped Raspberry is not powerful enough to power even just two SSDs serenely.

From the choice of power brick

On the left the official AllNet.China brick – unusable – and on the right our savior, a very good 60W model signed Anker

We finally set our sights on a brick designed by Anker, a well-known Chinese brand. Many other models should be able to work, but with this one, we were able to power our Raspberry RAID, with its four SSDs. Note however that things will differ depending on the models of SSD and HDD will be more greedy. We therefore suggest that you consult this Wiki page dedicated to the power / consumption of the Quad SATA HAT.

Software: OpenMediaVault and the Linux RAID stack

It is done ! Your small hardware is now assembled and it must be recognized that a NAS of this format, it will impress more than one! Technically, it is possible to associate 2.5 inch hard drive models capable of storing 3 TB of data … and even 8 TB in the case of SSD. You can imagine that the cost of such products is at odds with our objective “low price”.

It is however quite possible to get your hands on units at 50 euros each for a total of 100 euros so if you limit yourself to RAID 1, or even 200 euros for RAID 5. At this price level, there do not think too big, but the prices having dropped, we can find products of 1 TB (HDD) or 250 GB (SSD).

Toshiba L200 1 TB

The Toshiba L200 1 TB offers acceptable performance for a low price © Toshiba

The next step is therefore to set up the software environment and it obviously starts with the operating system of our Raspberry Pi 4B. Our idea is not to limit ourselves to only RAID functions and always have a real little Raspberry perfectly usable for something else. So we set our sights on the Linux distribution specifically designed for the Pi, Raspbian.

You need a microSD card of almost any capacity, but for peace of mind, we suggest a 16 GB model. Here we have several brands of choice, the kind that should not leave you fall at the worst time: the Sandisk Ultra / Extreme or the Samsung EVO Select / Plus are references that have never been lacking. Insert the said card into a USB adapter or card reader and you’re ready to go.

MicroSD Sandisk Ultra / Samsung EVO Select

Two quality microSD cards. Beware of copies that swarm on the Net © Sandisk / Samsung

A suite that requires a visit to the Raspberry Foundation website in order to download the image. There are several possibilities, but you can hardly say that you have made a bad choice for what we have planned: whether you choose NOOBS, the “beginners” version of the distribution, or for Buster, the grind for the “regulars”, you will be “in good hands”. We simply advise you to take the 2.5 GB versions of one or the other: they come with more applications which may be useful to you.

Downloaded, the Raspbian image must be installed on your microSD. Again, there are several choices and if Raspberry has its own fully functional tool – the Raspberry Pi Imager – we are used to using balenaEtcher. In one case as in the other, it is formidable simplicity: we launch the program, we select a “destination” (our microSD) and we choose our image file. On balenaEtcher, click on the “Flash!” »Launches the process.

Raspberry Pi RAID: the solution for a space-saving and inexpensive NAS? 2

A few minutes later, balenaEtcher specifies that its work is finished … You now have a working Raspbian system on your microSD. If you had closed the Raspberry RAID case, you will have to reopen it to insert said microSD: if you took care to take a look at our entire file before acting, you will not have to “go back to your steps ”.

Without an on / off button, turning on the Raspberry RAID requires a simple connection to the mains. If everything is correctly assembled and connected, you should see the various stages of the boot on your screen: the Raspberry Pi, even in its 4B version, not being a powerhouse, this start-up can take a little while … but above all it is only the very first step of our software installation.

Raspbian update

Installation of multiple packages for the Raspbian, just to be “quiet” © Nerces for Clubic

Since the Raspbian image is not updated every four mornings, it seems important to us to start with a complete system update before starting the RAID procedure. By default, the login on Raspbian is ‘Pi’ and the password ‘raspberry’. The system will suggest that you change it quickly, but for the rest of our demo, we will pretend that it hasn’t been done. In the taskbar, on the desktop of Raspbian, you will find a window ‘Terminal’, it is from there that we will make the updates.

Raspbian update

Second step, updating all the packages themselves © Nerces for Clubic

Once the ‘Terminal’ window is open, we invite you to type this

sudo apt update

This command starts the installation of the essential packages for the whole system … Of course, it is important that your Raspberry Pi is connected to the network and, preferably, to Ethernet. We will not come back here to the configuration of said network: by default Raspbian needs a DHCP service to function without hindrance and on the majority of Boxes, such a service is activated as standard.

sudo apt full-upgrade

An essential complement to the previous command, it focuses on the updates currently available for your system. It is generally faster than the previous one, but it remains quite variable. Between one and the other of these commands, you should probably leave 10 to 30 minutes for the Raspberry to install / update everything.

curl -sL https://rock.sh/get-rockpi-sata-hat | sudo -E bash –
sudo reboot

Then, it is important that Raspbian correctly recognizes all the hardware elements that we have added by proceeding with the installation of the Quad SATA HAT and its various components. Things are done quite automatically, but we stay away from plug & play which some of you are used to.

sudo systemctl enable ssh
sudo systemctl start ssh

Still via a ‘Terminal’ window – perhaps after a small reboot of the system – it is now a question of activating SSH. Note that this can also be done via the Raspbian GUI. We are also presenting a screenshot of the window allowing such activation, but since we had started on the use of the ‘Terminal’, we might as well continue.

SSH configuration under Raspbian

The Raspbian graphical interface also allows the activation of SSH © Nerces for Clubic

The advantage of activating SSH is that from now on, you will no longer need to “physically” access your Raspberry RAID. You can normally store it in its small corner and disconnect keyboard / mouse and even the screen. Keep the power supply anyway, otherwise it will be complicated!

The fully operational SSH, you can access your Rapsberry RAID from any machine … for example our PC under Windows. To do this, it is obviously necessary to install an SSH client and if there are many, we have a clear preference for PuTTy, very small, very practical. It is of course available for download on Clubic.

PuTTy - Login screen

Nothing could be easier than connecting via PuTTy © Nerces for Clubic

At launch, PuTTy asks for the IP address of the remote machine you want to access and, this is where the small screen of the Raspberry RAID comes in handy: you just have to read the IP on it … Of course , users who are just a little bit more informed will have had no trouble defining the machine’s IP themselves and / or finding it via DHCP.

From there, everything will be done from the command line from the ‘Terminal’ which is accessed via PuTTy. More secure operating system than Windows, Raspbian – like any Linux – does not systematically give all rights to each user, on the contrary. To avoid many unnecessary manipulations, we therefore suggest that you grant yourself administrator rights during a session and we could have done so before 🙂

sudo -s

Then, we will have to modify a rules file intended to correct a small bug in the software installation previously carried out automatically. It is not very complicated, but it is necessary to follow the procedure step by step so as not to make mistakes. We call the editor and the file to modify directly from the command line above.

nano /lib/udev/rules.d/60-persistent-storage.rules

It is now a question of adding a rule related to the management of the disk controller. To do this, under the entry “Fall back usb_id for USB devices”, you must add and without modifying anything that we offer below. A line that will speak to Linux users and that is enough for the recognition of the controller to be done without a hitch.

# JMicron drive fix
KERNEL == “sd *”, ATTRS {idVendor} == “1058”, ATTRS {idProduct} == “0a10”, SUBSYSTEMS == “usb”, PROGRAM = “/ root / serial.sh% k”, ENV { ID_SERIAL} = “USB-% c”, ENV {ID_SERIAL_SHORT} = “% c”

Finally, the bug correction goes through a final step in three parts. This time it is first to create the file “serial.sh” in the folder root then edit it to add a very precise line and, finally, make it executable. Three steps, again, to be followed scrupulously so as not to run the slightest risk.
File creation and editing

nano /root/serial.sh

Addition of the necessary line

#! / bin / bash
/ sbin / hdparm -I / dev / $ 1 | grep ‘Serial Number’ | awk ‘{print $ 3}’

Make the file executable

chmod + x /root/serial.sh

From there, it is theoretically possible to launch the installation procedure of OpenMediaVault, (OMV) but the software is still a little finicky on Raspbian and we prefer to perform as many steps as possible before going under OMV. This is why we are going to create our RAID stack directly from the ‘Terminal’.

fdisk / dev / sda

The use of FDISK will allow the creation of partitions on each of the disks affected by the RAID. In our example, we have limited ourselves to RAID 1 with two units (nda and bathroom), but the same should be done with the other two units (sdc and sdd) in the case of a RAID 5 array on four disks.
By pressing ‘n’, FDISK creates a new partition. We leave everything by default by pressing ‘enter’ three times (Partition number, First sector and Last sector). Finally, we change the type of partition by pressing ‘t’ at the invitation of FDISK and we enter the velur ’29’ when we are asked for the type of partition. This ’29’ corresponds to a partition of type ‘Linux RAID’.

fdisk / dev / sdb

By pressing ‘w’, you tell FDISK that you want to exit by saving the changes. We can then do the same with the second disc and, possibly the third then the fourth. In our example, we now have two disks (nda and bathroom) suitably prepared to accommodate the creation of a RAID 1 array.

mdadm –create / dev / md0 –level = 1 –raid-devices = 2 / dev / sda1 / dev / sdb1

The MDADM command is precisely the tool allowing the creation of said RAID 1 stack (called md0). You will notice that the indication ‘level = 1’ corresponds to the RAID used: instead of ‘1’, it suffices to put ‘0’ for RAID 0 or ‘5’ for RAID 5. The variable ‘devices = 2 ‘specifies the number of units used knowing that’ / dev / sda1 ‘and’ / dev / sdb1 ‘define their respective paths.

cat / proc / mdstat

At the validation request by MDADM, just press ‘y’ for the creation to be launched. Note that the process can take a long time … especially in the case of a RAID 5 stack on units of 2 or 3 TB each. The CAT command allows you to follow the evolution of this creation phase directly from the ‘Terminal’ window.

umount / dev / md0
mdadm -S / dev / md0

Before starting the installation of OMV, we would like to draw your attention to two commands (above) which may be useful to you in case of problems during the creation of the RAID stack. The first (UMOUNT) is essential for the RAID volume (md0) is removed while the second (MDADM -S) allows the volume to be properly stopped. It is then possible to return to the previous creation steps.

wget -O – https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash

Admit that you hardly believe it anymore, but the above command does allow you to install OMV on your Raspberry RAID. We opted for an installation via a script: there is always the possibility of going through an image, but it is not the preferred solution today. Without any particular difficulty apart from copying the command line, this script has the advantage of being able to be installed on our Raspbian, without worry.

OpenMediaVault installation

A last little installation script and OMV will be fully functional © Nerces for Clubic

As with the system update, there again you have to wait a while until all the elements are first downloaded and then installed on your system. The download will clearly depend on your Internet connection while the installation time is difficult to compress: it is the Raspberry Pi 4B that is working and you have to take your trouble in patience.

After installation, reboot of rigor requested via PuTTy and the restart carried out, it is finally possible to “grab” your web browser to access the OMV interface … as for any QNAP or Synology brand NAS for example. Upon connection, OMV requests a login and password: ‘admin’ and ‘OpenMediaVault’ by default.

OpenMediaVault login

Login and default password to access OpenMediaVault … at the beginning © Nerces for Clubic

Our feedback, some benchmarks

We now approach the last part of our article, before the conclusion. From OpenMediaVault, we actually have to create the file system on our RAID volume (md0). There, several possibilities are available to us from the traditional EXT4 format via ZFS or XFS. You will no doubt find aficionados of one or the other and we will be careful not to judge them.

We opted for XFS which seems – in its latest versions – faster than EXXT4 for example, but to be completely honest, the speed of the file system is probably not a critical variable on our Raspberry RAID: the power of the machine is in any case much more limited than on a more “classic” NAS.

Our goal here is not to make a real test of the OpenMediaVault solution as a RAID platform. OMV is known and recognized by many users, just like FreeNAS for that matter. If it is not perfect, the system works generally well and offers many settings from a graphical interface which is quite clear.

Unsurprisingly, we are far from the functional richness of software such as QNS from QNAP or DSM from Synology, the two leaders in the sector. However, we must emphasize that many modules exist for OMV and that the community is dynamic. Users do not hesitate to put online tutorials well done to guide you in the installation of Plex for example (see the video above).

Adding a share under OpenMediaVault

Ajout d’un partage sous OpenMediaVault et configuration de base © Nerces pour Clubic

OMV dispose de base de toutes les fonctionnalitĂ©s essentielles dans la gestion des utilisateurs et des groupes. Il autorise la dĂ©finition de dossiers partagĂ©s de manière très simple et, bien sĂ»r, il gère prĂ©cisĂ©ment tout ce qui a trait aux quotas. On notera la prĂ©sence de services FTP, NFS, Resync ou SMB / CIFS et surtout l’existence de multiples plugins et d’extras.

Nous prĂ©fĂ©rons nous focaliser sur l’Ă©tude de notre solution Raspberry RAID afin de voir si tout ce que nous avons fait dĂ©bouche sur quelque chose de fonctionnel. Autant ĂŞtre clair, le Raspberry Pi 4B est un bon cran en deçà des performances offertes par les NAS quatre baies d’entrĂ©e de gamme du duo de poids lourds du secteur, QNAP et Synology.

CrystalDiskMark NAS Raspberry RAID 1

CrystalDiskMark met en évidence une certaine faiblesse en écriture © Nerces pour Clubic

Ă€ l’aide de CrystalDiskMark, nous avons ainsi pu mesurer plus ou moins 40 Mo/s. en Ă©criture. Soulignons qu’au moment de ces tests, nous travaillions sur une pile RAID 1, mais que les rĂ©sultats en RAID 5 ont finalement Ă©tĂ© très proches. En copie de fichiers directe depuis un PC sous Windows, les rĂ©sultats sont sensiblement supĂ©rieurs avec une moyenne de 50 Mo/s., mais d’importantes fluctuations ont Ă©tĂ© observĂ©es.

Copie de fichiers NAS Raspberry RAID 1

Faiblesse confirmée lors de la copie de fichiers depuis un PC sous Windows 10 © Nerces pour Clubic

Heureusement, en lecture, le bilan est autrement plus rĂ©jouissant. CrystalDiskMark semblait tendre vers les limites de l’interface Ethernet Gigabit et nos tests de copie directe depuis Windows ont confirmĂ© cette moyenne de 110 Mo/s. en lecture. Au cours de diffĂ©rents tests, nous avons lancĂ© la lecture de plusieurs vidĂ©os depuis notre Raspberry RAID vers un, puis deux clients pendant qu’un troisième Ă©coutait de la musique. Aucun problème particulier Ă  signaler, mais reconnaissons que nous n’avons pas non plus diffusĂ© de vidĂ©os 4K.

Dans les faits, le Raspberry RAID est une machine qui tourne plutĂ´t bien dès lors que l’on souhaite accĂ©der – Ă  un ou deux – aux donnĂ©es qui sont stockĂ©es sur ses disques. En revanche, toutes les phases de copie de fichiers ou d’envoi de donnĂ©es sur le Raspberry RAID sont bien plus laborieuses. Nous avons observĂ© les mĂŞmes limitations dans le cas d’une utilisation « base de donnĂ©es » : l’accès Ă  nos fichiers de travail se fait sans difficultĂ©, la synchronisation d’un vaste dossier plein de textes et autres comptes-rendus est moins agrĂ©able.

Notre Raspberry RAID désossé

Le « Raspberry RAID » selon AllNet.China : intéressant, mais largement perfectible © Nerces pour Clubic

AllNet.China Raspberry RAID : l’avis de Clubic

Sommes nous prĂŞts Ă  remplacer notre NAS Synology par un Raspberry RAID conçu autour de la solution conçue et commercialisĂ©e par AllNet.China ? La rĂ©ponse est actuellement sans appel : c’est non. Si les performances en lecture en font une machine tout Ă  fait convaincante, notre NAS n’est pas qu’une station multimĂ©dia destinĂ©e Ă  hĂ©berger photos souvenirs et films de vacances. Nous avons diverses image-disques rĂ©gulièrement mises Ă  jour et de nombreux documents de travail que nous synchronisons avec plusieurs utilisateurs. LĂ , les performances sont trop faibles pour un usage quotidien, intensif.

Reste que compte tenu de l’espace occupĂ© par le Raspberry RAID, c’est une solution Ă  nulle autre pareil. Nous en avons vu passer des NAS et mĂŞme les plus riquiquis ne peuvent rivaliser avec cette solution Ă  base de « chinoiserie » en provenance d’AllNet.China. Nous avons abouti Ă  un NAS remarquablement discret et compact et, grâce Ă  la gratuitĂ© d’OpenMediaVault, la facture totale reste mesurĂ©e. HĂ©las, le montage et la configuration ne sont pas de tout repos du fait de bugs inacceptables et les problèmes d’alimentation – en utilisant pourtant la brique recommandĂ©e par AllNet.China – nous incitent Ă  une certaine prudence. En attendant l’arrivĂ©e d’une version 2 expurgĂ©e de ces dĂ©fauts « de jeunesse », le principe reste lui, remarquablement sĂ©duisant. Avis aux bidouilleurs.

Raspberry Pi Quad SATA HAT

+ Design sobre et élégant

+ Une solution hyper compacte

+ 4 unités / 32 To de stockage

+ Petit Ă©cran LCD bien pratique

+ DĂ©bits corrects en lecture

+ Ventilation bien étudiée

– Soucis techniques (visserie, ports)

– SĂ©rieux problèmes d’alimentation

– Faibles dĂ©bits en Ă©criture

– Pas exactement plug & play

escort malatya escort bursa escort antalya escort konya mersin escort