| 2008-08-18 17:45:15 |
ceg |
bug |
|
|
added bug |
| 2008-08-23 13:09:04 |
tricky1 |
mdadm: status |
New |
Confirmed |
|
| 2008-08-23 13:09:04 |
tricky1 |
mdadm: statusexplanation |
|
Bug still present in Alpha 4 |
|
| 2009-11-25 16:36:33 |
ceg |
summary |
home array not run when degraded on boot |
non-root raids fail to run degraded on boot |
|
| 2009-11-26 03:22:25 |
Dustin Kirkland |
removed subscriber Dustin Kirkland |
|
|
|
| 2010-03-07 16:44:00 |
ceg |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-03-07 16:47:32 |
ceg |
description |
Binary package hint: mdadm
It is said that the intrepid fix to Bug #120375 added support to mdadm and initramfs-tools for configurable booting degraded RAIDs, but a systems with /home on a degraded array doesn't come up.
The particular array needs to be "mdadm --run /dev/md1" after the fsck fails and the user is dropped to a console.
A regular init script like /etc/init.d/mdadm-degrade (run earlier than mdadm) is missing that will run necessary arrays if they are degraded.
(/usr/share/initramfs-tools/hooks/cryptroot contains code that may be usefull to determine devices that the fstab depends on.) |
Binary package hint: mdadm
It is said that the intrepid fix to Bug #120375 re-added support to mdadm and initramfs-tools for configurable booting degraded RAIDs, but a systems with /home on a degraded array doesn't come up.
The particular array needs to be "mdadm --run /dev/md1" after the fsck fails and before any user is dropped to a console.
A regular init script like /etc/init.d/mdadm-degrade (run earlier than mdadm) is missing that used to run necessary arrays if they are degraded.
(Within the ubuntu hotplug-scheme /usr/share/initramfs-tools/hooks/cryptroot contains code that may be usefull to determine devices that the fstab depends on.)
|
|
| 2010-03-14 10:47:54 |
ceg |
summary |
non-root raids fail to run degraded on boot |
degraded non-root raids are not run on boot |
|
| 2010-03-28 23:20:07 |
ceg |
description |
Binary package hint: mdadm
It is said that the intrepid fix to Bug #120375 re-added support to mdadm and initramfs-tools for configurable booting degraded RAIDs, but a systems with /home on a degraded array doesn't come up.
The particular array needs to be "mdadm --run /dev/md1" after the fsck fails and before any user is dropped to a console.
A regular init script like /etc/init.d/mdadm-degrade (run earlier than mdadm) is missing that used to run necessary arrays if they are degraded.
(Within the ubuntu hotplug-scheme /usr/share/initramfs-tools/hooks/cryptroot contains code that may be usefull to determine devices that the fstab depends on.)
|
Systems with say /home on raid won't come up booting when raid wasdegraded during downtime.
An init script like /etc/init.d/mdadm-degrade or because of the already doing that kind of watchdog functionality "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout..
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of-incomplete-array>
mdadm --incremental --run <arbitrary-member-device-of-incomplete-array>
(See https://wiki.ubuntu.com/ReliableRaid "How would you decide what device is needed?" about determining the md devices that the devices mentioned in fstab depend on.)
|
|
| 2010-03-28 23:23:18 |
ceg |
description |
Systems with say /home on raid won't come up booting when raid wasdegraded during downtime.
An init script like /etc/init.d/mdadm-degrade or because of the already doing that kind of watchdog functionality "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout..
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of-incomplete-array>
mdadm --incremental --run <arbitrary-member-device-of-incomplete-array>
(See https://wiki.ubuntu.com/ReliableRaid "How would you decide what device is needed?" about determining the md devices that the devices mentioned in fstab depend on.)
|
Systems with say /home on raid won't come up booting when raid wasdegraded during downtime.
An init script like /etc/init.d/mdadm-degrade or because of the already doing that kind of watchdog functionality "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout..
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of-incomplete-array>
mdadm --incremental --run <arbitrary-member-device-of-incomplete-array>
(See https://wiki.ubuntu.com/ReliableRaid "mountall" functionality related:" about determining the md devices that the devices mentioned in fstab depend on.)
|
|
| 2010-03-28 23:24:53 |
ceg |
summary |
degraded non-root raids are not run on boot |
degraded non-root raids don't appear on boot |
|
| 2010-03-28 23:25:57 |
ceg |
description |
Systems with say /home on raid won't come up booting when raid wasdegraded during downtime.
An init script like /etc/init.d/mdadm-degrade or because of the already doing that kind of watchdog functionality "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout..
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of-incomplete-array>
mdadm --incremental --run <arbitrary-member-device-of-incomplete-array>
(See https://wiki.ubuntu.com/ReliableRaid "mountall" functionality related:" about determining the md devices that the devices mentioned in fstab depend on.)
|
Systems with say /home on raid won't come up booting when raid was degraded during downtime.
An init script like /etc/init.d/mdadm-degrade - or because of already doing that kind of watchdog functionality - "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout.
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of-incomplete-array>
mdadm --incremental --run <arbitrary-member-device-of-incomplete-array>
(See https://wiki.ubuntu.com/ReliableRaid "mountall" functionality related:" about determining the md devices that the devices mentioned in fstab depend on.)
|
|
| 2010-03-28 23:26:30 |
ceg |
bug task added |
|
mountall (Ubuntu) |
|
| 2010-03-29 11:46:11 |
ceg |
summary |
degraded non-root raids don't appear on boot |
degraded NON-root raids never --run on boot |
|
| 2010-03-29 11:53:31 |
ceg |
description |
Systems with say /home on raid won't come up booting when raid was degraded during downtime.
An init script like /etc/init.d/mdadm-degrade - or because of already doing that kind of watchdog functionality - "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout.
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of-incomplete-array>
mdadm --incremental --run <arbitrary-member-device-of-incomplete-array>
(See https://wiki.ubuntu.com/ReliableRaid "mountall" functionality related:" about determining the md devices that the devices mentioned in fstab depend on.)
|
Systems with say /home on raid won't come up booting when raid was degraded during downtime.
An init script like /etc/init.d/mdadm-degrade - or because of already doing that kind of watchdog functionality - "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout.
Because the proper mdadm --incremental mode command is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of-incomplete-array>
mdadm --incremental --run <arbitrary-member-device-of-incomplete-array>
(See https://wiki.ubuntu.com/ReliableRaid "mountall" functionality related:" about determining the md devices that the devices mentioned in fstab depend on.)
---
The possibility that large server RAIDs may take minutes until they come up, but regular ones are quick, can be handled nicely:
"NOTICE: /dev/mdX didn't get up within the first 10 seconds.
We continue to wait up to a total of xxx seconds complying to the ATA
spec before attempting to run the array degraded.
(You can lower this timeout by setting the rootdelay= parameter.)
<counter> seconds to go.
Press escape to stop waiting and to enter a rescue shell.
|
|
| 2010-04-14 01:06:01 |
Scott James Remnant (Canonical) |
mountall (Ubuntu): status |
New |
Invalid |
|
| 2010-04-14 01:06:26 |
Scott James Remnant (Canonical) |
mountall (Ubuntu): status |
Invalid |
Triaged |
|
| 2010-04-14 01:06:37 |
Scott James Remnant (Canonical) |
mountall (Ubuntu): importance |
Undecided |
Wishlist |
|
| 2010-04-14 01:08:02 |
Scott James Remnant (Canonical) |
mountall (Ubuntu): status |
Triaged |
Incomplete |
|
| 2010-04-22 01:22:00 |
Scott James Remnant (Canonical) |
mountall (Ubuntu): status |
Incomplete |
Triaged |
|
| 2010-08-06 17:58:36 |
Paul Chaplin |
bug |
|
|
added subscriber Paul Chaplin |
| 2011-04-06 05:38:17 |
Jaakko Heinonen |
bug |
|
|
added subscriber Jaakko Heinonen |
| 2011-04-08 17:10:38 |
TheDreamer |
bug |
|
|
added subscriber TheDreamer |
| 2011-05-01 08:33:57 |
Till Ulen |
removed subscriber Alexander Konovalenko |
|
|
|
| 2012-05-19 07:22:35 |
Steve Langasek |
mountall (Ubuntu): status |
Triaged |
Invalid |
|
| 2012-05-20 05:53:18 |
Aryeh Gregor |
removed subscriber Aryeh Gregor |
|
|
|
| 2012-07-01 14:54:44 |
Hans Deragon |
bug |
|
|
added subscriber Hans Deragon |
| 2012-12-17 17:43:24 |
Grant Slater |
bug |
|
|
added subscriber Grant Slater |
