Works fine if correct Debian live-boot 3.0 practices are followed (i.e. no
putting / in live-persistence.conf)

Hi,

thanks a lot for taking care of this bug report! Please feel free to close this 
issue if you think it's known to be working fine nowadays. If you think we could 
improve existing documentation feel free to edit the wiki pages or send us any 
patches. Thanks!

regards,
Mika

Hi Charles et al.,

"Charles A. Hewson" <bts@bts.grml.org> writes:

> Charles A. Hewson <cahewson@eskimo.com> added the comment:
>
> Will,
>
> Please post the contents of live-persistence.conf file in the root of
> 'custom-ov' partition.
>
> Charles
>
> ----------
> priority:  -> bug
> status: unread -> chatting

I just wanted to close this old bug.  I had been trying to use live-boot
3.0 persistence just like the old live-boot 2.0 "live-rw" option,
i.e. to persist everything.  I have since seen the error of my ways,
with the help of the Debian Live manual telling me that is no longer
supported.

Am now happily using both a 2012.05 persistent system and a
grml-sid daily build with persistence.  Both working smoothly.

Best,

-- 
Will
I use grml (http://grml.org/)

Will,

Please post the contents of live-persistence.conf file in the root of
'custom-ov' partition.

Charles

Hello,

When trying to use the persistence features of Grml 2012.05, I
encountered the following issue.

Steps to reproduce:

1. Format a flash drive as described in Grml wiki article
( http://wiki.grml.org/doku.php?id=persistency ).  The first partition
will be VFAT with grml32 and grml64 installed via grml2usb, the second
partition will be ext2 under LUKS encryption, labelled either `full-ov'
(to attempt a full persistent overlay) or `custom-ov' (partial overlay).

2. Boot a grml from the flash drive with the bootoptions "persistence
persistence-encryption=luks".

Expected result:

Grml boots into persistent mode, with the overlay partition mounted to
the Aufs filesystem.

What actually happens:

- If attempting with `full-ov' partition: Grml does try to search for
  overlay partitions (it tried all the LUKS volumes it could find on my
  system, as in 2011.12 release), but it then complains about not being
  able to move /overlay to /root/live/overlay and does not actually
  mount the partition.

- If attempting with `custom-ov' partition (with live-persistence.conf
  of one line, telling it to persist / directory), again Grml searches
  LUKS volumes, but then after unlocking the one containing my custom-ov
  partition, it complains of wrong root partition and drops to recovery
  shell.

(I may have been abusing the custom-ov settings by trying to get it to
mount root as if it were full-ov, but that's ultimately what I want; I've
been using full persistency with Grml for a few years now and I find it
useful.)

Please find attached output from grml-hwinfo (running on persistent
grml-2011.12).

Best,
Will