[Leaplist] Floppy problem in Lenny - Debian

[John Hayden]

Far out in left field, are you sure that disk is DOS of any kind and not
MAC?

J.T. Hayden
   KG4BFJ

Home/office:     407.891.1835
Office/mobile:    407.922.3091

-----Original Message-----
From: leaplist-bounces at leap-cf.org [mailto:leaplist-bounces at leap-cf.org] On
Behalf Of Richard F. Ostrow Jr.
Sent: Wednesday, July 11, 2007 15:11
To: This is the Leap Main List
Subject: Re: [Leaplist] Floppy problem in Lenny - Debian

Hmm... hate to say it, but I'm running out of ideas. 


>>> modprobe vfat and now at the top of the new lsmod list I get:
>>>
>>> brightsun:/# lsmod
>>> Module                  Size  Used by
>>> vfat                   11648  0
>>> msdos                   8576  0
>>> fat                    45980  2 vfat,msdos

>>> So I just popped in a floppy to the drive and
>>>
>>> brightsun:/# mount -t msdos /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

Like I said, I don't believe that's the problem here, I'm just
stating possibilities (admittedly distant) because I'm running out of
ideas.

>>> brightsun:/# dmesg | tail
>>> FAT: bogus number of reserved sectors
>>> VFS: Can't find a valid FAT filesystem on dev fd0.
>>> FAT: bogus number of reserved sectors
>>> VFS: Can't find a valid FAT filesystem on dev fd0.
>>>
>>
>> Pretty clear it's not reading correctly... the question is why?
>> Maybe the fs is incorrect?
>>
>>
> brightsun:/# mount -t vfat /dev/fd0 /media/floppy0
> mount: /dev/fd0 is not a valid block device

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.

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.


_______________________________________________
Leaplist mailing list
Leaplist at leap-cf.org
http://lists.leap-cf.org/mailman/listinfo/leaplist