| 2010-04-25 20:05:50 |
Dustin Kirkland |
bug |
|
|
added bug |
| 2010-04-25 20:06:07 |
Dustin Kirkland |
mdadm (Ubuntu): importance |
Undecided |
High |
|
| 2010-04-25 20:06:21 |
Dustin Kirkland |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-04-25 20:06:21 |
Dustin Kirkland |
bug task added |
|
mdadm (Ubuntu Lucid) |
|
| 2010-04-25 20:06:32 |
Dustin Kirkland |
mdadm (Ubuntu Lucid): milestone |
|
ubuntu-10.04 |
|
| 2010-04-25 20:13:28 |
Dustin Kirkland |
bug task added |
|
grub2 (Ubuntu) |
|
| 2010-04-28 07:12:11 |
HX_unbanned |
mdadm (Ubuntu Lucid): status |
New |
Invalid |
|
| 2010-05-01 16:17:43 |
Dustin Kirkland |
mdadm (Ubuntu): status |
Invalid |
Confirmed |
|
| 2010-05-01 16:17:50 |
Dustin Kirkland |
mdadm (Ubuntu Lucid): status |
Invalid |
Confirmed |
|
| 2010-05-09 21:42:53 |
Dustin Kirkland |
mdadm (Ubuntu): assignee |
|
Colin Watson (cjwatson) |
|
| 2010-05-10 07:11:23 |
Master Jason |
removed subscriber Master Jason |
|
|
|
| 2010-05-12 20:56:19 |
Dustin Kirkland |
mdadm (Ubuntu Lucid): assignee |
|
Colin Watson (cjwatson) |
|
| 2010-07-05 00:40:05 |
Steve Langasek |
mdadm (Ubuntu Lucid): milestone |
ubuntu-10.04 |
|
|
| 2010-07-05 00:40:14 |
Steve Langasek |
mdadm (Ubuntu): milestone |
ubuntu-10.04 |
|
|
| 2010-07-14 13:12:31 |
Stu Thompson |
bug |
|
|
added subscriber Stu Thompson |
| 2010-08-15 21:32:21 |
Unlogic |
bug |
|
|
added subscriber Unlogic |
| 2010-08-19 09:13:36 |
Eduard Wulff |
bug |
|
|
added subscriber Eduard Wulff |
| 2010-08-21 19:20:03 |
scottgun |
bug |
|
|
added subscriber scottgun |
| 2010-08-22 05:30:01 |
Plutocrat |
bug |
|
|
added subscriber Plutocrat |
| 2010-08-22 18:46:36 |
Guido Scalise |
bug |
|
|
added subscriber Guido Scalise |
| 2010-09-03 06:39:53 |
Thierry Carrez |
tags |
|
server-mro |
|
| 2010-09-03 08:13:25 |
Jean-Luc Boss |
bug |
|
|
added subscriber Jean-Luc Boss |
| 2010-09-07 07:03:03 |
D_A_N_K_O |
bug |
|
|
added subscriber D_A_N_K_O |
| 2010-09-08 10:43:53 |
Stefan Lesicnik |
bug |
|
|
added subscriber Stefan Lesicnik |
| 2010-09-16 15:46:33 |
hovis |
bug |
|
|
added subscriber Richard Hosking |
| 2010-09-20 12:00:39 |
Luigi Messina |
bug |
|
|
added subscriber Luigi Messina |
| 2010-09-22 10:28:02 |
Alvin |
bug |
|
|
added subscriber Alvin |
| 2010-09-28 20:10:14 |
Colin Watson |
grub2 (Ubuntu): status |
New |
Invalid |
|
| 2010-09-28 20:10:31 |
Colin Watson |
grub2 (Ubuntu Lucid): status |
New |
Invalid |
|
| 2010-09-28 20:11:14 |
Colin Watson |
affects |
mdadm (Ubuntu) |
partman-base (Ubuntu) |
|
| 2010-09-28 20:11:14 |
Colin Watson |
partman-base (Ubuntu): status |
Confirmed |
In Progress |
|
| 2010-09-28 20:15:37 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/partman-base/ubuntu |
|
| 2010-09-28 20:15:40 |
Colin Watson |
summary |
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 |
|
| 2010-09-28 20:18:11 |
Colin Watson |
description |
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
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. |
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
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). |
|
| 2010-09-28 20:18:38 |
Colin Watson |
partman-base (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2010-09-28 20:18:40 |
Colin Watson |
partman-base (Ubuntu Lucid): status |
Confirmed |
Triaged |
|
| 2010-09-28 20:19:05 |
Colin Watson |
nominated for series |
|
Ubuntu Maverick |
|
| 2010-09-28 20:19:05 |
Colin Watson |
bug task added |
|
grub2 (Ubuntu Maverick) |
|
| 2010-09-28 20:19:05 |
Colin Watson |
bug task added |
|
partman-base (Ubuntu Maverick) |
|
| 2010-09-28 20:19:15 |
Colin Watson |
partman-base (Ubuntu Lucid): status |
Triaged |
Fix Committed |
|
| 2010-09-28 20:21:53 |
Colin Watson |
partman-base (Ubuntu Maverick): milestone |
|
ubuntu-10.10 |
|
| 2010-09-28 20:21:57 |
Colin Watson |
partman-base (Ubuntu Lucid): milestone |
|
ubuntu-10.04.2 |
|
| 2010-09-28 20:24:21 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/partman-base/lucid-proposed |
|
| 2010-10-01 06:48:13 |
Launchpad Janitor |
partman-base (Ubuntu Maverick): status |
Fix Committed |
Fix Released |
|
| 2010-10-01 07:20:50 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/partman-base |
|
| 2010-10-11 17:41:18 |
Alf Gaida |
bug |
|
|
added subscriber Alf Gaida |
| 2010-10-18 05:46:16 |
Crimson_Fox |
removed subscriber Crimson_Fox |
|
|
|
| 2010-11-03 09:32:29 |
Launchpad Janitor |
branch linked |
|
lp:debian/sid/partman-base |
|
| 2010-11-05 19:37:28 |
dahias |
bug |
|
|
added subscriber dahias |
| 2010-12-06 16:12:16 |
Colin Watson |
partman-base (Ubuntu Lucid): status |
Fix Committed |
In Progress |
|
| 2010-12-06 16:14:16 |
Colin Watson |
description |
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
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). |
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
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).
To validate this from -proposed (once available), please note that you will need to use a netboot installation image and boot with apt-setup/proposed=true on the kernel command line. |
|
| 2010-12-10 17:49:11 |
Martin Pitt |
partman-base (Ubuntu Lucid): status |
In Progress |
Fix Committed |
|
| 2010-12-10 17:49:19 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2010-12-10 17:49:23 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2010-12-10 17:49:29 |
Martin Pitt |
tags |
server-mro |
server-mro verification-needed |
|
| 2010-12-10 18:25:46 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/lucid-proposed/partman-base |
|
| 2011-01-26 06:22:24 |
Martin Pitt |
tags |
server-mro verification-needed |
server-mro verification-done |
|
| 2011-01-26 09:33:12 |
Launchpad Janitor |
partman-base (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2011-09-19 21:14:46 |
Ubuntu Foundations Team Bug Bot |
tags |
server-mro verification-done |
server-mro testcase verification-done |
|
| 2012-03-03 08:29:10 |
Stefan Eggers |
bug |
|
|
added subscriber Stefan Eggers |
| 2012-12-17 09:57:14 |
Thierry Carrez |
removed subscriber Thierry Carrez |
|
|
|
