| 2012-05-10 08:53:39 |
Peter Maloney |
bug |
|
|
added bug |
| 2012-05-10 14:45:23 |
Peter Maloney |
description |
https://help.ubuntu.com/12.04/serverguide/advanced-installation.html
The above page is missing three very important details.
1. /boot must be raid1, since it is apparently the only way to successfully boot degraded. I tested raid10, which boots until you pull any disk, and then you get either a black screen, or:
error: no such disk.
grub rescue>
So my solution was to have a separate boot raid device that is raid1, while the root system is raid10. Separate raid10s has the same problem (I had them separated already due to the metadata 0.90 not supporting large disks).
2. Tt should mention that metadata 0.90 is required on the boot raid device. I am fairly sure the installer did not do this. And from command line I fixed it by backing up the files, destroying and recreating with:
mdadm --create -e 0.90 ...
3. With a GPT partition, the installer happily continues without a bios_grub partition, which is very wrong. Manually run, the grub-install command line will produce errors and break the boot, but these don't make it to the installer for the user to see, and the system will still boot until "grub-install" is run. (This is a documentation problem, and also an installer software bug)
My system details:
lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
mdadm
3.2.3-2ubuntu1
grub-install
1.99-21ubuntu3
Linux
3.2.0-23-generic |
https://help.ubuntu.com/12.04/serverguide/advanced-installation.html
The above page is missing three very important details.
1. /boot must be raid1, since it is apparently the only way to successfully boot degraded. I tested raid10, which boots until you pull any disk, and then you get either a black screen, or:
error: no such disk.
grub rescue>
So my solution was to have a separate boot raid device that is raid1, while the root system is raid10. Separate raid10s has the same problem (I had them separated already due to the metadata 0.90 not supporting large disks).
2. It should mention that metadata 0.90 is required on the boot raid device. I am fairly sure the installer did not do this. And from command line I fixed it by backing up the files, destroying and recreating with:
mdadm --create -e 0.90 ...
3. With a GPT partition, the installer happily continues without a bios_grub partition, which is very wrong. Manually run, the grub-install command line will produce errors and break the boot, but these don't make it to the installer for the user to see, and the system will still boot until "grub-install" is run. (This is a documentation problem, and also an installer software bug)
My system details:
lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
mdadm
3.2.3-2ubuntu1
grub-install
1.99-21ubuntu3
Linux
3.2.0-23-generic |
|
| 2013-06-11 00:30:43 |
John Kim |
bug task added |
|
serverguide |
|
| 2013-06-11 00:31:02 |
John Kim |
tags |
|
serverguide |
|
| 2013-06-12 13:26:07 |
John Kim |
ubuntu-docs (Ubuntu): status |
New |
Invalid |
|
| 2013-06-12 22:43:47 |
Doug Smythies |
bug task deleted |
ubuntu-docs (Ubuntu) |
|
|
| 2017-07-25 08:09:50 |
Peter Maloney |
description |
https://help.ubuntu.com/12.04/serverguide/advanced-installation.html
The above page is missing three very important details.
1. /boot must be raid1, since it is apparently the only way to successfully boot degraded. I tested raid10, which boots until you pull any disk, and then you get either a black screen, or:
error: no such disk.
grub rescue>
So my solution was to have a separate boot raid device that is raid1, while the root system is raid10. Separate raid10s has the same problem (I had them separated already due to the metadata 0.90 not supporting large disks).
2. It should mention that metadata 0.90 is required on the boot raid device. I am fairly sure the installer did not do this. And from command line I fixed it by backing up the files, destroying and recreating with:
mdadm --create -e 0.90 ...
3. With a GPT partition, the installer happily continues without a bios_grub partition, which is very wrong. Manually run, the grub-install command line will produce errors and break the boot, but these don't make it to the installer for the user to see, and the system will still boot until "grub-install" is run. (This is a documentation problem, and also an installer software bug)
My system details:
lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
mdadm
3.2.3-2ubuntu1
grub-install
1.99-21ubuntu3
Linux
3.2.0-23-generic |
https://help.ubuntu.com/12.04/serverguide/advanced-installation.html
The above page is missing three very important details.
1. /boot must be raid1, since it is apparently the only way to successfully boot degraded. I tested raid10, which boots until you pull any disk, and then you get either a black screen, or:
error: no such disk.
grub rescue>
So my solution was to have a separate boot raid device that is raid1, while the root system is raid10. Separate raid10s has the same problem (I had them separated already due to the metadata 0.90 not supporting large disks).
2. It should mention that metadata 0.90 is required on the boot raid device (or 1.0 seems to work well on grub 2.x; I didn't test 1.9x). I sure the installer did not do this. And from command line I fixed it by backing up the files, destroying and recreating with:
mdadm --create -e 0.90 ...
3. With a GPT partition, the installer happily continues without a bios_grub partition, which is very wrong. Manually run, the grub-install command line will produce errors and break the boot, but these don't make it to the installer for the user to see, and the system will still boot until "grub-install" is run. (This is a documentation problem, and also an installer software bug)
My system details:
lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
mdadm
3.2.3-2ubuntu1
grub-install
1.99-21ubuntu3
Linux
3.2.0-23-generic |
|
| 2017-07-25 08:10:26 |
Peter Maloney |
summary |
doc boot issues: raid10 boot device will not boot when degrade; metadata 0.90 is required; bios_grub is required for GPT |
doc boot issues: raid10 boot device will not boot when degraded; metadata 0.90 is required; bios_grub is required for GPT |
|
