On Mon, Sep 03, 2007 at 08:44:10PM +0200, maximilian attems wrote: > [ please use reportbug in furture it adds important info ] ...and add python to my system... grrr :) > On Mon, 03 Sep 2007, Mario 'BitKoenig' Holbe wrote: > > using a device name like /dev/md/0 or /dev/md/root as root device breaks > hmm that's partitioned md, or is this still the old devfs naming scheme? Well... mdadm knows two 'standard' naming schemes /dev/mdNN and /dev/md/NN for non-partitioned arrays - probably the latter from devfs times, yes - and /dev/md_dNN and /dev/md/dNN for 2.6 partitioned arrays. Furthermore, mdadm adds some "auto" functionality which is expected to be used to create device entries with more meaningful names like /dev/md/root. In this case it was a non-partitioned raid which i just tried to name more meaningful. I tried both - first to rename my array to /dev/md/root and since this didn't work I went a step back and tried to name it /dev/md/0 which didn't work as well. > please post output of > cat /proc/cmdline > sed 's/#.*$//;/^[[:space:]]*$/d' /etc/initramfs-tools/initramfs.conf > find /sys/block Would not help you, since I reverted the changes to get back a bootable system :) Kernel command line would most likely have contained something like root=97F (lilo), initramfs.conf is unmodified: holbe@darkside:/home/holbe% md5sum /etc/initramfs-tools/initramfs.conf b155f3c78e63f9779ccf77ff77fcbb5d /etc/initramfs-tools/initramfs.conf holbe@darkside:/home/holbe% grep /etc/initramfs-tools/initramfs.conf /var/lib/dpkg/status /etc/initramfs-tools/initramfs.conf b155f3c78e63f9779ccf77ff77fcbb5d holbe@darkside:/home/holbe% and /sys/block would most likely have contained something like a md127 directory, would the system have booted :) Mario -- <delta> talk softly and carry a keen sword
Attachment:
signature.asc
Description: Digital signature