Announcement

**Qqmike** · Nov 12, 2018, 03:51 PM

============================= Boot Info Summary: =============================== => Grub2 (v2.00) is installed in the MBR of /dev/sda

Good.

Code:

sda5:
    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Ubuntu 18.04.1 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab 
                       /boot/grub/i386-pc/core.img

And that is good. So your 18.04 did get moved to sda5.

Looking at:

Suggested repair
The default repair of the Boot-Repair utility would reinstall the grub2 of sda5 into the MBR of sda.
Additional repair would be performed: unhide-bootmenu-10s fix-windows-boot

Do the suggested repair? Why not? I don't think I have ever seen a case where re-installing GRUB messed things up. In a sense, it can't hurt. And it may help if sda5 is detected and made bootable after the repair.

**Qqmike** · Nov 12, 2018, 03:57 PM

So, what can it hurt to do that suggested boot repair? THEN we'll see if you can boot into sda5. THEN we could see if you can expand that sda5 partition for 18.04. Correct? What about that so-called file system error? I do not really know for sure. The partitions do look valid as all the utilities are detecting the partitions.

I agree about gparted versus KDE partition utility. They should be the same, basically. In the past, they did not seem to work the same (gparted was more reliable). Experts here at kubuntuforums tell us that you CAN trust KDE partition manager. I do like to have gparted on a thumb drive, though ;-)

**GreyGeek** · Nov 12, 2018, 04:37 PM

There is at least one interesting finding in your report. The first is a reference to msdos9 but that partition is NOT listed in the partition list. Was there an sda9 partition before the sfdisk -r /dev/sda was run?

sda2 is shown as the boot partition (*) which is your Win10 boot.

The grub.cfg on sda5 references msdos8 and msdos9. There are unknown bootloaders on sda4 and sdb1. The os-prober reports it found Ubuntu 18.04 on sda5 and Ubuntu 16.04 on sda6, but the menu entry for 18.04 shows (hd0, msdos8).

First, recover all the Kubuntu & Windows 10 data you can from sda. IF you made Win10 recovery CDs then I would used them to restore Win10, IF possible, and then re-install the Kubuntu distros you want from scratch. IF you cannot restore Win10 from recovery disks, for what ever reason, then your choices are:
1) forget Win10 and install Kubuntu,
2) buy a copy of Win10, install it and forget Kubuntu.
3) buy a copy of Win10 and install it, resize the partition to give Kubuntu some and install Kubuntu.
4) abandon computers and take up golf as a hobby.

Code:

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1                  63        80,324        80,262  de Dell Utility
/dev/sda2    *         81,920     1,617,919     1,536,000   7 NTFS / exFAT / HPFS
/dev/sda3           1,617,920   177,500,584   175,882,665   7 NTFS / exFAT / HPFS
/dev/sda4         177,502,206   976,766,975   799,264,770   f W95 Extended (LBA)
/dev/sda5         177,502,208   490,000,383   312,498,176  83 Linux
/dev/sda6         637,235,200   854,462,463   217,227,264  83 Linux
/dev/sda7         854,465,283   870,658,739    16,193,457  82 Linux swap / Solaris
/dev/[B]sda8[/B]         870,658,803   976,766,975   106,108,173   7 NTFS / exFAT / HPFS


