FSCK code 4

[alexankius]

Hi all,

Have been running Debian for a year now off an SSD (that is where Debian resides).

I got an FSCK error code 4 on the root device which is /dev/sdh1

I run both all of the folloiwng

fsck /dev/sdh1
fsck -fy /dev/sdh1

but the message is that there are still errors.

When I reboot i get stuck again at the same FSCK error code....

[Head_on_a_Stick]

What filesystem is on /dev/sdh1?

Code: Select all

# wipefs /dev/sdh1

[alexankius]

Hi can i check that?

[alexankius]

wipefs does not work

[alexankius]

When I run wipefs I get

Sh: wipefs : not found

I'm at the stage were during boot I get a prompt that the root filesystem requires a manual fsck

BusyBox v1. 22

[Head_on_a_Stick]

When I run wipefs I get

Sh: wipefs : not found

It's in the util-linux package and resides at /sbin/wipefs, which is not in your normal user's PATH.

EDIT: hold on, are you saying you can't boot normally and only get to a busybox prompt?

[alexankius]

exactly, I can't boot normally.

The boot sequence is interrupted and then I get the FSCK error code 4.

When i run fsck at the end of it all i get a message that there are still problems....

So i am stuck at the BusyBox....

[p.H]

Please post fsck's error messages.

[alexankius]

I've been trying to upload a few screenshots but get an apachee error:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, forum-admin@forums.debian.net and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

any pointers?

[Head_on_a_Stick]

any pointers?

Upload the screenshots to an image sharing site and post a link here.

Try https://postimage.org if you're not dismayed by spam adverts.

[alexankius]

https://photos.app.goo.gl/chKHJhCzEiv7YJLv9

[alexankius]

IMG 230 is what happens when i boot.
IMG 248 is after i run fsck -y /dev/sdh1
IMG 302 is after i run fsck dev/sdh1
and then i Run Journal which gets me to IMG 308

[p.H]

I can't access this site at the moment.

[alexankius]

https://drive.google.com/file/d/1ZUhtZ8 ... sp=sharing
https://drive.google.com/file/d/1RD7pC9 ... sp=sharing
https://drive.google.com/file/d/1IC6sLH ... sp=sharing
https://drive.google.com/file/d/1FLi6Wi ... sp=sharing

[p.H]

Nor this one. I'll have to wait until I am back home this evening.

[alexankius]

It's relatively easy for me to reinstall Debian.

The issue is that I have a ZFS Pool (iSCSI SCST) that I can not lose and am not sure whether I can just import it without first exporting...

I would appreciate your feedback..

[Segfault]

Aren't you doing it the hard way?
I'd boot from an external media, I have a SystemRescueCD USB stick for this purpose, and diagnose and repair as needed. SysemRescueCD allows you to run GUI and post on forums, copy and paste from terminal window, no need for clumsy images. If you need to know what filesystem is in your device use 'file -s /dev/sdh1".

[p.H]

Looks like a defective disk or SATA link.

[bw123]

I usually use kernel parameter fsck.mode=force appended to grub 'linux' line to check root device. Sometimes checks are skipped if the journal says the fs is clean.

Are you sure the fs you are checking is the bad one? Try fsck on them all. Maybe make sure you have a decent backup though before doing too much. Use a live system is a good idea.

Is it possible the fs is full? or if you don't have recovery usb/cd can you run any other commands from busybox that might help gather more information? Do a websearch and read a lot before doing possibly destructive things. On a rescue media like systemrescueCD, tune2fs -l would be the first thing I'd look at.

Also check Manual page fsck.ext4(8) for the -p option, and -v flag to gather more info.

[llivv]

the flush cache error on ssd is a bugger.... live boot or install to another disk
if possible so you have a full system to check the disk with.
It would be great if you could recover the ssd and document it here.
Although what I'm seeing seems to point to disk failure.
And I can't find much regarding the flush cache error.

Also get the make and model of the ssd and see if it includes hardware trim.
Or post the ssd make and model here.