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
LVL 3
LawISAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rindiCommented:
You'd just have to start fsck from the prompt (fsck /dev/hda2). If you run man fsck you get all the details on the command, and what sitches you can use with it.

It's quite likely there is a bigger error with the HD, and to check that you should run the HD manufacturer's diagnostic utility. You'll have to be onsite to run that tool though. You'll find it on the UBCD:

http://ultimatebootcd.com


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LawISAuthor Commented:
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?
0
rindiCommented:
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
0
gheistCommented:
rtc error may mean motherboard problem.
fsck of 2006 is very old. you may need something new off the recent distro.
ext3 does not suffer from problem displayed.

you have to hold F1 when BIOS loads lilo or grub. then add "single" to fdefault command line. you get minimal system with fsck hopefully.
run fsck -a -p -y (fixes blindly - might be some data loss)
0
LawISAuthor Commented:
This became too much of an issue to deal with remotely, so I've replaced the unit and will look into your suggestions the next time I get access to the unit.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Programming

From novice to tech pro — start learning today.