# Unable to mount on partition after update

**URL:** <https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [March 9, 2024, 12:14pm UTC](https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198 "2024-03-09T12:14:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryan](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/a8b319/32.png) [@ryan](https://forum.endeavouros.com/u/ryan)\
**Post date:** [March 9, 2024, 12:14pm UTC](https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198/1 "2024-03-09T12:14:42Z")

</div>

I updated to plasma 6 and other package then reboot after that. However, after reboot I am unable to mount the encrypted drive.

For context, I use the LUK encryption. I use grub as a bootloader. I also have timeshift but I didn’t enable to work on the grub menu.

Is there a way to use timeshift in the emergency sh in the image below or from a live usb?

I am stuck at this screen.

 ![IMG_20240309_123740](https://forum.endeavouros.com/uploads/default/original/3X/9/3/93d8b079b2983b41a5d50f6481d454783e2701fb.jpeg)

Any help or what to look into is appreciated.

---

<div class="post-metadata">

**Author:** ![linuxislife](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/linuxislife/32/91372_2.png) [@linuxislife](https://forum.endeavouros.com/u/linuxislife)\
**Post date:** [March 9, 2024, 1:09pm UTC](https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198/2 "2024-03-09T13:09:02Z")

</div>

> [@ryan](#):
>
> Is there a way to use timeshift in the emergency sh in the image below or from a live usb?

I’m not the best person to help you, maybe @dalto could  
But you can look **[here](https://forum.endeavouros.com/t/howto-gpt-uefi-install-with-full-disk-encryption-btrfsonluks-with-separate-root-home-and-pkg-subvolumes-hibernation-with-a-swapfile-auto-snapshots-with-easy-system-rollback-gui-boot-into-snapshots/3782/)** (the C and D points)

> **@2000 wrote**
>
> > [@HOWTO - GPT/UEFI install with full disk encryption: BTRFSonLUKS with separate root, home and pkg subvolumes; hibernation with a swapfile; auto-snapshots with easy system rollback (GUI); boot into snapshots](https://forum.endeavouros.com/t/howto-gpt-uefi-install-with-full-disk-encryption-btrfsonluks-with-separate-root-home-and-pkg-subvolumes-hibernation-with-a-swapfile-auto-snapshots-with-easy-system-rollback-gui-boot-into-snapshots/3782/1):
> >
> > **#** - **How to RESTORE a snapshot (previous system state)**
> > 
> > **A** - If you ever need to reset your system to a stored state, just
> > 
> > 1. Launch `Timeshift` from the menu (or desktop shortcut)
> > 2. Select a snapshot and hit restore
> > 3. Reboot
> > 
> > That’s all. Takes mere seconds and doesn’t get any easier.  
> > BTW, you could also restore a snapshot from the cli!
> > 
> > * * *
> > 
> > **B** - In case you can’t boot into your desktop environment try to
> > 
> > 1. Boot directly into a snapshot from the GRUB (boot) menu
> > 2. see A (above) …
> > 
> > * * *
> > 
> > **C** - In case you need to restore a snapshot from a live system (e. g. EndeavourOS Install medium)
> > 
> > 1. Boot into the live environment
> > 2. Install Timeshift into the live environment; run
> > 
> > > ```auto
> > > sudo pacman --noconfirm -Syy cronie
> > > 
> > > ```
> > 
> > yay --noconfirm -S timeshift
> > 
> > > ```auto
> > > 
> > > ```
> > 
> > 1. see A (above) …
> > 
> > * * *
> > 
> > **D** - In case you need to **`chroot`** from a live system (e. g. EndeavourOS Install medium)
> > 
> > 1. Boot into the live environment
> > 2. Decrypt and mount your luks partition (e. g. /dev/sda2)
> > 
> > > ```auto
> > > sudo cryptsetup luksOpen /dev/sda2 crypt &&
> > > 
> > > ```
> > 
> > sudo mount -o compress=zstd,subvol=@ /dev/mapper/crypt /mnt
> > 
> > > ```auto
> > > 
> > > ```
> > 
> > 1. Mount your EFI boot folder (e. g. /dev/sda1)
> > 
> > > ```auto
> > > sudo mount /dev/sda1 /mnt/boot/efi
> > > 
> > > ```
> > 
> > 1. `chroot` into your system
> > 
> > > ```auto
> > > sudo arch-chroot /mnt
> > > 
> > > ```
> > 
> > 1. Do some _root_ stuff …

---

<div class="post-metadata">

**Author:** ![ryan](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/a8b319/32.png) [@ryan](https://forum.endeavouros.com/u/ryan)\
**Post date:** [March 9, 2024, 3:23pm UTC](https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198/3 "2024-03-09T15:23:07Z")

</div>

Thanks for the suggestion. I will try it and report back.

---

<div class="post-metadata">

**Author:** ![ryan](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/a8b319/32.png) [@ryan](https://forum.endeavouros.com/u/ryan)\
**Post date:** [March 9, 2024, 4:37pm UTC](https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198/4 "2024-03-09T16:37:37Z")

</div>

Just an update.

The guide you mention really helped a lot. Especially the point you mention.

Timeshift is now working.

Thank you very much.

Although, the update still cause the problem. At least I have a way to do trail and error now to fix it now.

---

<div class="post-metadata">

**Author:** ![linuxislife](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/linuxislife/32/91372_2.png) [@linuxislife](https://forum.endeavouros.com/u/linuxislife)\
**Post date:** [March 9, 2024, 4:44pm UTC](https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198/5 "2024-03-09T16:44:46Z")

</div>

Cheers !

I don’t use plasma but I see a looooot of post with people having problem with the last update.

---

<div class="post-metadata">

**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\
**Post date:** [March 11, 2024, 4:45pm UTC](https://forum.endeavouros.com/t/unable-to-mount-on-partition-after-update/52198/6 "2024-03-11T16:45:18Z")

</div>

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