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.
I had been happily using this system till now. And then, I had to extend the size of the root & home partitions. I did so with the help of the 'Mini partition tool self bootable cd'. And suddenly my Linux operating system fails to boot. I had done such partition extensions earlier without any problems. Now I don't know what went wrong.
I tried to edit the fstab in the /etc and update the grub in the /usr/sbn. But it didn't help.
With the help of 'Mini partition tool self bootable cd' I have already done the desired extensions. My problem is that after these extensions I am not able to boot into the LM OS.
What are the error messages if any when it fails to boot?
You should be able to verify the integrity of your hard drive partitions by booting the mint live USB. Can't remember if they will automount but you can manually do that. Post the output of the lsblk command.
I did as you said. I downloaded the Boot-repair iso image & burned it on a DVD and booted the system with the disk. First I created the INFO file, then opted for the RECOMMENDED REPAIR. Then again created the INFO file. Then I restarted.
However, nothing changed. As usual I was unable to boot.
What are the error messages if any when it fails to boot?
You should be able to verify the integrity of your hard drive partitions by booting the mint live USB. Can't remember if they will automount but you can manually do that. Post the output of the lsblk command.
Thank you michaelk,
for coming,
There are no error messages now. Earlier there used to be a message that said something like, 'unable to mount press S to skip'.
Now all I get is the;
busybox v1.21.1 (ubuntu 1:1.21.0-1ubuntu1) built-in shell, that says enter 'help' for a list of built-in commands.
(initramfs)_
The output of the lsblk command;
mint@mint ~ $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 298.1G 0 disk
├─sda1 8:1 0 40G 0 part
├─sda2 8:2 0 165G 0 part
├─sda3 8:3 0 1K 0 part
├─sda5 8:5 0 10G 0 part
├─sda6 8:6 0 10G 0 part
├─sda7 8:7 0 25G 0 part
├─sda8 8:8 0 6G 0 part [SWAP]
└─sda9 8:9 0 39G 0 part
sdb 8:16 1 1.9G 0 disk
└─sdb1 8:17 1 1.9G 0 part /cdrom
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 1.1G 1 loop /rofs
mint@mint ~ $
sda7 is the root & sda9 is the /home
The partitions don't automount but yes, I can manually mount them.
I was merely making a comment. If os-prober can't find Linux, then it won't attempt to build an entry in the grub.cfg.
Looks like it looks for the (dynamic) loader to ascertain if the filesystem is a Linux distro.
I don't know what may have gone wrong - the partitions obviously mount ok.
You think it may be due to the 3Gigs of unallocted space?
Hello EDDY1,
Thanks for coming.
The unallocated space was there earlier too, when the system was working fine. However, it was 13GB large, then. I extracted 20GB from sda1 and 10GB from the unallocated space and extended the /home partition to its current size 39GB, which was earlier only 9GB large.
Your boot repair script shows Grub in the MBR pointing to the boot files on sda7 and the entries in it's grub.cfg file look correct. Did you move the location of the boot files, move the beginning of the root partition to the right? That could be the problem if you didn't immediately update-grub.
Interesting that you have a grub.cfg on the windows partition, sda2. Since windows boots I wouldn't worry about that.
When you chroot, the script reports that it can't find grub-install or update-grub in /usr/sbin of the installed Mint. Did you check to see if those scripts are actually present? You might try doing this manually although I don't know if that would be any better than the boot repair. See the link below.
Have you tried blkid & compared to /etc/fstab to see if it matches?
Hello EDDY1,
Earlier I had checked once. I found that they did not match; so I tried to edit fstab according to the blkid. But with no result. Nothing happened. The system did not boot.
Now since you mentioned, I verified again and to my utter surprise I found that there is no etc folder at all! it has disappeared altogether!
I don't understand how it can happen. I have not deleted it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.