Solved /bin/sh error

joplass

Active Member

Reaction score: 30
Messages: 209

I did not change anything on this system. I started the box and I am faced with
11.png


after /rescue/sh, the system asked to run fsck I did but then I am faced with [y/n]. I really don't know what I have to do to solve the issue. I first picked "y" then back to square one as shown below

22.png


I will appreciate some help. Why should I pick "y" or "n" to what end. I just don't know enough.

Thank you,
 

Zirias

Daemon

Reaction score: 1,051
Messages: 1,892

You should change the thread title, what you have is a severely b0rked filesystem.

Then, your only chance for recovery is, indeed, selecting y here. If you're sure nothing unusual happened (like a forced power-off, some attempt to access the disk from a different system, whatever), then this might be a hardware issue.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 10,608
Messages: 36,269

Filesystem errors typically come in batches. And you usually want to fix them. So be prepare to enter Y a lot. Or simply run fsck -y and accept any and all fixes.

Agree with Zirias find out why they happened. Sudden power outage? Hit the reset button at the wrong time? Or you could have a disk that's on the verge of dying.
 
OP
J

joplass

Active Member

Reaction score: 30
Messages: 209

You should change the thread title, what you have is a severely b0rked filesystem.

Then, your only chance for recovery is, indeed, selecting y here. If you're sure nothing unusual happened (like a forced power-off, some attempt to access the disk from a different system, whatever), then this might be a hardware issue.
That yes, I accessed the system from another freebsd machine via ssh.

At least I picked "y" throughout then the system did some auto-checks including "pathnames" and others I can't remember. At the end it displayed "SYSTEM IS CLEAN" or something in that regard. Needless to say, I am smooth sailing over here.

As always, thank you for your attention.

Did I say I love this forum? 👍
 

ralphbsz

Son of Beastie

Reaction score: 1,976
Messages: 2,937

Even with a sudden power cut, a UFS file system that uses soft updates and journal should not get interesting fsck problems. I suspect there is something more fundamentally wrong with the underlying storage. I would tread carefully and take lots of backups.
 
OP
J

joplass

Active Member

Reaction score: 30
Messages: 209

Even with a sudden power cut, a UFS file system that uses soft updates and journal should not get interesting fsck problems. I suspect there is something more fundamentally wrong with the underlying storage. I would tread carefully and take lots of backups.
Thank you for the advise. I have another SATA drive around that I will probably use.
 
Top