Package: dmraid
Version: 1.0.0.rc14-4
Severity: critical
Justification: breaks the whole system


I upgraded dmraid from an earlier version, I don't know which one, but it was
from the pre-udev startup.

After the upgrade the boot stops at waiting for the root filesystem. I get a
busybox prompt. I figured out what to type to continue booting up:
$ modprobe dm-mirror
$ dmraid -ay
$ exit

Then I found bug 499060, message #45 which might solve my problem. So I have 
added
the first 2 missing modprobe lines to /etc/.../85_dmraid.rules file which looks 
like
this now:

# ...
RUN+="/sbin/modprobe dm-mod"
RUN+="/sbin/modprobe dm-mirror"
SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_TYPE}=="disk", 
ENV{ID_FS_USAGE}=="raid", KERNEL=="hd[a-z]|sd[a-z]", \
        RUN+="/sbin/dmraid-activate %k"

After recreating initramfs, and rebooting, I still get the busybox prompt. But 
now
I don't have to type "modprobe dm-mirror" anymore, simply executing "dmraid -ay"
works, it creates the devices under /dev/mapper/ and boot goes on. So the 
problem
is partly solved.

At the moment I have no more time to debug this further. Why dmraid is not 
executed
automatically? Any idea?

Thanks,
Peter

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dmraid depends on:
ii  libc6                        2.7-13      GNU C Library: Shared libraries
ii  libdevmapper1.02.1           2:1.02.27-3 The Linux Kernel Device Mapper use
ii  libselinux1                  2.0.65-5    SELinux shared libraries
ii  libsepol1                    2.0.30-2    Security Enhanced Linux policy lib
ii  udev                         0.125-7     /dev/ and hotplug management daemo

dmraid recommends no packages.

dmraid suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to