[CLOSED] check of the root filesystem failed

[Pepper-Mint-Patty]

I have done a clean install of LM 19.2 cinn including all the updates.
The original problems didn't go: at some time between 1 and 30 minutes the system freezes completely: keys dont work, touchpad nore mouse. Only way to close by power button.
After restart sometimes only cursor showed up. When it did start freezing happened again and again.
Now i really dont know what to do. This shows up:

Code: Select all

failure file system check of the root filesystem failed.
the root filesystem on /dev/sdb1 requires a manual fsck

busybox v1.27.2 (ubuntu 1:1.27.2-2ubuntu3.3) built-in shell (ash)
(initramfs) _

I guess live boot but what next? btw in live boot no freezing so it can't be a hardware issue.

[JoeFootball]

the root filesystem on /dev/sdb1 requires a manual fsck

fsck /dev/sdb1

[Pepper-Mint-Patty]

Code: Select all

sudo fsck /dev/sdb1

had a lot to correct. Is it of any interest to copy that info here?

[JoeFootball]

Is it of any interest to copy that info here?

Maybe. If you'd like, post the output between [code]output-goes-here[/code] tags.

The question I would be contemplating, is the file system corruption the cause of the system freezing, or the result of the hard power off?

Tip: Should you find yourself in a scenario where you cannot shutdown normally, try this first. Holding down the Alt key, press SysRq (often shared with the PrtSc key), then r e i s u, and then o to Shutdown (or b to Reboot). This sequence should close your system cleanly.

[Pepper-Mint-Patty]

The question I would be contemplating, is the file system corruption the cause of the system freezing, or the result of the hard power off?

It hsn't worked as good as now. So we will see where it is going.

I've written down the shutdown command, thanks for that!

Here's the damage

Code: Select all

mint@mint:~$ sudo fsck /dev/sdb1
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sdb1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix<y>? yes
Inode 392670 was part of the orphaned inode list.  FIXED.
Inode 392680 was part of the orphaned inode list.  FIXED.
Inode 668052 was part of the orphaned inode list.  FIXED.
Inode 786774 was part of the orphaned inode list.  FIXED.
Inode 1467425 was part of the orphaned inode list.  FIXED.
Inode 1467458 was part of the orphaned inode list.  FIXED.
Inode 1467496 was part of the orphaned inode list.  FIXED.
Inode 1479887 was part of the orphaned inode list.  FIXED.
Inode 1480024 was part of the orphaned inode list.  FIXED.
Inode 1480027 was part of the orphaned inode list.  FIXED.
Inode 1480033 was part of the orphaned inode list.  FIXED.
Inode 1480037 was part of the orphaned inode list.  FIXED.
Inode 1480041 was part of the orphaned inode list.  FIXED.
Inode 1480085 was part of the orphaned inode list.  FIXED.
Inode 1480086 was part of the orphaned inode list.  FIXED.
Inode 1480092 was part of the orphaned inode list.  FIXED.
Inode 1480284 was part of the orphaned inode list.  FIXED.
Deleted inode 1480480 has zero dtime.  Fix<y>? yes
Inode 1480510 was part of the orphaned inode list.  FIXED.
Inode 1480512 was part of the orphaned inode list.  FIXED.
Inode 1480513 was part of the orphaned inode list.  FIXED.
Inode 1480516 was part of the orphaned inode list.  FIXED.
Inode 1480540 was part of the orphaned inode list.  FIXED.
Inode 1480542 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -690880 -(691200--691406) -(1162252--1162259) -(1162392--1162394) -(1162497--1162505) -(1162584--1162591) -1162681 -(1162772--1162774) -(1162853--1162855) -(1162921--1162928) -(1163034--1163036) -1838600 -1838791 -(1838803--1838805) -(1881629--1881631) -(1881644--1881646) -(1881675--1881677) -(3942839--3942909) -(5826131--5826138) -(5846082--5846089) -(5847688--5847690) -6340822 -6896379
Fix<y>? yes
Free blocks count wrong for group #21 (179, counted=387).
Fix<y>? yes
Free blocks count wrong for group #35 (6821, counted=6867).
Fix<y>? yes
Free blocks count wrong for group #56 (1996, counted=2001).
Fix<y>? yes
Free blocks count wrong for group #57 (657, counted=666).
Fix<y>? yes
Free blocks count wrong for group #120 (29676, counted=29747).
Fix<y>? yes
Free blocks count wrong for group #177 (4725, counted=4733).
Fix<y>? yes
Free blocks count wrong for group #178 (19155, counted=19166).
Fix<y>? yes
Free blocks count wrong for group #193 (5802, counted=5803).
Fix<y>? yes
Free blocks count wrong for group #210 (8746, counted=8747).
Fix<y>? yes
Free blocks count wrong (6151317, counted=5589284).
Fix<y>? yes
Inode bitmap differences:  -392670 -392680 -668052 -786774 -1467425 -1467458 -1467496 -1479887 -1480024 -1480027 -1480033 -1480037 -1480041 -(1480085--1480086) -1480092 -1480284 -1480480 -1480510 -(1480512--1480513) -1480516 -1480540 -1480542
Fix<y>? yes
Free inodes count wrong for group #48 (2006, counted=2008).
Fix<y>? yes
Free inodes count wrong for group #81 (0, counted=1).
Fix<y>? yes
Free inodes count wrong for group #96 (327, counted=328).
Fix<y>? yes
Free inodes count wrong for group #179 (0, counted=3).
Fix<y>? yes
Free inodes count wrong for group #181 (5526, counted=5543).
Fix<y>? yes
Free inodes count wrong (1992065, counted=1956517).
Fix<y>? yes

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 618923/2575440 files (0.1% non-contiguous), 4702940/10292224 blocks
mint@mint:~$ 

