Mondo 3.2.2 issues
"Kalchik, Jeffery" <[email protected]> Tue, 19 Nov 2019 19:15:31 +0000
| Newsgroups | gmane.linux.mondo.devel |
|---|---|
| Message-ID | <BN7PR01MB3732FC4431C168B354097EAFCC4C0@BN7PR01MB3732.prod.exchangelabs.com> |
Good morning/afternoon/evening/fill in the blank..... I'm having to circle the wagons around. I've had Mondorescue running here for physical system recovery for years on EL5 and derivatives, albeit on a slightly older version due to name lookup issues. Unfortunately, I now have a requirement to get it running on EL7 & derived systems. So.... 1. Install a clean host running CentOS 7, completely patched (at least, within the last couple of weeks.) 2. Latest mondo, mindi, afio, buffer, etc. installed. 3. EXTRA_SPACE=600000 in /etc/mindi/mindi.conf set. 4. Mondoarchive, sending to an NFS mount (via autofs,) successful run. 5. Boot from image 1 successfully in expert mode, and validate that I have name lookup capabilities. 6. Mondorestore to run a compare operation. Accepting the defaults for a net mount, prompts for NFS share, user, etc., then throws a dialog box for "Please mount that partition before you try to backup to or restore from it" error and then dies back to a command prompt. 7. I can successfully mount the NFS share (with "-o nolock",) successfully, exactly as shown in /tmp/mondorestore.cfg. Both mondoarchive and mondorestore have been executed with "-K 99" for as much data as I can gather. I do see during the initial boot phase that I still have name lookup issues, but after the root filesystem is created/mounted/etc., those now clear up. I've noted this on both Oracle Linux 7 and CentOS 7. I'm at a loss at this point to figure out what I'm missing. Anybody care to take a quick look at the logs I've posted to https://pastebin.com/8kE9y8KA and tell me what I'm missing, or messed up? Jeff Kalchik Land O'Lakes Managed Resources _______________________________________________ Mondo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mondo-devel