Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!in2.uu.net!usc!news.service.uci.edu!medusa.acs.uci.edu!ssapozni
From: ssapozni@mercury.sfsu.edu (Sam Sapoznick)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: SCSI Problem: uhhh..
Date: 16 Nov 1995 12:33:38 GMT
Organization: University of California, Irvine
Lines: 27
Message-ID: <48fb32$4vj@news.service.uci.edu>
NNTP-Posting-Host: medusa.acs.uci.edu
read your reply, but despite what you say about it just being a silly error
that doesn't mean anything, it <really> doesn't work..
I've read the man pages for fdisk, newfs, and disklabel, and none of those
commands will do anything to the disk, it seems.
Newfs complains that /dev/sd0 is "not a character-special device" and "'0'
partition unavailable."
Fdisk -u gives the message I mentioned before: ioctl DIOWLABEL op. not supportedby device.
Disklabel says bad pack magic number, etc.
As I understand it, first I need to partition the disk, then label it, and
then make a filesystem on it. For whatever reasons, none of the commands are
working. The kernel <does> recognize the SCSI controller (BusLogic BT-545C)
and there are no irq conflicts, etc.
Any further insights?
-sam
--
Sam Sapoznick
ssapozni@uci.edu
-stupid sig file.