On Fri, August 11, 2006 7:23, Mike Kasick said: > raid1: raid set md0 active with 2 out of 2 mirrors > mdadm: /dev/md/0 has been started with 2 drives. > Success: success > Done. > Volume group "ep.root" not found > /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 147: panic: > not found > Command failed: Error opening device: No such file or directory > /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 196: cannot > open /dev/mapper/crypt0: No such file > /scripts/local-top/cryptroot: fstype not recognized, bad password or > options? > Command failed: Error opening device: No such file or directory > /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 196: cannot > open /dev/mapper/crypt0: No such file > /scripts/local-top/cryptroot: fstype not recognized, bad password or > options? > Command failed: Error opening device: No such file or directory > /scripts/local-top/cryptroot: /scripts/local-top/cryptroot: 196: cannot > open /dev/mapper/crypt0: No such file > /scripts/local-top/cryptroot: fstype not recognized, bad password or > options?
I see...there are two problems here 1) The initramfs script doesn't source the file with the panic function 2) It seems to not find your md0 device Could you please try a boot and add "break" to the kernel command line which will drop you into a rescue shell. Then report back with the contents of /conf/conf.d/cryptroot? Regards, David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
