det@hawkmoon.MN.ORG (Derek E. Terveer) (06/26/89)
(Sorry if you get this twice) I have just installed a second floppy drive, 3.5" 1.44M in my ACER 1100 running uPort 386/3.0e Unix. The 5.25" (1.2M) is drive 0 and the the 3.5" is drive 1. I am accessing them with /dev/dsk/f0q15dt and /dev/dsk/f13ht. I am currently experiencing some problems with accessing drive 0 (the 5.25"). I had both drives mounted, did some work involving both drives, then umounted the 5.25" drive and inserted another floppy. The 3.5" fs remained mounted. When i did a labelit on the second floppy (in the 5.25" drive) with either the raw or block device it got the label and superblock from the previously mounted floppy! No matter what i do, i can't get rid of the superblock from the previous floppy, short of rebooting. If i actually mount the second floppy, the files are garbage because the super block doesn't match what is actually on the floppy. I've tried using sync, fsck, multiple umounts, etc to try and get the system to recognise that i have changed floppies, but to no avail. It will even sometimes report a label when the driver door is open! I am using a WD1003-WA2 controller which was not designed for a 3.5" drive, but seems to be able to access the 3.5" drive ok-- it looks like the problems i'm experiencing are software related (like the superblock isn't getting flushed/being marked as flushed, etc), not hardware. But that's just a guess. I'm happy that i got my second floppy drive, but the potential of having to reboot the system every time i change floppies in drive 0 (the 5.25") is somewhat daunting, to say the least.... Has anyone heard of this problem and have a fix for it? I was thinking of calling uPort tech support on this, but from what i gather they don't really have anyone left at the office --. Do any of the uPort BBS patches affect this problem? derek -- Derek Terveer det@hawkmoon.MN.ORG || ..!uunet!rosevax!elric!hawkmoon!det w(612)681-6986 h(612)688-0667 "A proper king is crowned" -- Thomas B. Costain