[JoeFootball]

Here's the damage

That would have cautious me wonder about the age/condition of the hard drive; is the file system corruption hardware related? Regardless, I would verify external backups first and foremost.

You may want to consider checking the other partitions as well. When I'm skeptical of a file system, I use GParted, which is installed by default on the live version of LM that you appear to have used for fsck.

Boot to live, run GParted from the application menu, right-click on the questionable partition, and select "Check", then "Apply" (the check mark), where it then runs a set of commands to fix and tune the file system.

[Moonstone Man]

Holding down the Alt key, press SysRq (often shared with the PrtSc key), then r e i s u, and then o to Shutdown (or b to Reboot).

Just fyi, Joe, r e i have been redundant for some years now. s u o or s u b are sufficient. The Ctrl key should also be held down together along with Alt while the four remaining keys are pressed one after the other.

Hold down Ctrl+Alt then tap each of SysRq s u b
Hold down Ctrl+Alt then tap each of SysRq s u o

[JoeFootball]

Just fyi, Joe, r e i have been redundant for some years now.

Thank you, I didn't know that.

Hold down Ctrl+Alt ...

Hmm, just holding down Alt has always worked for me, though I can't say I've tried it in a while. I shall add this to my experiment list.

[Moonstone Man]

Just fyi, Joe, r e i have been redundant for some years now.

Thank you, I didn't know that.

Hold down Ctrl+Alt ...

Hmm, just holding down Alt has always worked for me, though I can't say I've tried it in a while. I shall add this to my experiment list.

No worries, mate. I'll double check my use of Ctrl too.

[Pepper-Mint-Patty]

Kadaitcha Man wrote:
Just fyi, Joe, r e i have been redundant for some years now.

thbnx for informing Joe, Kadaitcha Man.
Unfortunately i just had totry. and it rebooted perfectly.

Is there anything you shoud do after a total freeze? like rerun

Code: Select all

sudo fsck /dev/sdb1

[Moonstone Man]

Hmm, just holding down Alt has always worked for me, though I can't say I've tried it in a while. I shall add this to my experiment list.

No need to test it. I was wrong about Ctrl. You learn something new every day.

[JoeFootball]

Is there anything you shoud do after a total freeze? like rerun sudo fsck /dev/sdb1

Well, if fsck returned nothing to fix after a system freeze, you could infer the hard power off was more likely the cause of the file system corruption, rather than the corruption causing the freeze (or the result of the freeze itself).

[JoeFootball]

You learn something new every day.

Then we both learned something today.

[Pepper-Mint-Patty]

thanx for your lovely conversation Joe & Kadaitcha.

Maybe we can go back on track now?!

Is there anything you should do after the mentioned reboot command from a total freeze?
like rerun

Code: Select all

sudo fsck /dev/sdb1

[JoeFootball]

Maybe we can go back on track now?!

Is there anything you should do after the mentioned reboot command from a total freeze?
like rerun sudo fsck /dev/sdb1

As I had mentioned, it could provide some comfort if it returns nothing after a subsequent system freeze, so I can't say it's a bad idea to do so, especially given that you don't know what's causing said freezes.

[fooster]

<deleted>

[Larry78723]

@fooster - Please start a thread of your own. It is impolite to piggyback on somebody else's thread as well as a violation of forum rules. Before you do, please read  How to get help paying special attention to item #5.