Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: where to find the message "Your disk drives are being checked for errors"
Operating Systems Linux Ubuntu where to find the message "Your disk drives are being checked for errors" Post 302472563 by rbatte1 on Wednesday 17th of November 2010 12:26:14 PM
Old 11-17-2010
This is probably nothing to worry about. The boot process will look at the filesystems to mount and check the status flag on each. If they are all marked as clean (i.e. unmounted correctly at shutdown) then the thing will whizz through. If there is a problem, it will either stop and prompt at the console or possibly try to fix simple problems, but you will at least see more output from this and it will take a little while usually.

It depends what flavour of OS you have as to what it does. Some versions stop and prompt for the root password so you can get into Single User and you manually fix things there.

On the whole, if it runs, it runs. Don't worry, it is a normal checking function.
This User Gave Thanks to rbatte1 For This Post:
xib.be
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

"find command" to find the files in the current directories but not in the "subdir"

Dear friends, please tell me how to find the files which are existing in the current directory, but it sholud not search in the sub directories.. it is like this, current directory contains file1, file2, file3, dir1, dir2 and dir1 conatins file4, file5 and dir2 contains file6,... (9 Replies)
Discussion started by: swamymns
9 Replies

2. Red Hat

"No Drives Found" error during Redhat Linux AS 4 installation

I'm trying to install Redhat LInux AS 4 update 4 on an IBM x306 series server. I keep getting following error: "No Drives Found. An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem." I called IBM and... (2 Replies)
Discussion started by: pieman8080
2 Replies

3. AIX

"too big" and "not enough memory" errors in shell script

Hi, This is odd, however here goes. There are several shell scripts that run in our production environment AIX 595 LPAR m/c, which has sufficient memory 14GB (physical memory) and horsepower 5CPUs. However from time to time we get the following errors in these shell scripts. The time when these... (11 Replies)
Discussion started by: jerardfjay
11 Replies

4. Shell Programming and Scripting

how to let "this" find all hard drives correctly

hi all I've been working on a project to create a custom centos live-cd with a tsm client installed. so far, the kickstart script isnt working properly to add icons into a live user's desktop. I found there is a expression looking strange. it isnt working, neither. ... (1 Reply)
Discussion started by: rs6000er
1 Replies

5. Solaris

Help:"Bad checksum in disk label" and "Can't open disk label package"?

Hello, I'm brand new to Sun/Solaris. I have a Sun Blade 150, with SunOS 5.8. I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies

6. UNIX for Dummies Questions & Answers

Unix "look" Command "File too large" Error Message

I am trying to find lines in a text file larger than 3 Gb that start with a given string. My command looks like this: $ look "string" "/home/patrick/filename.txt" However, this gives me the following message: "look: /home/patrick/filename.txt: File too large" So, I have two... (14 Replies)
Discussion started by: shishong
14 Replies

7. Red Hat

Problem in starting: message shown is "disk out of space"

Hi all, I was using centos on VMware platform. It is not getting started, as it is showing the following message: GDM could not write to your authorization file. This could mean that you are out of disk space or that your home directory could not be opened for writing. In any case, it is not... (2 Replies)
Discussion started by: CAch
2 Replies

8. Shell Programming and Scripting

Find lines with "A" then change "E" to "X" same line

I have a bunch of random character lines like ABCEDFG. I want to find all lines with "A" and then change any "E" to "X" in the same line. ALL lines with "A" will have an "X" somewhere in it. I have tried sed awk and vi editor. I get close, not quite there. I know someone has already solved this... (10 Replies)
Discussion started by: nightwatchrenba
10 Replies

9. Shell Programming and Scripting

find . -path "*_nobackup*" -prune -iname "*.PDF" \( ! -name "*_nobackup.*" \)

These three finds worked as expected: $ find . -iname "*.PDF" $ find . -iname "*.PDF" \( ! -name "*_nobackup.*" \) $ find . -path "*_nobackup*" -prune -iname "*.PDF" They all returned the match: ./folder/file.pdf :b: This find returned no matches: $ find . -path "*_nobackup*" -prune... (3 Replies)
Discussion started by: wolfv
3 Replies

LEARN ABOUT X11R4

fsck.hfsplus

FSCK_HFS(8)						    BSD System Manager's Manual 					       FSCK_HFS(8)

NAME

     fsck.hfs -- HFS file system consistency check

SYNOPSIS

     fsck.hfs -q [-df] special ...
     fsck.hfs -p [-df] special ...
     fsck.hfs [-n | -y | -r] [-dfgl] [-m mode] [-c size] special ...

DESCRIPTION

     The fsck.hfs utility verifies and repairs standard HFS and HFS+ file systems.

     The first form of fsck.hfs quickly checks the specified file systems to determine whether they were cleanly unmounted.

     The second form of fsck.hfs preens the specified file systems.  It is normally started by fsck(8) during systen boot, when a HFS file system
     is detected.  When preening file systems, fsck.hfs will fix common inconsistencies for file systems that were not unmounted cleanly.  If more
     serious problems are found, fsck.hfs does not try to fix them, indicates that it was not successful, and exits.

     The third form of fsck.hfs checks the specified file systems and tries to repair all detected inconsistencies.

     If no options are specified fsck.hfs will always check and attempt to fix the specified file systems.

     The options are as follows:

	   -c size Specify the size of the cache used by fsck.hfs internally.  Bigger size can result in better performance but can result in
		   deadlock when used with -l option.  Size can be specified as a decimal, octal, or hexadecimal number.  If the number ends with
		   a ``k'', ``m'', or ``g'', the number is multiplied by 1024 (1K), 1048576 (1M), or 1073741824 (1G), respectively.

	   -d	   Display debugging information.  This option may provide useful information when fsck.hfs cannot repair a damaged file system.

	   -f	   When used with the -p option, force fsck.hfs to check `clean' file systems, otherwise it means force fsck.hfs to check and
		   repair journaled HFS+ file systems.

	   -g	   Causes fsck.hfs to generate its output strings in GUI format.  This option is used when another application with a graphical
		   user interface (like Mac OS X Disk Utility) is invoking the fsck.hfs tool.

	   -l	   Lock down the file system and perform a test-only check.  This makes it possible to check a file system that is currently
		   mounted, although no repairs can be made.

	   -m mode Mode is an octal number that will be used to set the permissions for the lost+found directory when it is created.  The
		   lost+found directory is only created when a volume is repaired and orphaned files or directories are detected.  fsck.hfs places
		   orphaned files and directories into the lost+found directory (located at the root of the volume).  The default mode is 01777.

	   -p	   Preen the specified file systems.

	   -q	   Causes fsck.hfs to quickly check whether the volume was unmounted cleanly.  If the volume was unmounted cleanly, then the exit
		   status is 0.  If the volume was not unmounted cleanly, then the exit status will be non-zero.  In either case, a message is
		   printed to standard output describing whether the volume was clean or dirty.

	   -y	   Always attempt to repair any damage that is found.

	   -n	   Never attempt to repair any damage that is found.

	   -r	   Rebuild the catalog file on the specified file system.  This option currently will only work if there is enough contiguous
		   space on the specified file system for a new catalog file and if there is no damage to the leaf nodes in the existing catalog
		   file.

SEE ALSO

     fsck(8)

BUGS

     fsck.hfs is not able to fix some inconsistencies that it detects.

HISTORY

     The fsck.hfs command appeared in Mac OS X Server 1.0 .

Mac OS X							 November 21, 2002							  Mac OS X
All times are GMT -4. The time now is 02:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy