Originally Posted by
dcstar
What happens when you use the "Create RAID" option in the Disk Utility?
Similar scene. it changes md0 to md127 Fortunately my system boots but see:
Code:
wangberg@box:~$ sudo fdisk -l
[sudo] password for wangberg:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00069f26
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 943316991 471657472 83 Linux
/dev/sda2 943319038 976771071 16726017 5 Extended
/dev/sda5 943319040 976771071 16726016 82 Linux swap / Solaris
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008e086
Device Boot Start End Blocks Id System
/dev/sdb1 63 976768064 488384001 fd Linux raid autodetect
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0003c52d
Device Boot Start End Blocks Id System
/dev/sdc1 63 976768064 488384001 fd Linux raid autodetect
Disk /dev/md127: 500.0 GB, 499970801664 bytes
2 heads, 4 sectors/track, 122063184 cylinders, total 976505472 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md127 doesn't contain a valid partition table
Additionally, when i did a system update, i found this error:
Code:
update-initramfs: Generating /boot/initrd.img-3.5.0-25-generic
W: mdadm: the array /dev/md/RAID_0 with UUID 344ff0b4:0b5f45df:78c7c50f:4c5de621
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
w: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.
For Reference:
/etc/mdadm/mdadm.conf
Code:
DEVICE partitions
ARRAY /dev/md0 metadata=1.2 name=nala:0 UUID=ba9aea27:ca8ea022:71ca3902:19f07b8b
MAILADDR root
Bookmarks