Why the root file system when the problem is on one of my volumes in an external drive? Dave. Krishnaprasad_K@xxxxxxxx wrote:
Boot into runlevel 1 and then fix the bad block using the following command e2fsck -y /dev/sdxx where sdxx is your root file system partition.. Thanks, Krishnaprasad -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Dave Martini Sent: Thursday, March 13, 2008 10:28 PM To: General Red Hat Linux discussion list Subject: fsck ext3 One of my est3 file systems went into read only mode. Does this usually mean the drive is going bad? When I umounted and the mounted it again it said to run fsck manually. I did but keep getting the Illegal block in inode messages below. Is there a way to fix this? Thanks. Dave. #fsck -v /u02 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004) Resize inode not valid. Recreate<y>? yes /ora_za3 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 54473213 has illegal block(s). Clear<y>? yes Illegal block #-1 (542592844) in inode 54473213. CLEARED. Illegal block #-1 (1162168403) in inode 54473213. CLEARED. Illegal block #-1 (1162545998) in inode 54473213. CLEARED. Illegal block #-1 (542723148) in inode 54473213. CLEARED. Illegal block #-1 (1380929357) in inode 54473213. CLEARED. Illegal block #-1 (843188549) in inode 54473213. CLEARED. Illegal block #-1 (1142960440) in inode 54473213. CLEARED. Illegal block #-1 (1728513729) in inode 54473213. CLEARED. Illegal block #-1 (1869376609) in inode 54473213. CLEARED. Illegal block #-1 (822506350) in inode 54473213. CLEARED. Illegal block #-1 (808662326) in inode 54473213. CLEARED. Too many illegal blocks in inode 54473213. Clear inode<y>? yes Inode 54473328 has illegal block(s). Clear<y>?
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
