Timeline for mdadm RAID array disappered after reboot
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2020 at 16:31 | vote | accept | Andreas | ||
| Apr 12, 2020 at 16:31 | answer | added | Andreas | timeline score: 0 | |
| Apr 12, 2020 at 16:26 | comment | added | Andreas | This fixed it. Writing an answer. | |
| Apr 12, 2020 at 16:15 | comment | added | Andreas | May be related to this nvme quirk: serverfault.com/questions/892134/… Will try this method next and report back here: unix.stackexchange.com/questions/411286/… | |
| Apr 12, 2020 at 16:11 | comment | added | Andreas | Yes. I just discovered that the issue may be that I am creating the array on partitions rather than directly on the block device, however if I try to create it directly: sudo mdadm --create --verbose --level=0 --metadata=1.2 --raid-devices=3 /dev/md/hpa /dev/nvme0 /dev/nvme1 /dev/nvme2 it tells me that this isn't a block device. | |
| Apr 12, 2020 at 14:21 | comment | added | Chris Davies |
Have you got your mdadm --detail --scan output in /etc/mdadm/mdadm.conf?
|
|
| Apr 12, 2020 at 14:19 | history | edited | Chris Davies | CC BY-SA 4.0 |
Formatting for readability. Also please don't use "edit" as there is an edit history. Keep your question readable
|
| Apr 12, 2020 at 12:58 | history | edited | Andreas | CC BY-SA 4.0 |
added 313 characters in body
|
| Apr 5, 2020 at 18:38 | history | asked | Andreas | CC BY-SA 4.0 |