okay people , so i tried fixing it again with live usb
so my efi partition was FAT32 , and flagged with boot and esp
then the first step that i did was mounted the root partition of Manjaro
next step was editing the /etc/fstab file and putting the new UUID
saving and exiting and then un-mounting ,all this i have understood now
now it was time to restore grub bootloader
so i did root and manjaro-chroot -a
which listed all my linux os and asked me to choose the number for manjaro , which i did
so i further tried pacman -Syu grub
but this command didn’t get executed as my system hasn’t been updated from long and it resulted in error , so i closed the terminal and restarted my comp
this time i got to login and access my manjaro
there i tried to install grub using sudo update grub which installed some 0.1 mb file
and to configure it , grub-mkconfig -o /boot/grub/grub.cfg
after a few restarts the system was working , even tho the manjaro grub bootloader didn’t load up on boot , and then i turned of computer and later came back removed the live usb and tried to boot into manjaro and now i’m welcomed by another error
Failed to stat resume device '/dev/disk/by-uuid/8eb80e10-0b17-4e68-8d79-e1c69a79
2054` : No such file or directory
_
again i have booted with live usb and lsblk -f and realised now it’s something with swap memory of manjaro,i.e - sdb9
lsblk -f ✔
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/miso/sfs/livefs
loop1 squashfs 4.0 0 100% /run/miso/sfs/mhwdfs
loop2 squashfs 4.0 0 100% /run/miso/sfs/desktopfs
loop3 squashfs 4.0 0 100% /run/miso/sfs/rootfs
sda
├─sda1
├─sda2 ntfs Basic Softwares 0A241F40241F2E67
├─sda3 ntfs New Volume A47C0DD47C0DA262
└─sda4 ntfs WD Recovered 9C30E37D30E35CB0
sdb
├─sdb1 swap 1 4ddeeafa-1e01-40b5-9acd-1964b5d7d904
├─sdb2 ext4 1.0 deaf8b37-bb62-4476-b25b-01cfa045338e
├─sdb3 vfat FAT32 97D4-30D3
├─sdb4 ext4 1.0 427984c1-6f4d-4c2c-84da-d8455e70fd15
├─sdb5 ext4 1.0 965006b0-1683-4dd3-8e93-fd482161729d
├─sdb7 ext4 1.0 411dc37c-e651-4220-b380-d3306c59e042
├─sdb8 ext4 1.0 30fde1a2-8594-4a14-86fa-6cdad59bc450
├─sdb9 swap 1 8eb80e10-0b17-4e68-8d79-e1c69a792054
├─sdb10 vfat FAT32 6E2B-F8D9
├─sdb11 swap 1 94829c5d-b261-4d3d-87c5-0f25511c93e2
├─sdb12 vfat FAT32 NO_LABEL 3B51-861D
└─sdb13 ext4 1.0 c4596ece-df47-4850-b449-a3d299717e9c
sdc
└─sdc1 ntfs My Passport 8AB462C7B462B57B
sdd iso9660 Joliet Ext MANJARO_KDE_2405 2024-07-30-08-30-25-00 0 100% /run/miso/bootmnt
├─sdd1 iso9660 Joliet Ext MANJARO_KDE_2405 2024-07-30-08-30-25-00
└─sdd2 vfat FAT12 MISO_EFI 0DE6-E8D4
nvme0n1
├─nvme0n1p1
│ vfat FAT32 ESP ECD2-9948
├─nvme0n1p2
│
├─nvme0n1p3
│ ntfs 7442456342452B66
├─nvme0n1p4
│ swap 1 d324bf6e-b84b-4f82-8fa4-a90b4a84dd40
├─nvme0n1p5
│ ext4 1.0 3c057d72-e5fa-4534-a2b4-ff716922382e
├─nvme0n1p6
│ ext4 1.0 6b63debb-f5de-4218-8e24-27b1f0072975
└─nvme0n1p7
ntfs DELLSUPPORT 522074D82074C50F
On checking sdb9 from gparted , there is an option to turn on swapon , do i need to turn it on?
a similar issue was reported but i don’t see any answer to it
Idk , if posting links from other forums is allowed , but found something similar to my issue
https://www.linuxquestions.org/questions/debian-26/resume-could-not-stat-the-resume-device-file-573538/
in the discussion , they point out using hibernation as a cause , which would have resulted into some dummy storage on swap and its not accessible , in my case the pc went off due to power cut , does that mean , swap got corrupted and can i format and remake it just like efi and then change the UUID in /etc/fstab?
@dmt @soundofthunder @nachlese , can i anyone suggest me something on it ?