chroot failure

Issues related to software problems.
dichar
Posts: 10
Joined: 2014/07/14 01:24:21

Re: chroot failure

Post by dichar » 2014/07/16 19:35:57

After entering that command fsck -f, I got the repaly : no such file or directory.

Any other advises?

gerald_clark
Posts: 10642
Joined: 2005/08/05 15:19:54
Location: Northern Illinois, USA

Re: chroot failure

Post by gerald_clark » 2014/07/16 19:41:36

We can't help you when you don't show EXACTLY what you type and the EXACT errors you get.

dichar
Posts: 10
Joined: 2014/07/14 01:24:21

Re: chroot failure

Post by dichar » 2014/07/16 22:46:06

It is like I said. After using the rescue disk, and enting in skip mode. I didn t mount any directory like you said, and entered on the prompt the command fsck -f.
And the result I got is "no such file or directory".

User avatar
TrevorH
Forum Moderator
Posts: 26983
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: chroot failure

Post by TrevorH » 2014/07/16 23:57:22

You have to tell fsck what to check - in your case, from the graphic on the previous page, that would be /dev/VolGroup01/LogVol00. Just running `fsck -f` doesn't do anything
CentOS 5 died in March 2017 - migrate NOW!
CentOS 6 goes EOL sooner rather than later, get upgrading!
Full time Geek, part time moderator. Use the FAQ Luke

dichar
Posts: 10
Joined: 2014/07/14 01:24:21

Re: chroot failure

Post by dichar » 2014/07/19 14:20:10

Thanks for your help Trivorti;

After chosing the skip option on rescue mode. On the prompt I ve entered the next command:

sh-3.2# fsck -f /dev/VolGroup01/LogVol00

The replay I got

Warning: Couldn't open /etc/fstab: No such file or directory e2fsck 1.39 (29-may-2006) fsck ext2: No such file or directory while trying to open /dev/VolGroup01/LogVol00 The superblock could not be read or does not describe a correct ext2 file system. if the device is valid and if really contains an ext2 file system (and not swap or ufs or somthing else) the superblock is corrupt and you might try running e2fsck with an alternate superbloick: e2fsck -b 8193<device>

Any other suggestions?

User avatar
TrevorH
Forum Moderator
Posts: 26983
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: chroot failure

Post by TrevorH » 2014/07/19 15:00:41

Last post on the previous page:
You may also need to run lvm vgchange -a y to activate the logical volumes so that you can see them in order to fsck them.
CentOS 5 died in March 2017 - migrate NOW!
CentOS 6 goes EOL sooner rather than later, get upgrading!
Full time Geek, part time moderator. Use the FAQ Luke

dichar
Posts: 10
Joined: 2014/07/14 01:24:21

Re: chroot failure

Post by dichar » 2014/07/20 12:29:44

Thanks TrevorH very much you saved me.

This has solved my problem, and the server running normal again.

dichar
Posts: 10
Joined: 2014/07/14 01:24:21

Re: chroot failure

Post by dichar » 2014/08/03 09:29:44

Hi;

After working fine for more then 12 days, the system is not booting again.
I ve tried to write as much I could about the errors I got when reboting again.

Checking filesystems...
/dev/VolGroup01/LogVol00 contains a file system with errors check forced
/dev/VolGroup01/LogVol00 inodes that were part of a corrupted orphan linked list found
/dev/VolGroup01/LogVol00 unexpected inconsistency; run fsck manually
(i.e., without -a or -p options))
** An error occurred during the file system check.
*** propping you to a shell; the system will reboot
*** when you leave the shell./
Give root password for maintenance (or type control -D to continue)

Any help over there?

User avatar
TrevorH
Forum Moderator
Posts: 26983
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: chroot failure

Post by TrevorH » 2014/08/03 12:38:43

You need to do exactly the same as you did before. I'd also recommend that you check your logs for disk errors and run smartctl -a /dev/sda (if /dev/sda is your disk device). Having this happen twice in the space of a couple of weeks is suspicious and may point to hardware problems.
CentOS 5 died in March 2017 - migrate NOW!
CentOS 6 goes EOL sooner rather than later, get upgrading!
Full time Geek, part time moderator. Use the FAQ Luke

dichar
Posts: 10
Joined: 2014/07/14 01:24:21

Re: chroot failure

Post by dichar » 2014/08/03 13:44:55

I ve done the same as before and the server is online again.

1- linux mode entered.
2- "Skip" option chosen.
3- runned "lvm vgchange -a -y" command
4- then run "fsck -f /dev/VolGroup01/LogVol00" just choose "y" to every request.
5- en then reboot

What can be the problem if this will has happened after a short time of its fixing?
Should I do something special to fix this problem for ever?

Thanks.

Post Reply

Return to “CentOS 5 - Software Support”