Bug 130995 - /etc/init.d/boot.loadmodules started to late in booting process
Summary: /etc/init.d/boot.loadmodules started to late in booting process
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: All SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Hannes Reinecke
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-27 13:06 UTC by Andreas Pfaller
Modified: 2006-05-23 12:46 UTC (History)
4 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Pfaller 2005-10-27 13:06:55 UTC 
/etc/init.s/boot.localfs fails to mount (non-noauto) filesystems
if they depend on a driver specified in MODULES_LOADED_ON_BOOT.
Im my opinon boot.loadmodules should be called as early as
possible in the boot process.
Comment 1 Dr. Werner Fink 2005-10-27 13:59:19 UTC 
Drivers for filesystems required for /etc/init.d/boot.localfs
should always included in INITRD_MODULES in /etc/sysconfig/kernel.

Do not forget to run mkinitrd afterwards.
Comment 2 Andreas Pfaller 2005-10-27 14:49:53 UTC 
Well, obviously this is the workaround and I am using it at the moment.
But is there any technical necessity for this? I am not talking of an
disk driver needed for access to the root file system.

I consider initrd's a maintenance nightmare since their use pushes 
configuration specific data to an fairly static location which is not
easily updated (e.g. from a remote system).
Comment 3 Hannes Reinecke 2006-02-06 16:17:44 UTC 
Kay, it should be moved prior to boot.udev, right?
And if so, would you mind doing it?
Comment 4 Kay Sievers 2006-02-06 16:23:21 UTC 
What driver is it, that needs to be specified in MODULES_LOADED_ON_BOOT?
Comment 5 Andreas Pfaller 2006-02-06 20:37:05 UTC 
A Highpoint IDE Controller (Module hpt366). In my case my /home partition
was not mounted if this module is not specified in INITRD_MODULES with
the result that no login (except root) was possible from kdm.
However switching to the console and manually mounting it worked. 

Just for info: I usually disable the Highpoint Controller (in the BIOS) before installing a new SuSE version since otherwise the Installer insists that
it is my primary boot device (which in reality is a disk connected to an
onboard via82cxxx). It also completely messes up device naming if it is 
enabled during installation. 
This probably caused it not to be included in INITRD_MODULES automatically.
Comment 6 Christian Zoz 2006-02-07 10:04:51 UTC 
Why does current boot.loadmodules require boot.localfs and boot.udev?
Comment 7 Kay Sievers 2006-02-08 19:32:57 UTC 
It's a base system decision to change the dependencies. Reassign it.
Comment 9 Andreas Jaeger 2006-02-14 11:18:14 UTC 
If it can be easily fixed, I would say fix it.

If this causes to much work, I would say fix it for 10.2.
Comment 10 Hannes Reinecke 2006-03-22 10:35:07 UTC 
I've changed the dependencies in boot.loadmodules to solely depend on boot.udev; additionally boot.localfs has now an additional dependency on boot.loadmodules.

So effectively boot.loadmodules will be started _after_ boot.udev, but before boot.localfs.
So this should be okay now.
Comment 11 Hannes Reinecke 2006-03-22 10:36:46 UTC 
Updated aaa_base package submitted to autobuild. Will be on 10.1 RC1.
Comment 12 Olaf Hering 2006-05-21 08:43:10 UTC 
Required-Start is likely wrong.
Make it Should-Start for sles10.
Comment 13 Hannes Reinecke 2006-05-23 12:46:57 UTC 
udev is mandatory for SLES10. I doubt any SLES10 installation will properly with udev deinstalled. And we certainly won't support it.