On Sun, Feb 24, 2008 at 01:20:31AM +0000, Kjö wrote: > > > cryptsetup: unknown fstype, bad password or options? > > > Command failed: Device busy > > > Command failed: Device already exists > > > cryptsetup: cryptsetup failed, bad password or options? > > > Command failed: Device already exists > > > cryptsetup: cryptsetup failed, bad password or options? > > > cryptsetup: pmaximum number of tries exceeded > > > > not sure what these things mean. > > I thing this is the problem... Seems the he's not able to mount the file system ? yeah, I agree. escpecially in light of you not being able to mount them withing busybox as well. > > > did it ever really work with '[' and ']' in the filename? if so, I'm > > shocked. > > I replaced the name of my volume group (which is the name of my computer) by > [vg]. It not the true name, sorry not to have explained that. okay. > > > Do you still have old kernel's and initrd's lying around that might > > work? That's where I"d start, get booted into an older system... > > The problem is that I tried all my kernels, and that none is working. I think > all my initrd's were updated with the not working cryptsetup, and that I'm > blocked outside of my system... my system automatically keeps one backup of the initrds. Yours might as well. Edit the initrd line in your grub boot from the grub prompt. You can use tab completion to see what initrd's are available. Mine are all of the form initrd.img-<kernel version>-<arch>.bak Hopefully that helps. Are any of the lvm tools available in the busybox? A
Attachment:
signature.asc
Description: Digital signature