Hello again, dear Manjaro people!!
@maycne.sonahoz Yes. Maybe it is not I2P to blame but the way I reset the system by holding down the power button to off-and-on. That could’ve damaged the filesystem, yes?
**A person I saw recently said I should have used the technique of holding Alt + Print Screen while pressing REISUB (or BUSIER backwards) and this is much safer. **
Anyway I decided to test (mind the pun) testdisk and it worked! I hoped to use software only available on the live disk but beggers can’t be choosers. The lost+found folder appeared to me again, and had a number of folders in it and together they are many GB and possibly the entire operating system?? The extent of what has been restored is here.
One folder (maybe /boot ??) contains:
drwx------ 0 0 4096 ..
drwxr-xr-x 0 0 4096 efi
drwxr-xr-x 0 0 4096 grub
drwxr-xr-x 0 0 4096 memtest86+
-rw-r--r-- 0 0 XXX linux54-x86_64.kver
(...)
-rw-r--r-- 0 0 XXX linux510-x86_64.kver
-rw-r--r-- 0 0 XXX vmlinuz-5.8-x86_64
-rw-r--r-- 0 0 XXX initramfs-5.8-x86_64.img
-rw-r--r-- 0 0 XXX initramfs-5.8-x86_64-fallbac
-rw-r--r-- 0 0 XXX linux59-x86_64.kver
-rw-r--r-- 0 0 XXX vmlinuz-5.9-x86_64
-rw-r--r-- 0 0 XXX initramfs-5.9-x86_64.img
Another folder ()
lrwxrwxrwx 0 0 3 lib64
lrwxrwxrwx 0 0 3 sbin
drwxr-xr-x 0 0 XXX bin
drwxr-xr-x 0 0 XXX include
drwxr-xr-x 0 0 XXX lib
drwxr-xr-x 0 0 XXX local
drwxr-xr-x 0 0 XXX share
drwxr-xr-x 0 0 XXX src
drwxr-xr-x 0 0 XXX lib32
drwxr-xr-x 0 0 4096 libexec
Another folder
drwx------ .gnupg
drwx------ .cache
-rw-r--r-- .bash_logout
-rw-r--r-- .bash_profile
-rw-r--r-- .bashrc
drwxr-xr-x .config
-rw-r--r-- .screenrc
-rwxr-xr-x .Xclients
-rw-r--r-- .dir_colors
-rw-r--r-- .profile
-rw-r--r-- .xinitrc
drwx------ .dbus
Another folder
(the contents of /home/ !! )
Another folder (/var?)
lrwxrwxrwx 0 0 XXX lock
lrwxrwxrwx 0 0 XXX mail
lrwxrwxrwx 0 0 XXX run
drwxr-xr-x 0 0 4096 cache
drwxr-xr-x 0 0 4096 db
drwxr-xr-x 0 0 4096 empty
drwxrwxr-x 0 50 4096 games
drwxr-xr-x 0 0 4096 lib
drwxr-xr-x 0 0 4096 local
drwxr-xr-x 0 0 4096 log
drwxr-xr-x 0 0 4096 opt
drwxr-xr-x 0 0 4096 spool
drwxrwxrwt 0 0 4096 tmp
-rw-r--r-- 0 0 XXX .updated
Another folder
dr-xr-xr-x 0 11 4096 ftp
drwxr-xr-x 0 0 4096 http
Another folder
lrwxrwxrwx 0 0 XXX arch-release
lrwxrwxrwx 0 0 XXX os-release
drwxr-xr-x 0 0 4096 binfmt.d
drwxr-xr-x 0 0 4096 cron.daily
drwxr-xr-x 0 0 4096 cron.monthly
drwxr-xr-x 0 0 4096 exports.d
drwxr-xr-x 0 0 4096 gssproxy
drwxr-xr-x 0 0 4096 iptables
drwxr-xr-x 0 0 4096 kernel
drwxr-xr-x 0 0 4096 lvm
drwxr-xr-x 0 0 4096 mkinitcpio.d
drwxr-xr-x 0 0 4096 modprobe.d
(... skipped files ...)
drwxr-xr-x 0 0 4096 sensors.d
-rw-r--r-- 0 0 XXX ts.conf
drwxr-xr-x 0 0 4096 grub.d
-rw-r--r-- 0 0 XXX tlp.conf
drwxr-xr-x 0 0 4096 openldap
-rw-r--r-- 0 0 XXX resolvconf.conf
-rw-r--r-- 0 0 XXX ostree-mkinitcpio.conf
-rw-r--r-- 0 0 XXX anacrontab
drwxr-xr-x 0 0 4096 libnl
-rw-r--r-- 0 0 XXX mhwd-x86_64.conf
drwxr-xr-x 0 0 4096 timeshift
I’ve done a bunch of searches online about whether an O/S can be restored from files collected in Lost+found but nothing seems to talk in those terms. Possibly because its difficult to guarantee that a bunch of restored files will function as a whole system. Not even the website of System Rescue seemed to talk about it.
Maybe I should cut my losses and just go through the process of reinstalling the O/S?
I would like to try to repair the O/S and/or partition and/or GRUB though, as an exercise in seeing whether I really have a bad HDD or its just a software glitch.
When I boot I get:
error: file `/boot/grub/x86_64-efi/normal.mod' not found.
Entering rescue mode...
grub rescue>
Whenever I run fsck though, irrespective of which superblock I try (with fsck -b [SUPERBLOCK]) I’m always getting the same