SCSI IDs in Fuel question
- From: Walther Mathieu <mathieu.nospam@xxxxxxxxx>
- Date: Sun, 23 Apr 2006 11:25:07 +0200
Hello,
if there are two harddisks built into a SGI Fuel,
with their jumper settings for SCSI addresses 0/1
(that is no jumper set / only SCSI ID0 set):
how can it happen that these show up in hinv as
Controller 0, (dksc(0,2,0))
Controller 0, (dksc(0,3,0)) ?
Is there any mechanism that remembers former SCSI
ID settings and kind of maps that over the real one?
The system drive (3) was created on another Fuel
using the "system drive by cloning" method (where
another two disks resided under address 1 and 2),
then jumpered to be on SCSI address 3.
Then, all SCSI jumpers pulled, it refused to boot on
the target machine until the variables were set to
root=dks0d3s0
SystemPartition=dksc(0,3,8)
OSLoadPartition=dksc(0,3,0)
This appears to be some kind of workaround only.
I´d like to know what´s going on, or, better,
how to make the drives show up as what they are
jumpered for.
TIA
Walther
.
- Follow-Ups:
- Re: SCSI IDs in Fuel question
- From: Tony 'Nicoya' Mantler
- Re: SCSI IDs in Fuel question
- From: Thomas Jahns
- Re: SCSI IDs in Fuel question
- Prev by Date: Fuel PCI issues
- Next by Date: Re: SCSI IDs in Fuel question
- Previous by thread: Fuel PCI issues
- Next by thread: Re: SCSI IDs in Fuel question
- Index(es):
Relevant Pages
|
Loading