INIT: version 2.86 bootingEXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557062 in dir #1556708EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481Welcome to CentOS release 5.5 (Final)Press ‘I’ to enter interactive startup.EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481Setting clock : Mon Jan 17 10:21:37 EST 2011 [ OK ]EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481Starting udev: EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481MAKEDEV: no such user: rootEXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481[ OK ]EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557062 in dir #1556708Setting hostname vps.cutemobi4u.com: [ OK ]No devices foundSetting up Logical Volume Management: [ OK ]Checking filesystemsChecking all file systems.[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1/dev/sda1 contains a file system with errors, check forced./dev/sda1: Inodes that were part of a corrupted orphan linked list found./dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.(i.e., without -a or -p options)[FAILED]*** An error occurred during the file system check.*** Dropping you to a shell; the system will reboot*** when you leave the shell.EXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557074 in dir #1556481sulogin: cannot open password database!Unmounting file systemsumount: none: not foundumount: /proc/sys/fs/binfmt_misc: not mountedumount: tmpfs: not foundumount: /dev/shm: not mountedEXT3-fs error (device sda1): ext3_lookup: unlinked inode 1557062 in dir #1556708Automatic reboot in progress.
A few days ago, one of my domU felt into infinite loop of reboot and was unable to boot properly. Upon checking, its file system was corrupted. As this happened, the best is shut down this domU and fsck its lvm logical volume.
Lets check the logical volume name with following command,
lvdisplay | grep domU name
then, run below fsck command
e2fsck -f -y /full/path/to/domU/logical/volume
You will see the repairing process. Once it is done, just start up the domU and you shall be able to powering it up.
Note : During this fsck, some file system / partition might be corrupted and cant recover. Be prepared to build a new domU and perform migration.