On 05/09/14 11:38, Ian Campbell wrote:
On Thu, 2014-09-04 at 07:02 -0400, Li, Peng wrote:
Thanks for looking into this. Here's output.
Strange, that all looks like I would expect so I'm not sure why it isn't
working.
I've got a dmesg for the non-working case in the thread but could you
post
On Sun, 2014-09-07 at 15:56 +0100, Tim Fletcher wrote:
On 05/09/14 11:38, Ian Campbell wrote:
On Thu, 2014-09-04 at 07:02 -0400, Li, Peng wrote:
Thanks for looking into this. Here's output.
Strange, that all looks like I would expect so I'm not sure why it isn't
working.
I've got a
On 2014-09-07 11:35, Ian Campbell wrote:
On Fri, 2014-09-05 at 10:49 -0400, Li, Peng wrote:
Here's dmesg out put. Let me know whether there's info you are looking
for.
It's what I asked for but not actually what I wanted, sorry.
What meant to ask for was the serial console log, i.e. with all
On 2014-09-05 06:38, Ian Campbell wrote:
On Thu, 2014-09-04 at 07:02 -0400, Li, Peng wrote:
Thanks for looking into this. Here's output.
Strange, that all looks like I would expect so I'm not sure why it
isn't
working.
I've got a dmesg for the non-working case in the thread but could you
On 2014-09-04 04:32, Ian Campbell wrote:
On Mon, 2014-09-01 at 11:46 -0400, Li, Peng wrote:
HI Tim,
I am glad to report that, it's now working. Many thanks to Tim
and Ian as well.Peng
2. The setting was not stayed and we ended up on /dev/ram situation
again.
To make the change in
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=0xa0,0x90 ramdisk=34816
now I issued boot.
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=0xa0,0x90
On 2014-08-31 17:21, Ian Campbell wrote:
On Sun, 2014-08-31 at 22:16 +0100, Tim Fletcher wrote:
I think the root= here will be overridden by the flash-kernel hook
in
the initrd (the script I pointed to earlier). A better bet might be
to
hack that to override the root to /dev/VG01/root or
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
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
HI Tim,
I am glad to report that, it's now working. Many thanks to Tim
and Ian as well.Peng
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
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
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
On 31/08/14 21:16, Li, Peng wrote:
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?
This one, the setenv command only changes the setting in memory, if this
works then you will need to save it to flash afterwards
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
On Sun, 2014-08-31 at 21:06 +0100, 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
On 31/08/14 22:11, Ian Campbell wrote:
On Sun, 2014-08-31 at 21:06 +0100, 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
On 31/08/14 22:21, Ian Campbell wrote:
On Sun, 2014-08-31 at 22:16 +0100, Tim Fletcher wrote:
I'm pretty sure that even without the added complication
of LUKS / RAID / LVM a normal debian install would fail with
root=/dev/ram
It should work due to the initrd override, that override exists
On 16/08/14 12:00, peng wrote:
[0.00] Kernel command line: console=ttyS0,115200 root=/dev/ram
initrd=0xa0,0x90 ramdisk=34816
I think that is your problem, change this to be the root partition
inside LVM
--
Tim Fletcher t...@night-shade.org.uk
--
To UNSUBSCRIBE, email to
On 30/08/14 14:38, Li, Peng wrote:
HI Tim,
Can you elaborate a bit? After installion, I didn't put these in myself.
How do it do it?
If you can get a console on the device then hand boot it with the
correct root= setting, let the system boot and then run:
update-initramfs -k all -u
And
HI Tim,
Can you elaborate a bit? After installion, I didn't put these in myself.
How do it do it?
Was it supposed to be done by installer correctlying point correct root
device?
thanks
peng
On 2014-08-30 04:48, Tim Fletcher wrote:
On 16/08/14 12:00, peng wrote:
[0.00] Kernel
On Sat, 2014-08-30 at 14:59 +0100, Tim Fletcher wrote:
On 30/08/14 14:38, Li, Peng wrote:
HI Tim,
Can you elaborate a bit? After installion, I didn't put these in myself.
How do it do it?
If you can get a console on the device then hand boot it with the
correct root= setting, let the
To: debian-arm@lists.debian.org debian-arm@lists.debian.org
Subject: Re: QNAP 219 P II, Luks, Debian
From: Björn Wetterbom bj...@wetterbom.se
Date: Thu, 14 Aug 2014 09:12:50 +0200
Message-id:
cajbciayp8izmlo_gemsuqlsxlpkrs0fwlq8mbaws+ri2f0h...@mail.gmail.com
In-reply
On Thu, Aug 14, 2014 at 12:09 AM, peng li...@f2f10.com wrote:
So, here's my test.
1. Sole relying U-boot/kernel/initramd, with /root on hard disk, I can
enter passphrase for luks (for /root), but will land in shell and complain
lacking of /dev/ram.
2. Creating a seperate /boot either on
On 2014-08-09 14:17, peng wrote:
Hi All,
I followed http://www.cyrius.com/debian/kirkwood/qnap/ts-219/ and
converted my NAS to Debian. I tried the following,
1. raid0 (1G) as swap(encrypted as well with random key) and raid1
(rest of 2x1T); luks on raid1; lvm on luks; /root and /home on lvm
2.
On Sat, Aug 9, 2014 at 8:17 PM, peng li...@f2f10.com wrote:
Hi All,
I followed http://www.cyrius.com/debian/kirkwood/qnap/ts-219/ and
converted my NAS to Debian. I tried the following,
1. raid0 (1G) as swap(encrypted as well with random key) and raid1 (rest
of 2x1T); luks on raid1; lvm on
Hi All,
I followed http://www.cyrius.com/debian/kirkwood/qnap/ts-219/ and
converted my NAS to Debian. I tried the following,
1. raid0 (1G) as swap(encrypted as well with random key) and raid1 (rest
of 2x1T); luks on raid1; lvm on luks; /root and /home on lvm
2. raid0 (1G) and raid1 (rest of
27 matches
Mail list logo
