Jump to content

floppy drive shows system files


Trio3b
 Share

Recommended Posts

1. MDK 10.0 on this PC for about 4 months now......all OK except recently, floppy device access thru GUI now opens to a window with 8 or 9 files with strange lettering and showing to be about 13 gB worth of info. And this is with no floppy disk in the drive!

 

The only thing I can think of is somehow the floppy got linked to the HD. I have created and deleted this floppy icon with both the MCC and by right clicking on desktop to "create a device" here. Same results.

 

If it helps, here is my fstab:

 

[root@192 etc]# cat fstab

/dev/hda1 / ext3 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hda6 /home ext3 defaults 1 2

/dev/hdc /mnt/cdrom auto umask=0,user,codepage=850,iocharset=iso8859-1,noauto,ro ,exec 0 0

/dev/fd0 /mnt/fd0 iso9660 umask=0,iocharset=iso8859-1,sync,codepage=850 0 0

none /proc proc defaults 0 0

/dev/hda5 swap swap defaults 0 0

 

This is what happens when I try to mount the fd0

 

[root@192 /]# mount /dev/fd0

mount: wrong fs type, bad option, bad superblock on /dev/fd0,

or too many mounted file systems

This happens no matter what floppy disk I put in.

 

2. Also, if I create floppy device on desktop with MCC, then rightclick only gives me open and properties menu. I would like the complete context menu to open when I right click on the icon.

 

3. Just curious.......when floppy was working, it took forever to load/mount/view contents.

 

Any ideas?

Thanks

 

[moved from Software by spinynorman]

Link to comment
Share on other sites

iso9660 is not a filesystem you're especially likely to get on a floppy disk. That's probably the problem.

 

Somebody, paste a floppy drive fstab line that works - I don't have a floppy drive so I don't have one to crib :)

Edited by adamw
Link to comment
Share on other sites

I already replied to the regular MDK forum, but anyway...

Supermount enabled:

none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0022,iocharset=utf8,sync 0 0

Replace utf8 with whatever charset you use, and you can also play with the "fs=ext2:vfat" setting, trying either of them (but not ISO9660 of course).

Without supermount:

/dev/fd0 /mnt/floppy fs=ext2:vfat,umask=0022,iocharset=utf8,sync 0 0

HAL managed:

/dev/fd0 /mnt/floppy auto user,exec,noauto,comment=managed 0 0

(on some systems it will be /media/floppy and not /mnt/floppy).

If you have toyed with your udev rules then /dev/fd0 might have moved now to /dev/floppy/0 just check your /dev directory.

Edited by scarecrow
Link to comment
Share on other sites

OK.....tried your suggestion.....no go. Also. fired up the kids' PC also with MDK 10. Floppy working fine in it. Copied that fstab onto this PC....no luck..

 

Here's what it looks like now

 

/dev/hda1 / ext3 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hda6 /home ext3 defaults 1 2

/dev/hdc /mnt/cdrom auto umask=0,user,codepage=850,iocharset=iso8859-1,noauto,ro,exec 0 0

none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso=8559-1,sync,codepage=850 0 0

none /proc proc defaults 0 0

/dev/hda5 swap swap defaults 0 0

 

 

remember...floppy is fine on the kids' PC using this fstab.

On bad PC the drive doesn't even appear to engage(no drive led, but a window opens with nothing in it even tho I know files are on the disk)

 

 

By the way in /mnt there are both floppy/ and fd0/ , in addition to cdrom/, whereas on the working PC, there is only floppy/ and cdrom/

 

Could this be causing confusion?

thanks

Edited by Trio3b
Link to comment
Share on other sites

In MCC, devfs is running at startup

 

I do not find a udev daemon

 

now for some reason am receiving this error upon trying to mount the floppy

 

only root can mount /dev/fd0 on /mnt/fd0

 

I thought I had changed permissions but maybe not. If I mount from term I get.

 

[root@192 root]# mount /dev/fd0 /mnt/fd0

/dev/fd0: No such file or directory

mount: you must specify the filesystem type

[root@192 root]# mount /dev/fd0 /mnt/floppy

/dev/fd0: No such file or directory

mount: you must specify the filesystem type

 

I'm fairly certain I never had to specify file type before, unless the file sys type is not specified in the fstab. In MCC it is set at auto.

 

Thanks for any help

Link to comment
Share on other sites

OK. There is an fd0@ (I think it's a link) in the /dev directory and all the entries in /dev are identical to those in another PC also running MDK 10 in which the floppy device is working fine.

 

I have copied the fstab and mtab entries to imitate what is in those files on the "working" PC........still no go.

 

[root@192 etc]# cat fstab

/dev/hda1 / ext3 defaults 1 1

none /dev/pts devpts mode=0620 0 0

/dev/hda6 /home ext3 defaults 1 2

none /mnt/cdrom supermount dev=/dev/hdc,fs=auto,ro,exec,--,umask=0,user,iocharset=iso8859-1,codepage=850 0 0

none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0

none /proc proc defaults 0 0

/dev/hda5 swap swap defaults 0 0

 

and when I try to mount from terminal I get this...

 

 

[root@192 etc]# mount /dev/fd0 /mnt/floppy

mount: you must specify the filesystem type

doesn't the entry ,fs=ext2:vfat, take care of this?

 

Now the drive seems to engage and I get the drive LED but still no files viewable on a floppy disk I know to contain files

Thanks :wall:

Edited by Trio3b
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...