Kernel Panic: floppy drive trouble

Mark Orr (markorr@intersurf.com)
Sun, 30 Jun 1996 00:14:41 -0500 (CDT)


This might have been mentioned before, but I don't see anything
on homer about it, so I'll let you know what I have.

This afternoon, I experienced a series (well, 4 of 'em) of seemingly
repeatable kernel panics while trying to mount a floppy disk.

Running Linux 2.0.0 ; P5/100,16 Mb+16 Mb swap; Mount version 2.5j.
I have the floppy driver compiled as a module ; installed using
kerneld, which gives me no problems.

The floppy was ext2 formatted. I ran e2fsck -c (v1.04) on the floppy
and it turned up a bad block...but it doesn't look like I lost anything
on the floppy or my HD -- the first crash locked up while in X...but
I got it to lock up at the console bash prompt.

Here's what the syslog tells me:

(at the time of the first crash -- I got a whole series of these with
increasing sector #'s)
Jun 28 06:05:36 darkstar linux: 6>inserting floppy driver for 2.0.0
Jun 28 06:08:02 darkstar kernel: floppy0: disk absent or changed during
operation
Jun 28 06:08:02 darkstar kernel: end_request: I/O error, dev 02:00, sector
10

(later, next crash)
Jun 29 16:34:23 darkstar linux: 6>inserting floppy driver for 2.0.0
Jun 29 16:34:25 darkstar kernel: floppy0: sector not found: track 0, head
0, sector 8, size 2
Jun 29 16:34:26 darkstar kernel: floppy0: sector not found: track 0, head
0, sector 8, size 2
Jun 29 16:34:26 darkstar kernel: end_request: I/O error, dev 02:00, sector
7

(one of the kernel panic messages)
Jun 29 17:15:13 darkstar kernel: end_request: I/O error, dev 02:00, sector
0
Jun 29 17:15:21 darkstar kernel: EXT2-fs warning: mounting unchecked fs,
running e2fsck is recommended
Jun 29 17:15:22 darkstar kernel: floppy0: sector not found: track 0, head
0, sector 8, size 2
Jun 29 17:15:22 darkstar kernel: floppy0: sector not found: track 0, head
0, sector 8, size 2
Jun 29 17:15:22 darkstar kernel: end_request: I/O error, dev 02:00, sector
7
Jun 29 17:15:22 darkstar kernel: Kernel panic: EXT2-fs panic (device
02:00): read_block_bitmap: Cannot read block bitmap - block_group = 0,
block_bitmap = 3

...looking at the log, I did get kernel panic messages for all the crashes
all with the same "cannot read block bitmap" message and values.

------

just thought you'd like to know :-)

Mark Orr
markorr@intersurf.com