Mourning the loss of our friend, WhitPhil.
There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
Search
 
Linux and Unix
Tag Cloud
access audio black screen blue screen boot bsod connection crash dell desktop driver drivers dvd email error excel firefox hard drive hardware hijackthis internet keyboard laptop malware monitor motherboard network networking outlook problem processor ram recovery registry cleaner router screen slow sound spyware tdlwsp.dll trojan video virus vista vundo windows windows 7 windows vista windows xp wireless
Search
Search for:
Tech Support Guy Forums > Operating Systems > Linux and Unix >
superblock last mounted in the future

Tip: Click here to scan for System Errors and Optimize PC performance
[ Sponsored Link ]

Closed Thread
 
Thread Tools
compdict's Avatar
Junior Member with 3 posts.
 
Join Date: Jun 2008
30-Jun-2008, 07:26 AM #1
superblock last mounted in the future
Every time I do a fsck on the / and /home directory I get this message:
superblock last mounted in the future

Can someone help to fix this problem?
lotuseclat79's Avatar
Distinguished Member with 14,989 posts.
 
Join Date: Sep 2003
Location: -71.45091, 42.27841
30-Jun-2008, 10:10 AM #2
Hi compdict,

Welcome to TSG!

First, fsck requires that when run against a disk's filesystem, that the disk be unmounted - was your disk unmounted?

There is a field in the super block that sets the number of reboots without an fsck to about 30, then on the 31st reboot, fsck will run during bootup.

Do not attempt to run fsck separately against / or /home as fsck is intended to be run against an entire file system.

If you have a Linux Live CD, and you can boot from it - i.e. BIOS boot order specifies CD before hard drive, you can determine if your disk(s) are unmounted (by running the mount command with no parameters), unmount the disk (if necessary) with the umount /dev/xxxx command (where xxxx is the devices' name of the disk which the mount command will tell you), and run fsck with the command (from root account):
# script -c fsck fsck.out
where the script command will capture the output of the fsck command in the file fsck.out

If you manage to do this, post the output in this thread. When fsck is successfully run against a disk, the superblock count for the number of reboots without an fsck will be reset to 0, and again be able to be counted up to the limit.

-- Tom
__________________
The independence created by philosophical insight is - in my opinion - the mark of distinction
between a mere artisan or specialist and a real seeker after truth. - Einstein 1944
Imagination is more important than knowledge. - Einstein

Last edited by lotuseclat79 : 30-Jun-2008 10:25 AM.
Closed Thread Bookmark and Share

THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Smart Search

Find your solution!



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.

Thread Tools


You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -5. The time now is 07:54 AM.
Copyright © 1996 - 2009 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2009, Jelsoft Enterprises Ltd.
Powered by Cermak Technologies, Inc.