|
1 | | - |
2 | 1 | ############# |
3 | 2 | SATA |
4 | 3 | ############# |
5 | 4 |
|
6 | 5 | .. note:: |
7 | 6 |
|
8 | | - **Documentation coming soon!** |
9 | | - This section will be updated shortly with detailed instructions and information. Stay tuned for more! |
| 7 | + The vicharak-axon board includes a native SATA interface designed to connect one or more SATA drives. This page documents how to use the SATA interface on the board. |
| 8 | + |
| 9 | +Overview |
| 10 | +-------- |
| 11 | + |
| 12 | +- The SATA interface on the vicharak-axon board is exposed to the host operating system as standard storage devices (e.g., /dev/sda or /sdX). |
| 13 | +- The interface is designed for straightforward data transfer, drive management, and typical OS-level tooling (partitioning, formatting, mounting, SMART monitoring). |
| 14 | + |
| 15 | +.. image:: /_static/images/rk3588-axon/axon-SATA.webp |
| 16 | + :width: 70% |
| 17 | + |
| 18 | +SATA connectors and power |
| 19 | +-------------------------- |
| 20 | + |
| 21 | +The board provides a 16-pin SATA 3.0 connector that integrates both SATA data and power signals. |
| 22 | + |
| 23 | +- Data connector: standard 7-pin SATA data connector |
| 24 | +- Power connector: power slots are provided for 5v and 12v besides SATA slot |
| 25 | + |
| 26 | +Getting started |
| 27 | +--------------- |
| 28 | + |
| 29 | +.. figure:: /_static/images/rk3588-axon/axon-sata-hat.webp |
| 30 | + :width: 70% |
| 31 | + |
| 32 | + Vicharak axon board connected with SATA expansion board/HAT |
| 33 | + |
| 34 | +.. note:: |
| 35 | + |
| 36 | + In the following commands, the SATA storage device is represented as /dev/sdX. Use the lsblk command to determine the correct device name assigned by the Linux system, and replace /dev/sdX accordingly before executing the commands. |
| 37 | + |
| 38 | + |
| 39 | +- Steps: |
| 40 | + |
| 41 | + 1) Connect a SATA drive like a SATA HDD or SSD to the board using a Vicharak SATA expansion board or HAT with SATA data cable as shown in image above. |
| 42 | + 2) Power on the board and boot into the operating system. |
| 43 | + 3) Confirm the OS detects the drive: |
| 44 | + |
| 45 | + .. code-block:: bash |
| 46 | +
|
| 47 | + lsblk |
| 48 | + sudo dmesg | grep -i sata |
| 49 | +
|
| 50 | + to verify /dev/sdX (e.g., /dev/sda or /dev/sdb) appears. |
| 51 | + 4) Partition and format the drive as needed: |
| 52 | + |
| 53 | + - Create a partition table and partitions. |
| 54 | + - Create filesystems (e.g., ext4, xfs). |
| 55 | + 5) Mount the filesystem: |
| 56 | + - Create a mount point and mount the new partition: |
| 57 | + |
| 58 | + .. code-block:: bash |
| 59 | +
|
| 60 | + sudo mkdir -p /mnt/data |
| 61 | + sudo mount /dev/sdX1 /mnt/data |
| 62 | +
|
| 63 | +Using Linux with the SATA interface |
| 64 | +------------------------------------ |
| 65 | + |
| 66 | +- Detecting drives: |
| 67 | + |
| 68 | + |
| 69 | + .. code-block:: bash |
| 70 | +
|
| 71 | + lsblk -f |
| 72 | + sudo fdisk -l |
| 73 | +- Creating partitions and filesystems: |
| 74 | + |
| 75 | + .. code-block:: bash |
| 76 | +
|
| 77 | + sudo parted /dev/sdX mklabel gpt |
| 78 | + sudo parted -a optimal /dev/sdX mkpart primary ext4 0% 100% |
| 79 | + sudo mkfs.ext4 /dev/sdX1 |
| 80 | +- Mounting and fstab: |
| 81 | + |
| 82 | + .. code-block:: bash |
| 83 | +
|
| 84 | + sudo mkdir -p /mnt/data |
| 85 | + sudo mount /dev/sdX1 /mnt/data |
| 86 | +- Basic health and monitoring: |
| 87 | + |
| 88 | + .. code-block:: bash |
| 89 | +
|
| 90 | + sudo smartctl -a /dev/sdX |
| 91 | + sudo lsblk -f |
| 92 | + sudo blkid |
| 93 | +
|
| 94 | +Troubleshooting |
| 95 | +--------------- |
| 96 | + |
| 97 | +- Drive not detected: |
| 98 | + |
| 99 | + - Verify power is connected to the drive. |
| 100 | + - Re-seat the SATA data and power cables. |
| 101 | + - Try a different SATA port on the board. |
| 102 | + |
| 103 | +- Drive detected but inaccessible: |
| 104 | + |
| 105 | + - Verify partition table and filesystem: |
| 106 | + |
| 107 | + .. code-block:: bash |
| 108 | +
|
| 109 | + sudo fdisk -l /dev/sdX |
| 110 | + sudo file -s /dev/sdX1 |
| 111 | +
|
| 112 | + - Check dmesg for errors related to the SATA controller or drive: |
| 113 | + |
| 114 | + .. code-block:: bash |
| 115 | +
|
| 116 | + dmesg | grep -i sata |
| 117 | +- Data access issues: |
| 118 | + |
| 119 | + - Check filesystem integrity: |
| 120 | + |
| 121 | + .. code-block:: bash |
| 122 | +
|
| 123 | + sudo fsck /dev/sdX1 |
| 124 | +
|
| 125 | + - Ensure proper mounting options and permissions. |
0 commit comments