[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: QNAP 219 P II, Luks, Debian



HI Tim,

thanks for a quick reply. Just want to clarify one more thing. Do I do that "setenv...." by interrupting U-Boot and do it?

Or, Do I wait for encryption prompt and do it after it land on "initrd" mode after failing to locate /dev/ram.? At this moment, in a brief time, the system will reboot it self.

Much appreciated.!
peng

On 2014-08-31 16:06, Tim Fletcher wrote:
On 31/08/14 20:40, Li, Peng wrote:
Hi Ian/Tim,

Trying to make sure I understand a correct steps. I'd like to re-install
the whole system again. I do have a serial console connection.

My plan is to have a /boot on a USB disk, with a 512bits data as
passphrase from usb key. whole two disk SDA/SDB will be RAID1 with LUKS
on top. Then LVM inside luks. Then, /root and /home.

From the boot log you shared I'm almost certain the /boot on usb is
not needed for this to work, all you need to do to fix you current
install is to change the single setting in flash to make init look in
the correct place for the root disk.

The complex steps, ie finding and assembling the RAID, decrypting the
drive and finding the VG inside have all worked you have a single
problem left to solve which is the kernel commandline string.

Try on your serial console setting the following:

setenv bootargs console=ttyS0,115200 root=/dev/VG01/root
initrd=0xa00000,0x900000 ramdisk=34816

Then type boot

Note the setenv line is one line, and I've assumed the LV for your
root volume is called root.

I understand that I have to manage to change /dev/ram to /dev/??? (root
in lvm?? on top of Luks).

This is a setting that is stored in the flash along with the kernel and initrd.

--
Tim Fletcher <tim@night-shade.org.uk>


Reply to: