{ "ok": true, "data": { "title": "EP-0180", "rev_id": 15904, "updated_at": "2025-05-28T05:57:57+00:00", "chunk_count": 28, "chunks": [ { "title": "EP-0180", "rev_id": 15904, "heading_path": "", "chunk_index": 0, "content": "# EP-0180", "char_count": 9, "token_estimate": 3 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Quad NVMe expansion board for Raspberry Pi 5", "chunk_index": 1, "content": "
\n\"EP-0180-01.jpg\"\n
EP-0180-01.jpg<\/figcaption>\n<\/figure>", "char_count": 162, "token_estimate": 41 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Description", "chunk_index": 2, "content": "The Raspberry Pi 5 Expansion Board is a versatile accessory designed to enhance the capabilities of the Raspberry Pi 5 through a PCIe interface. This board not only provides a power conversion solution but also serves as a high-speed storage expansion device. It is equipped with a 9V-20V Power Delivery (PD) input that converts the power supply to a stable 5.1V\/5A output, ensuring reliable operation of the Raspberry Pi 5. The board requires a 9V-20V PD-compatible power source for activation and can power both the Raspberry Pi and attached storage devices, with the highest allowable voltage being 20V.", "char_count": 606, "token_estimate": 152 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Features", "chunk_index": 3, "content": "- Power Delivery Support: <\/strong>It supports from 9V-20V PD (65W PD recommended) and will automatically read the user's power supply PDO.\n- Dual-Purpose Power Supply:<\/strong> Powers both the Raspberry Pi 5 and connected storage devices.\n- Storage Expansion:<\/strong> Supports four M.2 NVMe SSDs for high-speed data storage and retrieval.\n- Versatile Form Factor Compatibility:<\/strong> Accommodates M.2 SSDs in sizes 2230, 2242, 2260, and 2280.\n- Application Flexibility:<\/strong> Ideal for use in Samba file systems or NAS setups, providing a robust disk expansion foundation.", "char_count": 630, "token_estimate": 158 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Features > Specifications", "chunk_index": 4, "content": "- Interface: PCIe\n- Input Voltage: 9V- 20V Power Delivery (PD), Recommand：up to 65W PD protocol Power supply\n- Output Voltage & Current: 5.1V \/ 5A\n- SSD Support: M.2 NVMe SSDs in 2230, 2242, 2260, and 2280 sizes\n- Power Requirement: Powered by 9V-20V PD-compatible power source to initiate operation.\n- Use Case: Suitable for Raspberry Pi 5 models, enhancing storage capabilities for applications such as Samba servers or Network Attached Storage (NAS).", "char_count": 465, "token_estimate": 117 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Features > Important Note", "chunk_index": 5, "content": "NOTE: Please note following issue<\/br> Why does the disk fail to start after sleep mode when the Raspberry Pi is running? Is it necessary to restart to use the disk? The disk is an NVMe one, connected to the Raspberry Pi 5 via the PCIe interface.", "char_count": 246, "token_estimate": 62 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Features > Possible Reasons", "chunk_index": 6, "content": "- 1\\. Hardware Compatibility Issues\n\n\\- There may be compatibility issues between the Raspberry Pi 5's PCIe interface and certain NVMe disks. For example, some Western Digital SN series disks (such as the SN550 and SN570) may fail to boot as a system disk. - Some disks may not be correctly awakened by the Raspberry Pi after sleep mode, leading to startup failure.\n\n- 2\\. Boot Order Configuration Issues\n\n\\- If the boot order of the Raspberry Pi is not correctly set, it may fail to recognize the disk. Ensure that the boot order is set to prioritize booting from the NVMe disk. You can modify the boot order using the following command:\n\nsudo rpi-eeprom-config --edit\n\nSet \\`BOOT_ORDER\\` to \\`0xf416\\`.\n\n- 3\\. Power Supply Issues\n\n\\- The power supply of the Raspberry Pi 5 may not be sufficient to support the startup of the NVMe disk. It is recommended to use a power supply that supports the PD protocol.\n\n- 4\\. System Configuration Issues\n\n\\- Ensure that the PCIe interface is enabled on the Raspberry Pi. You can add the following lines to \\`\/boot\/firmware\/config.txt\\`:\n\ndtparam=pciex1\n dtparam=pciex1_gen=3\n\n` This will enable the PCIe interface and set it to Gen3 speed.`", "char_count": 1193, "token_estimate": 299 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Features > Possible Reasons", "chunk_index": 7, "content": "- 5\\. Solid State Drive Partition and Mount Issues\n\n\\- If the disk fails to start after sleep mode, there may be issues with partitioning or mounting settings. Ensure that the disk is correctly partitioned and that the mount points are correctly set in \\`\/etc\/fstab\\`.\n\n- 6\\. Firmware and Driver Issues\n\n\\- Ensure that the firmware and drivers of the Raspberry Pi are up-to-date. You can update the firmware using the following commands:\n\nsudo apt update\n sudo apt full-upgrade\n sudo rpi-update\n\n#### Solutions\n\n- Replace the Disk<\/strong>: If the current disk has compatibility issues, consider replacing it with another NVMe disk that is known to be compatible.\n- Reconfigure Boot Order<\/strong>: Ensure that the boot order prioritizes starting from the NVMe disk.\n- Check Power Supply<\/strong>: Use a power supply that supports the PD protocol.\n- Update Firmware and Drivers<\/strong>: Ensure that the firmware and drivers of the Raspberry Pi are up-to-date.\n\nIf the problem persists, it is recommended to seek further assistance on the official Raspberry Pi forums or related communities.", "char_count": 1145, "token_estimate": 287 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Gallery", "chunk_index": 8, "content": "- Product outlook (frontal face)\n\n\"EP-0180-01.jpg\"\n\\* Product outlook (back face) \"EP-0180-02.jpg\"\n\\* Dimension \"EP-0180-03.jpg\"\n\\* Port definitions \"EP-0180-04.jpg\"\n\\* Compatibility \"EP-0180-05.jpg\"\n\\* The appearance from the front after assembly \"EP-0180-06.jpg\"\n\\* The appearance from the back after assembly \"EP-0180-07.jpg\"\n\\* Product details \"EP-0180-08.jpg\"\n\\* Application scenario \"EP-0180-09.jpg\"\n\"EP-0180-10.jpg\"\n===How to assmeble it?===\n\n- Please assemble it according to following figure:", "char_count": 1185, "token_estimate": 297 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Gallery", "chunk_index": 9, "content": "\"EP-0180-安装.jpg\"", "char_count": 84, "token_estimate": 29 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Package Includes", "chunk_index": 10, "content": "- Please check following figure\n\n\"EP-0180-清单.jpg\"", "char_count": 119, "token_estimate": 38 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to enable PCIe on Raspberry Pi 5", "chunk_index": 11, "content": "- We assume that you are using Raspberry Pi OS (bookworm) 2024-03-15", "char_count": 70, "token_estimate": 18 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to enable PCIe on Raspberry Pi 5 > Step 1", "chunk_index": 12, "content": "- Enable PCIe function\n\nEdit \/boot\/firmware\/config.txt file and adding following parameter in to the file. And the connection is certified for Gen 2.0 speed (5 GT\/sec), but you can force it to Gen 3.0 (10 GT\/sec) if you add the following line after: dtparam=pciex1_gen=3, but some SSD may not take effect, if not, please remove this line. The Raspberry Pi 5 is not certified for Gen 3.0 speeds. PCIe Gen 3.0 connections may be unstable.\nRefer to: \\[ \\]\nso that the dtparam=pciex1_gen=3 is optional. <\/strong>\n\nNOTE:\n PCIe 4.0 (fourth-generation) solid-state drives (SSDs) are typically designed to be backward compatible, meaning they can operate on lower PCIe versions such as PCIe 2.0 or 3.0. This backward compatibility means that even if the Raspberry Pi 5's PCIe interface only supports up to Gen 2.0, a PCIe 4.0 SSD can still function on a Gen 2.0 interface, but its speed will be limited to the rates of Gen 2.0.", "char_count": 1017, "token_estimate": 255 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to enable PCIe on Raspberry Pi 5 > Step 1", "chunk_index": 13, "content": "Specifically, the speed of a PCIe 4.0 SSD on a Gen 2.0 interface will be capped at about 5 GB\/s (the theoretical maximum bandwidth of a PCIe 2.0 x1 interface), rather than the higher speeds achievable with a PCIe 4.0 x4 interface. Therefore, while PCIe 4.0 SSDs can be backward compatible with Gen 2.0, they cannot perform at their full potential on a Gen 2.0 interface.\n\ndtparam=pciex1\n dtparam=pciex1_gen=3\n\n\"Config.txt_file.png\"\nSave it and then do remember reboot your Raspberry Pi to take effect.", "char_count": 582, "token_estimate": 146 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to enable PCIe on Raspberry Pi 5 > Step 2", "chunk_index": 14, "content": "- Check if the SSD drive has been recognized\n\n\n\nsudo lspci\n sudo lsblk\n\nResult be like: \"Pcieinfor.png\"\n\"Diskinfo.png\"\n===Step 3 ===\n\n- Partitioning\n\n\"Partitionning.png\"\nPlease divide the partition according to actual needs. Here I simply divided a partition and formatted it into ext4. Please refer to the configuration method related to the fdisk command to operate.\n\nsudo fdisk \/dev\/nvme0n1\n >d\n >n\n >p\n >1\n > Enter > Enter\n > w\n sudo partprobe \/dev\/nvme0n1\n\n- Formating\n\n\n\nsudo mkfs.ext4 \/dev\/nvme0n1p1\n\n- Create mounting point and mount the partition to directory.\n\n\n\nmkdir mynvme01\n sudo mount -t ext4 \/dev\/nvme0n1p1 \/home\/pi\/mynvme01 -v\n\n- Grant access permission\n\n\n\nsudo chown -R pi:pi \/home\/pi\/mynvme01\n sudo chmod -R 775 \/home\/pi\/mynvme01\n\n- Modify the \/etc\/fstab to enable automount function.\n\n\n\nsudo nano \/etc\/fstab\n\nadding:\n\n\/dev\/nvme0n1p1 \/home\/pi\/mynvme01 ext4 defaults,noatime 0 0", "char_count": 1188, "token_estimate": 297 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to enable PCIe on Raspberry Pi 5 > Step 2", "chunk_index": 15, "content": "save it and execute:\n\nsudo umount \/dev\/nvme0n1p1\n sudo mount -a\n sudo systemctl daemon-reload\n df -Th\n\nNOTE: Same steps for the rest of NVMe SSDs.", "char_count": 155, "token_estimate": 39 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to setup Raid 0 on Raspberry Pi 5", "chunk_index": 16, "content": "- Prepare Hardware:<\/strong> Ensure you have multiple SD cards or USB flash drives, as well as a Raspberry Pi.\n\n\n\n- Partitioning:<\/strong> Use the dd or fdisk command to clear the boot sector and partition table, then use fdisk or gdisk to create partitions of the same size,or just use all raw disk.\n\n\n\n- Install mdadm: <\/strong>Install the RAID management tool by running:\n\n\n\nsudo apt-get update && sudo apt-get install mdadm\n\n- Create RAID Device:<\/strong> Use the mdadm command to create a RAID 0 device, for example:\n\n\n\nsudo mdadm --create --verbose --level=0 --metadata=1.2 --raid-devices=4 \/dev\/md0 \/dev\/nvme{0..3}n1\n\n- Format:<\/strong> Create a file system such as f2fs using:\n\n\n\nsudo mkfs.ext4 \/dev\/md0\n\n- Mount the RAID Device:<\/strong> Create a mount point and mount the RAID device, for example:\n\n\n\nmkdir -pv \/home\/pi\/myraid0\n sudo mount -t ext4 \/dev\/md0 \/home\/pi\/myraid0\n\n- Set Up Boot Mounting:<\/strong> Edit the \/etc\/fstab file to add the mount information for the RAID device and update the mdadm configuration.\n\n\n\nsudo vim.tiny \/etc\/fstab", "char_count": 1184, "token_estimate": 296 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to setup Raid 0 on Raspberry Pi 5", "chunk_index": 17, "content": "Adding following parameters into it.\n\n\/dev\/md0 \/home\/pi\/myraid0 ext4 defaults,noatime 0 0\n\nSave it and quit.\n\n- Update mdadm Configuration:<\/strong> After the RAID array is active, you can update the mdadm configuration file to save the current setup. Run the following command:\n\n\n\nsudo mdadm --detail --scan | sudo tee -a \/etc\/mdadm\/mdadm.conf\n\nThis command appends the configuration details of all assembled arrays to the mdadm.conf file.\n\n- Update initramfs:<\/strong>After updating the mdadm.conf, you need to update the initial RAM filesystem to ensure that the RAID array is recognized and assembled at boot time:\n\n\n\nsudo update-initramfs -u\n\n- Reboot System:<\/strong> Finally, reboot your system to ensure that the RAID array is assembled automatically upon startup:\n\n\n\nsudo reboot\n\n- Verify RAID Array:<\/strong>After the system reboots, check that the RAID array is active and functioning as expected:\n\n\n\ncat \/proc\/mdstat", "char_count": 1011, "token_estimate": 253 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to setup Raid 0 on Raspberry Pi 5", "chunk_index": 18, "content": "This command will display the status of all RAID arrays. Remember to replace \/dev\/md0 and the device names with the actual names used in your configuration. It's also a good practice to back up the mdadm.conf file before making changes, so you can restore it if something goes wrong.", "char_count": 283, "token_estimate": 71 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to setup Raid 5 on Raspberry Pi 5", "chunk_index": 19, "content": "- Hardware Selection:<\/strong> Choose at least three storage devices, which can be USB hard drives or flash drives.\n\n\n\n- Connect Storage Devices:<\/strong>Use at least 3 pcs of M.2 NVMe SSDs to N16 Quad NVMe expansion board to the Raspberry Pi.\n\n\n\n- Install Operating System:<\/strong> Install the latest Raspberry Pi OS (bullseye 64bit) on the Raspberry Pi.\n\n\n\n- Install mdadm:<\/strong> Same as for RAID 0 setup.\n\n\n\n- Create RAID 5 Array: <\/strong>Use the mdadm to create a RAID 5 array, for example:\n\n\n\nsudo mdadm --create \/dev\/md0 --level=5 --raid-devices=4 \/dev\/nvme{0..3}n1\n sudo mdadm --detail --scan | sudo tee -a \/etc\/mdadm\/mdadm.conf\n sudo update-initramfs -u\n\n- Format and Mount:<\/strong> Format the RAID array to ext4 or another file system and mount it to the system.\n\n\n\nsudo mkfs.ext4 \/dev\/md0\n\n- Mount the Raid Device:<\/strong> Create a mount point and mount the Raid device.\n\n\n\nmkdir -pv \/home\/pi\/myraid5\n sudo mount -t ext4 \/dev\/md0 \/home\/pi\/myraid5\n df -Th", "char_count": 1109, "token_estimate": 278 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to setup Raid 5 on Raspberry Pi 5", "chunk_index": 20, "content": "- Set Up Boot Mounting:<\/strong>Edit the \/etc\/fstab file to add the mount information for the RAID device and update the mdadm configuration.\n\nadding following parameters:\n\n\/dev\/md0 \/home\/pi\/myraid5 ext4 defaults,noatime 0 0\n\nsave it and execute following command:\n\nsudo systemctl daemon-reload\n\n- Waiting for rebuild stripping information:<\/strong>\n\n\n\nsudo mdadm --detail \/dev\/md0\n\nTo check if a RAID 5 array has been synchronized, you can use the following methods:\n\n- Check \/proc\/mdstat:<\/strong> This file provides information about the status of all active RAID devices. You can view the current status of your RAID devices by running the command:\n\n\n\ncat \/proc\/mdstat\n\n- Look for the RAID device in question and check for terms like \"active\", \"resync\", or \"clean\". If the status is \"clean\" and the device shows as \"active\", it typically means the RAID array is synchronized and operating normally.\n\nUse mdadm Command: The mdadm utility is a tool for managing and monitoring RAID devices in Linux. To get detailed information about a RAID device, use:\n\nmdadm --detail \/dev\/md0", "char_count": 1133, "token_estimate": 284 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to setup Raid 5 on Raspberry Pi 5", "chunk_index": 21, "content": "or Check RAID Status with mdadm -D: This command provides a detailed description of the RAID device's status, including whether it is actively syncing or if the sync is complete:\n\nmdadm -D \/dev\/md0\n\nLook for the \"State\" line in the output. A \"clean\" state with no pending writes indicates synchronization is complete.\n\n- Check for Resync Completion:<\/strong>If a RAID 5 array was resyncing, you can check if the resync has completed by looking for the absence of \"resync\" in the cat \/proc\/mdstat output or by using the mdadm --detail command. When the resync is complete, you should no longer see any mention of resync in progress.\n\n\n\n- Check Array Events:<\/strong> You can also check for any events related to the RAID array by using:\n\n\n\nmdadm --monitor --scan\n\nThis command will show the events related to the RAID devices, which can help you determine if there have been any recent issues or if the array is stable.\n\n- Review System Logs:<\/strong>Sometimes, the system logs can provide information about the RAID array's synchronization status. You can use the dmesg command or check the logs in \/var\/log\/ for any RAID-related messages.\n\n", "char_count": 1195, "token_estimate": 299 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "How to setup Raid 5 on Raspberry Pi 5", "chunk_index": 22, "content": "- Configure Network Sharing:<\/strong>Install and configure network sharing services such as Samba or NFS to access the RAID storage over the network.\n\nPlease note that RAID 0 offers data striping to improve read and write speeds but has no redundancy; if one drive fails, all data is lost. RAID 5 provides data striping and parity, offering better redundancy, but write performance may be slightly lower. When building a RAID system, also consider factors such as power supply, cooling solutions, and network performance.", "char_count": 531, "token_estimate": 133 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "YOUTUBE VIDEOS", "chunk_index": 23, "content": "- Official Channel: \\[ \\]\n- Leepsvideo Channel: \\[ \\]", "char_count": 149, "token_estimate": 38 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "YOUTUBE VIDEOS > NOTE", "chunk_index": 24, "content": "------------------------------------------------------------------------\n\nIf a RAID 5 array has not completed synchronization, it is generally possible to write data to it, but there are several considerations and potential issues to be aware of:\n\n- 1\\. Performance Impact: Writing to a RAID 5 array that is still in the process of resynchronization can significantly impact the performance of the array. The system may be slower to write data because it has to update both the data and the parity information across multiple disks.\n\n\n\n- 2\\. Increased Wear on SSDs: If your RAID 5 array includes SSDs, the ongoing resynchronization process can contribute to increased write amplification and thus wear on the SSDs.\n\n\n\n- 3\\. Risk of Data Loss: If the RAID 5 array is in the middle of a resync due to a previous disk failure or other issues, writing new data could potentially increase the risk of data loss in the event of another disk failure during the resync process. This is because the array is in a transitional state and may not have full redundancy.\n\n", "char_count": 1088, "token_estimate": 272 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "YOUTUBE VIDEOS > NOTE", "chunk_index": 25, "content": "- 4\\. Data Corruption: In rare cases, if there is a bug or hardware issue during the resynchronization process, there is a small risk that the new data written could become corrupted or could inadvertently corrupt existing data due to incorrect parity calculations.\n\n\n\n- 5\\. System Stability: Writing to the array during resync might also affect the stability of the system, especially if the resync process is already consuming a significant amount of system resources.\n\n\n\n- 6\\. Interruption of Resync: Some RAID controllers or software may pause the resynchronization process when new writes are detected, to avoid conflicts between the old and new data. This could effectively prolong the resync time.\n\n\n\n- 7\\. Priority of Resync: On some systems, the RAID controller may prioritize the completion of the resync process over new write operations, which could delay the writing of new data until the resync is complete.", "char_count": 953, "token_estimate": 239 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "YOUTUBE VIDEOS > NOTE", "chunk_index": 26, "content": "In summary, while it is usually possible to write to a RAID 5 array that has not finished resynchronizing, it is generally recommended to wait until the resync is complete to ensure optimal performance, minimize wear on SSDs, and reduce the risk of data loss or corruption. If it is necessary to write to the array during resync, it is important to monitor the system closely and ensure that there are robust backup procedures in place.\n\n------------------------------------------------------------------------", "char_count": 510, "token_estimate": 128 }, { "title": "EP-0180", "rev_id": 15904, "heading_path": "Keywords", "chunk_index": 27, "content": "- Quad NVMe SSD expansion board for Raspberry Pi 5, nas cluster expansion board for rpi5, pcie M.2 NVME SSD exppansion board, m.2 nvme ssd adapter board for Raspberry Pi 5.", "char_count": 174, "token_estimate": 44 } ] } }