Nächster Test.
Zwei RAID1, insgesamt 4 HDDs und eine SSD 30GB als System.
Hardware
- ROCKPro64v2.1 mit 2GB RAM
- PCIe SATA Karte JMS585
- 2 * 2,5 Zoll HDD 2TB Seagate
- 2 * 2,5 Zoll HDD HGST 1TB
- 1 30GB SSD Kingston
Also, alles in allem nix besonderes, so Kram der sich hier angesammelt hat 
Software
- Kamils Release 0.10.11
- u-boot im SPI 2020.01-ayufan-2014-gff2cdd38
Der Plan
md0
md1
System
Übersicht
root@rockpro64:~# blkid
/dev/sde2: SEC_TYPE="msdos" LABEL_FATBOOT="boot-efi" LABEL="boot-efi" UUID="ABCD-FC7D" TYPE="vfat" PARTLABEL="boot_efi" PARTUUID="72e36967-4050-4bb3-8f8f-bf6755c38f28"
/dev/sde3: LABEL="linux-boot" UUID="8e289a3e-0f9b-4da1-a147-51e03390637c" TYPE="ext4" PARTLABEL="linux_boot" PARTUUID="fe944fd2-3e42-4202-8a95-656e9bdb4be6"
/dev/sde4: LABEL="linux-root" UUID="3e9513c6-dfd1-48c9-bee2-04bb5a153056" TYPE="ext4" PARTLABEL="linux_root" PARTUUID="d2d1dd88-030d-4f74-998f-7c9ce7d385d0"
/dev/sda: UUID="ff08805b-a249-f512-6b2d-ed9ef86665be" UUID_SUB="27fa92a3-6275-8a3c-d06b-8ccd02e931ae" LABEL="rockpro64:0" TYPE="linux_raid_member"
/dev/sdb: UUID="ff08805b-a249-f512-6b2d-ed9ef86665be" UUID_SUB="f5f18413-ab32-58d3-21d0-0fef26947d1c" LABEL="rockpro64:0" TYPE="linux_raid_member"
/dev/sdc: UUID="eca7e4b4-1436-71df-4261-c05037dc9070" UUID_SUB="8d1b00bd-552d-51c9-ed87-9145591a02c1" LABEL="rockpro64:1" TYPE="linux_raid_member"
/dev/sdd: UUID="eca7e4b4-1436-71df-4261-c05037dc9070" UUID_SUB="c4ee7d26-e264-690d-0933-93ae74ba43f4" LABEL="rockpro64:1" TYPE="linux_raid_member"
/dev/sde1: PARTLABEL="loader1" PARTUUID="37466429-e4a4-495c-b9a1-3f74625a3cae"
Einrichtung mdadm
root@rockpro64:~# apt install mdadm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
dracut-core
Recommended packages:
default-mta | mail-transport-agent
The following NEW packages will be installed:
mdadm
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 425 kB of archives.
After this operation, 1223 kB of additional disk space will be used.
Get:1 http://cdn-fastly.deb.debian.org/debian buster/main arm64 mdadm arm64 4.1-1 [425 kB]
Fetched 425 kB in 1s (468 kB/s)
Preconfiguring packages ...
Selecting previously unselected package mdadm.
(Reading database ... 41667 files and directories currently installed.)
Preparing to unpack .../archives/mdadm_4.1-1_arm64.deb ...
Unpacking mdadm (4.1-1) ...
Setting up mdadm (4.1-1) ...
Generating mdadm.conf... done.
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for systemd (241-7~deb10u3) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.6.0-1132-ayufan-g81043e6e109a
Einrichtung md0
Raid anlegen
root@rockpro64:~# mdadm --create /dev/md0 --auto md --level=1 --raid-devices=2 /dev/sda /dev/sdb
mdadm: partition table exists on /dev/sda
mdadm: partition table exists on /dev/sda but will be lost or
meaningless after creating array
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: partition table exists on /dev/sdb
mdadm: partition table exists on /dev/sdb but will be lost or
meaningless after creating array
Continue creating array? Y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
Filesystem anlegen
root@rockpro64:~# mkfs.ext4 /dev/md0
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 244157616 4k blocks and 61046784 inodes
Filesystem UUID: 174a13ea-5ac9-4628-9741-3f802e110b34
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Mounten
root@rockpro64:~# mkdir /mnt/DATA
Einrichtung md1
Raid anlegen
root@rockpro64:~# mdadm --create /dev/md1 --auto md --level=1 --raid-devices=2 /dev/sdc /dev/sdd
mdadm: partition table exists on /dev/sdc
mdadm: partition table exists on /dev/sdc but will be lost or
meaningless after creating array
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: partition table exists on /dev/sdd
mdadm: partition table exists on /dev/sdd but will be lost or
meaningless after creating array
Continue creating array? Y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md1 started.
Filesystem anlegen
root@rockpro64:~# mkfs.ext4 /dev/md1
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 488345616 4k blocks and 122093568 inodes
Filesystem UUID: e697a0f3-8b24-497c-b453-820d70059ac3
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Mounten
root@rockpro64:~# mount /dev/md1 /mnt/NAS
Ergebnis
Filesystem Size Used Avail Use% Mounted on
udev 918M 0 918M 0% /dev
tmpfs 192M 5.2M 187M 3% /run
/dev/sde4 28G 5.1G 22G 20% /
tmpfs 957M 0 957M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 957M 0 957M 0% /sys/fs/cgroup
/dev/sde3 105M 45M 53M 46% /boot
/dev/sde2 12M 0 12M 0% /boot/efi
tmpfs 192M 0 192M 0% /run/user/1000
/dev/md0 916G 77M 870G 1% /mnt/DATA
/dev/md1 1.8T 77M 1.7T 1% /mnt/NAS
Und jetzt sind die RAIDs erst mal am resyncen......
Every 10.0s: cat /proc/mdstat rockpro64: Thu Apr 16 15:15:54 2020
Personalities : [raid1]
md1 : active raid1 sdd[1] sdc[0]
1953382464 blocks super 1.2 [2/2] [UU]
[>....................] resync = 3.4% (66640768/1953382464) finish=450.5min speed=69797K/sec
bitmap: 15/15 pages [60KB], 65536KB chunk
md0 : active raid1 sdb[1] sda[0]
976630464 blocks super 1.2 [2/2] [UU]
[==>..................] resync = 10.3% (101341312/976630464) finish=170.2min speed=85702K/sec
bitmap: 8/8 pages [32KB], 65536KB chunk
unused devices: <none>
wird fortgesetzt...
Nachdem ich nur noch eine Festplatte mit Bootdevice hatte und diese als Device 4:0 angeschlossen war (entspricht dem Port 5 auf der Karte) bootete das System nicht mehr.
