[Bug 224171] Re: Upgrade to 8.04 (Hardy) trashed RAID Array
Dave Walker
davewalker at ubuntu.com
Wed Oct 12 19:16:13 UTC 2011
Hardy release notes have long since passed. Marking the ubuntu-release-
notes as Invalid.
Thanks.
** Changed in: ubuntu-release-notes
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/224171
Title:
Upgrade to 8.04 (Hardy) trashed RAID Array
Status in Release Notes for Ubuntu:
Invalid
Status in “mdadm” package in Ubuntu:
Invalid
Bug description:
This issue should be covered in the release notes, but appears not to
be.
I was upgrading an Xubuntu based server from 7.10 to 8.04. This system
ran a 2.6.22-14-server kernel image and had an ATA-133 IDE system disk
(/dev/hda) and two SATA 320GB disks as a RAID-1 array (/dev/sda1 and
/dev/sdb1 configured as /dev/md0). The array was defined by an entry
in mdadm.conf:
ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1
Following the upgrade to the 2.6.24-16-server kernel image, the device names for the disks changed:
/dev/hda -> /dev/sda
/dev/sda -> /dev/sdb
/dev/sdb -> /dev/sdc
This was not expected and appeared as a failure to assemble the RAID
array. An attempt to manual start the RAID array brought it up with a
single disk only (/dev/sdb1). Only by poking around with fdisk was it
apparent that /dev/sda had a different partition scheme to that
expected - and was really /dev/hda1.
This problem was corrected by adding /dev/sdc1 back into the RAID
array and by updating mdadm.conf. However, the change to device names
should have been flagged up in the release notes and a warning given
during the upgrade process. This is probably only one example of how
an unexpected change to device names can screw up an upgrade.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/224171/+subscriptions
More information about the foundations-bugs
mailing list