Re: [suse-sparc] Floppy: /dev/fd0 is not a valid block device

From: Joshua Uziel (uzi@suse.com)
Date: Mon Nov 27 2000 - 15:18:33 PST

  • Next message: dan carter: "Re: [suse-sparc] Installing Suse 7.0 on Sparcstation 20"

    Date: Mon, 27 Nov 2000 15:18:33 -0800
    From: Joshua Uziel <uzi@suse.com>
    Message-ID: <20001127151833.A25268@gimp.org>
    Subject: Re: [suse-sparc] Floppy: /dev/fd0 is not a valid block device
    

    * Thomas Weiler <thweiler@informatik.rwth-aachen.de> [001127 08:48]:
    > I've got a SPARCStation Voyager (sun4m).
    > When I try to mount a floppy (fat, vfat, ext2) I've got the following
    > error message:
    >
    > mount: /dev/fd0 is not a valid block device
    >
    > In /var/log/messages the following lines are found:
    >
    > kernel: VFS: Disk change detected on device fd(2,0)
    > kernel: end_request: I/O error, dev 02:00 (floppy), sector 0
    >
    > I compiled a new kernel (2.2.16, 2.2.17, 2.4.0-test11) with fat, vfat,
    > umsdos and msdos support (according to a former posted message about
    > that problem) but allways with the same result.

    Well, you don't need the umsdos support... but under "Floppy, IDE, and
    other block devices" which has a "Normal floppy disk support" option I'm
    assuming you selected. Another thing to check would be if your /dev/fd0
    device file looks correct. Finally, I don't know of other people using
    a Voyager, so I don't know if that has anything special about it's
    floppy drive (though I suspect not... but that machine is a bit
    special).

    > The floppy device seems to be physically ok: I could boot from
    > (Redhat...) Installation-Floppy (because SuSE's installation floppy
    > didn't work on my machine -> bad magic number).

    There's a fixed SuSE boot floppy I've put in http://suse.com/~uzi/sparc/
    that you can download and test with. Funny that I was gonna suggest it
    possibly being a bad disk drive (since while I made that boot floppy, I
    had nothing but problems until I figured out that my test machine had a
    bad floppy drive in it).

    > Does anybody have an idea, how to fix this problem?

    Try and test those suggestions... if nothing else, we'll look into it
    more.



    This archive was generated by hypermail 2.1.0 : Wed Jun 06 2001 - 11:08:22 PDT