[SOLVED] emergency boot mode, unable to boot in to mx linux, multiple boot with mx linux, win 10 and linux mint.
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
emergency boot mode, unable to boot in to mx linux, multiple boot with mx linux, win 10 and linux mint.
Hello,
I am using desktop with three drives.
ssd - mx linux
hdd - win 10
hdd - mint
Mx linux became unbootable after I tried to delete and rearrange some partitions while using win 10.
Then I tried to troubleshoot reading some articles and then it messed up win 10. Then I used win 10 ISO and repaired the win 10.
I am able to boot in to win 10 and linux mint, but when I try to boot in to mx linux, it shows emergency mode.
I also have bootable usb made with Ventoy, which contains following tools
1. boot-repair-disk-64bit.iso
2. gparted-live-1.1.0-1-amd64
3. HBCD_PE_x64
4. MX-21.2.1_x64
5. rescatux-0.74
6. systemrescuecd-amd64-6.1.5
I don't want to troubleshoot by my own as I am noobi and I don't understand linux as expert does.
Can some one help? please let me know what kind of logs I need share
I like your attitude. You are prepared to provide information and that is the first step to getting a solution.
The first thing I would do in this kind of situation is to boot into Mint, open a terminal, and run sudo fsck on your mx root partition. If you can't remember exactly where that is, use sudo fdisk -L to list the partitions on the ssd. It won't tell you explicitly what the partitions are for but their sizes should give you a clue. Or you can find out the long way by using sudo mount to mount each partition in turn on /mnt and see what's on it.
The important point here is that examining the problematic ssd drive with fdisk, or its partitions with mount, won't cause any further changes to the contents, which you don't want in this kind of situation. Running fsck on the root partition once you have found it won't do any harm and might do some good. It depends on whether this is a simple disk corruption or you have actually destroyed some essential files.
When you say "emergency mode" what precisely do you mean? What is the last thing the boot process tells you before it goes on strike?
Are all three installa UEFI? If so, do you not see an option to select MX in the BIOS firmware boot options? Are you booting Mint and windows from grub on Mint and if so, have you run sudo update-grub from Mint?
Thanks for guidance. The problem is solved.
There were some entries for deleted partition in fstab file and hence it was getting stuck at the boot showing emergency mode.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.