On 01/09/14 16:27, Li, Peng wrote:
On 2014-09-01 11:03, Tim Fletcher wrote:On 01/09/14 15:44, Li, Peng wrote:HI Tim/Ian, I interrupted the boot process and enterred U-boot console by pressing "enter" during boot. I put the suggested one-line, which I modified to my setting. "setenv bootargs console=ttyS0,115200 root=/dev/mapper/VG01-LVG01 initrd=0xa00000,0x900000 ramdisk=34816" now I issued "boot". It comes back asking Luks passphrase and it got into a correct system after that.That's good news, at least we have found the problemOnce I reboot it again, it goes to problem of looking for /dev/ram again. So, can you help let me know How do I do it again, to put it a permanent? Will this survive for future kernel upgrade?The first thing to try is to hand boot the system again and then run: update-initramfs -k all -u once this has finished run: flash-kernel and reboot again, if this works this is a permanent fix. If the boot doesn't work again then you will need to change a setting in u-boot but lets see if debian tools fix the problem first1. It seems "update-initramfs -k all -u" will trigger "flash-kernel" automatically. I did "flash-kernel" anyway. It may not be necessary or may cause problem?
That's fine I was just covering all the options
2. The setting was not stayed and we ended up on /dev/ram situation again.
To make the change in u-boot stay before you type boot, type saveenv That will save your changes to u-boot's flash storage
Volume group "VG01" not found Skipping volume group VG01 Unable to find LVM volume VG01/LVG01
Error about not finding the root LV, possibly from the initramfs hook Ian highlighted?
Unlocking the disk /dev/disk/by-uuid/bd88fd91-a823-4657-945c-cfec66b95a74 (md1_crypt) Enter passphrase: Reading all physical volumes. This may take a while... Found volume group "VG01" using metadata type lvm2 2 logical volume(s) in volume group "VG01" now active /scripts/local-top/cryptroot: line 1: can't open /dev/ram: no such file
cryptroot is trying to use /dev/ram
cryptsetup: md1_crypt set up successfully
done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/ram does not exist. Dropping to a shell!
For others looking at this, note the ordering of the errors does cryptroot need to be taught about the changing of root= from the initramfs hook?
-- Tim Fletcher <tim@night-shade.org.uk>