[Leaplist] Floppy problem in Lenny - Debian-RichardO

[Richard F. Ostrow Jr.]

On Wed, July 11, 2007 9:24 pm, Whit Hansell wrote:
>
> Richard F. Ostrow Jr. wrote:
>> This really perplexes me... unless fd0 is a bad symlink to the device.
>> What does an "ls -l /dev/fd0" reveal? Does it point somewhere else? Does
>> the spot where it's pointing actually exist? Mine is a symlink pointing
>> to
>> "floppy/0", which would translate to /dev/floppy/0.
>>
>>
> brightsun:/# ls -l /dev/fd0
> brw-rw---- 1 root floppy 2, 0 2007-07-10 16:01 /dev/fd0
>
> brightsun:/dev# ls fd0
> fd0

Ok, so your device is right there in the /dev folder, no symlink.
Shouldn't be a problem. Otherwise, that looks about the same as my own
entry:

brw-rw---- 1 root floppy 2, 0 Jul 11 03:24 /dev/floppy/0

>> One more thing to try is to see if the device works *at all*. Here's
>> where
>> you get to try formatting ext3... put a blank disk in there and run
>> "mke2fs -j /dev/fd0" (not sure if -j would work with so little space,
>> but
>> that's what makes the difference between ext2 and ext3. If not, just
>> take
>> -j out). You should at least see the drive fire up, and if it finishes
>> successfully, you should be able to mount it as an ext3 (or 2)
>> filesystem.
>>
>>
> This one was done w. a floppy disk that I didn't seem to be able to
> access but I know had been formatted previously using DOS.....
>
> brightsun:/# mke2fs -j /dev/fd0
> mke2fs 1.40-WIP (14-Nov-2006)
> /dev/fd0: Not enough space to build proposed filesystem while setting up
> superblock
>
> This is using a floppy that I formatted today w. DOS on another linux
> box I have using kfloppy formatter and was successful as to what that
> program stated.  So I'm sticking this in w. DOS already formatted on it
> and now trying to put ext2 on it.
>
> brightsun:/# mke2fs -j /dev/fd0
> mke2fs 1.40-WIP (14-Nov-2006)
> Filesystem label=
> OS type: Linux
> Block size=1024 (log=0)
> Fragment size=1024 (log=0)
> 184 inodes, 1440 blocks
> 72 blocks (5.00%) reserved for the super user
> First data block=1
> Maximum filesystem blocks=1572864
> 1 block group
> 8192 blocks per group, 8192 fragments per group
> 184 inodes per group
>
> Writing inode tables: done
>
> Filesystem too small for a journal
> Writing superblocks and filesystem accounting information: done
>
> This filesystem will be automatically checked every 32 mounts or
> 180 days, whichever comes first.  Use tune2fs -c or -i to override.
>
> Then I tried to mount it ext2....
>
> brightsun:/# mount -t ext2 /dev/fd0 /media/floppy0
> mount: wrong fs type, bad option, bad superblock on /dev/fd0,
>        missing codepage or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so

That's not an ext2 filesystem... or rather, it wouldnt be if mke2fs wasn't
smart enough to automatically disable journaling (see the above status you
got when you ran mke2fs). When you add the -j flag to mke2fs, it adds
journaling. That makes it an ext3 filesystem. Still, I don't think that
would cause this level of hemorhaging (sp?).

> So I ran dmesg | tail and received....
>
> brightsun:/# dmesg | tail
> DROPPED IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:0f:3d:4f:72:96:08:00
> SRC=192.168.0.102 DST=192.168.0.255 LEN=235 TOS=0x00 PREC=0x00 TTL=63
> ID=0 DF PROTO=UDP SPT=138 DPT=138 LEN=215
> floppy0: sector not found: track 0, head 0, sector 18, size 2
> floppy0: sector not found: track 0, head 1, sector 1, size 2
> floppy0: sector not found: track 0, head 1, sector 2, size 2
> floppy0: sector not found: track 0, head 1, sector 3, size 2
> floppy0: sector not found: track 0, head 1, sector 3, size 2
> floppy0: sector not found: track 0, head 1, sector 3, size 2
> end_request: I/O error, dev fd0, sector 20
> EXT2-fs error (device fd0): ext2_get_inode: unable to read inode block -
> inode=2, block=10
> EXT2-fs: corrupt root inode, run e2fsck

If I didn't know you dual-booted and used this drive in WinXP, this would
tell me the drive itself was toast... but we know better. Something really
weird is going on...

> So I tried to do another format in ext2....
>
> brightsun:/# mke2fs -j /dev/fd0
> mke2fs 1.40-WIP (14-Nov-2006)
> Warning: could not erase sector 2: Attempt to write block from
> filesystem resulted in short write
> Filesystem label=
> OS type: Linux
> Block size=1024 (log=0)
> Fragment size=1024 (log=0)
> 184 inodes, 1440 blocks
> 72 blocks (5.00%) reserved for the super user
> First data block=1
> Maximum filesystem blocks=1572864
> 1 block group
> 8192 blocks per group, 8192 fragments per group
> 184 inodes per group
>
> Warning: could not read block 0: Attempt to read block from filesystem
> resulted in short read
> Warning: could not erase sector 0: Attempt to write block from
> filesystem resulted in short write
> Writing inode tables: 0/1
> Could not write 8 blocks in inode table starting at 10: Attempt to write
> block from filesystem resulted in short write
>
>
> So then I tried another mount...
>
> brightsun:/# mount -t ext2 /dev/fd0 /media/floppy0
> mount: wrong fs type, bad option, bad superblock on /dev/fd0,
>        missing codepage or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
>
> brightsun:/# dmesg | tail
> floppy0: data CRC error: track 0, head 0, sector 2, size 2
> floppy0: data CRC error: track 0, head 0, sector 2, size 2
> end_request: I/O error, dev fd0, sector 1
> floppy0: data CRC error: track 0, head 0, sector 17, size 2
> floppy0: data CRC error: track 0, head 0, sector 17, size 2
> end_request: I/O error, dev fd0, sector 16
> floppy0: sector not found: track 0, head 0, sector 3, size 2
> floppy0: sector not found: track 0, head 0, sector 3, size 2
> end_request: I/O error, dev fd0, sector 2
> EXT2-fs: unable to read superblock

CRC errors are a bad thing, and almost always mean a failing media... of
course in this case, it may well not mean that as the drive seems to have
completely lost its mind.