You can just highlight the blkid output with the mouse (left click and drag), then cut it (ctrl+shift+c) and paste it (ctrl+v) into a message here, no images needed.
Here is the result of the blkid ask. Next step was to open the root partition and check /etc/fstab. I am not sure exactly how to do that. Through the file manager I find a folder called root, then open in file manager and enter /etc/fstab and get "permission denied" The root directory has a big red X on it, by the way. Opening the properties show "contents unreadable". HELP
Once again, would there be any future in trying to just download the upgrade again?
/dev/sda2: LABEL="Ubuntu" UUID="6496c978-c968-4bdf-8a40-f3b3f0b0233b" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="77cb2e96-3e43-4e65-8073-3971a676c183"
/dev/sda3: UUID="748c985b-1fe1-4dac-9dae-b3b8190a8652" TYPE="swap" PARTLABEL="primary" PARTUUID="a166aaa4-de0e-48d0-9f3e-7120808fb581"
/dev/sda1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="E980-6849" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="72ad959e-885d-48fa-a5ee-0ebbb0cc3777"
/dev/loop1: TYPE="squashfs"
/dev/loop29: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop37: TYPE="squashfs"
/dev/loop27: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop35: TYPE="squashfs"
/dev/loop25: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop33: TYPE="squashfs"
/dev/loop23: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop31: TYPE="squashfs"
/dev/loop21: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/loop28: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop36: TYPE="squashfs"
/dev/loop26: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/loop34: TYPE="squashfs"
/dev/loop24: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop32: TYPE="squashfs"
/dev/loop22: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop30: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
Like this:
Should produce something like:Code:less /etc/fstab
Code:# /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> # / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation /dev/disk/by-id/dm-uuid-LVM-0ZAaK5oRVBHO3ZRf1fioebvMh26oly5hCDIqf16aLTP7b1xuKPXWiqztjufoeves / ext4 defaults 0 1 # /boot was on /dev/sdc2 during curtin installation /dev/disk/by-uuid/31ce1973-70eb-434b-9d53-158685cb189c /boot ext4 defaults 0 1 # /boot/efi was on /dev/sdc1 during curtin installation /dev/disk/by-uuid/DA34-E212 /boot/efi vfat defaults 0 1 /swap.img none swap sw 0 0
"When you practice gratefulness, there is a sense of respect toward others." >>Dalai Lama
Looks like a typo somewhere, the actual UUID is as blkid reported:6496c978-c968-4bdf-8a40-f3b3f0b0233b The error message has ...fb3f0... missing a 3
ubfan1, yes it is my typo. the UUIDs are identical. I dropped a 3 when typing the error message.
Dear Friends,
So sorry this is taking so long. Here is the response to less /etc/fstab
What next? Sorry to be so helpless.Code:# /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/sda2 UUID=6496c978-c968-4bdf-8a40-f3b3f0b0233b / ext4 noatime,errors=remount-ro 0 1 # /dev/sda1 UUID=E980-6849 /boot/efi vfat umask=0077 0 1 # /dev/sda3 UUID=748c985b-1fe1-4dac-9dae-b3b8190a8652 none swap sw 0 0 ~ ~ ~ ~ ~ ~
Yours hopefully,
Joe
ps, once again, since I can get this machine kind of running in recovery mode, would it be worth trying to download Ubuntu 24.04 again and see if it straightens things out?
Last edited by ajgreeny; 2 Weeks Ago at 10:44 AM. Reason: Code tags repaired
CowDoctor; Ouch
Your /etc/fstab file does not in almost all respects agree with what blkid reports.
Let's see what we can do to make it right.
Post back:
so we know what the boot partition is and *IF* there is a swap partition.Code:sudo fdisk -lu swapon --summary
maybe, this is all there is to it
Thank you. This, I believe, is the relevant part of the response to the fdisk request:
There were 38 loops reported, all nearly identical except for some numbers in the first lines. The above code between loops 7 and 8.Code:Disk /dev/sda: 111.8 GiB, 120040980480 bytes, 234455040 sectors Disk model: WDC WDS120G2G0B- 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: BA5E4D98-D80E-415E-A1C7-9ADE1CE33BBB Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 226064383 225013760 107.3G Linux filesystem /dev/sda3 226064384 234452991 8388608 4G Linux swap
I can copy the whole thing if you wish.
and here is the swapon:
Hope this is usefulCode:oe@Bucky:~$ swapon --summary Filename Type Size Used Priority /dev/sda3 partition 4194300 0 -2
CowDoctor; Well yeas
All looks good - and all agrees. (why using code tags is so important, as I did goof in reading)
OK go back and verify that the UUID 6496c978-c968-4bdf-8a40-fb3f0b0233b is a typo on your part relaying to the post.
else we got to go hunting.
it's in the process
Bookmarks