John G. Heim | 17 Apr 05:07 2015
Picon

grml virtualbox

I am trying to create a grml virtualbox virtual machine. My problem is 
that it hangs during the boot from the live iso image. I'm blind so I 
can't see the screen but I took a screen shot and ran an ocr on it.  The 
last 2 lines say this:

a it ganr sgsten hangs nan, disahie udeu uith buutuptiun "nuudeu .
a starting the hutplug euents dispatcher: udeud.

When grml is booting, at some point it says something like, "If your 
system hangs now disable something or other". I am thinking that is what 
is happening. But the ocr is so bad I don't know what to disable. Can 
somebody tell me what that whole message says?

I created the vm with vboxmanage at the command line. So there might be 
something wrong with the vm itself. Here is the output from showvminfo 
if it helps:

Name:            grml
Groups:          /
Guest OS:        Debian (32 bit)
UUID:            0c3d9b10-476c-4d44-984c-672223bd593d
Config file:     /home/john/VirtualBox VMs/grml/grml.vbox
Snapshot folder: /home/john/VirtualBox VMs/grml/Snapshots
Log folder:      /home/john/VirtualBox VMs/grml/Logs
Hardware UUID:   0c3d9b10-476c-4d44-984c-672223bd593d
Memory size:     1024MB
Page Fusion:     off
VRAM size:       128MB
CPU exec cap:    100%
HPET:            off
(Continue reading)

Michael Hekel | 9 Apr 11:22 2015
Picon
Picon

Persisteny feature not working

Hi,
 
I followed the instructions on: http://wiki.grml.org/doku.php?id=persistency
 
Some data:
 
blkid:
/dev/sr0: UUID="2014-11-14-14-44-49-00" LABEL="grml64-full 2014.11" TYPE="iso9660" PTUUID="30667644" PTTYPE="dos"
/dev/sda1: LABEL="persistence" UUID="6eb587f3-5f92-4be4-812b-7575f2738145" TYPE="ext2" PARTUUID="dff7adbd-01"
/dev/loop0: TYPE="squashfs"
 
persistence.conf:
/ union
 
