🚀 go-pugleaf

bentj93@cserve.cs.adfa.oz.au (Tim Benham) writes:
>Recently I made the mistake of mke2fs-ing my remaining 57MB MSDOS
>partition.

I presume you mean it was a mistake because you have not been able to
get it to work, rather than you mkfs'ed over your dos fs by mistake. :)

>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.

Two things to try. First if you are using e2fsprogs 0.5 then you *MUST*
upgrade to 0.5a, as 0.5 has some bugs (one of which caused something
very similar to what you're experiencing on my machine). Secondly, try
running e2fsck by hand (ie without the -a switch) and answer 'y' to
everything.


 - Mike

-- 
  Mike Battersby   <mike@starbug.apana.org.au>   <mib@bruce.cs.monash.edu.au>
          CompSci honours student, Linux user and part time beggar.
           GCS d-(--) p c++ l++(+++) u+ e+ m+@ s+/- n+(---) h--(*)
                           f-- !g w+ t++@ r(+) y?

Good news! I have my system booting again. Bad news: no fewer than 9
block special and 25 character special files (including /dev/null)
has disappeared from /dev. In their place I have a whole swag of files
in /lost+found with cool names like #20205.

My question is, what the heck am I supposed to do about this? Should
I mv the files back to /dev? should I create new special files?

Tim Benham (bentj93@cserve.cs.adfa.oz.au) wrote:
: 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

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

Tim Benham (tim@duh.cs.adfa.oz.au) wrote:
: Good news! I have my system booting again. Bad news: no fewer than 9
: block special and 25 character special files (including /dev/null)
: has disappeared from /dev. In their place I have a whole swag of files
: in /lost+found with cool names like #20205.

: My question is, what the heck am I supposed to do about this? Should
: I mv the files back to /dev? should I create new special files?

have you tried running the MAKEDEV script in your /dev directory? Snoop 
around in the script and run MAKEDEV generic, MAKEDEV std, and whatever 
other entries that correspond to your missing /dev files.

Good luck!

-- Gary F.

Mike Battersby (mike@starbug.apana.org.au) wrote:
...
: Two things to try. First if you are using e2fsprogs 0.5 then you *MUST*
: upgrade to 0.5a, as 0.5 has some bugs (one of which caused something
: very similar to what you're experiencing on my machine). Secondly, try
: running e2fsck by hand (ie without the -a switch) and answer 'y' to
: everything.

Yes, that seems to be why e2fsck wasn't correctly correcting the
filesystem. Version 0.5a did the trick.  How my filesystem got to be
in such a state is what bothers me now; why so many crashes...

Many thanks to Mike and those who responded by email.
--
		  People who like this sort of thing
       	      will find this the sort of thing they like.
Tim J.Benham                                       bentj93@cs.adfa.oz.au

In article <1994Jul16.010625.25751@sserve.cc.adfa.oz.au>, bentj93@cserve.cs.adfa.oz.au (Tim Benham) writes:
>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.
>
[lots of info deleted]

Question - Did you run the Linux fdisk first?

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

/* Greg Nowicki | Mail Stop 401A | LIDAR Applications Group */
/* NASA Langley Research Center  | Hampton, Virginia  23681-0001 */
/* Voice: (804) 864-2713         | FAX: (804) 864-7790 */
/* nowicki@tardis.larc.nasa.gov  | My opinions and mine alone . . . */