Ubuntu

/dev/hda1 mounted 33x without being checked

Asked by Bruce M.

Hi folks,

  Today I saw, "/dev/hda1 mounted 33x without being checked", and fsck started it's thing.
  I've read a few posts here and understand that it's an aoutomatic thing with Ubuntu.
  Good, I'm happy that Ubuntu automatically checks for problems. Another plus for Ubuntu.

  BUT as it was doing it's check, I "something" flashed by my screen with a RED FLAG: FAILED.

  I have no idea what it was, it was too fast for me to read.
  Is there a log file I can check somewhere?

Bruce MIlmine

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Bruce M.
Solved:
Last query:
Last reply:
Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#1

At startup, when the system boot, you can see some FAILED startup messages if some startup service fails to start.

Try to check /var/log/boot

Open a Terminal and type:

cat /var/log/boot | grep -i failed

HTH

Revision history for this message
Bruce M. (canar-ciudad) said : 		#2

Hi elart

bruloo@The-Team:~$ cat /var/log/boot | grep -i failed
bruloo@The-Team:~$

  Blank! :(

Bruce Milmine

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#3

Ok there are no "failed" words in /var/log/boot file
to view, and check, all the file content open a terminal and type:

cat /var/log/boot | pg

HTH

Revision history for this message
Bruce M. (canar-ciudad) said : 		#4

Hi again elart,

bruloo@The-Team:~$ cat /var/log/boot | pg
(Nothing has been logged yet.)
(EOF):

  Well, that has to be a good sign. Doesn't it?

Bruce Milmine

Revision history for this message
Collin Stocks (collinstocks) said : 		#5

If fsck found any corrupt files, it will have put them in "/lost+found". You can look in there as root and see if it is empty or not. *Make sure you are root! Otherwise nautilus will always tell you it is empty!*

From the command line:

~$ cd /
/$ sudo su
/# cd ./lost+found
/lost+found# ls -a

Revision history for this message
Bruce M. (canar-ciudad) said : 		#6

Collin,

  Action:

bruloo@The-Team:~$ cd /
bruloo@The-Team:/$ sudo su
root@The-Team:/# cd ./lost+found
root@The-Team:/lost+found# ls -a
. ..
root@The-Team:/lost+found#

  Guess I'm good.
  Now I'm wondering what that RED FAILED was.

  Quick Q: Could it have failed ... and fsck tried a second time and it worked??

Bruce Milmine