Would you excuse a brief advert? Our Aussie gap-year technician has to return home suddenly for medical reasons. We have a potentially full-time post for a replacement, preferably resident. Write to me - don't clog the list .... -- Christopher Dawkins, Felsted School, Dunmow, Essex CM6 3JG 01371-822698, mobile 07816 821659 cchd@felsted.essex.sch.uk
SuSE 7.2 I can't mount my floppy disk although the machine boots from the floppy. Any ideas please? All was working well. History: I inadvertently deleted the contents of ect! and then tried to open the floppy to update some files that I had deleted. The machine told me that fstab did not exist. It was at this point that I noted that ect was in the bin! (by the way, never noticed before that there is no restore from the bin!) I replaced the files but it will still not mount the floppy I have tried several floppy disks, re-booted etc. Below is a copy of my fstab and the errors that I can generate. I'm sure that I used to use an fstab editor, can anyone suggest what it may have been? Adrian PS what are "proc" & "devpts" ? I don't remember seeing these before. fstab entry /dev/sda7 / ex2 defaults 1 1 /dev/sda5 /boot ext2 defaults 1 2 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy msdos noauto,user,sync 0 0 proc /proc proc defaults 0 0 /dev/sda1 /windows/c vfat noauto,user 0 0 /dev/sda6 swap swap pri=42 0 0 Errors When trying to mount the floppy drive using a freshly formatted, known to be good, disk mount: wrong fs type, bad option, bad super block on /dev/fd0 or too may mounted file systems. If fstab entry for the FDD is set to 'auto' I get mount: you must specify the filesystem type And if fstab entry for the FDD is set to 'dos' I get mount: fs type not supported by kernel
Have you tried mounting the floppy specifying the mount point and fs type? I.E. not relying on the fstab Robin At 14:38 06/05/2003 +0100, you wrote:
SuSE 7.2 I can't mount my floppy disk although the machine boots from the floppy. Any ideas please? All was working well.
History: I inadvertently deleted the contents of ect! and then tried to open the floppy to update some files that I had deleted. The machine told me that fstab did not exist. It was at this point that I noted that ect was in the bin! (by the way, never noticed before that there is no restore from the bin!) I replaced the files but it will still not mount the floppy
I have tried several floppy disks, re-booted etc.
Below is a copy of my fstab and the errors that I can generate. I'm sure that I used to use an fstab editor, can anyone suggest what it may have been?
Adrian
PS what are "proc" & "devpts" ? I don't remember seeing these before.
fstab entry
/dev/sda7 / ex2 defaults 1 1 /dev/sda5 /boot ext2 defaults 1 2 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy msdos noauto,user,sync 0 0 proc /proc proc defaults 0 0 /dev/sda1 /windows/c vfat noauto,user 0 0 /dev/sda6 swap swap pri=42 0 0
Errors When trying to mount the floppy drive using a freshly formatted, known to be good, disk
mount: wrong fs type, bad option, bad super block on /dev/fd0 or too may mounted file systems.
If fstab entry for the FDD is set to 'auto' I get
mount: you must specify the filesystem type
And if fstab entry for the FDD is set to 'dos' I get
mount: fs type not supported by kernel
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
--- "adrian.wells" <adrian.wells@sidcot.org.uk> wrote:
SuSE 7.2 I can't mount my floppy disk although the machine boots from the floppy. Any ideas please? All was working well.
If it is a boot-floppy such as a rescue disk, then you can't.
History: I inadvertently deleted the contents of ect! and then tried to open the floppy to update some files that I had deleted. The machine told me that fstab did not exist. It was at this point that I noted that ect was in the bin! (by the way, never noticed before that there is no restore from the bin!) I replaced the files but it will still not mount the floppy
I have tried several floppy disks, re-booted etc.
Ah, then this is interesting.....
Below is a copy of my fstab and the errors that I can generate. I'm sure that I used to use an fstab editor, can anyone suggest what it may have been?
Adrian
PS what are "proc" & "devpts" ? I don't remember seeing these before.
fstab entry
/dev/sda7 / ex2 defaults 1 1 /dev/sda5 /boot ext2 defaults 1 2 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy msdos noauto,user,sync 0 0 proc /proc proc defaults 0 0 /dev/sda1 /windows/c vfat noauto,user 0 0 /dev/sda6 swap swap pri=42 0 0
mount: you must specify the filesystem type
And if fstab entry for the FDD is set to 'dos' I get
mount: fs type not supported by kernel
Your kernel is missing several in-built modules by the sounds of things. If you can re-compile it, or use SuSE's YAST tool to re-copy the original kernel. proc is a virtual fs used by the kernel. -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com __________________________________________________ Yahoo! Plus For a better Internet experience http://www.yahoo.co.uk/btoffer
Thanks for everyones help so far :-) The plot thickens... Since the Box is dual booting I started in windows so that I could check the hardware against another OS, and guess what, can't read the disk! So I now assume that the FDD died in a two hour slot covering the time that I mangled the etc folder - Okay, I'll accept that. However the boot disk still works! Any ideas why the boot disk should be so fault resistent and if this is the reason, why is it that this file system is not used as a general floppy format? Kind regards Adrian
On Wed, May 07, 2003 at 10:25:12AM +0100, adrian.wells wrote:
Thanks for everyones help so far :-)
The plot thickens...
Since the Box is dual booting I started in windows so that I could check the hardware against another OS, and guess what, can't read the disk! So I now assume that the FDD died in a two hour slot covering the time that I mangled the etc folder - Okay, I'll accept that. However the boot disk still works!
As another poster said you won't be able to mount the boot disk, so no point even trying.
Any ideas why the boot disk should be so fault resistent and if this is the reason, why is it that this file system is not used as a general floppy format?
Have you tried formatting a disk on that machine. Either with Windows or by "fdformat /dev/fd0; mke2fs /dev/fd0" then seeing if it will mount? -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
At 10:25 07/05/2003 +0100, you wrote:
Thanks for everyones help so far :-)
The plot thickens...
Since the Box is dual booting I started in windows so that I could check the hardware against another OS, and guess what, can't read the disk! So I now assume that the FDD died in a two hour slot covering the time that I mangled the etc folder - Okay, I'll accept that. However the boot disk still works! Any ideas why the boot disk should be so fault resistent and if this is the reason, why is it that this file system is not used as a general floppy format?
Kind regards
Adrian
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
Sounds like the drive is out of tolerance compared to the drive your creating the disks on, as the other poster says, try formatting a disk in the machine. Rob
--- s-clarob@st-aidans.cumbria.sch.uk wrote:
Sounds like the drive is out of tolerance compared to the drive your creating the disks on, as the other poster says, try formatting a disk in the machine.
Rob
I agree. It is worth mentioning, that floppy drives are two a penny these days. I would suggest that if *after* the other suggestions posted to this list fail, then replace the floppy drive. Also, try looking at "/dev/fd0" with "badblocks" (man badblocks). -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com __________________________________________________ Yahoo! Plus For a better Internet experience http://www.yahoo.co.uk/btoffer
Okay, last one! :-) I eventually got around to adding another FDD this morning. I could boot the system from either FDD, but I could not read or format a disk in either of them from LINUX or windows. Okay, it's GOT to be the mother board. I reset the BIOS as a last ditch option befor replacing the mother board and all works fine! How I hate coincidence, especially since I'm a cynical, parranoid old Hector. Again, thanks to everyone for all the input. Adrian
----- Original Message ----- From: <s-clarob@st-aidans.cumbria.sch.uk>
Sounds like the drive is out of tolerance compared to the drive your creating the disks on, as the other poster says, try formatting a disk in the machine.
I wondered if this was the case (since the boot disk works) but it will not format a disk in LINUX or windows. It sounds like it's write protected in the BIOS, but I'm not sure that this BIOS supports this - I'll check it though. It must make an attempt at formatting since I can no longer read the disk in other machines (reports as unformatted!). This is (hopefully) academic as I intend changing the drive during lunch, however I may then not be able to boot the machine as my boot disk may not be read if it's a misalignment problem! Doh! ----- Original Message ----- From: Mark Evans <mpe@st-peters-high.devon.sch.uk>
As another poster said you won't be able to mount the boot disk, so no point even trying. Indeed, I noted that thanks, and had found it to be the case in the past. I was trying to reading a normal dos formatted disk(s), I was asking questions about the boot disk because that still works and wondered why (points to misalignment but the inability to format does not bear this out unless the misalignment has become too severe).
Kind regards Adrian
So you system only boots from floppy? is the boot loader not installed? Install a second floppy drive if you still need the dodgy one, then copy the boot disk to the second better drive and remove the original drive. Rob At 11:41 07/05/2003 +0100, you wrote:
----- Original Message ----- From: <s-clarob@st-aidans.cumbria.sch.uk>
Sounds like the drive is out of tolerance compared to the drive your creating the disks on, as the other poster says, try formatting a disk in the machine.
I wondered if this was the case (since the boot disk works) but it will not format a disk in LINUX or windows. It sounds like it's write protected in the BIOS, but I'm not sure that this BIOS supports this - I'll check it though. It must make an attempt at formatting since I can no longer read the disk in other machines (reports as unformatted!). This is (hopefully) academic as I intend changing the drive during lunch, however I may then not be able to boot the machine as my boot disk may not be read if it's a misalignment problem! Doh!
----- Original Message ----- From: Mark Evans <mpe@st-peters-high.devon.sch.uk>
As another poster said you won't be able to mount the boot disk, so no point even trying. Indeed, I noted that thanks, and had found it to be the case in the past. I was trying to reading a normal dos formatted disk(s), I was asking questions about the boot disk because that still works and wondered why (points to misalignment but the inability to format does not bear this out unless the misalignment has become too severe).
Kind regards Adrian
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
On Tue, May 06, 2003 at 02:38:13PM +0100, adrian.wells wrote:
SuSE 7.2 I can't mount my floppy disk although the machine boots from the floppy. Any ideas please? All was working well.
History: I inadvertently deleted the contents of ect! and then tried to open the floppy to update some files that I had deleted. The machine told me that fstab did not exist. It was at this point that I noted that ect was in the bin! (by the way, never noticed before that there is no restore from the bin!) I replaced the files but it will still not mount the floppy
I have tried several floppy disks, re-booted etc.
Below is a copy of my fstab and the errors that I can generate. I'm sure that I used to use an fstab editor, can anyone suggest what it may have been?
Adrian
PS what are "proc" & "devpts" ? I don't remember seeing these before.
"proc" is the proc filesystem, which undoubtedly was there before, "devpts" is support for the pty98 standard. If you don't know what this is don't worry about it.
fstab entry
/dev/sda7 / ex2 defaults 1 1 /dev/sda5 /boot ext2 defaults 1 2 /dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0 devpts /dev/pts devpts defaults 0 0 /dev/dvd /media/dvd auto ro,noauto,user,exec 0 0 /dev/fd0 /media/floppy msdos noauto,user,sync 0 0 proc /proc proc defaults 0 0 /dev/sda1 /windows/c vfat noauto,user 0 0 /dev/sda6 swap swap pri=42 0 0
Errors When trying to mount the floppy drive using a freshly formatted, known to be good, disk
mount: wrong fs type, bad option, bad super block on /dev/fd0 or too may mounted file systems.
Most likely it isn't an MSDOS formatted floppy.
If fstab entry for the FDD is set to 'auto' I get
mount: you must specify the filesystem type
And if fstab entry for the FDD is set to 'dos' I get
mount: fs type not supported by kernel
Try "ext2,vfat", this should cope with most floppies. -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
participants (5)
-
adrian.wells -
Christopher Dawkins -
Mark Evans -
s-clarob＠st-aidans.cumbria.sch.uk -
Thomas Adam