dry nexus
it was running alright even after the update yesterday. today it suddenly shows this
i have never encountered this problem
please help
update:
fsck -f [partition] run for as long as it takes
Dependency failed for /home
restive crater
@dry nexus do you still have the usb flashed?
dry nexus
<@537196716013649930> do you still have the usb flashed?
yes
does it matter if the iso is old
dry nexus
<@537196716013649930> boot into it please
yes done
restive crater
now chroot
dry nexus
now chroot
do i chroot into the home partition?
heady wind
do i chroot into the home partition?
you can't chroot in the home partition
heady wind
ohh, they can't run a service through chroot
can you just exit from chroot, umount the partitions and run fsck on the home partition
restive crater
you should still be able to log in even tho ur in emergency mode you’ll only have the cli iirc
journalctl -xb
heady wind
you should still be able to log in even tho ur in emergency mode you’ll only hav...
yup, that's the other way but they are already in the iso
restive crater
¯_(ツ)_/¯ i’ll brb
dry nexus
just run `fsck` on your home partition
do i run this and check if it works?
dry nexus
can you just exit from chroot, umount the partitions and run fsck on the home pa...
do i need to pass any arguments
heady wind
should be something like :-
fsck -f /dev/home-par
heady wind
do i run this and check if it works?
yes, but you have to umount your partitions first
heady wind
did it showed some corrupted inodes
heady wind
are my files at risk? ")
what's the output
dry nexus
heady wind
yup
you have to press y for all the optimization it asks
or maybe you can run fsck -fy /dev/sda3 for automatically considering yes for all the optimizations
dry nexus
i did yes to all
there was a prompt for it
heady wind
just try rebooting now
dry nexus
dry nexus
just try rebooting now
is this normal
heady wind
do you have a faulty ram?
heady wind
I don't thinks that's normal
running fsck on the home partition shouldn't affect your system this way
dry nexus
do i ctrl c?
heady wind
do i ctrl c?
I don't think ctrl c will work
heady wind
that can happen due to loose display connection too
dry nexus
what do i do
heady wind
irrc arch iso has some memory test build it, you can boot in that through the grub menu
heady wind
have you tried rebooting again?
heady wind
how do i get off the matrix rain
hard poweroff
heady wind
do you see some memtest option
restive crater
BIOS may have memtest too
heady wind
ohh, if you can boot in your iso you should be able to boot in your system
dry nexus
do you see some memtest option
yes
heady wind
maybe try running that, just in case.
first can you try booting in your system.
as it might have occurred due to some kernel panic or something
dry nexus
running memtest
heady wind
running memtest
I don't think the problem is with the memory
you are booting in your archiso fine
restive crater
@dry nexus update?
dry nexus
<@537196716013649930> update?
i let memtest run
I'm hard rebooting rn
restive crater
roger that
heady wind
wait
restive crater
please journalctl -xb
dry nexus
heady wind
does pressing enter takes you to the rootfs?
dry nexus
yes
heady wind
run fsck -p /dev/sda3
and try rebooting again, if this doesn't work will chroot in the system through arch iso and see the pacman logs first
dry nexus
heady wind
run `fsck -p /dev/sda3`
.
heady wind
you can also use fsck -fy /dev/sda3
dry nexus
you can also use `fsck -fy /dev/sda3`
i did fsck -f -y /dev/sda3
it led to demonic possession
restive crater
heady wind
i did `fsck -f -y /dev/sda3`
it led to demonic possession
again?
restive crater
fsck service exec might be jacked
dry nexus
is it normal for arch to break like this
heady wind
don't put that y and manually press y for all the conformation
heady wind
is it normal for arch to break like this
No, it might have occurred due to some broken update and maybe some corruption
restive crater
/dev/sda3 was unmounted right?
dry nexus
/dev/sda3 was unmounted right?
yes i did it from iso
restive crater
oh ok
heady wind
don't put that `y` and manually press `y` for all the conformation
have you tried this?
it might be the issue with some systemd-libs or something
restive crater
can we get a cat /etc/fstab to see fsck order? it might be worth running fsck on another sda partition to see if it produces the same result if we cant get any pertinent information from manually y paging through this next fsck -f /dev/sda3 that he's ab to run.
am i making sense here
dry nexus
have you tried this?
i did not have to put y once
and the random numbers start appearing
restive crater
you mean demon mode lol
heady wind
i did not have to put y once
and the random numbers start appearing
can you show the output once
you have to put in y multiple times depending on the corruption level
dry nexus
heady wind
it's just asking for clearing the corrupted inodes
bronze eagle
do you mounted /home exterally
bronze eagle
yeah it is
heady wind
you have to put in y multiple times depending on the corruption level
just type y for every prompt fsck -f /dev/sda3 shows
restive crater
daemonic possession ha
dry nexus
ohh so you are in the arch system itself
doesn't matter
even if i do it through the installer it's the same
heady wind
I don't think they need to reformat the drive
bronze eagle
ca we do force fsck
heady wind
it might be some other hardware issue
restive crater
already done
heady wind
ca we do force fsck
they are having daemonic possession when they do fsck
heady wind
like this
bronze eagle
they are having daemonic possession when they do fsck
oh
heady wind
let's check the pacman logs
less /var/log/pacman.log
press shift-g and starts scrolling up.
check for some errors
you don't have to scroll too up, just scroll for 1 update
dry nexus
umm
restive crater
you can try grep -C 3 -i 'fsck' /var/log/pacman.log | egrep 'error|fail|warning'
if you dont want to pan through like 1000 lines of a log
dry nexus
yea i had like 600 packages updated
bronze eagle
I think there is corrupt metadata on that filesystem, why not backup and recreate filesystem
restive crater
that's what i'm leaning to tbh but idk
do you have a backup of your home directory?
bronze eagle
fsck.ext4 -f -b 8193 /dev/sda3 - this will tries an alternative superblock backup location.
dry nexus
you can try ```grep -C 3 -i 'fsck' /var/log/pacman.log | egrep 'error|fail|warni...
all errors are from 2023 june
there are no recent errors
restive crater
roger that.
restive crater
fsck.ext4 -f -b 8193 /dev/sda3 - this will tries an alternative superblock back...
-B or -b?
bronze eagle
-b
-b 8193, tells fsck to use the superblock backup located at offset 8193, instead of the primary superblock at offset 0
restive crater
Instead of using the normal superblock, use an alternative superblock specified by superblock. This option is normally used when the primary superblock has been corrupted. The location of the backup superblock is dependent on the filesystem's blocksize. For filesystems with 1k blocksizes, a backup superblock can be found at block 8193; for filesystems with 2k blocksizes, at block 16384; and for 4k blocksizes, at block 32768. ```
from [fsck.ext4](https://linux.die.net/man/8/fsck.ext4)its like 1:45am here so i'm runnin on fumes lol
dry nexus
what do i do now ")
restive crater
fsck.ext4 -f -b 8193 /dev/sda3
dry nexus
will it delete my files?
restive crater
no its just running fsck again
heady wind
yea i had like 600 packages updated
have you checked the pacman log
restive crater
yes lol it didn't return anything
dry nexus
have you checked the pacman log
yes the errors are from 2023
restive crater
he's running e2fsck against the backup superblock
dry nexus
heady wind
ohh you aren't getting the scrollable view
restive crater
no he ran grep
dry nexus
do you have vim/nvim installed?
i had scrollable view no errors there
restive crater
you can try ```grep -C 3 -i 'fsck' /var/log/pacman.log | egrep 'error|fail|warni...
^
heady wind
@dry nexus
less /var/log/pacman.log
press shift-g
restive crater
bro haha leave the pacman logs lie
dry nexus
dry nexus
<@537196716013649930>
less /var/log/pacman.log
press shift-g
i did
there are no errors
restive crater
ah
dry nexus
this is the fsck output
dry nexus
are you sure, there were no errors or something like that?
nope
restive crater
@dry nexus dumpe2fs /dev/sda3 | grep -i superblock
heady wind
ohh, why does it say like superblock does not describe a valid filesystem?
dry nexus
i am still in the arch system btw
restive crater
because goofy ah ext4 might not have a superblock at 8193
heady wind
i am still in the arch system btw
have you tried running fsck via arch-iso without mounting any partition?
dry nexus
heady wind
because goofy ah ext4 might not have a superblock at 8193
their system was running fine till the update, I seriously don't know what's exactly wrong
restive crater
Gyat
dry nexus
have you tried running fsck via arch-iso without mounting any partition?
i tried running just by mounting root partition
heady wind
i tried running just by mounting root partition
can you try running without mounting any partition
dry nexus
on it
heady wind
on it
boot through the iso don't mount any partition and run fsck on the home partition
restive crater
i thought he already ran fsck from iso
dry nexus
dry nexus
i thought he already ran fsck from iso
i ran but mounting / partition
i didn't think it'd make any difference
restive crater
oh
well typically only that specific partition needs to be unmounted to run fsck but its worth a shot
heady wind
i didn't think it'd make any difference
yeah, but we have to try something.
dry nexus
welp
restive crater
incredible
restive crater
```fsck.ext4 -f -b 32768 /dev/sda3```
can we try ^ now
dry nexus
I'll try from iso
dry nexus
can we try ^ now
on it right now
restive crater
roger
dry nexus
can we try ^ now
restive crater
the numbers mason
what do they mean
i'm so lost in the sauce rn i dont even know what to think ab this
heady wind
just don't try this yet
dry nexus
only linus can help me now
restive crater
-S
Write superblock and group descriptors only. This is useful if all of the superblock and backup superblocks are corrupted, and a last-ditch recovery method is desired. It causes mke2fs to reinitialize the superblock and group descriptors, while not touching the inode table and the block and inode bitmaps. The e2fsck program should be run immediately after this option is used, and there is no guarantee that any data will be salvageable. It is critical to specify the correct filesystem blocksize when using this option, or there is no chance of recovery. ```
from [mkfs.ext4](https://linux.die.net/man/8/mkfs.ext4)i would try it
mkfs.ext4 -S /dev/sda3 && fsck.ext4 -f /dev/sda3
dry nexus
i saw in the manjaro forums that fsck -f -y [home partition] fixed their issue
dry nexus
yes
my computer booted even after the update yesterday
it's just today it's being a bitch
restive crater
`mkfs.ext4 -S /dev/sda3 && fsck.ext4 -f /dev/sda3`
let us know how this goes
restive crater
dry nexus
let us know how this goes
will it erase my data
restive crater
not if you run it with the -S flag
bronze eagle
will it erase my data
what does mkfs cmmd do
restive crater
```
-S
Write superblock and group descriptors only. This is useful if all of...
@bronze eagle ^
bronze eagle
<@881391695806234644> ^
yeah I read it
restive crater
he ran fsck.ext4 -f -b 8193 /dev/sda3 and it still threw a fit so I had him run dumpe2fs /dev/sda3 | grep -i superblock to see where the superblocks were
restive crater
he posted this, so we reran fsck at superblock 32768
same error
then @heady wind posted about the -S flag for mkfs which rewrites superblock and group descriptors only. if its corrupted metadata this should hopefully fix it.
bronze eagle
If he still unable to recover it then I think he should use ddrescue or photorec tools to recover home partition data, and then format it and then mount it again
restive crater
we're getting there, I want to see if mkfs is going to do anything for him first
bronze eagle
ok
heady wind
Don't run that command yet
bronze eagle
Don't run that command yet
which one
restive crater
`mkfs.ext4 -S /dev/sda3 && fsck.ext4 -f /dev/sda3`
this i think
heady wind
will it erase my data
It can
bronze eagle
The one I sent image of
that cmmd will wipe out his data and then create a superblock to all over entire partition. Isn't this is Irrelevant now
restive crater
It can
if superblocks are missaligned with the inodes if i'm reading correctly
if he's going to run it he should actually run dumpe2fs /dev/sda3 | grep -i "Block size" first, then specify the block size in the mkfs.ext4 command. so it should actually be mkfs.ext4 -S -b { block size } && fsck.ext4 -f /dev/sda3
Specify the size of blocks in bytes. Valid block-size values are 1024, 2048 and 4096 bytes per block. If omitted, block-size is heuristically determined by the filesystem size and the expected usage of the filesystem (see the -T option). If block-size is negative, then mke2fs will use heuristics to determine the appropriate block size, with the constraint that the block size will be at least block-size bytes. This is useful for certain hardware devices which require that the blocksize be a multiple of 2k. ```
from [mkfs.ext4](https://linux.die.net/man/8/mkfs.ext4)Higher one is for handling larger files smaller is for handling small size files
dry nexus
is there no way without wiping out my data
i got too much important stuff
bronze eagle
is there no way without wiping out my data
i got too much important stuff
why not use tools like ddrescue or phtorec to recover data
restive crater
probably best to just run disk recovery software on your drive tbh
bronze eagle
It's 3am I'm going to bed. I'll check in tomorrow. night boys
good ni8
dry nexus
so i tried mounting /home manually and there are some things
3 error messages
ext4_check_descriptors: Block bitmap for group 2666 not in group (block 10444675469559614510)
216.324314) EXT4-fs (sda3): group descriptors corrupted!
mount: /home: fsconfig system call failed: Structure needs cleaning.
you can't mount that, it has corrupted descriptors
@dry nexus can you add TLDR about your issue and what you've tried so that a new person may easily comprehend the issue?
dry nexus
when i tried to boot
/home partition could not mount apparently for corrupted descriptors
and running fsck -f -y on the partition would lead to infinite scroll of numbers
TLDR of the issue
restive crater
Troubleshooting Steps Taken
fsck -f /dev/sda3 from archiso :: inode scrolling issue occurs/var/log/pacman.log for fsck errors, fails, and warnings :: no recent logsfsck.ext4 -f -b 8193 /dev/sda3 :: bad magic number, superblock could not be readdumpe2fs /dev/sda3 | grep -i superblock :: first backup superblock begins at 32769fsck.ext4 -f -b 32769 /dev/sda3 :: inode scrolling issue still occursmount /dev/sda3 :: block bitmap for group 2666 not in group; group descriptors corrupted@dry nexus when you get the inode scrolling issue, do you let it run or do you stop it?
dry nexus
good morning
dry nexus
<@537196716013649930> when you get the inode scrolling issue, do you let it run ...
i stopped it
by force rebooting
restive crater
by force rebooting
good morning lol. I've never seen fsck behave this way, but you may want to just try letting it run, despite the scrolling nonsense. I'm pretty sure those are inode numbers. You could try to let it run for like 5-10 minutes or so and see if it stops on its own. If you don't want to try that, then like we were talking about last night you should probably run ddrescue like @bronze eagle suggested.
dry nexus
I'll run fsck for some time to see if it stops automatically
then I'll have to run ddrescue ig
restive crater
okay, I'm not sure exactly what the implications of letting run are, and you may decide to let it run longer than 10 minutes if its taking that long. This is beyond the scope of what I'm familiar with so, just a suggestion
heady wind
good morning lol. I've never seen fsck behave this way, but you may want to just...
Yup, I have seen a similar issue where the author has to run the fsck for 30mins
i even dm'd @dry nexus about this
dry nexus
i even dm'd <@537196716013649930> about this
I'm sorry i did not get the notification
I'll run fsck from iso and let it run
restive crater
sounds good, keep us updated.
dry nexus
so i will not mount any partitions
just plain fsck -f -y /dev/sda3
restive crater
that'll work
heady wind
sounds good
dry nexus
I'll send a message here which will be the starting time
started
demonic possession is on
dry nexus
i forced shutdown
been more than an hour
I'll try again tomorrow ")
with ddrescue ig
restive crater
I'll try again tomorrow ")
with ddrescue ig
👍🏻
dry nexus
@restive crater what exactly do i do with ddrescue
dry nexus
Troubleshooting Steps Taken
- ran `fsck -f /dev/sda3` from archiso :: inode scr...
also fsck.ext4 -f -b 32769 /dev/sda3 returns
restive crater
<@456226577798135808> what exactly do i do with ddrescue
To be perfectly honest with you I’ve never personally used ddrescue but I’ve seen good things and I think that’s the direction you should head. ddrescue tutorial I found. maybe give that a watch or wait for @bronze eagle or @heady wind to see if they can help you further. I gotta go to bed lol I have a full day tomorrow.
dry nexus
also `fsck.ext4 -f -b 32769 /dev/sda3` returns
@bronze eagle
i have not started using ddrescue yet
bronze eagle
<@881391695806234644>
I'll free tomorrow, will talk further on this
dry nexus
yes please
dry nexus
guys @heady wind @bronze eagle @restive crater
there is update
so i read somewhere that fsck might have a bug
which is why i flashed a new version of the iso just to have the closure (and honestly i don't know if it's anyhow relevant)
so i tried running fsck -f /dev/sda3 and let it run as long as it takes
and after a good amount of time ..
it took 2 hours and 14 minutes
lmao
bronze eagle
mout it
bronze eagle
today was my semster last paper, and it's done
I'll just have a lunch then will look at it
dry nexus
it's solved
dry nexus
i'm in my system now
bronze eagle
you using waybar
dry nexus
[SOLVED] Dependency failed for /home
i want to use ags but i still haven't got time to sit around with javascript
also i have my sems coming up
bronze eagle
i want to use ags but i still haven't got time to sit around with javascript
I use somone config for ags, I also didn't have much time. I invested a month in customising hyprland + waybar setup
dry nexus
i tried using end_04's config for ags
they made a material 3 themed bar and widgets
but it's for laptop
and the config is very big
bronze eagle
i tried using end_04's config for ags
they made a material 3 themed bar and wid...
I used it too It's messy but looks great.
and I get too many error during installation, that dotfile uses plasma ags together
dry nexus
yeah same
so i thought i'll write my own ags and take components from others
bronze eagle
yeah same
so i thought i'll write my own ags and take components from others
it would be great, take pieces and build at your preferences
dry nexus
easiest way to build configs
fsck -f [partition] run for as long as it takes
heady wind
Great
restive crater
So glad to hear this. Great Job @dry nexus !