Timeline for Error setting up Raid 1 with mdadm at RaspberryPi 2
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 20, 2018 at 2:51 | answer | added | Mark | timeline score: 0 | |
| Jan 8, 2018 at 21:19 | comment | added | Cauti | Sadly it doesn't work. Since I've done this (and also set a reboot delay), I can only find md0 but like avove /dev/sda1 is active and the other drive is "removed". Don't know why. Before rebooting both drives where active. mdadm.conf says: ARRAY /dev/md0 metadata=1.2 name=raspberrypi:0 UUID=97660f1c:97eabbc5:789d6f50:92703ab2 | |
| Jan 8, 2018 at 20:15 | comment | added | ridgy | I think you missed one important step: Create /etc/mdadm/mdadm.conf before rebooting (e.g. blog.alexellis.io/hardened-raspberry-pi-nas/#30theraidarray or stewright.me/2017/08/create-raid-volume-raspberry-pi). As mdadm.confdoes not describe your configuration, there will be a guess when finding raid info and the raid will be named from md127downwards. So just create mdadm.conf as described, then modify it to read md0instead of md127. After reboot it should work again. | |
| Jan 8, 2018 at 16:57 | review | First posts | |||
| Jan 8, 2018 at 16:59 | |||||
| Jan 8, 2018 at 16:54 | history | asked | Cauti | CC BY-SA 3.0 |