Re: boot hangs on pass phrase to unock encrypted root
On Wed, 2010-01-27 at 01:23 +0000, mictlan tecutli wrote:
>
> im usiing a custom kernel, but ive also tried the 2.6.29-2-amd64 from
> debian repos and i get the same results.
2.6.29-2-amd64 doesn't seem current for any of the distributions right
now. From your versions below (iniramfs, grub) you appear to be running
squeeze/testing.
http://packages.debian.org/search?searchon=names&suite=all§ion=all&keywords=linux-image-2.6-amd64
> i also have tried single user mode with the same result
> . i also tried debian-live 64bit rescue image (on usb) which boots to
> console, and i have no keyboard their either.
> however with a debian-live with which boots X keyboard works fine.
Great, you can inspect logs, var/cache and such. Anything else funny
that might indicate udev / kernel issues? How old is this live cd?
kernel?
> i can change to console with cntrl-alt-f1 and keyboard does work.
> i just instaled a new kernel, linux-image-2.6.32-trunk-amd64 from sid,
> to see what happens with initramfs on the new kernel.
I'd suggest starting with the kernel paired with udev for your
distribution 2.6.32+23 to start.
> on install i get the following errors. the "invalid line
> in /etc/cryptab -" has always appeared but not caused any harm. the
> grub-probe error may be related to the chroot, however should be noted
> that ls /dev shows that its full of devices.
>
> Running update-initramfs.
> update-initramfs: Generating /boot/initrd.img-2.6.32-trunk-amd64
> W: Possible missing firmware /lib/firmware/rtl8168d-2.fw for module r8169
> W: Possible missing firmware /lib/firmware/rtl8168d-1.fw for module r8169
> cryptsetup: WARNING: invalid line in /etc/crypttab -
> cryptsetup: WARNING: invalid line in /etc/crypttab -
> Running update-grub.
> /usr/sbin/grub-probe: error: cannot find a device for / (is /dev
> mounted?).
> i updated my system, but it powered down, battery ran out of juice. it
> was an aptitude safe-upgrade but im not sure what all packets got
> updated. have not touched udev rules. the next time i booted is when i
> could no longer login.
Okay, this is sorta what it sounded like from the start.. bad/broken
upgrade. Correlation with an upgrade should have been the starting
point.
Using your live cd, go inspect the packages that updated/changed
using /var/log/dpkg.log and/or /var/cache/apt/archives (file
datestamps); I usually ls -al to text file and squirrel away in /root as
the next steps I suggest will flush the archives
chroot in, mount proc and any relavant fstab mount points
apt-get clean
apt-get update
apt-get upgrade (if anything happens here.. retry boot test first)
apt-get install <packagesthat changed> --reinstall
If no change (still hung), just apt-get to the versions you had before
(per your review of apt archives or dpkg.log) and see if the issue goes
away.
Likely it will be resolved by a) corrupt upgrade fix or b) reverting to
previous package set, the later which can be narrowed down easily for a
bug report as required.
Noting that you are coming from 2.6.29-2 on squeeze means your upgrade
appears to have been from mid 2009 or earlier based on changelogs;
Since the packages below are current squeeze, IMHO you probably had an
upgrade and dist-upgrade pending and didn't get to second step
Since you are unsure the upgrade finished, and given there was such a
large number of updates pending, I would guess it probably dies on a
pre/post package configuration screen. udev would certainly have had a
warning on the deprecated_sysfs kernel compatibility issues with the
newer version if this is the case.
I would have guessed you would see incomplete package updates on your
chroot and install of the sid/trunk kernel packages. Did apt or dpkg
give you any output suggesting that the upgrade did not finish?
In any event, hopefully a re-install/upgrade resolves the issue or gives
you some more insight.
>
> > More details on kernel and package versions might be helpful
>
> initramfs-tools=0.93.4
> grub=0.97-59
> udev=150-2
>
Best of luck; I am fresh out of ideas now.
Reply to: