LM 17 Unable to boot after partition extension
 

Hello there,

I have;

A Laptop : Samsung RV509, i3, 300GB HDD, 3GB Ram, Dual boot Windows7 & LM 17cinnamon 32bit

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.

However, my Windows OS works normally.

Please help.

I have a live usb, if that can be of any help.

Anil

Anil,

First, backup any valuable personal data to an external drive!!

If you do not have Gparted already installed, open a Terminal:

Open gparted:

Then follow:

https://www.rootusers.com/use-gparte...ive-partition/

Thank you beachboy2,

For connecting.

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.

Thank you

Anil

Anil,

Try this:

https://help.ubuntu.com/community/Boot-Repair

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.

Hello beachboy2,

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.

Here are the links to the Boot-repair Info files before and after.

Before Boot-repair- http://paste.ubuntu.com/11611711/

After Boot-repair- http://paste.ubuntu.com/11611787/

Thank you for being with me

Anil

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.

Here is the screenshot of the Gparted;

Attachment 18625

Thank you michaelk

Anil

This doesn't look very usefulWonder how it determines that.

Thank you syg00, for coming.

I sent the message through my email account.

I could not crteate an account here, because I didn't know the information required to create one [Name of the outgoing server?!.:confused:]

Is it OK?

Thank you

Anil

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.

Thank you

Anil

Have you tried blkid & compared to /etc/fstab to see if it matches?

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.

https://help.ubuntu.com/community/Gr...ing#via_ChRoot

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.

So now what should I do? :confused:

Thank you for being with me.

Anil