Mark Everett <[EMAIL PROTECTED]> wrote:
>Sorry for not making this more clear to begin with, but in
>fact my very next objective is to create a partition table
>(via: 'fdisk /dev/sd[c-?]') and then lay down a filesystem
>(via: 'mkfs /dev/sd[c-?]').
Partially my fault as well. After re-reading your first message and this
reply I realize my earlier attempt at being helpful was totally
wrong. (D-oh!) Sorry about that. Yes, you can't run fdisk to create the
partition table if Linux hasn't assigned the drive a device file. Sorry
about that.
>I'm pretty sure
>my first external disk, 'scsi2:0:1:0', was automatically mapped to
>'sdb', which fdisk recognized without a problem.
Correct. New drives are normally recognized without a problem, even
without a valid partition table.
>I ran 'cd /dev; ./MAKEDEV update' but that did not seem to help.
No, it won't. The device files are already in /dev. The only time I've
had to run MAKEDEV is when I had more partitions on a drive than there were
entries in /dev.
>Are my expectations incorrect? Have I overlooked a step?
>Do I need to manually create the raw device file somehow before
>I can use fdisk to create a partition table? Do I need to define
>this disk's geometries and disk partition characteristics somehow?
You shouldn't heed to create the device file - it should already be in
/dev. If you don't have /dev/sdc, that's probably the problem.
>The disk in question, a 'DotHill' 360WSV, is a 36GB LVD device.
>Is there a size limit to the size of disk that Linux can recognize?
Don't have any experience with DotHill drives. AFAIK, there's no size
limit on SCSI drives. As long as the SCSI card is supported, pretty much
any SCSI disk *should* work. The biggest I have is 18Gb though.
>dmesg output:
><snip>
>(scsi1:0:0:0) Synchronous at 20.0 Mbyte/sec, offset 15.
>(scsi2:0:1:0) Synchronous at 20.0 Mbyte/sec, offset 15.
> Vendor: SEAGATE Model: ST34371N Rev: 0484
> Type: Direct-Access ANSI SCSI revision: 02
>Detected scsi disk sdb at scsi2, channel 0, id 1, lun 0
><snip>
You said earlier that there was nothing else plugged into the SCSI
card. Is the card properly terminated and all that jazz? I'm wondering if
that might be the source of your parity errors when wide negotiation is
enabled as well. I'm also wondering if it doesn't like being set at SCSI
ID 0, which is normally reserved for boot disks. I'd check the cable
connections, termination and try moving the SCSI ID to something other than
zero.
-Eric
Eric Sisler
Library Computer Technician
Westminster Public Library
Westminster, CO, USA
[EMAIL PROTECTED]
Linux - don't fear the Penguin.
Want to know what we use Linux for?
Visit http://gromit.westminster.lib.co.us/linux
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
