You are not logged in.
Pages: 1
my current setup :
asus rog strix g15 (2022) laptop ryzen 9 6900hx, rtx 3070 ti, 32gb ram, physical mux switch
when i am working with my laptop it restarts randomly after a few minutes of use and when it reboots it displays this message :
A password is required to access the root volume:
Enter passphrase for /dev/nvme0n1p2:
/dev/mapper/root: recovering journal
/dev/mapper/root: Clearing orphaned inode 2899369 (uid=1000, gid=1000, mode=0100644, size=1915)
/dev/mapper/root: Clearing orphaned inode 2899330 (uid=1000, gid=1000, mode-0100644, size=40348)
/dev/mapper/root: Clearing orphaned inode 2884321 (uid=1000, gid=1000, mode=0100644, size=23612)
/dev/mapper/root: Clearing orphaned inode 2885168 (uid=1000, gid=1000, mode=0100644, size=38300)
/dev/mapper/root: Clearing orphaned inode 2895907 (uid=1000, gid=1000, mode=0100644, size=22128)
/dev/mapper/root: Clearing orphaned inode 2899331 (uid=1000, gid=1000, mode-0100644, size=69076)
/dev/mapper/root: Clearing orphaned inode 2897606 (uid=1000, gid=1000, mode-0100644, size=16068)
/dev/mapper/root: Clearing orphaned inode 2898596 (uid=1000, gid=1000, mode-0100644, size=59360)
/dev/mapper/root primary superblock features different from backup, check forced.
/dev/mapper/root: Orphan file (inode 12) block 0 is not clean.
CLEARED.
/dev/mapper/root: 644505/61014016 files (0.3% non-contiguous), 36249882/244055040 blocks
when it comes to this line :
/dev/mapper/root: Orphan file (inode 12) block 0 is not clean.
it always says inode 12 but each time it says a different block number
steps that i have already done:
- i checked an article in the arch forum but the person concerned started having this issue after he started using a new external drive
- i booted into kali linux to do a check to the file system with these commands :
sudo cryptsetup luksOpen /dev/nvme1n1p2 myencryptedpartition
sudo e2fsck -f /dev/mapper/myencryptedpartition
the result was that it detected some orphan inodes and suggested to clean them which after that i did that it didn't have an effect
if anyone can help i would appreciate it
Offline
https://wiki.archlinux.org/title/Ryzen#Random_reboots
The filesystem errors are a follow-up problem because of the unclean shutdown, they'll go away when the system stops dropping out.
Offline
i have fast-start disabled both from windows and from the BIOS, but this issue still persists.
i don't get what i need to do with Fix your xinitrc an what is the point of it
Offline
i don't get what i need to do with Fix your xinitrc an what is the point of it
That's you're looking-at it's the User's Signature .. LoL
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
@Hamza193 as d.ALT pointed out, that'S my signature and not a specific reply to your inquiry.
The relevnat part is the link to the Ryzen wiki - the architecture is notorious for the behavior.
Offline
Pages: 1