Re: Mondo 3.2.2 issues

Kalchik, Jeffery said on Fri, Nov 22, 2019 at 02:37:22PM +0000:
><scratches head>  I see initrd.img in the root of the #1 ISO.  I also see images/all.tar.gz that would seem to be rather important.
>I've unpacked both into a temporary filesystem.  usr/sbin/mondorestore appears in images/all.tar.gz, but not in initrd.img.  I'd have to bet that images/all.tar.gz is supposed to be getting unpacked after the boot phase 1.  Unpacking both results in about 1.25gb of space, so a 4gb RAM disk should be way more than sufficient.  Unfortunately, until I get the base ramdisk issue sorted out, I'm sunk, as practically nothing is available at the Mindi command line.

Yes all.tar.gz is extracted by install-additional-tools.
Another case where an issue could araise is if the number of inodes of the FS is exceeded (lots of very small files).
Don't have other ideas for now...

>On CentOS 6:
>
>Name resolution still succeeds, but the NFS mount still fails during a mondorestore run.  Well, wait.  Name resolution succeeds after the boot is fully complete and leaves me at a command line (expert mode.)  Name resolution *IS* failing during the boot phase 1, not sure that's entirely significant.  http:// 140.190.50.94/mondorestore-3.3.0-CentOS6-20191122-1.log

The fail of resolution in first phase is an issue for me. That should be fixed. Will reproduce and work on that.
Now I see you're using automount, and that not something MondoRescue is well supporting. 
mondorestore checks that the mount point is there by looking for the ':' separator, which in your case is not found (due to the resolv issue).

Will let you know when I have a working resolv configuration so you can test as well.
Bruno.
-- 
HPE WW FLOSS Technology Strategist      http://www.hpe.com/engage/opensource
Open Source Profession, WW Linux Community Lead    http://github.com/bcornec
FLOSS projects:     http://mondorescue.org        http://project-builder.org
Musique ancienne?   http://www.musique-ancienne.org  http://www.medieval.org