I am running Ubuntu as a dual boot with Windows 10 and a few months ago faced the issue where I wasn't able to boot into Ubuntu and was getting an error similar to the error message in the title of this question.
After I followed some of the instructions in various other questions, I believe I messed up my configuration even more and started getting this error. Now, I don't even remember what all steps I had followed but I can share the current state of my system using a live CD, hoping that someone on this forum can help me recover my Ubuntu installation.
Here is the output of sudo fdisk -l
Disk /dev/loop0: 2.13 GiB, 2285019136 bytes, 4462928 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: 4 KiB, 4096 bytes, 8 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: 61.93 MiB, 64917504 bytes, 126792 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: 54.24 MiB, 56872960 bytes, 111080 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: 43.6 MiB, 45703168 bytes, 89264 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: 248.78 MiB, 260841472 bytes, 509456 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: 65.22 MiB, 68378624 bytes, 133552 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/nvme0n1: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 980 1TB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: gpt
Disk identifier: F4B482C8-CEFA-4AF7-88D7-5B3A306A710D
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 502988799 502421504 239.6G Microsoft basic data
/dev/nvme0n1p4 502988800 998166527 495177728 236.1G Linux filesystem
/dev/nvme0n1p5 998166528 1000214527 2048000 1000M Windows recovery environment
/dev/nvme0n1p6 1000214528 1482485759 482271232 230G Linux filesystem
/dev/nvme0n1p7 1482485760 1953523711 471037952 224.6G Microsoft basic data
Disk /dev/sda: 28.66 GiB, 30752636928 bytes, 60063744 sectors
Disk model: Ultra
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
Disk identifier: 0x001fbc63
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 60063743 60061696 28.7G c W95 FAT32 (LBA)
sudo fdisk -l /dev/nvme0n1p4 shows this
Disk /dev/nvme0n1p4: 236.12 GiB, 253530996736 bytes, 495177728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
sudo fdisk -l /dev/nvme0n1p1 shows this
Disk /dev/nvme0n1p1: 260 MiB, 272629760 bytes, 532480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: dos
Disk identifier: 0x500a0dff
Device Boot Start End Sectors Size Id Type
/dev/nvme0n1p1p1 1948285285 3650263507 1701978223 811.6G 6e unknown
/dev/nvme0n1p1p2 0 0 0 0B 74 unknown
/dev/nvme0n1p1p4 28049408 28049848 441 220.5K 0 Empty
Partition 1 does not start on physical sector boundary.
I think previously I messed up the config by pointing the boot loader to try and boot from /dev/nvme0n1p4 hence the error message. Is there anything I can do to fix this?
Any help in pointing me in the right direction will be greatly appreciated.
