So after a while, I just ran sudo fsck -cfy /dev/sda5 and it worked.
Terminal returned some stuff which led to the path of ungoogled chromium which I don’t know if it’s the cause, I forgot to saving the output of the terminal but rebooting into EndeavourOS worked just fine, after running sudo pacman -Syu and rebooting since kernels updated, it gave another /dev/sda5 contains a file system with errors, check forced.. But after the check it worked just fine, rebooting again didn’t give any errors so I guess I’m fine for now?
And just out of curiosity what caused the error in the beginning? A system update or something else? And can it happen again?
Seems like your system ran into some bad sectors which were making read/write to disk hard. And fsck forced rewrite might have fixed it. Is your hard disk in good health?
I don’t know to be honest, I had my laptop for over 9 years now without changing any parts so probably not. How do I check if it’s or not?
First thing to do: make sure you have a backup of any personal data. Write it on an external disk.
Hard disk health is variable, one doesn’t get to choose the components in the laptop.
My wife uses 2 laptops (don’t ask) both running Windoze.
One was purchased in 2014 the other in 2019.
Both were lenovo and use seagate hard disks and I had to replace both of them, last month because the laptops had slowed down massively.
Weirdly, smartctl was listing millions of seek and read errors, not write errors.
Replaced with an M2 NVMe in the newer laptop and SATA SSD in the older laptop.
they run for long enough.
So the same bug occurred and it’s the same as the one I mentioned at the beginning of the post, I will rerun sudo fsck -cfy /dev/sda5 then backup my data and use smartmontools like lucidae recommended, before the issue I faced another one, same issue I believe except it had a shell to run commands with the user being “rootfs” I think, I don’t know why that occurred but I will probably try to reinstall EOS and if that didn’t help I will just switch my hard drive.
So after running sudo fsck -cfy /dev/sda5 I got a very different result then the one I got the first time running sudo fsck -cfy /dev/sda5. Here is the result (it’s so long):
fsck from util-linux 2.37.2
e2fsck 1.46.4 (18-Aug-2021)
Checking for bad blocks (read-only test): done
/dev/sda5: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -562243 -562463 -562485 -562487 -562489 -562495 -(562844--562845) -562847 -562866 -(562868--562869) -562871 -(562917--562922) -562925 -562927 -570342 -570347 -570351 -570880 -(570883--570884) -(570887--570893) -(570895--570899) -(570901--570902) -(570908--570911) -570914 -(570916--570927) -(570929--570930) -(570932--570935) -(570940--570947) -(570949--570952) -570954 -(570956--570958) -(570960--570966) -570971 -(570974--570975) -(570977--570981) -570987 -570989 -(570991--570992) -(570994--570996) -(570999--571000) -(571003--571005) -571008 -571010 -(571013--571014) -571017 -(571022--571023) -(571031--571032) -(571035--571039) -(571041--571051) -(571057--571061) -(571063--571064) -571067 -(571072--571073) -571075 -571079 -(571082--571086) -(571088--571092) -571096 -(571098--571099) -(571103--571106) -571108 -(571111--571120) -571125 -(571127--571129) -(571133--571136) -(571138--571141) -(571143--571144) -571147 -571153 -571155 -(571158--571160) -(571163--571164) -(571167--571168) -571171 -(571173--571180) -571183 -(571186--571187) -(571190--571191) -571193 -(571196--571197) -1056830 -1056913 -1083373 -1083376 -1087554 -(1088768--1088794) -1104575 -1114114 -1478079 -(1478652--1478654) -(1481806--1481912) -1584162 -1584165 -1584417 -1611482 -1650163 -1661497 -1690193 -1690196 -1690199 -1690202 -1690205 -(1804064--1804785) -1835123 -(1835126--1835127) -1836327 -1963552 -2111302 -(2127136--2127145) -2178299 -(2228309--2228322) -2635378 -2655241 -(2752631--2752650) -(2850010--2850015) -3202999 -3572157 -(3638944--3638975) -(3644847--3644853) -(3645440--3645695) -(3645888--3645920) -(3647488--3647988) -3680443 -3708617 -3845495 -3899455 -3909388 -(4103621--4103666) -(4164608--4165631) -4206491 -5572931 -5573237 -6912902 -(7373550--7373551) -(7376240--7376242) -(7376245--7376247) -(7376516--7376521) -(7479152--7479164) -(7874363--7874394) -(7941504--7941543) -(7957910--7957949) -(7987656--7987657) -7987659 -(8028236--8028301) -8098210 -8098213 -(8098284--8098285) -8098287 -8098878 -(8099328--8099348) -8099457 -(8119296--8119787) -(8121344--8122190) -(8122366--8122687) -(8122877--8123196) -(8123388--8123706) -8123962 -(8161280--8161531) -8323139 -(8401346--8401364) -8484554 -8486527 -(8487003--8487007) -8519720 -8520243 -8651237 -(8890272--8890291) -8962555 -9044072 -(9078272--9078465) -(9497146--9497153) -9863174 -(10062161--10062206) -10085434 -(10321921--10321966) -(10321984--10322102) -(10330048--10330290) -(11340800--11341310) -(11341633--11341758) -(11349258--11349543) -11545076 -12631036 -12635788 -12645007 -12700157 -(12701419--12701427) -(14213678--14213682) -(14213685--14213740) -(14213742--14213752) -(16944576--16944621) -(16978897--16978942) -32617036 -32618112
Fix? yes
Free blocks count wrong for group #17 (2359, counted=2572).
Fix? yes
Free blocks count wrong for group #32 (14713, counted=14715).
Fix? yes
Free blocks count wrong for group #33 (5292, counted=5323).
Fix? yes
Free blocks count wrong for group #34 (351, counted=352).
Fix? yes
Free blocks count wrong for group #45 (25412, counted=25523).
Fix? yes
Free blocks count wrong for group #48 (15191, counted=15194).
Fix? yes
Free blocks count wrong for group #49 (30929, counted=30930).
Fix? yes
Free blocks count wrong for group #50 (15116, counted=15118).
Fix? yes
Free blocks count wrong for group #51 (18715, counted=18720).
Fix? yes
Free blocks count wrong for group #55 (19328, counted=20050).
Fix? yes
Free blocks count wrong for group #56 (14186, counted=14190).
Fix? yes
Free blocks count wrong for group #59 (16928, counted=16929).
Fix? yes
Free blocks count wrong for group #64 (18606, counted=18617).
Fix? yes
Free blocks count wrong for group #66 (15961, counted=15962).
Fix? yes
Free blocks count wrong for group #68 (6639, counted=6653).
Fix? yes
Free blocks count wrong for group #80 (17466, counted=17467).
Fix? yes
Free blocks count wrong for group #81 (31654, counted=31655).
Fix? yes
Free blocks count wrong for group #84 (9382, counted=9402).
Fix? yes
Free blocks count wrong for group #86 (5691, counted=5697).
Fix? yes
Free blocks count wrong for group #97 (4242, counted=4243).
Fix? yes
Free blocks count wrong for group #109 (8876, counted=8877).
Fix? yes
Free blocks count wrong for group #111 (26886, counted=27715).
Fix? yes
Free blocks count wrong for group #112 (21518, counted=21519).
Fix? yes
Free blocks count wrong for group #113 (548, counted=549).
Fix? yes
Free blocks count wrong for group #117 (5341, counted=5342).
Fix? yes
Free blocks count wrong for group #119 (3133, counted=3135).
Fix? yes
Free blocks count wrong for group #125 (11490, counted=11536).
Fix? yes
Free blocks count wrong for group #127 (23914, counted=24938).
Fix? yes
Free blocks count wrong for group #128 (13301, counted=13302).
Fix? yes
Free blocks count wrong for group #170 (30133, counted=30135).
Fix? yes
Free blocks count wrong for group #210 (29882, counted=29883).
Fix? yes
Free blocks count wrong for group #225 (12814, counted=12828).
Fix? yes
Free blocks count wrong for group #228 (15175, counted=15188).
Fix? yes
Free blocks count wrong for group #240 (6078, counted=6110).
Fix? yes
Free blocks count wrong for group #242 (6380, counted=6460).
Fix? yes
Free blocks count wrong for group #243 (8726, counted=8729).
Fix? yes
Free blocks count wrong for group #245 (3295, counted=3361).
Fix? yes
Free blocks count wrong for group #247 (5208, counted=7537).
Fix? yes
Free blocks count wrong for group #249 (4961, counted=5213).
Fix? yes
Free blocks count wrong for group #254 (32766, counted=32767).
Fix? yes
Free blocks count wrong for group #256 (7967, counted=7986).
Fix? yes
Free blocks count wrong for group #258 (5866, counted=5868).
Fix? yes
Free blocks count wrong for group #259 (23370, counted=23375).
Fix? yes
Free blocks count wrong for group #260 (14879, counted=14881).
Fix? yes
Free blocks count wrong for group #264 (9768, counted=9769).
Fix? yes
Free blocks count wrong for group #271 (2452, counted=2472).
Fix? yes
Free blocks count wrong for group #273 (124, counted=125).
Fix? yes
Free blocks count wrong for group #276 (31901, counted=31902).
Fix? yes
Free blocks count wrong for group #277 (5672, counted=5866).
Fix? yes
Free blocks count wrong for group #289 (5319, counted=5327).
Fix? yes
Free blocks count wrong for group #301 (32760, counted=32761).
Fix? yes
Free blocks count wrong for group #307 (13084, counted=13131).
Fix? yes
Free blocks count wrong for group #315 (27069, counted=27477).
Fix? yes
Free blocks count wrong for group #346 (31007, counted=31930).
Fix? yes
Free blocks count wrong for group #352 (23053, counted=23054).
Fix? yes
Free blocks count wrong for group #385 (17850, counted=17853).
Fix? yes
Free blocks count wrong for group #387 (26571, counted=26581).
Fix? yes
Free blocks count wrong for group #433 (29411, counted=29483).
Fix? yes
Free blocks count wrong for group #517 (24504, counted=24550).
Fix? yes
Free blocks count wrong for group #518 (23504, counted=23550).
Fix? yes
Free blocks count wrong for group #995 (32764, counted=32766).
Fix? yes
Free blocks count wrong for group #1008 (24523, counted=24525).
Fix? yes
Free blocks count wrong (44146108, counted=44840425).
Fix? yes
Inode bitmap differences: -262152 -262182 -(262211--262213) -262242 -262309 -262313 -279723 -279787 -279805 -279809 -279819 -(279823--279824) -279837 -419237 -419241 -(422354--422355) -422357 -422362 -422364 -422369 -422372 -422375 -422378 -423962 -423967 -(423973--423981) -424169 -424187 -424190 -535334 -(676330--676331) -(939686--939687) -1714811 -(1835538--1835540) -1837752 -(1839458--1839460) -(1841145--1841146) -(1967183--1967184) -(2908622--2908623)
Fix? yes
Free inodes count wrong for group #32 (148, counted=156).
Fix? yes
Directories count wrong for group #32 (761, counted=759).
Fix? yes
Free inodes count wrong for group #34 (6978, counted=6986).
Fix? yes
Free inodes count wrong for group #51 (4381, counted=4406).
Fix? yes
Directories count wrong for group #51 (296, counted=293).
Fix? yes
Free inodes count wrong for group #65 (5332, counted=5333).
Fix? yes
Directories count wrong for group #65 (607, counted=606).
Fix? yes
Free inodes count wrong for group #82 (3604, counted=3606).
Fix? yes
Directories count wrong for group #82 (1184, counted=1183).
Fix? yes
Free inodes count wrong for group #114 (7624, counted=7626).
Fix? yes
Directories count wrong for group #114 (204, counted=203).
Fix? yes
Free inodes count wrong for group #209 (7405, counted=7406).
Fix? yes
Free inodes count wrong for group #224 (2055, counted=2064).
Fix? yes
Free inodes count wrong for group #240 (26, counted=28).
Fix? yes
Free inodes count wrong for group #355 (7696, counted=7698).
Fix? yes
Directories count wrong for group #355 (34, counted=33).
Fix? yes
Free inodes count wrong (12144927, counted=12173769).
Fix? yes
/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 966199/13139968 files (0.2% non-contiguous), 7701783/52542208 blocks
I will restart, use smartmontools and report back.
I would suggest you get a new drive. If you got 9 years that is exceptional. Normally they would have needed replacement by now.
Your HDD is going bye-bye. It seems that your drive is starting to fail and it’s just hinting at you to replace me with a new one. As many suggested it is ideal for your to stop running fsck because it’s kind of doing hard writing to fix the sectors which lead to lowering the health. Anyway, get the data you want and just go for a new drive.
Alright, I backed up my stuff and I will try to use this hard drive for as long as possible. But can a SD card be used to run EOS? I don’t have any plans to buy a new hard drive right now since I will have a Macbook soon, which I will use EOS on as well, so buying a new hard drive won’t be a great idea really. So basically can I install EOS on a SD card or not?
Personally i wouldn’t but it may work? SSD drives are cheap and it’s not like you need a very large one to run EndeavourOS on. But it’s not my nickel and entirely your decision. You could try it and see?
I think last time I installed EOS it had a option to install it on my SD, even the Bootloader had a option to be installed on the SD card. I will try it whenever this hard disk dies.
1 Like