Ubuntu

18.10 update/upgrade included GRUB: Destroyed my Windows entry in GRUB.

Asked by William Sandhu

Dual boot system. Raid1 using Intel Rapid Store Technology. Intel i7 system. ASUS Z97 usb 3.1 motherboard. 32GB mem. Been working fine until now. After doing an APT update + upgrade today, which I noticed included grub upgrades, my windows 10 entry got wiped out... After reboot, the system goes directly into Ubuntu - bypasses the grub menu at boot.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said : 		#1

Support for Ubuntu 8.10 has ended eight years ago.
Sorry, but we cannot help with "ancient" releases of Ubuntu any more.

Revision history for this message
William Sandhu (wsandhu) said : 		#2

Missed the leading digit. 18.10 (corrected). Current release. Cosmic Cuttlefish.

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

For diagnostic purposes, what is the output of the commands

uname -a
lsb_release -crid
sudo os-prober
sudo update-grub
sudo fdisk -l

Revision history for this message
William Sandhu (wsandhu) said : 		#4

wssan@lynx:~$ uname -a
Linux lynx 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

wssan@lynx:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 18.10
Release: 18.10
Codename: cosmic

wssan@lynx:~$ sudo os-prober
wssan@lynx:~$

wssan@lynx:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.18.0-10-generic
Found initrd image: /boot/initrd.img-4.18.0-10-generic
Found linux image: /boot/vmlinuz-4.15.0-36-generic
Found initrd image: /boot/initrd.img-4.15.0-36-generic
Adding boot menu entry for EFI firmware configuration
done

wssan@lynx:~$ sudo fdisk -l
Disk /dev/loop0: 86.9 MiB, 91099136 bytes, 177928 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

Disk /dev/loop1: 87.9 MiB, 92123136 bytes, 179928 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

Disk /dev/loop2: 13 MiB, 13619200 bytes, 26600 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

Disk /dev/loop3: 140.9 MiB, 147722240 bytes, 288520 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

Disk /dev/loop4: 6.3 MiB, 6643712 bytes, 12976 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

Disk /dev/loop5: 3.7 MiB, 3878912 bytes, 7576 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

Disk /dev/loop6: 42.1 MiB, 44183552 bytes, 86296 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

Disk /dev/loop7: 2.3 MiB, 2355200 bytes, 4600 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

The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt
Disk identifier: 4F4E0CDD-1EAD-4316-98D1-E762A1FB2CD0

Device Start End Sectors Size Type
/dev/sda1 2048 1023999 1021952 499M Windows recovery environment
/dev/sda2 1024000 1228799 204800 100M EFI System
/dev/sda3 1228800 1261567 32768 16M Microsoft reserved
/dev/sda4 1261568 201324543 200062976 95.4G Microsoft basic data

The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt
Disk identifier: 4F4E0CDD-1EAD-4316-98D1-E762A1FB2CD0

Device Start End Sectors Size Type
/dev/sdb1 2048 1023999 1021952 499M Windows recovery environment
/dev/sdb2 1024000 1228799 204800 100M EFI System
/dev/sdb3 1228800 1261567 32768 16M Microsoft reserved
/dev/sdb4 1261568 201324543 200062976 95.4G Microsoft basic data

Disk /dev/sdc: 149.1 GiB, 160041885696 bytes, 312581808 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: gpt
Disk identifier: 6774889E-94E8-4813-A395-6A5ADE4EE1EC

Device Start End Sectors Size Type
/dev/sdc1 34 32767 32734 16M Microsoft reserved
/dev/sdc2 32768 67141631 67108864 32G Microsoft basic data
/dev/sdc3 67141632 134250495 67108864 32G Microsoft basic data

The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/mapper/isw_cdcibijgfj_wynd: 96 GiB, 103079350272 bytes, 201326856 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: gpt
Disk identifier: 4F4E0CDD-1EAD-4316-98D1-E762A1FB2CD0

Device Start End Sectors Size Type
/dev/mapper/isw_cdcibijgfj_wynd1 2048 1023999 1021952 499M Windows recov
/dev/mapper/isw_cdcibijgfj_wynd2 1024000 1228799 204800 100M EFI System
/dev/mapper/isw_cdcibijgfj_wynd3 1228800 1261567 32768 16M Microsoft res
/dev/mapper/isw_cdcibijgfj_wynd4 1261568 201324543 200062976 95.4G Microsoft bas

The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/mapper/isw_cdcibijgfj_lynx: 142.5 GiB, 152975839232 bytes, 298780936 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: gpt
Disk identifier: EEFD2E9C-27D8-4336-93D6-94B7AD53E573

Device Start End Sectors Size Type
/dev/mapper/isw_cdcibijgfj_lynx1 2048 192002047 192000000 91.6G Linux files
/dev/mapper/isw_cdcibijgfj_lynx2 192002048 298778623 106776576 50.9G Linux files

