doc:appunti:hardware:raspberrypi_nas
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
doc:appunti:hardware:raspberrypi_nas [2021/03/11 10:54] – [Networking] niccolo | doc:appunti:hardware:raspberrypi_nas [2021/03/22 10:34] – [Home Mediacenter and NAS with the Raspberry Pi] niccolo | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Home Mediacenter and NAS with the Raspberry Pi ====== | ====== Home Mediacenter and NAS with the Raspberry Pi ====== | ||
- | This is my recipe to build a mediacenter and NAS box using the Raspberry Pi. This is the list of components: | + | This is my recipe to build a **[[wp> |
+ | |||
+ | * **Raspberry Pi** 4 Model B with 4 Gb RAM. | ||
+ | * 4 Tb **hard disk** Seagate IronWolf 3.5 inches. | ||
+ | * **Suptronics.com X835** USB to SATA adapter, to connect the hard disk. | ||
+ | * Ugreen **USB audio** adapter. | ||
+ | * **Gamepad** USB wireless (SNES-like) used as remote control. | ||
+ | |||
+ | {{.: | ||
+ | |||
+ | {{.: | ||
+ | **WARNING** :!: I cannot recommend this solution at all! It turned out that the Raspberry Pi, when it uses the **USB 3** interface, produces **radio interferences on the 2.4 GHz** band. It is **impossibile to connect to the 2.4 GHz WiFi** access point which is only 5 meters far. It was also **impossible to use a wireless keyboard and mouse**, using one USB dongle which also operates on the 2.4 GHz. To operate a **wireless gamepad** (which also uses an USB dongle on the 2.4 GHz frequencies) I had to distantiate the dongle from the Raspberry Pi using and USB **extension cable of about 0.5 meters**. | ||
+ | |||
+ | Due this **severe problem**, I can suggest this solution only if you will use the **Ethernet** interface or an access point on the **5 Ghz** band. As an alternative to the wireless gamepad or keyboard, you can use the **[[https:// | ||
- | * Raspberry Pi 4. | ||
- | * Seagate IronWolf 3.5 inch Hard disk, 4 Tb. | ||
- | * Suptronics.com X835 exapnsion board to connect SATA drives. | ||
====== Subsystems ====== | ====== Subsystems ====== | ||
Line 11: | Line 21: | ||
* **[[raspberrypi_nas_x835_sata_board]]** | * **[[raspberrypi_nas_x835_sata_board]]** | ||
* **[[raspberrypi_nas_smart_hard_disk]]** | * **[[raspberrypi_nas_smart_hard_disk]]** | ||
+ | * **[[raspberrypi_nas_networking]]** | ||
* **[[raspberrypi_nas_kodi]]** | * **[[raspberrypi_nas_kodi]]** | ||
* **[[raspberrypi_nas_audio]]** | * **[[raspberrypi_nas_audio]]** | ||
- | * **[[raspberrypi_nas_networking]]** | ||
* **[[raspberrypi_nas_mail]]** | * **[[raspberrypi_nas_mail]]** | ||
- | + | * **[[raspberrypi_nas_remote_control]]** | |
- | + | * **[[raspberrypi_nas_case]]** | |
- | ===== Mail system ===== | + | |
- | + | ||
- | I want a working **mail system** on the NAS, mainly because I want to eventually receive error messages from the various subsystems, think e.g. at the **smartd** daemon watching for S.M.A.R.T. hard drive errors... | + | |
- | + | ||
- | In the following examples **pimedianas** is the hostname of my Raspberry Pi Mediacenter NAS. I istalled the **postfix** package and configured it as **satellite system** using a **SMTP relay host**. The relevant settings in **/ | + | |
- | + | ||
- | < | + | |
- | myhostname = pimedianas | + | |
- | mydestination = $myhostname, | + | |
- | relayhost = mail.example.org: | + | |
- | default_transport = smtp | + | |
- | relay_transport = smtp | + | |
- | myorigin = $myhostname | + | |
- | # Rewrite some sender addresses. | + | |
- | sender_canonical_maps = hash:/ | + | |
- | # Relay host requires SASL authentication. | + | |
- | smtp_sasl_auth_enable = yes | + | |
- | smtp_sasl_password_maps = hash:/ | + | |
- | smtp_sasl_mechanism_filter = plain, login | + | |
- | smtp_sasl_security_options = | + | |
- | smtp_tls_security_level = may | + | |
- | </ | + | |
- | + | ||
- | The content of **/ | + | |
- | + | ||
- | < | + | |
- | root | + | |
- | root@pimedianas | + | |
- | root@localhost | + | |
- | root@localhost.localdomain pimedianas@example.org | + | |
- | </ | + | |
- | + | ||
- | Write the proper info about **localhost** in **/ | + | |
- | + | ||
- | < | + | |
- | 127.0.1.1 | + | |
- | </ | + | |
- | + | ||
- | Finally I had to put my **SMTP credentials** required by the relaying server into **/ | + | |
- | + | ||
- | < | + | |
- | mail.example.org pimedianas: | + | |
- | </ | + | |
- | + | ||
- | Last but not least, I redirected all the mail for root to my real email address in **/ | + | |
- | + | ||
- | < | + | |
- | root: | + | |
- | </ | + | |
- | + | ||
- | Remember to compile all the files and restart the service: | + | |
- | + | ||
- | < | + | |
- | postmap / | + | |
- | postmap / | + | |
- | newaliases | + | |
- | systemctl restart postfix.service | + | |
- | </ | + | |
- | + | ||
- | Now all the locally generated mails addressed to **root**, **%%root@pimedianas%%**, | + | |
- | + | ||
- | ===== Kodi ===== | + | |
- | + | ||
- | Installed the packages: | + | |
- | + | ||
- | * **kodi** | + | |
- | * **kodi-bin** - Contains the executable **kodi-standalone**, | + | |
- | * **kodi-peripheral-joystick** - Necessary to add support for the gamepad. | + | |
- | * **kodi-eventclients-kodi-send** - Contains the **kodi-send** tool, used to control Kodi from the command line. | + | |
- | + | ||
- | We create an user called **kodi** which belongs to the groups: **audio**, **video**, **input**, **pulse** and **pulse-access**. To execute kodi as a Systemd service we created an Unit file **/ | + | |
- | + | ||
- | < | + | |
- | [Unit] | + | |
- | Description = Kodi Media Center | + | |
- | + | ||
- | # if you don't need the MySQL DB backend, this should be sufficient | + | |
- | After = systemd-user-sessions.service network.target sound.target | + | |
- | + | ||
- | # if you need the MySQL DB backend, use this block instead of the previous | + | |
- | # After = systemd-user-sessions.service network.target sound.target mysql.service | + | |
- | # Wants = mysql.service | + | |
- | + | ||
- | [Service] | + | |
- | User = kodi | + | |
- | Group = kodi | + | |
- | Type = simple | + | |
- | ExecStart = / | + | |
- | Restart = always | + | |
- | RestartSec = 15 | + | |
- | + | ||
- | [Install] | + | |
- | WantedBy = multi-user.target | + | |
- | </ | + | |
- | + | ||
- | The service must be enabled and started. | + | |
- | + | ||
- | ===== Kodi Add-ons ===== | + | |
- | + | ||
- | We don't want to depend on auto-download, | + | |
- | + | ||
- | Despite installing the add-on from a zip file, any **required add-ons** not present into the system will be automatically downloaded from the net and installed. Fortunately you can find the zip files of this additional add-ons into the **$HOME/ | + | |
- | + | ||
- | + | ||
- | ===== Music ===== | + | |
- | + | ||
- | Beside Kodi, which has its own functions to play music, I want also the functions offered by the **[[https:// | + | |
- | + | ||
- | * **mpd** - The Music Player Daemon, the underlying daemon which actually plays music. | + | |
- | * **ncmpc** - It is a MPD client for text terminals, based on ncurses. | + | |
- | + | ||
- | ===== Transfer rate ===== | + | |
- | + | ||
- | We measured the **transfer rate** from other home NASes, just to figure out how much time is required to **transfer 500 Gb of data**. The receiving NAS is the **Raspberry Pi 4** with a **Seagate 4 Tb** IronWolf 3.5 inch hard disk connected through the **X835 USB3** interface. The network is limited to **100 Mbit** transfer rate, due to the limit of the LAN switch. | + | |
- | + | ||
- | ^ NAS model ^ Disk model ^ Transfer rate (Mbit) | + | |
- | | LaCie d2 Network | + | |
- | | QNAP TS-120 | + | |
doc/appunti/hardware/raspberrypi_nas.txt · Last modified: 2021/04/02 15:47 by niccolo