Click to See Complete Forum and Search --> : Cant access floppy


tomLinux
12-11-2002, 09:58 PM
When floppy mounted, cant access floppy as user or root, in command line or GUI. Attached is a GUI error message.

CLI : mount /mnt/floppy/
[root@localhost root]# cd /mnt/floppy/
bash: cd: /mnt/floppy/: Input/output error

WTF IS GOING ON... Sorry for yelling but Im frustrated and so is MkIII_Supra.

Thank you for your help.

mdwatts
12-12-2002, 10:17 AM
Is this a ext2 or msdos formatted floppy?

Insert diskette and try either

mount -t msdos /dev/fd0 /mnt/floppy

or

mount -t ext2 /dev/fd0 /mnt/floppy

and then

ls -al /mnt/floppy

or

cd /mnt/floppy

ls -al

If neither work, have a look at your system log.

dmesg

dmesg | grep fd0

less /var/log/messages

tomLinux
12-12-2002, 06:27 PM
Hey thanks mdwatts, but no good. Im soo new at this linux thing I dont know what to do. But here is what happened with the commands you told me to try. I havent looked at the system log yet. I wouldnt know what Im looking at anyways. Thanks for the help. I'll try anything that might work.

CLI: [root@localhost tom]# mount -t msdos /dev/fd0 /mnt/floppy/
mount: /dev/fd0 already mounted or /mnt/floppy/ busy
[root@localhost tom]# mount -t ext2 /dev/fd0 /mnt/floppy/
mount: /dev/fd0 already mounted or /mnt/floppy/ busy
[root@localhost tom]# ls -al /mnt/floppy/
total 1
drwxrwxrwx 2 root root 48 Dec 12 14:08 .
drwxr-xr-x 10 root root 240 Dec 4 22:45 ..
[root@localhost tom]# cd /mnt/floppy/
[root@localhost floppy]# ls -al
total 1
drwxrwxrwx 2 root root 48 Dec 12 14:08 .
drwxr-xr-x 10 root root 240 Dec 4 22:45 ..
[root@localhost floppy]#

mdwatts
12-12-2002, 06:37 PM
Does

mount

show /mnt/floppy as mounted?

First try umounting

umount /mnt/floppy

and then again what I previously posted.

tomLinux
12-13-2002, 05:34 PM
I tried the mount, umount. When not mounted, I can open /mnt/floppy but it doesnt read my disk. I can save in the directory, but its isnt saving on the disk.

JohnT
12-13-2002, 05:49 PM
I notice in all your post, with the exception of the last, your using a trailing slash at the end of all the commands. Try dropping that.

gcrosby15
12-14-2002, 04:33 PM
I'm having the same problem. I installed Mandrake 9.0 on a Panasonic CF-71 Toughbook Laptop computer using the CD-ROM. The floppy and CD are interchangable, you cannot have both in at the same time. I could access CDs with the CD-ROM in but can't access my floppy drive. The floppy drive a superdisk but I have only been trying to access 1.44 floppies. I did some of the things suggested. I did a: mount -t msdos /dev/fd0 /mnt/floppy and got:
mount: block device /dev/fd0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/fd0, or
too many mounted file systems.

It took a long time to get a response from the mount -t msdos ... , I thought the machine had hung up but after approx. two minutes the above messages came back. Also I never saw, green LED, or heard the floopy running. I know this is long winded but I also did a dmesg and found:

vesafb: framebuffer at 0xfd000000, mapped to 0xc8800000 size 2496k floppy drive(s): fd0 is 1.44M

further down I found:

ide1: BM-DMA at 0xfc98-0xfc9f, BIOS settings: hdc:pio, hdd:pio hdc: LS-120 SLIM3 00 UHD Floppy, ATAPI Floppy drive

The LS-120 SLIM is infact my floppy. I tried booting with the parameter "linux nobiospnp" as suggested from somewhere else on the web but this did not work. Also when I type MOUNT it returns:
...
none on /mnt/cdrom
none on /mnt/floppy
...

Also as a side note this is a dual boot machine with Win2000.

Please help

JohnT
12-14-2002, 06:46 PM
Think of your floppy drive as a directory and just "cd" to it. Then "ls" the contents.

cd /mnt/floppy (or whatever is listed in your /etc/fstab)

ls -l

tomLinux
12-14-2002, 09:11 PM
I tried 'ls -l', and this is what I got:
[root@localhost /]# cd /mnt/floppy/
[root@localhost floppy]# ls -l
total 1
drwxrwxrwx 2 root root 48 Dec 12 14:08 .
drwxr-xr-x 10 root root 240 Dec 4 22:45 ..
[root@localhost floppy]#

Now I know that there is info on this floppy it was from school. On the second permissions list, does the dashes mean that there are restrictions?? If so, how do I change them? Thanks again.

Originally posted by JohnT
Think of your floppy drive as a directory and just "cd" to it. Then "ls" the contents.