Disk /dev/loop8: 14.5 MiB, 15208448 bytes, 29704 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

Disk /dev/loop9: 2.3 MiB, 2433024 bytes, 4752 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

Disk /dev/loop10: 3.7 MiB, 3887104 bytes, 7592 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

Disk /dev/loop11: 87.9 MiB, 92119040 bytes, 179920 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

Disk /dev/loop12: 13 MiB, 13619200 bytes, 26600 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

Disk /dev/loop13: 14.5 MiB, 15196160 bytes, 29680 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

Disk /dev/loop14: 34.7 MiB, 36323328 bytes, 70944 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

Disk /dev/loop15: 4.9 MiB, 5148672 bytes, 10056 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

Disk /dev/loop16: 140.7 MiB, 147496960 bytes, 288080 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

Revision history for this message
Manfred Hampl (m-hampl) said : 		#5

Try mounting your Windows partition (I assume it's /dev/mapper/isw_cdcibijgfj_wynd4) somewhere, and re-run
sudo os-prober
What output do you receive?

Revision history for this message
William Sandhu (wsandhu) said : 		#6

root@lynx:~# cd /mnt
root@lynx:/mnt# mkdir wynd4
root@lynx:/mnt# mount -t /dev/mapper/isw_cdcibijgfj_wynd4 ./wynd4/
mount: ./wynd4/: can't find in /etc/fstab.
root@lynx:/mnt# mount /dev/mapper/isw_cdcibijgfj_wynd4 ./wynd4/
root@lynx:/mnt# cd ./wynd4/
root@lynx:/mnt/wynd4# ll
total 18656040
drwxrwxrwx 1 root root 4096 Oct 10 01:25 ./
drwxr-xr-x 11 root root 4096 Oct 18 16:34 ../
drwxrwxrwx 1 root root 0 Oct 10 01:16 '$Recycle.Bin'/
lrwxrwxrwx 2 root root 16 Oct 10 08:03 'Documents and Settings' -> /mnt/wynd4/Users/
-rwxrwxrwx 1 root root 13718237184 Oct 10 01:26 hiberfil.sys*
-rwxrwxrwx 1 root root 5368709120 Oct 10 01:26 pagefile.sys*
drwxrwxrwx 1 root root 0 Apr 11 2018 PerfLogs/
drwxrwxrwx 1 root root 4096 Oct 10 01:24 ProgramData/
drwxrwxrwx 1 root root 8192 Oct 10 01:24 'Program Files'/
drwxrwxrwx 1 root root 4096 Oct 10 01:22 'Program Files (x86)'/
drwxrwxrwx 1 root root 0 Oct 10 08:02 Recovery/
-rwxrwxrwx 1 root root 16777216 Oct 10 01:26 swapfile.sys*
drwxrwxrwx 1 root root 4096 Oct 10 01:12 'System Volume Information'/
drwxrwxrwx 1 root root 4096 Oct 10 01:18 Users/
drwxrwxrwx 1 root root 28672 Oct 10 01:23 Windows/
root@lynx:/mnt/wynd4# sudo os-prober
root@lynx:/mnt/wynd4#

Revision history for this message
Manfred Hampl (m-hampl) said : 		#7

What output do you receive for the commands

sudo dmraid -s -c
sudo dmraid -sa -c

Revision history for this message
William Sandhu (wsandhu) said : 		#8

root@lynx:~# sudo dmraid -s -c
isw_cdcibijgfj_lynx
isw_cdcibijgfj_wynd
root@lynx:~# sudo dmraid -sa -c
isw_cdcibijgfj_lynx
isw_cdcibijgfj_wynd
root@lynx:~#

Revision history for this message
Manfred Hampl (m-hampl) said : 		#9

I am sorry, but I do not understand why the os-prober script of grub does not find your windows partition.

Maybe running the script with trace helps finding the cause.
What is the output of

sudo sh -x /usr/bin/os-prober

Revision history for this message
William Sandhu (wsandhu) said : 		#10

wssan@lynx:~$ sudo sh -x /usr/bin/os-prober
[sudo] password for wssan:
+ set -e
+ . /usr/share/os-prober/common.sh
+ cleanup_tmpdir=false
+ progname=
+ type mapdevfs
+ newns
+ [ ]
+ exec /usr/lib/os-prober/newns /usr/bin/os-prober
wssan@lynx:~$

Revision history for this message
Manfred Hampl (m-hampl) said : 		#11

Sorry, I am lost. I am not able to identify the reason for your problem.
Maybe somebody else can help.

Revision history for this message
William Sandhu (wsandhu) said : 		#12

Thanks for taking the time to look into this. I have reverted back to the LTS version 18.04.01 (bionic). I also repurposed my SSD raid pairs for another project and am now running on a non-redundant PCIe M.2 NVMe system disk.

Revision history for this message
Launchpad Janitor (janitor) said : 		#13

This question was expired because it remained in the 'Open' state without activity for the last 15 days.