01-10-2023, 05:08 PM
(This post was last modified: 01-11-2023, 11:12 PM by ARMandHammer.)
This afternoon I set up armbian (22.11.1/Bullseye) and a 2 SSD, Software, Raid-1 array (mdadm, /dev/md0) on my Rockpro64 following this guide. I hoped to put my OS and files on that Raid Array using the "nand-sata-install" script below for speed and redundancy.
(https://forum.armbian.com/topic/9622-arm...ausb-drive)
When I run "sudo /usr/sbin/nand-sata-install"
When I tried cfdisk to create a partition, cfdisk outputs the following warning:
Questions:
Similar issue without raid complications:
https://forum.armbian.com/topic/17155-pa...a-install/
End Goal for Context:
Run a fast Nextcloud instance on top of OMV (using docker) so that I have a reliable cloud and file storage solution that allows me to work collaboratively without google, microsoft, or other privacy abusing dependancies.
(https://forum.armbian.com/topic/9622-arm...ausb-drive)
Quote:sudo /usr/sbin/nand-sata-install
When I run "sudo /usr/sbin/nand-sata-install"
- Choose "Boot from SPI - system on SATA, USB, or NVMe"
- Select "1 /dev/md0" as the destination (the only option)
- Press continue to the warning prompt "This script will erase your device /dev/md0. Continue?"
- Select filesystem type ext4
Quote:Partition too small. Needed: 1927 MB Avaliable: MB
When I tried cfdisk to create a partition, cfdisk outputs the following warning:
Quote:Device already contains a linux_raid_member signature; it will be removed by a write command.I am hesitant to add a partition using cfdisk since I don't want it to cause issues with the raid array.
Questions:
- Is there any way to create a partition or expand the current partition without deleting the array?
- Should I create partitions on those drives before I make the RAID array?
- Is LVM a viable solution?
- Am I approaching this incorrectly or missing a whole component of this process?
Similar issue without raid complications:
https://forum.armbian.com/topic/17155-pa...a-install/
End Goal for Context:
Run a fast Nextcloud instance on top of OMV (using docker) so that I have a reliable cloud and file storage solution that allows me to work collaboratively without google, microsoft, or other privacy abusing dependancies.