[Bug 1006718] [NEW] sata_sil not loaded at boot time, if driver-police is MODULES=DEP

[guenthert]

Public bug reported:

I just installed Ubuntu 12.04 LTS on a white box. After installation the
system failed to boot, as the root fs couldn't be found. I noticed that
some of the hard drives were not found and consequently the RAID5 stripe
hosting the LVM volume hosting the root fs couldn't be constructed. It
turned out that the sata_sil driver modules wasn't loaded at boot time,
hence the RAID controller (only used in JBOD mode here) wasn't
initialized at the drives attached to it not presented to the host.

I added the 'sata_sil' module to /etc/initramfs-tools/modules (along
with all the other modules loaded by the installation tool running in
rescue mode), changed the driver-policy in /etc/initramfs-tools/conf.d
/driver-policy from 'MODULES=dep' to 'MODULES=list' and rebuilt the
initramfs (using `dpkg-reconfigure linux-image-3.2.0-24-generic`. Now
the server boots successfully.

I like the idea of running the system only with the drivers needed, but
perhaps the tool deciding on which modules get in should err on the side
of a driver too much, rather than a driver too few.

--8<--
tho at paris:~$ dpkg -l|grep initramfs-tools
ii  initramfs-tools                  0.99ubuntu13                   tools for generating an initramfs
ii  initramfs-tools-bin              0.99ubuntu13                   binaries used by initramfs-tools
-->8--

hth

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1006718

Title:
  sata_sil not loaded at boot time, if driver-police is MODULES=DEP

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  I just installed Ubuntu 12.04 LTS on a white box. After installation
  the system failed to boot, as the root fs couldn't be found. I noticed
  that some of the hard drives were not found and consequently the RAID5
  stripe hosting the LVM volume hosting the root fs couldn't be
  constructed. It turned out that the sata_sil driver modules wasn't
  loaded at boot time, hence the RAID controller (only used in JBOD mode
  here) wasn't initialized at the drives attached to it not presented to
  the host.

  I added the 'sata_sil' module to /etc/initramfs-tools/modules (along
  with all the other modules loaded by the installation tool running in
  rescue mode), changed the driver-policy in /etc/initramfs-tools/conf.d
  /driver-policy from 'MODULES=dep' to 'MODULES=list' and rebuilt the
  initramfs (using `dpkg-reconfigure linux-image-3.2.0-24-generic`. Now
  the server boots successfully.

  I like the idea of running the system only with the drivers needed,
  but perhaps the tool deciding on which modules get in should err on
  the side of a driver too much, rather than a driver too few.

  --8<--
  tho at paris:~$ dpkg -l|grep initramfs-tools
  ii  initramfs-tools                  0.99ubuntu13                   tools for generating an initramfs
  ii  initramfs-tools-bin              0.99ubuntu13                   binaries used by initramfs-tools
  -->8--

  hth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1006718/+subscriptions