Dear all,
Due to the power failure, so i need to restart my redhat linux server. but i
got below error messages, pls everybody can help/teach me
fix the problem by return mail.
------------------------------------------------------------------------------------------------------------------------------------------------
Yours system appears to have shut down uncleanly
Press Y within 1 seconds to force file system integrity check .....
Check root filesystem
/:clean, 153836/1281696 files, 637336/2560359 blocks
[ok]
Remounting root filesystem in read-write mode: [ok]
Finding module dependencies:
[ok]
Checking filesystems
/boot:clean,32/6024 files, 6328/24066 blocks
/home:Attempt to read block from filesystem resulted in short read while reading
block 523
/home:Attempt to read block from filesystem resulted in short read reading
journal superblock
fsck.ext3:Attempt to read block from filesystem resulted in short read while
checking ext3 journal for /home
***An error occurred during the file system check.
***Dropping you to a shell;the system will reboot
***when you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup):
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Best Regards
Transport Groupage Int'l (HK) Ltd.
I.T. Supervisor
Billy Lee
Dear all,
Due to the power failure, so i need to restart my redhat linux server. but i
got below error messages, pls everybody can help/teach me
fix the problem by return mail.
------------------------------------------------------------------------------------------------------------------------------------------------
Yours system appears to have shut down uncleanly
Press Y within 1 seconds to force file system integrity check .....
Check root filesystem
/:clean, 153836/1281696 files, 637336/2560359 blocks
[ok]
Remounting root filesystem in read-write mode: [ok]
Finding module dependencies:
[ok]
Checking filesystems
/boot:clean,32/6024 files, 6328/24066 blocks
/home:Attempt to read block from filesystem resulted in short read while reading
block 523
/home:Attempt to read block from filesystem resulted in short read reading
journal superblock
fsck.ext3:Attempt to read block from filesystem resulted in short read while
checking ext3 journal for /home
***An error occurred during the file system check.
***Dropping you to a shell;the system will reboot
***when you leave the shell.
Give root password for maintenance
(or type Control-D for normal startup):
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Best Regards
Transport Groupage Int'l (HK) Ltd.
I.T. Supervisor
Billy Lee
On Oct 18, 2002 22:18 +0800, Billy Lee wrote:> Due to the power failure, so i need to restart my redhat linux server. > but i got below error messages, pls everybody can help/teach me > fix the problem by return mail. > > ------------------------------------------------------------------------ > Yours system appears to have shut down uncleanly > Press Y within 1 seconds to force file system integrity check ..... > Check root filesystem > /:clean, 153836/1281696 files, 637336/2560359 blocks > [ok] > Remounting root filesystem in read-write mode: [ok] > Finding module dependencies: [ok] > Checking filesystems > /boot:clean,32/6024 files, 6328/24066 blocks > /home:Attempt to read block from filesystem resulted in short read while reading block 523 > /home:Attempt to read block from filesystem resulted in short read reading journal superblock > fsck.ext3:Attempt to read block from filesystem resulted in short read while checking ext3 journal for /homeYou are likely getting IDE errors or something on the /home drive. You need to check "dmesg" for other error messages. Chances are that your hard drive is having problems. Cheers, Andreas -- Andreas Dilger http://www-mddsp.enel.ucalgary.ca/People/adilger/ http://sourceforge.net/projects/ext2resize/
On Fri, Oct 18, 2002 at 10:18:11PM +0800, Billy Lee wrote:> > Dear all, > > Due to the power failure, so i need to restart my redhat linux server. but i got below error messages, pls everybody can help/teach me > fix the problem by return mail. > > ------------------------------------------------------------------------------------------------------------------------------------------------ > Yours system appears to have shut down uncleanly > Press Y within 1 seconds to force file system integrity check ..... > Check root filesystem > /:clean, 153836/1281696 files, 637336/2560359 blocks > [ok] > Remounting root filesystem in read-write mode: [ok] > Finding module dependencies: [ok] > Checking filesystems > /boot:clean,32/6024 files, 6328/24066 blocks > /home:Attempt to read block from filesystem resulted in short read while reading block 523 > /home:Attempt to read block from filesystem resulted in short read reading journal superblock > fsck.ext3:Attempt to read block from filesystem resulted in short read while checking ext3 journal for /home > > ***An error occurred during the file system check. > ***Dropping you to a shell;the system will reboot > ***when you leave the shell. > Give root password for maintenance > (or type Control-D for normal startup):Try running fsck(8) followed by badblocks(8) on the filesystem, and let us know what it reports. -- -- Skylar Thompson (skylar@attglobal.net) -- http://lizw090-016.resnet.wisc.edu/~skylar/, http://www.earlham.edu/~thompsk/
Hi, On Fri, Oct 18, 2002 at 10:18:11PM +0800, Billy Lee wrote:> Checking filesystems > /home:Attempt to read block from filesystem resulted in short read while reading block 523 > /home:Attempt to read block from filesystem resulted in short read reading journal superblock > fsck.ext3:Attempt to read block from filesystem resulted in short read while checking ext3 journal for /homeThe fsck binary is trying to read from your home filesystem, but is getting IO errors back. This could be due to a number of things. The disk might be going bad, for example. Try "dmesg" to look at the kernel logs ("dmesg|less" is easier to parse), to see if there are errors indicating what sort of IO failure is going on. This does look more like an underlying storage problem than a filesystem problem. Cheers, Stephen