Score:0

After update, primary disk w/MBR lost mount point and will not boot

us flag

My primary MBR disk is encrypted using LUKS. I ran the recommended updates and lost the mount points on all 3 of my HDD's. Here is the fdisk and blkid for my primary drive. The others I use for storage only, so I'm not concerned about restoring mount points for those, but I sure do not want to have to reinstall 18.04. I do not want to have to reinstall all of my software.

root@ubuntu:~# fdisk -l

Disk /dev/loop0: 1.9 GiB, 2029981696 bytes, 3964808 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: 89.1 MiB, 93417472 bytes, 182456 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: 54.7 MiB, 57294848 bytes, 111904 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: 44.9 MiB, 47063040 bytes, 91920 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: 160.2 MiB, 167931904 bytes, 327992 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: 4.2 MiB, 4403200 bytes, 8600 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: 14.8 MiB, 15462400 bytes, 30200 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: 956 KiB, 978944 bytes, 1912 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/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb4ef2c8e

Device     Boot   Start        End    Sectors   Size Id Type
/dev/sda1  *       2048    1499135    1497088   731M 83 Linux
/dev/sda2       1501182 1953523711 1952022530 930.8G  5 Extended
/dev/sda5       1501184 1953523711 1952022528 930.8G 83 Linux

Partition 2 does not start on physical sector boundary.


Disk /dev/loop8: 3.7 MiB, 3825664 bytes, 7472 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

root@ubuntu:~# blkid

/dev/sda1: UUID="a7edcdc8-aad6-4eba-815b-b8eacae62e5a" TYPE="ext4" PARTUUID="b4ef2c8e-01"
/dev/sr0: UUID="2020-02-03-18-40-13-00" LABEL="Ubuntu 18.04.4 LTS amd64" TYPE="iso9660" PTUUID="6e037a9d" PTTYPE="dos"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda5: UUID="02ac378e-f62e-4195-abec-a818aa27a98e" TYPE="crypto_LUKS" PARTUUID="b4ef2c8e-05"
/dev/loop8: TYPE="squashfs"
/dev/mapper/luks-02ac378e-f62e-4195-abec-a818aa27a98e: UUID="Mw2EIi-Wd6m-zblD-xw6v-zq4F-Gdft-cp6p1k" TYPE="LVM2_member"
/dev/mapper/ubuntu--vg-root: UUID="09d47bb9-8439-4475-a0c2-075ebe8555c7" TYPE="ext4"
/dev/mapper/ubuntu--vg-swap_1: UUID="c0b5b2c9-0c90-4b07-91db-bcc751aad18c" TYPE="swap"

Can someone please guide me to recovery here? I have read many of the previous posts concerning editing /etc/fstab to restore mount points, but I guess I'm not finding in the instructions all that is necessary to complete the task.

enter image description here

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/ubuntu--vg-root /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=a7edcdc8-aad6-4eba-815b-b8eacae62e5a /boot           ext4    defaults        0       2
/dev/mapper/ubuntu--vg-swap_1 none            swap    sw              0       0

root@ubuntu:~# fsck -f /dev/mapper/ubuntu--vg-root

fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Inode 36045055 extent tree (at level 1) could be shorter.  Fix<y>? no
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/ubuntu--vg-root: 371495/60940288 files (0.3% non-contiguous), 8354382/243743744 blocks

root@ubuntu:~# lsblk

NAME                   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0                    7:0    0   1.9G  1 loop  /rofs
loop1                    7:1    0  89.1M  1 loop  /snap/core/8268
loop2                    7:2    0  54.7M  1 loop  /snap/core18/1668
loop3                    7:3    0  44.9M  1 loop  /snap/gtk-common-themes/1440
loop4                    7:4    0 160.2M  1 loop  /snap/gnome-3-28-1804/116
loop5                    7:5    0   4.2M  1 loop  /snap/gnome-calculator/544
loop6                    7:6    0  14.8M  1 loop  /snap/gnome-characters/399
loop7                    7:7    0   956K  1 loop  /snap/gnome-logs/81
loop8                    7:8    0   3.7M  1 loop  /snap/gnome-system-monitor/127
sda                      8:0    0 931.5G  0 disk  
├─sda1                   8:1    0   731M  0 part  
├─sda2                   8:2    0     1K  0 part  
└─sda5                   8:5    0 930.8G  0 part  
  └─luks-02ac378e-f62e-4195-abec-a818aa27a98e
                       253:0    0 930.8G  0 crypt 
    ├─ubuntu--vg-root  253:1    0 929.8G  0 lvm   
    └─ubuntu--vg-swap_1
                       253:2    0   976M  0 lvm   
sr0                     11:0    1     2G  0 rom   /cdrom

enter image description here

enter image description here

ru flag
Comments are not for extended discussion; this conversation has been [moved to chat](https://chat.stackexchange.com/rooms/127885/discussion-on-question-by-jamesreece-after-update-primary-disk-w-mbr-lost-mount).

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.