[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#275800: initrd-tools: raidstart fails with devfs=mount

Package: initrd-tools
Version: 0.1.74
Severity: normal

When a kernel is booted with devfs=mount, raidstart fails with "no MD
device file in /dev.".

I have built an initrd with busybox and looked at /dev in the initrd.
Of course the /dev in the initrd has been obscured by devfs. But there
is now the /dev/md directory, just like under /devfs/md. I don't
understand why raidstart can't cope with /dev/md/0.

But I certainly lack understanding of the underlying mechanisms.

BTW, the README.Debian in the devfsd package recommends adding
defvs=mount to lilo.conf. I did so, and this bugreport is the result.
I did not want to file a bug against this because I don't really
understand how this all *should* work together.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-lpc.5.k7
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages initrd-tools depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  cpio                          2.5-1.1    GNU cpio -- a program to manage ar
ii  cramfsprogs                   1.1-6      Tools for CramFs (Compressed ROM F
ii  dash                          0.5.1-3    The Debian Almquist Shell
ii  fileutils                     5.2.1-2    The GNU file management utilities 
ii  util-linux                    2.12-10    Miscellaneous system utilities

-- no debconf information

Reply to: