Not yet ~

i searched it via Google and found this website : http://www.experts-exchange.com/OS/Linux/Distributions/Red_Hat/Q_25043629.ht...

i do that said but this time screen displayed this :

/dev/VolGroup00/LogVol00 : faild Inodes that were part of a corrupted or phan linked list found . ...

What should i do ? Maybe it should to run the "fsck" to repair that filesystem .

On Mon, Mar 22, 2010 at 2:41 PM, Eero Volotinen eero.volotinen@iki.fiwrote:

2010/3/22 sync jiannma@gmail.com:

...

hi , guys:

when i reboot the server today ,the screen displays this ;

---

...

Setting hostname xxx [OK]

Your system appears to have shut down uncleanly Press Y within 1 seconds to force file system integrity check... Checking root filesystem

/dev/VolGroup00/LogVol 00: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. (i.e., without -a or -p options) [FAILED]

*** An error occured during the file system check. *** Droping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to continue)

---

...

is it the disk error ? What should i do to repair the disk ?

run fsck manually without a or p options?

-- Eero _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Thanks for all reply...

Because the boss don't let me do that . He said that would be dangerous and it would destroy all data in the hard disk

On Mon, Mar 22, 2010 at 4:03 PM, Nicolas Thierry-Mieg < Nicolas.Thierry-Mieg@imag.fr> wrote:

sync wrote:

...

run fsck manually without a or p options?

Not yet ~

why not?

...

i searched it via Google and found this website :

http://www.experts-exchange.com/OS/Linux/Distributions/Red_Hat/Q_25043629.ht...

...

i do that said but this time screen displayed this :

try reading the bottom of this page: http://www.centos.org/modules/tinycontent/index.php?id=16

it's publicly readable, unlike your link.

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Well , Thanks for your suggestions.

1.Which kind of file system is being used on the volume having trouble? A: it uses the ext2fs filesystem on CentOS 4.6 x86_64

2.Do you have backups? A: that server is used to backup other servers data , so itself has not any backups

3.Is the volume small enough and do you trust yourself enough with dd to duplicate it off to a USB|firewire|esata disk? (now THIS _is_ risky. :)

4.have you read `man fsck` to see why it was being suggested to run it WITHOUT the a or p options? A: Yeah ~ I have read that . In particular , "-p" options ,. This option is mainly provided for those sysadmins who don't want to repartition the root system to be small and compact( which is really the right solution)

....

On Mon, Mar 22, 2010 at 11:50 PM, Todd Denniston < Todd.Denniston@tsb.cranrdte.navy.mil> wrote:

sync wrote, On 03/22/2010 05:11 AM:

...

Thanks for all reply...

A) as Nicolas HINTED please read the _text_ that follows "Guidelines for CentOS Mailing List posts" at http://www.centos.org/modules/tinycontent/index.php?id=16

B) as time permits read the links in that section, I think the ones some of us want you to read are: http://www.caliburn.nl/topposting.html and a couple of supplementals: http://en.wikipedia.org/wiki/Posting_style#Interleaved_style or http://en.wikipedia.org/wiki/Posting_style#Bottom-posting

...

Because the boss don't let me do that . He said that would be dangerous and it would destroy all data in the

hard

...

disk

What did the boss say would "be dangerous and ... would destroy all data" i.e. what command and options would the boss not let you run?

It is a bit hard to comment on that which is not here.

Is the boss more qualified to be administrating the machine in critical times like this than you**? If so, then it is most likely time to hand him the keyboard and tell him he gets to keep the bits that are left intact (both before he starts typing and after). Will there be someone who you both trust to work on the machine in this state coming into the office soon?

I would expect that anyone who is willing to help you over email would want at least the following questions answered: Which kind of file system is being used on the volume having trouble? Do you have backups? Is the volume small enough and do you trust yourself enough with dd to duplicate it off to a USB|firewire|esata disk? (now THIS _is_ risky. :) have you read `man fsck` to see why it was being suggested to run it WITHOUT the a or p options?

** The boss "...said that would be dangerous and it would destroy all data..." comment, indicates to me that either you or he or both think that.

...

On Mon, Mar 22, 2010 at 4:03 PM, Nicolas Thierry-Mieg < Nicolas.Thierry-Mieg@imag.fr> wrote:

...

sync wrote:

...

run fsck manually without a or p options?

Not yet ~

why not?

...

...

try reading the bottom of this page: http://www.centos.org/modules/tinycontent/index.php?id=16

it's publicly readable, unlike your link.

-- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Thanks for all replies .

Today, I did the following things,and also met the other errror message:

First, I used the CentOS 4.6 DVD to boot for the linux rescue and then i copy all data to the another server

Then, reboot the server and then boot it from the hard disk.

This time, the screen came up with these:

Checking root filesystem: ---------------------------------------------- EXT3-fs error (device dm-0) : ext3_get_inode_loc: unable to read inode block -inode=7473432, block=14942282

fsck: error while loading shard libraries: libuuid.so.1:cannot open shared object file: Input/Output error:

*** An error occured during the file system check. *** Droping you to a shell; the system will reboot *** when you leave the shell. Give root password for maintenance (or type Control-D to continue)

--------------------------------------------------------------

It is obvious that the fsck command maybe not to use .

What could i do now ?

Maybe it is the only method to reinstall the CentOS operating system. isn't it?

On Tue, Mar 23, 2010 at 10:24 AM, Les Mikesell lesmikesell@gmail.comwrote:

sync wrote:

...

Well , Thanks for your suggestions.

1.Which kind of file system is being used on the volume having trouble? A: it uses the ext2fs filesystem on CentOS 4.6 x86_64

2.Do you have backups? A: that server is used to backup other servers data , so itself has not any backups

3.Is the volume small enough and do you trust yourself enough with dd to duplicate it off to a USB|firewire|esata disk? (now THIS _is_ risky. :)

4.have you read `man fsck` to see why it was being suggested to run it WITHOUT the a or p options? A: Yeah ~ I have read that . In particular , "-p" options ,. This option is mainly provided for those sysadmins who don't want to repartition the root system to be small and compact( which is really the right solution)

You are either going to have to run fsck and answer 'y' to whatever it suggests or learn more than it knows about fixing filesystems.

-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

sync wrote:

...

Thanks for all replies .

Today, I did the following things,and also met the other errror message:

<snip>

...

Then, reboot the server and then boot it from the hard disk.

This time, the screen came up with these:

Checking root filesystem:

EXT3-fs error (device dm-0) : ext3_get_inode_loc: unable to read inode block -inode=7473432, block=14942282

<snip>

...

It is obvious that the fsck command maybe not to use .

What could i do now ?

Maybe it is the only method to reinstall the CentOS operating system. isn't it?

That looks like you either have a physically bad hard disk, or directory/inode corruption in the entry needed to load fsck. Try running

<snip> Looks to me as though you definitely have a hard drive going bad. The thing that says that to me is "unable to read", not "error reading". I'd reboot from a DVD with linux rescue, do *not* mount the filesystems, and do an fsck -c (and any other options) on all the partitions that are formatted. This will check for bad blocks. If there's only a few, say, 1, or 10, note how many of them there are, and let it take its default to mark, and then fix everything else. If there's a *bunch* of them (100+), you need a new hard disk, now.

mark "done this too much recently"

On 03/22/2010 08:33 PM, sync wrote:

Well , Thanks for your suggestions.

1.Which kind of file system is being used on the volume having trouble? A: it uses the ext2fs filesystem on CentOS 4.6 x86_64

2.Do you have backups? A: that server is used to backup other servers data , so itself has not any backups

3.Is the volume small enough and do you trust yourself enough with dd to duplicate it off to a USB|firewire|esata disk? (now THIS _is_ risky. :)

4.have you read `man fsck` to see why it was being suggested to run it WITHOUT the a or p options? A: Yeah ~ I have read that . In particular , "-p" options ,. This option is mainly provided for those sysadmins who don't want to repartition the root system to be small and compact( which is really the right solution)

You need to look more closely at the manpage. That comment is for the "-P" (capital P) option, not the "-p" (lower case) option. The latter is not an option to 'fsck' itself but is passed down to 'fsck.ext2', where it has an entirely different meaning.