Hi there, I am writing in this bug cause noone seems to be able to help me in the aforementioned #427514 and #428399.
I have the same issues on a RAID 1 system. I'll copy paste all the info I gathered by reading the previous messages. -------start-------- I found this bug and I think that it's what's blocking my report #427514. I guess my 2.6.20 works because its initramfs has been created with the old version, while the newer kernels don't because of initramfs-tools = 0.88. Anyway, I have checked what has been suggested in the thread: /lib/udev/vol_id -t /dev/md0 and the output was LVM2_member To my surprise, since I never had LVM on this machine. In #427972 it was suggested that it could be the partitioner's fault: this machine has been partitioned only once at install time, with the d-i. Should this be reported against d-i or against (I think) parted? It is potentially very very troublesome... Anyway, I have tried to blank the sectors of the two partitions member of /dev/md0 as well as /dev/md0 itself, but with no luck, the output is still the same and the system does not boot. Is there any additional idea? It's worth noticing that if I mount manually the root: mount -t ext3 /dev/md0 /root and then exit the initramfs, the system boots just fine. That's why I think it's the same issue as the one of the OP here. -----------end---------- Thanks for any help, please ask for any additional info you might need! -- Campbell's Law: Nature abhors a vacuous experimenter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
