asked on

Thin Client fsck error

I am a network administrator for a company that utilizes a small number of thin clients for extremely remote locations. Recently, one of these thin clients has begun getting a fail on its start-up fsck, with a return code of 4. I am very unfamiliar with these systems and have never dealt with them in any regard until now. I realize that this is probably a basic fix since the files in question do not appear to be system critical, but I do not even know how to go about running a non-automatic fsck to remedy the issue. I have attached the picture of the screen that the user sent me. Thanks in advance for the help.
New-Image.JPG

ASKER CERTIFIED SOLUTION

rindi

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

LawIS

ASKER

I was going to have the user run

fsck n /dev/hda2

just to see the full extent of what fsck would be performing, but the user says that they have no ability to type anything other than ctrl-d. Is there a way to ensure that they get a prompt when the system is started?

rindi

Depends on the distro being used. In the boot menu there is sometimes an option to boot into single user or rescue mode. That should then open a bash prompt from which entries should be possible. Another option would be to boot with a PartedMagic CD and use that for doing the repairs.

http://distrowatch.com/table.php?distribution=partedmagic

SOLUTION

gheist