Unexpected behavious of raid array when replacing a drive. +++ This bug was initially created as a clone of Bug #6630 +++ I manage a SME 7.5 server. It had two 250gb HDDs synced OK with RAID. One of the drives (sda) failed and so we decided to get 2 new 500gb drives to upgrade with. I installed the first 500gb drive (as /dev/sda), went into array manager, and added it to the array which then went and sync'd it successfully. However, when I removed the 250gb drive, the machine wouldn't boot from the 500gb that had just been synced. It just hangs at the point that the grub menu should kick in. I have checked the bios is trying to boot the 500gb correctly. I re-installed the 250gb again, booted up, and verified that the array is showing full health/sync. The output of cat /proc/mdstat: [code]Personalities : [raid1] md2 : active raid1 sda2[0] sdb2[1] 244091520 blocks [2/2] [UU] md1 : active raid1 sda1[0] sdb1[1] 104320 blocks [2/2] [UU] unused devices: <none>[/code] The output of fdisk -l [code]Disk /dev/sda: 500.1 GB, 500106780160 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104384+ fd Linux raid autodetect Partition 1 does not end on cylinder boundary. /dev/sda2 13 60801 488279647 fd Linux raid autodetect Disk /dev/sdb: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 13 104391 fd Linux raid autodetect /dev/sdb2 14 30401 244091610 fd Linux raid autodetect Disk /dev/md1: 106 MB, 106823680 bytes 2 heads, 4 sectors/track, 26080 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2: 249.9 GB, 249949716480 bytes 2 heads, 4 sectors/track, 61022880 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/md2 doesn't contain a valid partition table Disk /dev/dm-0: 247.9 GB, 247900143616 bytes 2 heads, 4 sectors/track, 60522496 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 2013 MB, 2013265920 bytes 2 heads, 4 sectors/track, 491520 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk /dev/dm-1 doesn't contain a valid partition table[/code] I'm particularly concerned about the message near the top that says under sda1: "Partition does not end on cylinder boundary" Does anyone know what this means? I suspect it may be the cause
Set closed as per comment #6
This bug is linked to http://bugs.contribs.org/show_bug.cgi?id=6911 Can they both be closed ?
No worries Chris..
(In reply to Terry Fage from comment #2) > I have used the details here Bug 6630 and created a new section for this > wiki page in the Dicusssion page here: > http://wiki.contribs.org/Talk: > Raid#Replacing_and_Upgrading_Hard_Drive_after_HD_fail > > New section to go after here > http://wiki.contribs.org/Raid#Upgrading_the_Hard_Drive_Size in the wiki > > If agree confirm and I will do edit and bug can be closed I think we need to look at this further, I have no testing facilities at the moment, resolving IN PROGRESS for time being. We may need a senior Dev to check this.
I should add the current procedure for Upgrading the Hard Drive Size does not cover failed HDs or moving drives to sda, which is what appeasr to overcome the issue.
I have used the details here Bug 6630 and created a new section for this wiki page in the Dicusssion page here: http://wiki.contribs.org/Talk:Raid#Replacing_and_Upgrading_Hard_Drive_after_HD_fail New section to go after here http://wiki.contribs.org/Raid#Upgrading_the_Hard_Drive_Size in the wiki If agree confirm and I will do edit and bug can be closed.
Check comment #1 of original bug #6630