Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 177954 - sys-fs/mdadm requires an initscript for successful booting with baselayout-2
Summary: sys-fs/mdadm requires an initscript for successful booting with baselayout-2
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-10 18:12 UTC by Adam James
Modified: 2007-10-03 09:09 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
raid initscript for baselayout-2 (raid,530 bytes, text/plain)
2007-05-10 18:15 UTC, Adam James
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adam James 2007-05-10 18:12:02 UTC
>=sys-apps/baselayout-2.0.0_alpha2 no longer directly initialises the volume addons located in /lib/rcscripts/addons.

The solution is to provide an initscript to be run at boot that starts the raid addon.

Further background info in bugs #177100 and #175983.
Comment 1 Adam James 2007-05-10 18:15:38 UTC
Created attachment 118774 [details]
raid initscript for baselayout-2

Had to add lvm to `before', else lvm would try to start before all the raid arrays were initialised. Presumably this would be the same for other volume addons like evms?
Comment 2 Petteri Räty (RETIRED) gentoo-dev 2007-05-16 20:24:50 UTC
(In reply to comment #1)
> 
> Had to add lvm to `before', else lvm would try to start before all the raid
> arrays were initialised. Presumably this would be the same for other volume
> addons like evms? 
> 

Or document RC_USE="raid" to conf.d/lvm 
Comment 3 Roy Marples (RETIRED) gentoo-dev 2007-05-16 20:32:09 UTC
Right, the volume init scripts should not depend on each other in the script. At most provide defaults via RC_USE/RC_NEED/RC_BEFORE/RC_AFTER so the user can decide the correct order.
Comment 4 Adam James 2007-05-17 00:39:08 UTC
(In reply to comment #3)V
> Right, the volume init scripts should not depend on each other in the script.
> At most provide defaults via RC_USE/RC_NEED/RC_BEFORE/RC_AFTER so the user can
> decide the correct order.

How does VOLUME_ORDER from conf.d/volumes relate to this? It appears to define an order in which the addons are started, yet I cannot see where this is sourced during init.
Comment 5 Roy Marples (RETIRED) gentoo-dev 2007-05-17 06:35:15 UTC
(In reply to comment #4)
> How does VOLUME_ORDER from conf.d/volumes relate to this? It appears to define
> an order in which the addons are started, yet I cannot see where this is
> sourced during init.

It doesn't. volumes init and conf files no longer exist.
Comment 6 Duncan 2007-08-15 00:21:18 UTC
Just upgraded to baselayout-2.0.0-rc2-r1 and ran into this myself.  Worked around it temporarily with md= additions to the the kernel command line.  Now that I'm up and running again, I was able to find this bug and simply copied the lvm script to mdraid.

Suggestion:  The attachment here is called "raid".  Given the various kinds of raid, that's ambiguous.  mdraid should be suitably more descriptive, IMO.

Question:  The attachment here is slightly different than the existing lvm initscript (in rc2-r1).  Which style is current?
Comment 7 Duncan 2007-08-24 11:31:26 UTC
(In reply to comment #6)
> Suggestion:  The attachment here is called "raid".  Given the various kinds
> of raid, that's ambiguous.  mdraid should be suitably more descriptive, IMO.

Of course, as I quickly discovered, as currently written with the ${SVCNAME} placeholder, the addon script and the initscript must have the same name. <doh> Still, mdraid for both seems appropriate.
Comment 8 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2007-10-03 09:09:08 UTC
mdadm-2.6.3-r1 in the tree with this fix.