Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I had a software RAID 0 on an ec2 instance. I needed to make some changes so I stopped the RAID, unmounted it, and rebooted the instance. What's troubling is, I don't see a partition for one of the two storage units upon reboot. I see the partition /dev/sdc1 that I created, but I only see the physical disk /dev/sdb and not the partition I created /dev/sdb1 after reboot:

[root@ip-10-1-2-102 ~]# fdisk -l /dev/sdb

Disk /dev/sdb: 450.9 GB, 450934865920 bytes
255 heads, 63 sectors/track, 54823 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Am I risking losing partitions on reboot? Only one of my two disks are available now for a RAID0 and I don't think I'll be able to restore it, which is fine, I knew the risks for the particular data being stored here in that it is a RAID0 on ephemeral storage. What I did not expect however, is the partition to be missing upon reboot. What could be the cause of that?

share|improve this question
Performing a stop+start of the instance will lose any work you have done with ephemeral storage disks, but a simple system reboot should leave them intact and not affect them at all. You don't need to create partitions to raid across ephemeral volumes. –  Eric Hammond Aug 1 '13 at 16:23
add comment

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.