Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have an issue, I have cloned centos 7 VM with XFS file system in form of iso by mondo rescue. When I boot from that iso ant type nuke to restore machine, centos 7 wont boot. Instead grub rescue appears. Moreover all the portions shown by ls command has unknown file system. I am really stuck here. There is only unknown file system error with grub rescue shell. The ISO takes me to the grub rescue and VM wont boot further. Any help will be much appreciated.
Typically a VM is stored as an image file within the file system of the host operating system, not a partition on the drive. If you are running Mondo rescue in live mode, the operating system that the virtual software is installed is not running, therefore the Centos 7 VM is not running also. It will not show a file system when in image file state.
Your best bet is to create a new VM to attemp to repair Centos from there, here's a little insight on what you may need to do.
Are you booting the Mondo rescue ISO from within the virtual software as a boot option for the Centos 7 VM?
Last edited by Brains; 12-14-2018 at 04:07 PM.
Reason: Added question
Moreover all the portions shown by ls command has unknown file systemd
The grub boot code is probably missing the modules needed to access the filesystem to continue with the booting. Download a live iso then boot the live iso inside the vm to reinstall grub to centos 7
Typically a VM is stored as an image file within the file system of the host operating system, not a partition on the drive. If you are running Mondo rescue in live mode, the operating system that the virtual software is installed is not running, therefore the Centos 7 VM is not running also. It will not show a file system when in image file state.
Your best bet is to create a new VM to attemp to repair Centos from there, here's a little insight on what you may need to do.
Are you booting the Mondo rescue ISO from within the virtual software as a boot option for the Centos 7 VM?
Yes I am using VMWare workstation. I make new VM and put that ISO to at time of creation of new VM. When I power on this VM and then type nuke. But after reboot there is only grub rescue shell.
Well, as the previous poster mentioned, you can boot an ISO of a live CD or Grub rescue as a boot option for the VM that won't boot and attempt to repair Grub. Typically the best ISO to boot would be the Centos ISO originally used to do the installation, most installation ISOs will also have a rescue option, using the original installation media gives best chance of rescue as it will have proper version of packages contained within in case reinstalling packages is required.
With VMWare, you can take snapshots, which can be done after a fresh install. If you need to resort to a previous state such as the day of the installation, resorting to the snapshot works perfectly. As for backup purposes, you just need to copy the entire folder of the VM to a backup medium. So if you have a drive issue, or wish to use the VM on another computer, just copy that folder to the new/other drive and boot it after reinstalling VMWare. This way it will boot properly every time.
Super Grub2 and plop are great at loading the kernel thus getting it booted. Super Grub2 may also be able to fix the issue. You can download an ISO of each. Here is a tutorial on how to attempt fixing the issue from grub rescue mode.
Is this grub rescue from the iso grub, or an installed systems grub?
Mondo rescue made an ISO and during creation of VM I have booted the machine from that ISO after typing nuke to restore old machine, machine becomes rebooted and at the start at grub rescue shell.
Thank you so much for your reply. Problem becomes temporarily solved, I made an OS with following details:
1) Centos 7 64 bit
2) Separate boot parttion
3) Lvm for root directory and swap.
4) File system ext4
Mondorescue successfully backup-ed and recovered the machine. Mondorescue made an ISO during backed-up process.Then I made new VM in VMware Workstation and used this ISO .Old machine becomes booted from that ISO properly.
Problem:
I adopt the same method on the machine created in XEN. I used Mondorescue which gives me an ISO. Then I used this ISO at the time of creation of new VM in XEN Server. Machine boots from that ISO and then I type nuke but after typing this I am getting this error.
/dev/xvda not exist. Switch to Interactive Mode?Screenshot is attached. I am in big trouble. I have machine in XEN server which I cannot reboot nor take snapshot from XEN utility. I just want to make live clone of this machine otherwise I will be in big trouble. I tried everything ddrescue, dd but didnot succeed. Any help in this regard is much much appreciated.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.