0

During an automatic update on Ubuntu 16.04 LST with an update to Ubuntu 18.04 LST, I encountered and error which I have made worse by trying to fix.

To summarize I have a "boot drive" /sda1 with 3 partitions
Partition 1 512 FAT32 EFI system
Partition 2 512 Ext1 BIOS Bootable
Partition 3 959G Linux LVM - this contain the main HD and swap area

FYI, while I can "see" these partition on the Disk utility, I get nothing in the terminal when I type vgscan.

I have managed to destroy the BIOS Bootable - so that is blank and available When I currently boot, it appears to use the EFI and boot into grub, which if I knew what to do next may be fine.

I am currently booted off a USB flash drive Ubuntu 18.04 installation disk. When attempt to use the "Install Ubuntu App" click the "something else" since I just want to update not do a clean install and loose and data.

On the next page I am present wit the options of /dev/sda1 through dev/sda3, as partitions per above. I have tried several combinations and a warning that I need to increase a partition size to 4.9 gbytes.

So I need to set up the system so that it boots and mounts the LVM partition.

Thanks in advance

pf

Addendum: It appears that the fstab and grub.cfg are mess up. Below is additional information that may be of use:

# /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).  
#  
#                  
# / was on /dev/sda2 during installation  
UUID=3653100d-6690-4456-a6b9-13299060ad33 /               ext2    errors=remount-ro 0       1  
# /boot/efi was on /dev/sda1 during installation  
UUID=4CA2-4106  /boot/efi       vfat    umask=0077      0       1  
/swapfile

from the terminal:

root@ubuntu:~# blkid  
/dev/sda1: UUID="4CA2-4106" TYPE="vfat" PARTUUID="11a0c394-c5cd-47e1-a04a-82d581a5f507"    
/dev/sda2: UUID="3653100d-6690-4456-a6b9-13299060ad33" TYPE="ext2"   PARTUUID="3fc12e58-b028-4a45-976b-29ba68e01ba1"  
/dev/sdb1: LABEL="Alice" UUID="d661c71a-1931-44a2-91ec-92997fea6abe"   TYPE="ext4" PARTUUID="26d7b187-8019-4b5b-afa4-ac864b2fb772"  
/dev/sdc1: LABEL="UBUNTU 18_0" UUID="1DE3-3A5E" TYPE="vfat" PARTUUID="0298be7f-01"  
/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/sda3: PARTUUID="18ec3457-3f3e-4235-984f-390c89b388bc"

The volumes mounted using mount | grep "/dev/s" are

/dev/sdc1 /cdrom vfat   ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0   
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0  
/dev/sda1 /media/ubuntu/4CA2-4106 vfat   rw,nosuid,nodev,relatime,uid=999,gid=999,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0  
/dev/sda2 /media/ubuntu/3653100d-6690-4456-a6b9-13299060ad33 ext2   rw,nosuid,nodev,relatime,block_validity,barrier,user_xattr,acl,stripe=4 0 0  
/dev/sdb1 /media/ubuntu/Alice ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
root@ubuntu:/media/ubuntu/3653100d-6690-4456-a6b9-13299060ad33/etc# mount | grep "/dev/s"  
/dev/sdc1 on /cdrom type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)  
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)  
/dev/sda1 on /media/ubuntu/4CA2-4106 type vfat (rw,nosuid,nodev,relatime,uid=999,gid=999,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)  
/dev/sda2 on /media/ubuntu/3653100d-6690-4456-a6b9-13299060ad33 type ext2 (rw,nosuid,nodev,relatime,block_validity,barrier,user_xattr,acl,stripe=4,uhelper=udisks2)  
/dev/sdb1 on /media/ubuntu/Alice type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)

I cannot see the volume group using lvdisplay

So I either need a means of editing the fstab file to mount the LVM volume (which I have not found yet, I don't see a UUID for one) or I need an application that can open and read a LVM partition that runs either in Ubuntu, Windows 10 or Mac OS; the latter 2 being I pull the drive and copy it at home.)

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.