I cannot extend the size of Kubuntu 18.04

[Qqmike]

I thought we were just trying to fix a possibly damaged filesystem on sda7! What the heck is this sfdisk?
man sfdisk -- that re-orders/realigns partitions?!!! I hope not! We do not want to mess with the order of the partitions for now!

[Qqmike]

I thought gparted would check and fix a filesystem. Or, fsck, https://linux.die.net/man/8/fsck . Now, I don't know if you need to use TestDisk or what.

[nicrnicr]

oshunluvr wrote me to write "sfdisk -r /dev/sda".
After he advised me to run fsck on sda7.
Thank you Qqmike for advising me te use gparted, but I didn't know what to do with it. I'm normally using the partition software of Kubuntu 18.04.
The last time I wrote "sfdisk -r /dev/sda" in the terminal as I was logged in the partition sda7. Did I make a mistake? Was it better to write it in a terminal of a usb drive?

[GreyGeek]

From the sfdisk man page:

-r, --reorder device
Renumber the partitions, ordering them by their start offset.

That doesn't change their UUID, which is what should be used to mount them.
Grub was looking for (hd0, gptx) where x was the partition location of the boot loader. More details and how to use Grub rescue here:
https://linuxhint.com/grub_rescue_ubuntu_1804/

[Qqmike]

to write "sfdisk -r /dev/sda".

As he's pretty good with filesystems, better wait and see what he has in mind.

[nicrnicr]

ls gives:

(hd0) (hd0,msdos8) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)

any other command of the link provided by GreyGeek is declared as "Unknown".

[GreyGeek]

ls gives:

(hd0) (hd0,msdos8) (hd0,msdos7) (hd0,msdos6) (hd0,msdos5) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1)

any other command of the link provided by GreyGeek is declared as "Unknown".

That's because the examples used "gptX". You must replace gptX with msdosX, where X is a number. Try the "bad" commands again using the proper syntax..

[nicrnicr]

Thank you GreyGeek.
I tried the commands with "msdosX":
ls (hd0,msdos2)/
ls (hd0,msdos3)/
ls (hd0,msdos5)/
ls (hd0,msdos6)/
ls (hd0,msdos7)/
ls (hd0,msdos8)/
I also tried the commands without "msdosX" like lsmod, usb, lspci,

[Qqmike]

Boy, you got yourself into a thing here, my friend, with the grub> prompt. In the old GRUB legacy, I could boot ANYTHING at that prompt. I have not had such luck with the newer GRUB2 that we use now. That said, and I haven't used this stuff for years, I did include some discussion and (hopeful) examples in my GRUB2 how-to:
GRUB 2: A Guide for Users

https://www.kubuntuforums.net/showth...l=1#post193705

It is difficult to navigate this huge document, but note the Table of Contents, Section 3:

SECTION 3 Fixing Things
A checklist of things to try to fix a broken system
A Troubleshooting Outline
Ctrl+Alt+Del will reboot your PC
Super Grub Disk: Very Important
Key commands: grub-mkconfig and sudo grub-install
Timeout & Default OS, changing
Kernel options, changing
To see or to hide the boot menu
Missing OS entry in the boot menu
Editing the boot menu during booting: "e" key
The GRUB prompt grub> -- What to do with it
=> Getting information and booting an OS
Re-installing GRUB 2 using Live CD: Key Rescue Method
Using a Live CD to edit files in your OS

That section (that you must scroll down to access), contains discussion and a couple examples (booting by symlink), and it mentions that you can often boot by several other methods--these other methods are also covered in the how-to in the referenced sections. But, fact is, I think you should be able to boot by symink (discussed in Section 3). I have had mixed luck booting at the GRUB2 grub> prompt. However ... I did actually test everything in that how-to with real examples and printed what I found out. I did not include my many failures! (As I said, the old GRUB legacy was great, I never failed to boot by grub> there.)

I hope this helps.

[GreyGeek]

Thank you GreyGeek.
I tried the commands with "msdosX":
ls (hd0,msdos2)/
ls (hd0,msdos3)/
ls (hd0,msdos5)/
ls (hd0,msdos6)/
ls (hd0,msdos7)/
ls (hd0,msdos8)/
I also tried the commands without "msdosX" like lsmod, usb, lspci,

Are you using a capital O (oh) instead of 0 (zero)?
For one of the partitions you should have gotten something like this:


Did you do something else besides "sfdisk -r /dev/sda"?

[Qqmike]

It seems the partitions got lost.
Somehow, got way off track here, but not sure what to do now, except possibly TestDisk (unless you guys know how to "reverse" whatever sfdisk - did). Post #1 seemed to indicate a filesystem error, which I think would be fixable:

The error result is:
Grow partition ‘/dev/sda7’ from 149.01 GiB to 219.22 GiB
Job: Check file system on partition ‘/dev/sda7’
Command: e2fsck -f -y -v /dev/sda7
Check file system on partition ‘/dev/sda7’: Error

[nicrnicr]

Thank you GreyGeek.
I only did what I already described. I didn't write O but 0.

[Qqmike]

I guess you are waiting on some kind of smart response. I don't have one, yet. I presume you can't find any partitions? There are options, like using TestDisk from a live USB Kubuntu session. Or, booting to a live Kubuntu USB, see if you can discover anything about the current status of things. For example, sudo fdisk -lu can be run from a live Kubuntu session, at Konsole. I presume you can also run your favorite command, too, sfdisk, perhaps with the two commands --list and --verify.

[nicrnicr]

Thank you very much Qqmike for your further pieces of advice!
I booted with a live USB and uploaded the content of the partitions in this post and the following one. Some are not readable.
OS which seems to be a part of Windows.


149GB wich is sda7 and readable.


50,6GB wich seems to be a part of Windows


unreadable Kubuntu 16.04


I can't get rid of the following image that you can forget.

[nicrnicr]

readable Kubuntu 16.04


The partition of Loop device is not shown as it is that of the USB flash drive.

For the last 103,6GB partition, I show the homes of the two users aui and auie and the unreadable home in auie's home.
aui's home


auie's home


The unreadable home in auie's home