[COLOR=#ff0000][B]sda5[/B][/COLOR]/boot/grub/grub.cfg:

menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-00f32f0a-6530-474a-a83c-208645ea8a03' {
    recordfail
    load_video
    gfxmode $linux_gfx_mode
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_msdos
    insmod ext2
    set root='hd0,[COLOR=#ff0000]msdos8[/COLOR]'

menuentry 'Windows 10 (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-D28EE6808EE65C8B' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos2'

menuentry 'Ubuntu [B]14[/B].04.5 LTS (14.04) (on /dev/[B]sda6[/B])' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-84b62f09-e544-44b6-959b-ade9d18ba970' {
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos6'

menuentry 'Ubuntu [B]16[/B].04.4 LTS (16.04) ([COLOR=#ff0000][B]on /dev/sda9[/B][/COLOR])' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-514aa732-c876-4839-8a0b-8db3b6c47536' {
    insmod part_msdos
    insmod ext2
    set root='hd0,[COLOR=#ff0000][B]msdos9[/B][/COLOR]'

menuentry 'Ubuntu [B]18[/B].04.1 LTS (18.04) (auf /dev/[B]sda8[/B]) ([COLOR=#ff0000][B]on /dev/sda9[/B][/COLOR])' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-34-generic--514aa732-c876-4839-8a0b-8db3b6c47536' {
        insmod part_msdos
        insmod ext2
        set root='hd0,[COLOR=#ff0000][B]msdos9[/B][/COLOR]'


[B]sda5/etc/fstab:[/B]

menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-514aa732-c876-4839-8a0b-8db3b6c47536' {
    recordfail
    load_video
    gfxmode $linux_gfx_mode
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_msdos
    insmod ext2
    set root='hd0,[COLOR=#ff0000][B]msdos9[/B][/COLOR]'

submenu 'Erweiterte Optionen für Ubuntu' $menuentry_id_option 'gnulinux-advanced-514aa732-c876-4839-8a0b-8db3b6c47536' {
    menuentry 'Ubuntu, mit Linux 4.15.0-36-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-36-generic-advanced-514aa732-c876-4839-8a0b-8db3b6c47536' {
        recordfail
        load_video
        gfxmode $linux_gfx_mode
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_msdos

(Several more similar to the one above)

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 10 (loader) (auf /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-D28EE6808EE65C8B' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos2'

menuentry 'Ubuntu 14.04.5 LTS (14.04) (auf /dev/sda6)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-84b62f09-e544-44b6-959b-ade9d18ba970' {
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos6'

(A couple mmore similar to the one above)


submenu 'Erweiterte Optionen für Ubuntu 18.04.1 LTS (18.04) (auf /dev/sda8)' $menuentry_id_option 'osprober-gnulinux-advanced-00f32f0a-6530-474a-a83c-208645ea8a03' {
    menuentry 'Ubuntu (auf /dev/sda8)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-36-generic--00f32f0a-6530-474a-a83c-208645ea8a03' {
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos8'

(Three mmore similar to the one above)

/dev/sdb1: unknown GPT attributes
1000000000000001

/dev/sdb2: unknown GPT attributes
1000000000000001

[B]Unknown BootLoader on sda4[/B]

[B]Unknown BootLoader on sdb1[/B]

grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.
Partition 1 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
Partition 7 does not start on physical sector boundary.
Partition 8 does not start on physical sector boundary.


=================== os-prober:
/dev/[B]sda2[/B]:Windows 10 (loader):Windows:chain
/dev/[B]sda5[/B]:Ubuntu 18.04.1 LTS (18.04):Ubuntu:linux
/dev/[B]sda6[/B]:Ubuntu 16.04.4 LTS (16.04):Ubuntu1:linux




The boot files of [Ubuntu 18.04.1 LTS] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, >200MB, start of the disk). This can be performed via tools such as gParted. Then select this partition via the [Separate /boot partition:] option of [Boot Repair]. (https://help.ubuntu.com/community/BootPartition)

**Qqmike** · Nov 12, 2018, 04:45 PM

The os-prober reports it found Ubuntu 18.04 on sda5 and Ubuntu 16.04 on sda6, but the menu entry for 18.04 shows (hd0, msdos8).

That's the old menu entry, before running that sfdisk thing. That's why he needs to re-install GRUB now and hope the os-prober will generate a new and relevant GRUB boot menu. When he ran Boot-Repair, he opted to have only the report; he did not yet run the recommended repair.

**vinnywright** · Nov 12, 2018, 09:06 PM

I would concur with the idea of running that boot repair suggestion ,,,it couldn't hurt at this point .

VINNY

**nicrnicr** · Nov 13, 2018, 01:34 AM

Thank you very much GreyGeek for your remark.
Qqmike writes that it refers to the old menu entry. It doesn't change that there is no sda9 in the old configuration.
If my hdd looks anormal, it might be because I installed twice Kubuntu 18.04. These two Kubuntu 18.04 were different, until the day I did something and after it seemed that these two Kubuntu 18.04 merged.

I tried again to boot and the #15 still describes the bad situation.

I'm now repairing the boot.

**nicrnicr** · Nov 13, 2018, 03:24 AM

There has been a problem during the reparation.
"An error occurred during the repair.

Please write on a paper the following URL:
http://paste.ubuntu.com/p/YhhCkX8h38/

In case you still experience boot problem, indicate this URL to:
boot.repair@gmail.com

You can now reboot your computer.
Please do not forget to make your BIOS boot on sda (ATA WDC WD5000BPKT-7) disk!

The boot files of [Ubuntu 18.04.1 LTS] are far from the start of the disk. Your BIOS may not detect them. You may want to retry after creating a /boot partition (EXT4, >200MB, start of the disk). This can be performed via tools such as gParted. Then select this partition via the [Separate /boot partition:] option of [Boot Repair]. (https://help.ubuntu.com/community/BootPartition)"

**nicrnicr** · Nov 13, 2018, 03:41 AM

But I can boot :-)

Thank you very much for your help!

**Qqmike** · Nov 13, 2018, 06:17 AM

So you can boot into Kubuntu 18.04 on sda5? I would think so. And, according to the repair log, you should be able to boot into other OSs you have, at least on sda disk.

This is the key thing:

The default repair of the Boot-Repair utility will reinstall the grub2 of sda5 into the MBRs of all disks
(except live-disks and removable disks without OS).

Code:

grub-probe: error: cannot find a GRUB drive for /dev/sdb1.

That is your error and it means nothing, in my opinion, and you can ignore it.

You might know what sdb1 refers to. Looks strange to me! -->

Code:

Drive: sdb _____________________________________________________________________
Disk /dev/sdb: [COLOR=#ff0000][B]1.9 GiB[/B][/COLOR], 2004877312 bytes, 3915776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *              0     3,162,975     3,162,976   0 Empty
/dev/sdb2           3,136,968     3,141,703         4,736  ef EFI (FAT-12/16/32)

[B]/dev/sdb1 overlaps with /dev/sdb2[/B]

[B]GUID Partition Table detected, but does not seem to be used[/B].

Partition  Attrs   Start Sector    End Sector  # of Sectors System
/dev/sdb1   +  R              0     3,162,919     3,162,920 Data partition (Windows/Linux)
/dev/sdb2   +  R      3,136,968     3,141,703         4,736 Data partition (Windows/Linux)

A flash drive? It has a GPT (GUID Partition Table) that is not being used.
You can ignore this: "/dev/sdb1 overlaps with /dev/sdb2"
because that has to do with how live OSs are often installed to flash drives,
for some strange technical reason, and is OK (some of my good live flash drives look like that).
We've had discussion here at kubuntuforums about that strange flash drive set up,
and it's nothing to be concerned about (ref.: Steve Riley, myself, and others).
So, let's just ignore sdb, unless you say otherwise.

You do seem to have a lot of stuff (drives) attached to this computer!

At least, as you said, you can boot.

And thanks, Vinny, for your push! ;-)

**Qqmike** · Nov 13, 2018, 06:25 AM

btw, on sdb, again, you will see other weird messages on your Boot-Repair report.
Like Line 1519:
Unknown MBR on /dev/sdb

And keep looking at that MBR hex dump, down around 1532 and following:

Code:

....[B]isolinux[/B].bin|
000000c0  20 6d 69 73 73 69 6e 67  20 6f 72 20 63 6f 72 72  | [B]missing or corr[/B]|
000000d0  75 70 74 2e 0d 0a 66 60  66 31 d2 66 03 06 f8 7b  |[B]upt[/B]...f`f1.f...{|
000000e0  66 13 16 fc 7b 66 52 66  50 06 53 6a 01 6a 10 89  |f...{fRfP.Sj.j..|
000000f0  e6 66 f7 36 e8 7b c0 e4  06 88 e1 88 c5 92 f6 36  |.f.6.{.........6|
00000100  ee 7b 88 c6 08 e1 41 b8  01 02 8a 16 f2 7b cd 13  |.{....A......{..|
00000110  8d 64 10 66 61 c3 e8 1e  00 4f 70 65 72 61 74 69  |.d.fa....[B]Operati[/B]|
00000120  6e 67 20 73 79 73 74 65  6d 20 6c 6f 61 64 20 65  |[B]ng system load e[/B]|
00000130  72 72 6f 72 2e 0d 0a 5e  ac b4 0e 8a 3e 62 04 b3  |[B]rror[/B].

And keep reading, up comes the red print showing issues and so on and on.
That isolinux does indicate an attempt to make a bootable flash drive (with sdb ).
And there are errors as you can glean.
Again, just ignore this whole mess with sdb, sdb1, sdb2.
It is a separate subject.

**GreyGeek** · Nov 13, 2018, 12:55 PM

As long as he can mount the partitions and save off his data. If not, and the boot repair fails, all he has left is to destroy all the existing partitions and install a fresh copy of the OS's.

**Qqmike** · Nov 13, 2018, 01:51 PM

Post #53, he said,

But I can boot :-)

Seems to imply Boot-Repair succeeded. (If it had not, he should then run TestDisk to fix the partitions, if that's the cause of booting problems.)

**nicrnicr** · Nov 15, 2018, 08:12 AM

Thank you Qqmike & Greygeek for your further pieces of advice.

"That isolinux does indicate an attempt to make a bootable flash drive (with sdb )."
Yes Qqmike, you could figure out what 1,9 GB refers to: a flash drive which is too small for the installation of a persistent Kubuntu.

It took me a very long time to clean up some external hdd, in order to use one of them as persistent bootable Kubuntu to have boot repair definitely installed inside it. Through this medium I could enlarge the size of Kubuntu 18.04. It's done.

Btw: It's seems that this persistent Kubuntu 18.04 is the first that I have whose search function (on the top of a Dolphin window) searches.

**Qqmike** · Nov 15, 2018, 08:18 AM

It took me a very long time to clean up some external hdd, in order to use one of them as persistent bootable Kubuntu to have boot repair definitely installed inside it. Through this medium I could enlarge the size of Kubuntu 18.04. It's done.

Wow, very nice work, nicrnicr. And thanks for your feedback and progress report.

**jlittle** · Nov 16, 2018, 03:54 AM

Originally posted by nicrnicr View Post

It took me a very long time to clean up some external hdd, in order to use one of them as persistent bootable Kubuntu to have boot repair definitely installed inside it. Through this medium I could enlarge the size of Kubuntu 18.04.

You could have booted directly into a Kubuntu iso, no need to write it anywhere. I discussed this in this post. Could save a lot of mucking around.

Announcement

I cannot extend the size of Kubuntu 18.04

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment