on my laptop, i am running debian testing / squeeze.
my laptops batterie lately died. when i wanted to reboot, it told me something about fsck failed and maintainance mode, and since i had to run fsck in maintainance mode the last time i bootet (other reason - doesnt matter right now), i just entered the root pw and started fsck. cuz it was pretty late i didnt really think and just answered every question with default (return). so it 'fixed' lots of stuff. then, when i tried to reboot, it hangs and shouts the following:
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write acces will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
mount: mounting /dev on /root/dev failed: No such file or directory
/init: line 253: can't open /root/dev/console: no such file
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.30-2-686 #1
[<c031ccaa>] ? panic+0x38/0xdd
[<...>] ? do_exit+.../...
[<...>] ? redirected_tty_write+.../...
[<...>] ? vfs_write+.../...
[<...>] ? do_group_exit+.../...
[<...>] ? sys_exit_group+.../...
[<...>] ? syscall_call+.../...
my setup is a encrypted LUKS partition, with /, /home and swap encrypted on /dev/sda3 and /boot unencrypted on /dev/sda2.
mounting /home, / and /boot under ubuntu 9.04 liveCD with cryptsetup works fine.
any ideas how i can get my system bootable again?
thanks in advance
on boot-up, before i have to enter my password, he shouts:
Volume group "vg0" not found
Skipping volume group vg0
Unable to find LVM volume vg0/cryptedroot
Unlocking the disk /dev/disk/by-uuid/48530bc2-3c27-4da1-8735-865c3b7f6319 (sda3_crypt)
Enter Passphrase: _
after entering password, everything i can still read is:
File descriptor 3 (/conf/conf.d/cryptroot) leaked on lvm invocation. Parent PID 683 /bin/sh
3 logical volume(s) in volime group "vg0" now active
cryptsetup: sda3_crypt setup successfully
kinit: name_to_dev_t(/dev/disk/by-uuid/d3b68c59-c294-441c-afee-e04954a170c8) = dev(254,1)
kinit: trying to resume from /dev/disk/by-uuid/d3b68c59-c294-441c-afee-e04954a170c8
then it follows the output i wrote at the top. so it seems that something is wrong with my root partition...
i think im gonna experiment with testdisk if it can do something for it. since i am able to mount it using livedisk, it should be possible to repair it somehow, shouldn't it?