🚀 go-pugleaf

Recently I made the mistake of mke2fs-ing my remaining 57MB MSDOS
partition. Despite doing everything as I had been told - umounted
the dos partition, mke2fs'd it, edited /etc/fstab to suit - it
never mounted correctly during system boot. Instead the error message
shown at exhibit A was always displayed. Running fsck against /dev/hda1 
would always 'fix' the problem, but the error message remained the
same. I edited /dev/hda1 out of /etc/fstab so as not to be continually
reminded of the fact I had 57M of unusable disk.

A few days later things went from bad to worse. It crashed during an
X windows session (as it has always been wont to do) and now cannot
be booted. Now it prints the error message shown at exhibit B ad nauseam.

Needless to say this is very distressing, particularly as all my
research work is on the partition in question. Any suggestions as
to what might be the problem and, better, what might be the solution
would be much appreciated. In the meantime I am trying to procure a
boot floppy.

---------------- Exhibit A ----------------
Parallelizing fsck version 0.5 (28-Mar-94)
/dev/hda3 is clean, no check.
/dev/hda1 is clean, no check.
Remounting root device with read-write enabled.
EXT2-fs error (device 3/1): ext2_check_blocks_bitmap: Wrong free blocks count for group 6, stored = 7930, counted = 0
Remounting filesystem read-only
EXT2-fs error (device 3/1): ext2_check_blocks_bitmap: Wrong free blocks count in super block, stored = 55497, counted = 47567
Remounting filesystem read-only
/dev/hda1 on /a type ext2 (rw)

---------------- Exhibit B ----------------
ext2_fs error (device 3/3): ext2_find_entry: bad directory entry: rec_len%4!=0
offset=540, inode=20205, rec_len=4373, name_len=4369

--
		  People who like this sort of thing
       	      will find this the sort of thing they like.
Tim J.Benham                                       bentj93@cs.adfa.oz.au