grep persistence /var/log/live/boot.log:
+ LIVE_BOOT_CMDLINE=BOOT_IMAGE=/boot/grml64full/vmlinuz initrd=/boot/grml64full/initrd.img boot=live live-media-path=/live/grml64-full/ bootid=grml64full201411 apm=power-off vga=791 nomce persistence debug=1
+ overlays=live-rw home-rw persistence custom-ov
+ find_persistence_media live-rw home-rw persistence custom-ov
+ overlays=live-rw home-rw persistence custom-ov
+ probe_for_gpt_name live-rw home-rw persistence custom-ov /dev/sda1
+ overlays=live-rw home-rw persistence custom-ov
+ probe_for_fs_label live-rw home-rw persistence custom-ov /dev/sda1
+ overlays=live-rw home-rw persistence custom-ov
+ [ persistence = live-rw ]
+ [ persistence = home-rw ]
+ [ persistence = persistence ]
+ echo persistence=/dev/sda1
+ [ persistence = custom-ov ]
+ result=persistence=/dev/sda1
+ [ -n persistence=/dev/sda1 ]
+ ret= persistence=/dev/sda1
+ probe_for_gpt_name live-rw home-rw persistence custom-ov /dev/sda
+ overlays=live-rw home-rw persistence custom-ov
+ probe_for_fs_label live-rw home-rw persistence custom-ov /dev/sda
+ overlays=live-rw home-rw persistence custom-ov
+ [  = persistence ]
+ probe_for_file_name live-rw home-rw persistence custom-ov /dev/sda
+ overlays=live-rw home-rw persistence custom-ov
+ mount_persistence_media /dev/sda probe
+ backing=/live/persistence/sda
+ mkdir -p /live/persistence/sda
+ mount -t unknown -o rw,noatime /dev/sda /live/persistence/sda
mount: mounting /dev/sda on /live/persistence/sda failed: No such device
+ rmdir /live/persistence/sda
+ probe_for_gpt_name live-rw home-rw persistence custom-ov /dev/sr0
+ overlays=live-rw home-rw persistence custom-ov
+ probe_for_fs_label live-rw home-rw persistence custom-ov /dev/sr0
+ overlays=live-rw home-rw persistence custom-ov
+ [ grml64-full 2014.11 = persistence ]
+ probe_for_file_name live-rw home-rw persistence custom-ov /dev/sr0
+ overlays=live-rw home-rw persistence custom-ov
+ mount_persistence_media /dev/sr0 probe
+ backing=/live/persistence/sr0
+ mkdir -p /live/persistence/sr0
+ [ /live/persistence/sr0 != /live/medium ]
+ mount --move /live/medium /live/persistence/sr0
+ mount -o remount,rw,noatime /live/persistence/sr0
+ echo /live/persistence/sr0
+ backing=/live/persistence/sr0
+ [ -z /live/persistence/sr0 ]
+ path=/live/persistence/sr0//live-rw
+ [ -f /live/persistence/sr0//live-rw ]
+ path=/live/persistence/sr0//home-rw
+ [ -f /live/persistence/sr0//home-rw ]
+ path=/live/persistence/sr0//persistence
+ [ -f /live/persistence/sr0//persistence ]
+ path=/live/persistence/sr0//custom-ov
+ [ -f /live/persistence/sr0//custom-ov ]
+ umount /live/persistence/sr0
+ rmdir /live/persistence/sr0
+ [ -n  persistence=/dev/sda1 ]
+ echo persistence=/dev/sda1
+ echo persistence=/dev/sda1
+ media=persistence=/dev/sda1
+ mount_persistence_media /dev/sda1
+ backing=/live/persistence/sda1
+ mkdir -p /live/persistence/sda1
+ mount -t ext2 -o rw,noatime /dev/sda1 /live/persistence/sda1
+ echo /live/persistence/sda1
+ backing=/live/persistence/sda1
+ [ -z /live/persistence/sda1 ]
+ [ -r /live/persistence/sda1/persistence.conf ]
+ include_list=/live/persistence/sda1/persistence.conf
+ close_persistence_media /dev/sda1
+ backing=/live/persistence/sda1
+ [ -d /live/persistence/sda1 ]
+ umount /live/persistence/sda1
+ rmdir /live/persistence/sda1
+ newmount=/root/lib/live/mount/persistence/sr0
+ mkdir -p /root/lib/live/mount/persistence/sr0
+ mount -o move /live/persistence/sr0 /root/lib/live/mount/persistence/sr0
 
 
Any hints?
 
Thanks,
   Michael
<div><div>
<div>Hi,</div>

<div>&nbsp;</div>

<div>I followed the instructions on: http://wiki.grml.org/doku.php?id=persistency</div>

<div>&nbsp;</div>

<div>Some data:</div>

<div>&nbsp;</div>

<div>blkid:</div>

<div>
<div>/dev/sr0: UUID="2014-11-14-14-44-49-00" LABEL="grml64-full 2014.11" TYPE="iso9660" PTUUID="30667644" PTTYPE="dos"<br>
/dev/sda1: LABEL="persistence" UUID="6eb587f3-5f92-4be4-812b-7575f2738145" TYPE="ext2" PARTUUID="dff7adbd-01"<br>
/dev/loop0: TYPE="squashfs"</div>

<div>&nbsp;</div>

<div>persistence.conf:</div>

<div>
<div>/ union</div>

<div>&nbsp;</div>

<div>grep persistence /var/log/live/boot.log:</div>

<div>
<div>+ LIVE_BOOT_CMDLINE=BOOT_IMAGE=/boot/grml64full/vmlinuz initrd=/boot/grml64full/initrd.img boot=live live-media-path=/live/grml64-full/ bootid=grml64full201411 apm=power-off vga=791 nomce persistence debug=1<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ find_persistence_media live-rw home-rw persistence custom-ov<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ probe_for_gpt_name live-rw home-rw persistence custom-ov /dev/sda1<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ probe_for_fs_label live-rw home-rw persistence custom-ov /dev/sda1<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ [ persistence = live-rw ]<br>
+ [ persistence = home-rw ]<br>
+ [ persistence = persistence ]<br>
+ echo persistence=/dev/sda1<br>
+ [ persistence = custom-ov ]<br>
+ result=persistence=/dev/sda1<br>
+ [ -n persistence=/dev/sda1 ]<br>
+ ret= persistence=/dev/sda1<br>
+ probe_for_gpt_name live-rw home-rw persistence custom-ov /dev/sda<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ probe_for_fs_label live-rw home-rw persistence custom-ov /dev/sda<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ [&nbsp; = persistence ]<br>
+ probe_for_file_name live-rw home-rw persistence custom-ov /dev/sda<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ mount_persistence_media /dev/sda probe<br>
+ backing=/live/persistence/sda<br>
+ mkdir -p /live/persistence/sda<br>
+ mount -t unknown -o rw,noatime /dev/sda /live/persistence/sda<br>
mount: mounting /dev/sda on /live/persistence/sda failed: No such device<br>
+ rmdir /live/persistence/sda<br>
+ probe_for_gpt_name live-rw home-rw persistence custom-ov /dev/sr0<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ probe_for_fs_label live-rw home-rw persistence custom-ov /dev/sr0<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ [ grml64-full 2014.11 = persistence ]<br>
+ probe_for_file_name live-rw home-rw persistence custom-ov /dev/sr0<br>
+ overlays=live-rw home-rw persistence custom-ov<br>
+ mount_persistence_media /dev/sr0 probe<br>
+ backing=/live/persistence/sr0<br>
+ mkdir -p /live/persistence/sr0<br>
+ [ /live/persistence/sr0 != /live/medium ]<br>
+ mount --move /live/medium /live/persistence/sr0<br>
+ mount -o remount,rw,noatime /live/persistence/sr0<br>
+ echo /live/persistence/sr0<br>
+ backing=/live/persistence/sr0<br>
+ [ -z /live/persistence/sr0 ]<br>
+ path=/live/persistence/sr0//live-rw<br>
+ [ -f /live/persistence/sr0//live-rw ]<br>
+ path=/live/persistence/sr0//home-rw<br>
+ [ -f /live/persistence/sr0//home-rw ]<br>
+ path=/live/persistence/sr0//persistence<br>
+ [ -f /live/persistence/sr0//persistence ]<br>
+ path=/live/persistence/sr0//custom-ov<br>
+ [ -f /live/persistence/sr0//custom-ov ]<br>
+ umount /live/persistence/sr0<br>
+ rmdir /live/persistence/sr0<br>
+ [ -n&nbsp; persistence=/dev/sda1 ]<br>
+ echo persistence=/dev/sda1<br>
+ echo persistence=/dev/sda1<br>
+ media=persistence=/dev/sda1<br>
+ mount_persistence_media /dev/sda1<br>
+ backing=/live/persistence/sda1<br>
+ mkdir -p /live/persistence/sda1<br>
+ mount -t ext2 -o rw,noatime /dev/sda1 /live/persistence/sda1<br>
+ echo /live/persistence/sda1<br>
+ backing=/live/persistence/sda1<br>
+ [ -z /live/persistence/sda1 ]<br>
+ [ -r /live/persistence/sda1/persistence.conf ]<br>
+ include_list=/live/persistence/sda1/persistence.conf<br>
+ close_persistence_media /dev/sda1<br>
+ backing=/live/persistence/sda1<br>
+ [ -d /live/persistence/sda1 ]<br>
+ umount /live/persistence/sda1<br>
+ rmdir /live/persistence/sda1<br>
+ newmount=/root/lib/live/mount/persistence/sr0<br>
+ mkdir -p /root/lib/live/mount/persistence/sr0<br>
+ mount -o move /live/persistence/sr0 /root/lib/live/mount/persistence/sr0</div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div>Any hints?</div>

<div>&nbsp;</div>

<div>Thanks,</div>

<div>&nbsp;&nbsp; Michael</div>
</div>
</div>
</div>
</div></div>
Eric Thirolle | 7 Jan 17:07 2015
Picon

Remove dmraid package from GRML?

I noticed the following error printed to console during bootup of my custom GRML Live CD:

modprobde: module dm-raid45 not found in modules.dep

I did a bit of research into this module, and found it is called "dmraid" in the Debian package repositories. This package is available for wheezy/jessie, but not installed by default. However, "dmraid" *is* included in GRML's FAI classes:

# grep -R dmraid /etc/grml/fai/*
/etc/grml/fai/config/package_config/GRML_XL:dmraid
/etc/grml/fai/config/package_config/GRML_MEDIUM:dmraid
/etc/grml/fai/config/package_config/GRML_SMALL:dmraid
/etc/grml/fai/config/package_config/GRML_FULL:dmraid

The dmraid package is responsible for support for so-called "ATARAID", which is RAID for IDE drives provided by a number of old hardware RAID cards (details here: https://packages.debian.org/wheezy/dmraid & https://www.freebsd.org/cgi/man.cgi?query=ataraid&sektion=4&manpath=FreeBSD+8.3-RELEASE).

Given how old this RAID driver is... should dmraid be removed from the GRML FAI classes? Or is there something else that needs to be done to correct the "module dm-raid45 not found in modules.dep" error on the custom Live CD? 

Thanks!

Eric
<div><div dir="ltr">I noticed the following error printed to console during bootup of my custom GRML Live CD:<div><br></div>
<blockquote><div>modprobde: module dm-raid45 not found in modules.dep</div></blockquote>
<div><br></div>
<div>I did a bit of research into this module, and found it is called "dmraid" in the Debian package repositories. This package is available for wheezy/jessie, but not installed by default. However, "dmraid" *is* included in GRML's FAI classes:</div>
<div><br></div>
<blockquote>
<div><div># grep -R dmraid /etc/grml/fai/*</div></div>
<div><div>/etc/grml/fai/config/package_config/GRML_XL:dmraid</div></div>
<div><div>/etc/grml/fai/config/package_config/GRML_MEDIUM:dmraid</div></div>
<div><div>/etc/grml/fai/config/package_config/GRML_SMALL:dmraid</div></div>
<div><div>/etc/grml/fai/config/package_config/GRML_FULL:dmraid</div></div>
</blockquote>
<div><br></div>
<div>The dmraid package is responsible for support for so-called "ATARAID", which is RAID for IDE drives provided by a number of old hardware RAID cards (details here:&nbsp;<a href="https://packages.debian.org/wheezy/dmraid">https://packages.debian.org/wheezy/dmraid</a> &amp; <a href="https://www.freebsd.org/cgi/man.cgi?query=ataraid&amp;sektion=4&amp;manpath=FreeBSD+8.3-RELEASE">https://www.freebsd.org/cgi/man.cgi?query=ataraid&amp;sektion=4&amp;manpath=FreeBSD+8.3-RELEASE</a>).</div>
<div><br></div>
<div>Given how old this RAID driver is... should dmraid be removed from the GRML FAI classes? Or is there something else that needs to be done to correct the "module dm-raid45 not found in modules.dep" error on the custom Live CD?&nbsp;</div>
<div><br></div>
<div>Thanks!</div>
<div><br></div>
<div>Eric</div>
</div></div>
David Hare | 1 Dec 17:42 2014
Picon

grmlfull-32 2014.11

Trying out grmlfull-32 2014.11 iso as a virtualbox guest.

On two different machines (one wheezy, intel core2, 2GB RAM .. another 
jessie, intel core2, 1GB RAM)

In both cases it hangs at "Waiting for /dev to be fully populated..."

I have seen the bug report for udev but thought it was fixed.

A few lines above is a suggestion to boot with "noudev". Trying that 
gives errors "could not open /dev/tty1" repeated for other ttys .. then 
"could not chown/chmod tty device" ad infinitum.

Using "serial console" option boots to a prompt but freezes after X has 
started (static mouse cursor)

Any ideas what is wrong? I have tried also the "-small" and "daily 
build" versions with the same result.  No hardware immediately available 
to try cd or usb..

Other iso's work fine here in VB.. *except* recent custom builds with 
jessie+sysvinit+util-linux_25x which also cannot open a tty.

David Hare
Werner P. Schulz | 13 Nov 00:06 2014
Picon

Own Rescue-CD based on grml

Last weeks I worked again on remaster grml
http://www.wp-schulz.de/rescue-cd-mit-grml.html

Perhaps it may be useful for some of us.

Greetings Werner

Patrick Schleizer | 18 Oct 19:50 2014
Picon

Possible to run grml-debootstrap --vmfile inside docker?

Hi!

Was playing a bit with docker...

## On the host.
modprobe dm-mod

## Made my own image.
sudo apt-get install debootstrap
sudo -E /usr/share/docker.io/contrib/mkimage.sh -t $USER/minbase
debootstrap --variant=minbase stable

## Run a bash shell within.
sudo docker run -i -t $USER/minbase /bin/bash

## Install modprobbe.
apt-get install kmod

## Test modprobbe.
modprobe dm-mod
libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not
open moddep file '/lib/modules/3.16-2-amd64/modules.dep.bin'

Which failed, which is what grml-debootstrap would do.

And without dm-mod, also kpartx will fail.

Cheers,
Patrick

Charles Alan Hewson | 14 Sep 18:08 2014
Picon

GRML2USB encryption

Would it be practical to encrypt all of usb stick with grub2 modules? I have concerns about /boot on missing thumb drives.
Charles
<div><div>
<div>
<span></span><span>Would it be practical to encrypt all of <span class="mark">usb</span> stick with grub2 modules? I have concerns about /boot on missing <span class="">thumb</span> drives.</span>
</div>
<div>
<span>Charles</span><br>
</div>
</div></div>
Carlos Carlos | 28 Aug 17:44 2014
Picon

grml daily builds

Thanks Darshaka and Evgeni.
I didn't trust too much in md5 sums as I have seen in other daily build distro and unchanged/unmodified iso that the day it was build for the first time, lets say on 09 January, had x md5 then the automatic build system, rebuilt it again the next day, 10 January, and its md5 was different, who knows it could be the simple different number in the date or a glitch during the automatic build process, iso sizes were exactly the same, the iso was a final version so nothing was modified by the devs because they only add or change things between final versions not a day after a final version is released and their md5 were different.
That's why I thought the same thing happens in grml, iso is the same unless you see an increase or decrease in its size, md5 can be different as a matter or different date coded in the build so if you see the same size in 3 consecutive daily builds then you can expect no browser update, no openssl update and the like.
I don't know if the autobuild systems are controled by anything/anyone or if they simply keep rebuilding isos on a daily basis and autonomous way no matter if modifications were made or not, something like: It was programmed to do a rebuild every day at 11:00 or so
Thanks much for your replies.
<div><div dir="ltr">Thanks Darshaka and Evgeni.<br>I didn't trust too much in md5 sums as I have seen in other daily build distro and unchanged/unmodified iso that the day it was build for the first time, lets say on 09 January, had x md5 then the automatic build system, rebuilt it again the next day, 10 January, and its md5 was different, who knows it could be the simple different number in the date or a glitch during the automatic build process, iso sizes were exactly the same, the iso was a final version so nothing was modified by the devs because they only add or change things between final versions not a day after a final version is released and their md5 were different.<br>That's why I thought the same thing happens in grml, iso is the same unless you see an increase or decrease in its size, md5 can be different as a matter or different date coded in the build so if you see the same size in 3 consecutive daily builds then you can expect no browser update, no openssl update and the like.<br>I don't know if the autobuild systems are controled by anything/anyone or if they simply keep rebuilding isos on a daily basis and autonomous way no matter if modifications were made or not, something like: It was programmed to do a rebuild every day at 11:00 or so<br>Thanks much for your replies.<br>
</div></div>
Carlos Carlos | 25 Aug 20:43 2014
Picon

grml daily builds

Hi
I found the page that generates daily builds of unstable and stable grml, I notice that iso size can be exactly the same for 3 or 4 consecutive days so I suppose nothing was changed or added to the iso in those days, is this correct?. I might be wrong but I don't think there are devs coding new things or modifying old ones every single day.
I suppose that the app which generates the daily isos do it automatically and it doesn't matter if something new was added or not, modified or not, it simply keeps doing daily isos non stop, correct?.
Thanks in advance for any info.
<div><div dir="ltr">Hi<br>I found the page that generates daily builds of unstable and stable grml, I notice that iso size can be exactly the same for 3 or 4 consecutive days so I suppose nothing was changed or added to the iso in those days, is this correct?. I might be wrong but I don't think there are devs coding new things or modifying old ones every single day.<br>I suppose that the app which generates the daily isos do it automatically and it doesn't matter if something new was added or not, modified or not, it simply keeps doing daily isos non stop, correct?.<br>Thanks in advance for any info.<br>
</div></div>
Jens Mueller | 15 Jun 23:58 2014
Picon
Picon

Grml via ipxe's sanboot

Dear list,

I'm trying to boot GRML over ipxe's sanboot. It fails when mounting
root:
Begin: Mounting root file system ...
(initramfs) Unable to find a medium containing a live file system

This is probably no surprise because sanboot is similar to booting using
memdisk but without a download delay.
mika wrote in "Booting ISO images from within GRUB2"
(http://michael-prokop.at/blog/page/3/)
"The good news is that Grml supports the memdiskfind/phram/mtdblock
approach out-of-the-box."
Meaning you do something like

modprobe phram phram=memdisk,$(memdiskfind)
modprobe mtdblock

as mentioned here http://www.syslinux.org/wiki/index.php/MEMDISK#Linux.
But memdiskfind returns nothing.

My ipxe config contains

:grmlsan
sanboot ${url}/iso/grml32-small_2014.03.iso || goto failed

Any hints to boot Grml over sanboot?

Jens
Dan D. | 15 Mar 01:49 2014
Picon

PLEASE RE-ADD MIRRORS

We previously had these same mirrors up under Go-Part.com but then changed our domain to Go-Parts.com. The
mirror links then dropped off. We apologize deeply for this, and assure you that this is a one-time event.
Going forward, the mirrors will stay up for a very long time to come, and are being served from very reliable
and fast servers, and being monitored and maintained by a very competent server admin team.

PLEASE ADD:

(USA)
http://mirrors-usa.go-parts.com/grml
ftp://mirrors-usa.go-parts.com/grml
rsync://mirrors-usa.go-parts.com/grml

(UK)
http://mirrors-uk.go-parts.com/grml
ftp://mirrors-uk.go-parts.com/grml
rsync://mirrors-uk.go-parts.com/grml

(Australia)
http://mirrors-au.go-parts.com/grml
ftp://mirrors-au.go-parts.com/grml
rsync://mirrors-au.go-parts.com/grml

(Russia)
http://mirrors-ru.go-parts.com/grml
ftp://mirrors-ru.go-parts.com/grml
rsync://mirrors-ru.go-parts.com/grml

(Brazil)
http://mirrors-br.go-parts.com/grml
ftp://mirrors-br.go-parts.com/grml
rsync://mirrors-br.go-parts.com/grml

(Japan)
http://mirrors.go-parts.com/grml
ftp://mirrors.go-parts.com/grml
rsync://mirrors.go-parts.com/grml

Thanks,
Dan 		 	   		  

Gmane