My system will not restore from timeshift options in GRUB.
I was installing Master PDF Editor 5 with pacman and chose the option for the dependancies,
All was going well until a got a message that read "disk full"
The disk was not full and I couldnt access any thing -as though the system froze. The only thing that moved was the cursor.
So as I couldnt do anything, Id restore from GRUB timeshift.
I chose the latest snapshot, hit enter and 45 minutes later, the white progress marker no longer moves.
As I cannot get into a command prompt, I cannot type in the inxi thingy,
I have retired earlier restor points with the same result - the progress bar just hangs.
Not sure what to do as I cannot get into the system.
I tried some commands in the GRUB command but it only lists a few basic commands,
Have you tried chrooting from a live USB into your system (e.g. follow How to chroot Garuda Linux ) then free up some space if necessary. I think you can also reach your snapshots from the timeshift in the USB and delete old unneded snapshots.
Okay, good morning.
After reading how to chroot Garuda Linux I did the following:
sudo mkdir -p /mnt/broken (This executed no problem)
sudo mount /dev/sda3 /mnt/broken
mount: /mnt/broken: can't read superblock on /dev/sda3.
So this is where I am now stuck. Please help. Thanks
my error thank you - I didnt use sudo.
So tried again and got over 100 "root 486 inode 859744 errors 2001, no inode item, link count wrong
unresolved ref dir 218323 index 4351 namelen 10 name timestamps filetype 1 errors 4, no inode ref" messages.
Also got the following:
ERROR: errors found in fs roots
found 32967643136 bytes used, error(s) found
total csum bytes: 30371416
total tree bytes: 689061888
total fs tree bytes: 609189888
total extent tree bytes: 39501824
btree space waste bytes: 124991599
file data blocks allocated: 996641492992
Was scared to try this cos they give a strict warning - DO NOT TRY THIS UNLESS etc.
HOWEVER, Im past playing, so I hit enter and the terminal goes crazy.
deleting dir index - thousands of lines
Repairing something dir index - thousands of lines
2 hours later it stops.
Okay so I dont know enough commands to be fiddling in chroot so I reboot (otherwise I was going to format) and VOILA!!! it boots in to my GARUDA.
I must just run one or 2 checks, maybe Ill use an earlier snapshot and repair like.
A big thank you to all who gave input. My system is up and running. Not a journey I want to go through again - but I suppose thats the way we learn.