- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Problem with mondorescue 2.2.8 restore
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2009 12:10 PM
тАО10-26-2009 12:10 PM
Re: Problem with mondorescue 2.2.8 restore
I tried several more times to recover the system without any success. I have no choice at this point than to rebuild the system from scratch.
After that is done I am going to have to rethink how the backups are done using mondo in order for this incident not to occur again.
Thanks anyway for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2009 12:17 PM
тАО10-26-2009 12:17 PM
Re: Problem with mondorescue 2.2.8 restore
If anything, just do a fresh load of fc2, and them load mondorescue. Then use mondorestore to restore all the users data. That should work fine. My suggestion would be to not use mondo to backup your whole machine. I only use it to backup the main system directories. Then I use normal backups for everything else.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2009 12:40 PM
тАО10-26-2009 12:40 PM
Re: Problem with mondorescue 2.2.8 restore
I posted the question as part of the mondo-devel users group, and one suggestion that was made was to use the following syntax at the boot prompt of the mondo restoration cd:
denymods=fdomain
At the risk of sounding like an idiot, how would I go about determining the name of the kernel to enter at the prompt in conjunction with the above parameter?
Also, why would fdomain be causing the system to hang at freeing unused kernel memory?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2009 12:45 PM
тАО10-26-2009 12:45 PM
Re: Problem with mondorescue 2.2.8 restore
nuke denymods=fdomain
I am not sure if that will work, but it's worth a shot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 05:23 AM
тАО10-27-2009 05:23 AM
Re: Problem with mondorescue 2.2.8 restore
The nuke value at the boot prompt refers to the name of the kernel. If I knew the name of the kernel, I could insert that along with the denymods=fdomain argument.
I have a system that is the same model and operating system of the problem workstation. Is it possible to reference that system to get a clue to the name of the kernel?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 05:26 AM
тАО10-27-2009 05:26 AM
Re: Problem with mondorescue 2.2.8 restore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 05:45 AM
тАО10-27-2009 05:45 AM
Re: Problem with mondorescue 2.2.8 restore
I did try the nuke denymods=fdomain, and that is when I got confronted with the error indicating that mindi could not find a kernel with the name nuke.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 07:30 AM
тАО10-27-2009 07:30 AM
Re: Problem with mondorescue 2.2.8 restore
vmlinuz denymods=fdomain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 12:32 PM
тАО10-30-2009 12:32 PM
Re: Problem with mondorescue 2.2.8 restore
I ended up rebuilding the workstation from scratch, and now comes the fun part: determining what needs to be done in order to prevent this incident from reoccurring.
Enclosed with this posting is a copy of the script that is used to create the .iso images.
The script in its current form creates the backups based on the filesystems of the workstation.
I had several ideas concerning the script, and the backup:
1. Going by your example, modify the mindi file, specifically the FORCE_MODS line, on all workstations to include the arguments:
FORCE_MODS="diskdumplib diskdump mptbase mptscsi mptspi mptsas mptscsih ata_piix crc32 mii pcnet32 sunrpc nfs nfs_acl lockd loop"
2. Adding a section to the script that will run mindi, and place the created boot files at the same NFS location where the iso images are located.
Besides or instead of the above, is there anything else that I should consider putting into the script?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 01:49 PM
тАО10-30-2009 01:49 PM
Re: Problem with mondorescue 2.2.8 restore
Send me your e-mail address. Send it to thouaeti_at_guerrillamailblock_dot_com.
That's a temporary address. It might be easier than using this thread.
Later,
Court