Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!cs.utexas.edu!howland.reston.ans.net!ix.netcom.com!netcom.com!kientzle
From: kientzle@netcom.com
Subject: Re: ZIP drive, AIC6360, and 2.0R -> ``not configured''??
Message-ID: <kientzleDEyzxz.Gpo@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <kientzleDEq690.6uz@netcom.com> <433fcs$47q@bonnie.tcd-dresden.de>
Date: Fri, 15 Sep 1995 23:29:59 GMT
Lines: 25
Sender: kientzle@netcom12.netcom.com
In article <433fcs$47q@bonnie.tcd-dresden.de>,
J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote:
><kientzle@netcom.com> wrote:
>>Once the system is up, attempts to disklabel or mount an
>>MSDOS-format ZIP disk are greeted with ``device not configured''
>
>Can you read from the raw device? Just try a hexdump from /dev/rsd1
>or whatever SCSI disk unit it actually is. This is the least
>functionality that should work.
A-ha! That fixed one problem. A dump from rsd0d did produce
a lot of nulls, which answers the question ``which slice should
I be using?''
However, ``mount -t msdos /dev/disk/sd0d /dos/d:'' reports
``msdos: mount: Invalid argument''
Hmmm... I'll keep tinkering with it until I find the magic
incantation. At the least, this suggests I may be able
to newfs the thing and use it as a FreeBSD disk, which is
a step in the right direction.
- Tim