Can't boot Endeavour, and my boot partition is locked

General system Kernel, boot, graphics & hardware
1

Hi there everyone. I’ve been searching for a solution to this for a while, but I just can’t find anything matching my experience, hopefully this isn’t repetitive.

So after an update to my system, Endeavour completely disappeared from the systemd-boot menu. I thought that was weird, considering there was zero errors in the update process, so I decide to boot up a live disk to chroot into my system and figure out the issue. As I tried a couple of solutions, I kept being met with a Read-only file system error. Could I get some help on this? Thanks.

2

Can you post your /etc/fstab and maybe the part of the journal with the error message you mentioned?

3

Welcome to the community @hailfire :wave: :sunglasses: :enos_flag:

You might also query your drives S.M.A.R.T. to see if it reports any issue.

This will view the drives health status:

smartctl -H /dev/device

This will perform a quick test:

smartctl -t short /dev/device

Or a long test:

smartctl -t long /dev/device
4

Thank you Bink!
The S.M.A.R.T status appears to be fine. I also forgot to mention in my initial post that I’m using a dual boot setup with Windows 11, and the partition Endeavour is installed on is encrypted in case that is relevant.

5

Here’s the fstab

# /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>
UUID=30D0-B1E4                            /efi           vfat    fmask=0137,dmask=0027 0 2
/dev/mapper/luks-108c6cdb-b1c1-49be-b50d-e28684bbc84a /              ext4    noatime    0 1

How would I view the journal? Sorry, I’ve never really had to use it

6

is the EFI partition used by win and eos?

7

Yes, they’re shared.

8

could be entry was removed by a windows update… or the partition is simply in dirty bit state caused by windows , could be fast boot mode is reanabled on win from update too

9

Don’t think it would be a Windows Update, since there hasn’t been any updates to my system in a while.

I did a fsck check, and while there was a dirty bit, removing it didn’t do anything

I made sure to disable fastboot before coming to ask for help

10

i had similar issues on some installs over time.
Possible to recreate the efi partition and add the bootloader stuff in it again… not 100% the easy task … done that 3 times already.

11

I could do it, but I’d prefer to avoid it. If it’s the only solution, I’ll go ahead.

12

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

13

More a workaround, fat32 file system partition … not the best filesystem in the world i think.
Reason could be unattempted reboots or power loss ? but no clue, its annoying for sure.