# RAID 6 config gone after reboot

**URL:** <https://forums.suse.com/t/raid-6-config-gone-after-reboot/14197>\
**Category:** General\
**Created:** [May 7, 2019, 9:02pm UTC](https://forums.suse.com/t/raid-6-config-gone-after-reboot/14197 "2019-05-07T21:02:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lomankitchris](https://avatars.discourse-cdn.com/v4/letter/l/fbc32d/32.png) [@lomankitchris](https://forums.suse.com/u/lomankitchris)\
**Post date:** [May 7, 2019, 9:02pm UTC](https://forums.suse.com/t/raid-6-config-gone-after-reboot/14197/1 "2019-05-07T21:02:53Z")

</div>

Hello everyone,

I am new to RancherOS and currently trying to deploy a RancherOS instance with RAID 6 configuration. I setup, configure, and run mkfs.ext4 on the software RAID array before I ran “ros install -c cloud-config.yml” file. After the install completed successfully and rebooted, I was able to see the /dev/md0 in the output of “blkid”. When I rebooted the nodes, however, /dev/md0 disappeared and I need to run “mdadm --assemble --scan” to bring up the software RAID again. May I know what I am missing here? For your reference, I have attached my cloud-config.yml below:

#cloud-config

hostname: valkyrie-201905071020

rancher:  
network:  
dns:  
nameservers:  
- 192.168.9.241  
interfaces:  
eth0:  
address: 192.168.9.20/24  
gateway: 192.168.9.1  
state:  
autoformat:  
- /dev/sda  
dev: /dev/sda1  
fstype: auto

runcmd:

- wget [http://192.168.9.100/clo/cloud-config.yml](http://192.168.9.100/clo/cloud-config.yml) -P /home/rancher
- echo “hello” \>\> /home/rancher/test.org
- sudo mdadm --assemble --scan

mounts:

- ["/dev/md0", “/mnt/raid6”, “ext4”, “”]

Thank you,

Chris

---

<div class="post-metadata">

**Author:** ![Kuo\_Hugo](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/kuo_hugo/32/4737_2.png) [@Kuo\_Hugo](https://forums.suse.com/u/Kuo_Hugo)\
**Post date:** [July 30, 2019, 7:46am UTC](https://forums.suse.com/t/raid-6-config-gone-after-reboot/14197/2 "2019-07-30T07:46:23Z")

</div>

I encountered same problem here. How’s the way to bind the raid volume during reboot?
