I'll upload a fix for 10.04.2 once we've tested this for 10.10.
** Summary changed:
- mount: mounting /dev/md0 on /root/ failed: Invalid argument
+ partman sometimes creates partitions such that there is ambiguity between
whether the superblock is on the disk device or the partition device
** Description changed:
Binary package hint: mdadm
In a KVM, I can do this just fine:
- * Using 2 virtual disk images
- * Install Lucid Server amd64
- * Both disks partitioned to just one large Linux raid partition
- * RAID1 these two together, /dev/md0
- * Put / on an ext4 filesystem on /dev/md0
- * Install
+ * Using 2 virtual disk images
+ * Install Lucid Server amd64
+ * Both disks partitioned to just one large Linux raid partition
+ * RAID1 these two together, /dev/md0
+ * Put / on an ext4 filesystem on /dev/md0
+ * Install
The above works.
However, I have spent my entire weekend trying to get 10.04 on a RAID1
of two 500GB SATA disks, without success.
I partitioned them the same as above. And conducted the install.
When I boot into the new system, I get dropped to an initramfs shell.
I can see that /dev/md0 exists, and is in the process of resyncing.
I try to "mount /dev/md0 /root" and I get:
mount: mounting /dev/md0 on /root/ failed: Invalid argument
Also, see something else that's odd... My /dev/md0 looks "correct", in
that it's composed of /dev/sda1 and /dev/sdb1. However, I also see a
/dev/md0p1, which is composed of /dev/sda and /dev/sdb (the whole
disks?). Furthermore, if I go into /dev/disk/by-uuid, there is only one
symlink there, pointing to /dev/md0p1. And this UUID is what is in fact
in grub as the root device. That looks quite wrong.
This looks pretty release-critical, to me, as it's affecting RAID
installs of the server.
+
+ TEST CASE: The above problem should arise when attempting a RAID install
+ on any disk whose size is between 1048576*n+512 and 1048576*n+65535
+ bytes, for integer values of n. In order to reproduce this, the root
+ filesystem should be created on a RAID array whose member devices extend
+ all the way to the end of the disk (i.e. accept the default size for the
+ partition in the installer).
** Changed in: partman-base (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: partman-base (Ubuntu Lucid)
Status: Confirmed => Triaged
** Also affects: grub2 (Ubuntu Maverick)
Importance: Undecided
Status: Invalid
** Also affects: partman-base (Ubuntu Maverick)
Importance: High
Assignee: Colin Watson (cjwatson)
Status: Fix Committed
** Changed in: partman-base (Ubuntu Lucid)
Status: Triaged => Fix Committed
** Changed in: partman-base (Ubuntu Maverick)
Milestone: None => ubuntu-10.10
** Changed in: partman-base (Ubuntu Lucid)
Milestone: None => ubuntu-10.04.2
--
partman sometimes creates partitions such that there is ambiguity between
whether the superblock is on the disk device or the partition device
https://bugs.launchpad.net/bugs/569900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
