Had other committments this am but here is 15:00 update from seattle.
This testing based on GRML32_testing-20120114, i386.

On Sat, 14 Jan 2012, Michael Prokop wrote:

>
> Michael Prokop <mika@grml.org> added the comment:
>
> * Charles A. Hewson wrote in grml's BTS on 20120114 / 01:29:
>
>>> Hmmmmm, did you use the "persistent" option from the boot menu which included
>>> the "persistent=nofiles" boot option setting? If so can you please retry with
>>> just "persistent" (so drop the =nofiles)?
>
>> Persistent with nofiles boots. However, nothing from cpio.gz appears after
>> boot. Adding debug=1 and log with nofiles didn't provide clues. Files
>> in cpio were created 1/9/2012.
>
> Ok
>
>> Per http://lists.debian.org/debian-live/2011/11/msg00148.html (nofiles &&
>> cryptsetup) were | are | will go away. Since I could not discern if code
>> pushed in email got into grml I droped "=nofiles".
>
> Yeah, I stumbled upon this issue on my own today and updated
> grml-live templates so they don't use persistent=nofiles any longer
> but just "persistent"
>
>> If the code ref. in email is in grml this may be issue in up stream. And,
>> our wiki page on persistent needs more work. I would draft it after I
>> verify how it now works.
>
> Yeah, the wiki page on persistent definitely needs some love!
> Would be great if you could help us on improving that.
>
>> Persistent alone (with debug=1 & log only) drops to busybox shell (screen
>> print attached). I copied live-boot.log at that point. After <ctrl>D machine
>> locks up also attached.
>
> Thanks for that, this definitely helps:
>
>  blkid -o value -s TYPE /dev/sdb4
>  FSTYPE=vfat
>  [...]
>  mount: mounting aufs on /root/ failed: Numerical argument out of domain
>
> This matches exactly http://bts.grml.org/grml/issue1079 which I
> tried to reproduce but couldn't with a recent autobuild ISO.
>
> Could you please try again with persistency using on an ext3
> filesystem instead of vfat? Do you have the mkfs.vfat command line
> available you used for creating the file system?

I normally use mkfs.vfat but used 1 & 2 below from earlier attemt to get 
usb directly bootable.

live-boot.log is under same conditions as 20120106 but with 20120114.

grml.log.2120114 doesn's show much; console warnings about not finding 
persistent root filesystem and not mounting snapshots. I will not have 
access to screen capture on virtualbox instance until monday seattle 
time. Is their a debug=? option that would save the detailed logs on 
successful boot?

> > It would be very interesting to know whether you can reproduce this
> issue with the 2012-01-14 daily ISOs that are supposed to be
> available during the next few hours.
>
>> P.S. My goal is to have b43 firmware into system early for machine where
>> that is only outside link. And, when luks persistent is automounting
>> eliminate second usb for encrypted /etc & /home.
>
> nice :)
>
> Thanks, Charles!
>
> regards,
> -mika-
>
> _____________________________________
> GRML issue tracker <bts@bts.grml.org>
> <http://bts.grml.org/grml/issue1132>
> _____________________________________
>

Charles

-- 
Charles Hewson <cahewson@eskimo.com>
Seattle, WA. U.S.A.