Re: mondoarchive
I'm running kernel 2.4.27-2-k7
I checked my config file (config-2.4.27-2-k7) and:
CONFIG_CRAMFS=y
I call mondoarchive w/ the following options:
mondoarchive -O -i -E /mnt -I /home -d
/root/images/mondo/ -T /tmp
Then I receive this error:
Mindi failed to create your boot+data disks.
---promptpopup---1--- Fatal error. Filesystem cramfs
not supported for initrd image. Terminating.
I've attached the end of the log file ... where it
reports that cramfs is not supported. All logging to
this reports ".. Ran Just Fine"
I've also had no luck w/ the -k FAILSAFE option.
--- John Fleming <john@wa9als.com> wrote:
> ----- Original Message -----
> From: "Hugo Vanwoerkom" <hvw59601@care2.com>
> To: <debian-user@lists.debian.org>
> Sent: Thursday, September 13, 2007 12:41 PM
> Subject: Re: mondoarchive
>
>
> > debian user wrote:
> >> I am running Sarge.
> >>
> >> I apt-get(ted) the stable mondo tools and am
> trying to
> >> use mondoarchive.
> >>
> >> When doing a test archive for my /home dir,
> >> mondoarchive complains of a fatal error:
> >>
> >> Fatal error. Filesystem cramfs not supported for
> >> initrd image. Terminating.
> >>
> >> Does anyone have a suggestion?
> >>
> >
> > I see you posted to the mondo list also.
> > Found this:
> >
> >
>
http://lists.debian.org/debian-qa/2004/02/msg00059.html
> >
> > Which seems to suggest that you must use a
> failsafe kernel:
> >
> > man mondoarchive:
> >
> > ...
> > -k path Path of user's kernel. If you are
> a Debian or Gentoo user
> > then specify -k FAILSAFE as your kernel.
> Otherwise, you will rarely
> > need this option.
> > ...
> >
> > That said, I see that in my stock Debian I have in
> the .config:
> >
> > CONFIG_CRAMFS=y
> >
> > and I run mondoarchive just fine w/o failsafe.
> > But I run Sid.
> > What kernel are you running?
> >
> > Hugo
>
> FWIW (not much), I've been running mondoarchive with
> sarge and now etch with
> various 2.4 and 2.6 kernels WITHOUT needing the
> FAILSAFE kernel, and I've
> not had this problem. So it might be a kernel
> problem, but I doubt it's any
> "usual" problem - It's not just because it's a
> Debian kernel etc...
>
> - John
>
>
> --
> To UNSUBSCRIBE, email to
> debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
>
>
Unable to open proc
/dev/hda1 / ext3 266
/dev/hda9 /home ext3 29125
/dev/hda8 /tmp ext3 384
/dev/hda5 /usr ext3 4769
/dev/hda6 /var ext3 2863
/dev/hda7 swap swap 753
Tarring and zipping the groups...............^M Done.
Creating data disk #1...#2...#3...#4...^M Done.
Making 1722KB boot disk.....................Call GetFilesystemToUse() with parameter /boot/vmlinuz-2.4.27-2-k7 to get filesystem to use for initrd.
GetFilesystemToUse(): called with parameter: /boot/vmlinuz-2.4.27-2-k7.
GetFilesystemToUse(): gzip magic found at lvOffset 19028.
GetFilesystemToUse(): Filesytem to use for initrd is cramfs.
Creating cramfs initrd filesystem.
Fatal error. Filesystem cramfs not supported for initrd image. Terminating.
Please e-mail a copy of /tmp/mindi.err.2691.tgz to the mailing list.
See http://www.mondorescue.org for more information.
WE CANNOT HELP unless you enclose that file.
Mindi failed to create your boot+data disks.
Fatal error. Filesystem cramfs not supported for initrd image. Terminating.
[Main] newt-specific.c->fatal_error#377: Fatal error received - 'Failed to generate boot+data disks'
[Main] newt-specific.c->fatal_error#395: OK, I think I'm the main PID.
[Main] newt-specific.c->fatal_error#403: I'm going to do some cleaning up now.
[Main] newt-specific.c->fatal_error#404: killall mindi 2> /dev/null
running: kill `ps auxww | grep " /mondo/do-not " | awk '{print $1;}' | grep -vx "\?"` > /tmp/mondo-run-prog-thing.tmp 2> /tmp/mondo-run-prog-thing.err
--------------------------------start of output-----------------------------
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
--------------------------------end of output------------------------------
...ran with res=256
running: kill `ps auxww | grep " tmp.mondo " | awk '{print $1;}' | grep -vx "\?"` > /tmp/mondo-run-prog-thing.tmp 2> /tmp/mondo-run-prog-thing.err
--------------------------------start of output-----------------------------
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
--------------------------------end of output------------------------------
...ran with res=256
running: kill `ps auxww | grep " ntfsclone " | awk '{print $1;}' | grep -vx "\?"` > /tmp/mondo-run-prog-thing.tmp 2> /tmp/mondo-run-prog-thing.err
--------------------------------start of output-----------------------------
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
sh: line 1: kill: root: no such pid
--------------------------------end of output------------------------------
...ran with res=256
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
[Main] newt-specific.c->fatal_error#412: Waiting for child processes to terminate
Reply to: