[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Second IDE device on a Qube 3?
- Subject: Re: [cobalt-developers] Second IDE device on a Qube 3?
- From: "Matthew Nuzum" <cobalt@xxxxxxxxxxxxx>
- Date: Mon Mar 11 02:33:03 2002
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
I don't use a qube, so I can't say for sure, but I can say that in Linux,
your disk devices work like this:
/dev/hda <-- first disk on first ide
/dev/hdb <-- second disk on first ide
/dev/hdc <-- first disk on second ide
/dev/hdd <-- second disk on second ide
etc.
So if the cube has two ide headers, each presumably allowing two disks (for
a total of 4), the the master drive on the second chain would be /dev/hdc,
not /dev/hdb.
Don't know if this helps or not.
Matt Nuzum
----- Original Message -----
From: "Ed Halley" <ed@xxxxxxxxx>
To: <cobalt-developers@xxxxxxxxxxxxxxx>
Sent: Monday, March 11, 2002 10:02 AM
Subject: [cobalt-developers] Second IDE device on a Qube 3?
> There are two IDE cable headers inside the Qube 3, to match the two
> drive bays. The single-drive setup uses the IDE header closest to the
> edge of the baseboard pcb, and Linux enumerates that as /dev/hda.
>
> I tried a second drive in bay two, but this doesn't appear as /dev/hdb
> with a simple fdisk listing. Is this a second IDE chain (so both drives
> should be considered solo on their chain), or is this the same IDE chain
> (requiring master/slave jumpers, which seems odd if the second bay was
> intended for software RAID)?
>
> I don't want to use RAID, just interested in adding capacity for
> automated bz2 archive spooling. Any pointers would be helpful.
>
> --
> [ e d @ h a l l e y . c c ]
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>