Consecuencia de un mal apagado y solución! (gracias Dios)

["k" <mylist@ciudad.com.ar>]

Apagado mientras el disco esribia.
Cuando bootea ..

Unattachjed inode 48313

/dev/hda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
	  (i.e., without -a or -p options)

fsck failed. Please repair manually and reboot. Please note that the
root file system is currently mounted read-only. To remount it
read-write:

	#mount -n -o remount,rw /

CONTROL-D will wxit from this shell and REBOOT the system.

Give root password for maintenance
(or type Control-D for normal startup):


Al correr fsck me dice ....

Parallelizing fsck version 1.18 (11-Nov-1999)

Si corro la linea de arriba (la de mount) me dice ..

EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
EXT2-fs error (device ide0(3,1)): ext2_check_blocks_bitmap: Wrong free
blocks count for group 2, stored = 28087, counted = 28082
Remounting filesystem read-only
EXT2-fs error (device ide0(3,1)): ext2_check_blocks_bitmap: Wrong free
blocks count for group 3, stored = 25097, counted = 28096
Remounting filesystem read-only
EXT2-fs error (device ide0(3,1)): ext2_check_blocks_bitmap: Wrong free
blocks count in super block, stored = 868188, counted = 868182
Remounting filesystem read-only
EXT2-fs error (device ide0(3,1)): ext2_check_blocks_bitmap: Wrong free
inodes count for group 21, stored = 14843, counted = 14842
Remounting filesystem read-only
EXT2-fs error (device ide0(3,1)): ext2_check_blocks_bitmap: Wrong free
inodes count in super block, stored = 475119, counted = 475118
Remounting filesystem read-only


Solucion
1. umount /dev/hda1
2. e2fsck -c /dev/hda1
e2fsck chequeo los blocks y los inodes y los reparó

SALUDOS