cd /mnt/floppy (or whatever is listed in your /etc/fstab)

ls -l

JohnT
12-14-2002, 11:52 PM
The dashes separate .....owner-group-users ....permissions. d=directory r=read, w=write,=x=execute.

Learn to use the manpages.

man access permissions

paco
12-15-2002, 07:20 PM
indeed the permissions are not given when there is printed a -

the permissions list is as follows:


d rwx r-x r-x
| \_/ \_/ \_/__ permissions for 'other' users
| | |
| | +------- permissions for 'group' users
| |
| +----------- permissions for 'owner'
|
+-------------- file type


As johnT said the r,w,x mean read,write,execute for the type of
users.

file type can indeed be d=directory, but there are many more.

the listing that you have posted is very empty.

If you knew for sure that it was full then i think that it got empty
by maybe mounting it wrong the first time.

a directory always has two listings :

. (referece to this directory)

&

.. (reference to parent directory)

the changing of permissions id done with the 'chmod' utility.

program takes parameters like:

chmod u+rwx g+rx-w o+x <file or dir>

the above example sets rwx for owner, r-x for group and --x for other

there can also be used a for all : a+rwx means setting rwxrwxrwx on a file.

But changing the permissions will not help getting data from the disk.

Not very nice to say, i know, but i think the disk is empty now :'(

JohnT
12-15-2002, 11:14 PM
From the terminal you might try typing



ls -a (list hidden files - files that begin with "." character)

rather than "ls l

tomLinux
12-16-2002, 07:11 PM
Ok heres the latest attempt at resolving my floppy issue. Im running a duel boot system, I loaded my win2k and everything worked. When i restarted Mandrake 9.0, I got an error screen which I took screen shots from and will attach to this message. And also, the message with the error:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x41023739 in wait4 () from /lib/i686/libc.so.6
#0 0x41023739 in wait4 () from /lib/i686/libc.so.6
#1 0x410a0340 in sys_sigabbrev () from /lib/i686/libc.so.6
#2 0x40e64a73 in waitpid () from /lib/i686/libpthread.so.0
#3 0x40620f55 in KCrash::defaultCrashHandler(int) ()
from /usr/lib/libkdecore.so.4

Hayl
12-16-2002, 07:17 PM
( i never did get my floppy drive to work under linux. i always got "not a valid block device" no matter what i did. last time i recompiled a new kernel - i took out floppy support completely LOL :) )

Ptrper
12-16-2002, 08:23 PM
Hi folks,

Was just going through this post after helping out some students here at school...

If you are trying to mount the floppy, and it is formatted for MSDos, try:

mount -t vfat /dev/fd0 /mnt/floppy

once you've done this, type in cd /mnt/floppy, and then ls -l.

Hope this works out for you. ;)

Ed

PS. In reference to the chmod utility, you can use numerical instances:

chmod 777 filename

This will give everyone: read, write, and execute privileges.

PPS. Cyber, where did you get AMSN? That is too cool!

mdwatts
12-17-2002, 06:49 AM
Originally posted by tomLinux
Ok heres the latest attempt at resolving my floppy issue. Im running a duel boot system, I loaded my win2k and everything worked. When i restarted Mandrake 9.0, I got an error screen which I took screen shots from and will attach to this message. And also, the message with the error:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x41023739 in wait4 () from /lib/i686/libc.so.6
#0 0x41023739 in wait4 () from /lib/i686/libc.so.6
#1 0x410a0340 in sys_sigabbrev () from /lib/i686/libc.so.6
#2 0x40e64a73 in waitpid () from /lib/i686/libpthread.so.0
#3 0x40620f55 in KCrash::defaultCrashHandler(int) ()
from /usr/lib/libkdecore.so.4

Is that preventing KDE from starting up?

What did you last change in your system before this happened?

tomLinux
12-20-2002, 10:54 PM
No, I can do everything on the system except for the floppy. I ended up just reinstalling md 9.0 and everything is fine. thank you guys for all your help.

keywi
10-05-2003, 10:03 AM
I am trying to mount a superdisk drive with a superdisk media. I am unable to. Slackware 9, i keep getting a message "wrong fs type, bad options, bad superblock on /dev/fd0, or too many mounted files systems". I have did a search on JL and this is the only forum that came up.

William

www.keywi.org

keywi
10-05-2003, 11:20 AM
Ok, i figured out what was wrong with my superdisk drive and accessing it.

/dev/hdb is where the drive is.

edit fstab:
/dev/hdb1 /mnt/sdisk vfat noauto,user,kudzu,rw 0 0

mkdir /mnt/sdisk

this will try to access the drive but give me an error message of: wrong fs type, bad options, bad superblock on /dev/hdb1, or too many mounted file systems.

I have tried different files systems, with and without kudzu, users and owner.

Help

William
www.keywi.org