I tried different options from above menu. But each one results in very slow boot or blank screen. I can access my /home with login through command prompt.
click the ‘E’ button to edit boot options and remove from there this option: quiet and check where it its stuck… when you in your sytem provide logs: journalctl --boot=0 --priority=3 --no-pager
I’ve been there. After a lot of horrible time I discovered that:
BTRFS and Timeshift causes Baloo to reindex the new snapshot. Whenever a snapshot is taken (whether by BTRFS or Timeshift) Baloo reindexes all files in the snapshot. This is of course uses a lot of resources especially you say
What I did was:
Fresh install, default EXT4, [BTRFS (if you really want it) for boot/System only ] NOT FOR HOME AND USER DATA
I installed the previous LTS Kernel just in case.
There is a bug filed at Baloo about it keeping reindexing snapshots.
If you search for a a file you will find same file appearing several times, while it is only the same file in different snapshots and each one reindexed. Please let me know if this is the case with your files. If so, it proofs what I mentioned above.
Everything is working more than perfect with me now.
And let me know if no BTRFS/Timeshift works for you.
No it is not the case. In my case, symptoms worsened AFTER I disabled baloo, and restored system to a snapshot. And even when baloo was enabled, I was indexing /home/abad/Documents only. I was NOT indexing everything in my home folder.
is o.k. boot, esp = flag of the /boot/efi Partition (fat32 formatted). System needs this.
Do not touch nor move!!!.
BTRFS is the filesystem of sda2. Bad decision to put root and home on the same partition, I repeat!!
.
Try the following in Terminal: sudo mkinitcpio -P && sudo update-grub
Whats about: https://forums.linuxmint.com/viewtopic.php?t=337404
.
Timeshift and ext4 may be easier - but you need another drive, whereas btrfs resides on your sda2…
…btw. your system is waiting for drives, which do not exist 8any longer)
check your fstab if the three drives “timed out waiting…” are mentioned in fstab
And try in Terminal: blkid -o list whether disks / partition exist.
He is in an emergency shell without anything being mounted.
He has to mount root and extract pacman.log or pamac.log or alternatively chroot into system, provide what he did, update, etc.
Thanks tolerating me. And also for confirming that my partition scheme is good for timeshift snapshot. Puzzle remains that restoring a snapshot broke my system. Or I made mistake somewhere.