12.04 RAID 1 array

[Wangberg]

I've been a linux desktop user for a while. Was using 10.04 LTS and just upgraded to 12.04 LTS. In my previous system i successfully set up a RAID 1 array with two 500 GIG drives. The two drives are separate from the system drive.

I've done a lot of google searches looking for a guide on how to set this up and tried going through the same instructions to set up the array for 10.04 under 12.04. Unfortunately, i'm having problems when booting my machine and getting degraded errors and the array coming up as md127 instead of md0.

I was curious if a RAID 1 setup under 12.04 has been documented. Any help would go most appreciated!

Thanks in advance!

[dcstar]

I've been a linux desktop user for a while. Was using 10.04 LTS and just upgraded to 12.04 LTS. In my previous system i successfully set up a RAID 1 array with two 500 GIG drives. The two drives are separate from the system drive.

I've done a lot of google searches looking for a guide on how to set this up and tried going through the same instructions to set up the array for 10.04 under 12.04. Unfortunately, i'm having problems when booting my machine and getting degraded errors and the array coming up as md127 instead of md0.

I was curious if a RAID 1 setup under 12.04 has been documented. Any help would go most appreciated!

Thanks in advance!

What happens when you use the "Create RAID" option in the Disk Utility?

[Wangberg]

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:

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:

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

DEVICE partitions
ARRAY /dev/md0 metadata=1.2 name=nala:0 UUID=ba9aea27:ca8ea022:71ca3902:19f07b8b
MAILADDR root

[dcstar]

.........

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

DEVICE partitions
ARRAY /dev/md0 metadata=1.2 name=nala:0 UUID=ba9aea27:ca8ea022:71ca3902:19f07b8b
MAILADDR root

And what are the results of those explicit instructions?

[Wangberg]

And what are the results of those explicit instructions?

there is something I am missing. the mdadm.conf and mkconf files are incomplete. I don't know what necessary changes to make...any suggestions?

mkconf:

wangberg@box:~$ /usr/share/mdadm/mkconf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays

mdadm.conf:

wangberg@box:~$ cat /etc/mdadm/mdadm.conf 
DEVICE partitions
ARRAY /dev/md0 metadata=1.2 name=nala:0 UUID=ba9aea27:ca8ea022:71ca3902:19f07b8b
MAILADDR root

[Wangberg]

This is really getting frustrating.

1) what should a healthy mdadm.conf look like?
2) how can i restore my raid partition to reflect /md0 as opposed to /md127
3) there are inconsistencies all over the place from md0 vs md127 to disk utility saying this is a healthy raid array. How can i determine if this array is arunning properly?

in Ubuntu 10.04, this was a 15 minute project. in 12.04 this is turning into a project that i've been researching for the past week.

please, any direction would go most appreciated so i can just get my data backed up.