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.
Error Message
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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/tab
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)
Business Accounts
Answer for Membership
by: rindiPosted on 2009-06-30 at 23:08:49ID: 24751832
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