1. ? sd driver LUN > 1
Hello,
I have several RAID boxes attached to SWIFT controllers
on Ultra2's and SS20's running Solaris 2.5.1
with the recommended patch cluster
(as of August 1997).
RAID appears to the host as three physical disks
sitting on the same SCSI ID with different LUNs:
Target 0
Unit 0 Disk BoxHill RAID 5300 Turbo B.1
Unit 1 Disk BoxHill RAID 5300 Turbo B.1
Unit 2 Disk BoxHill RAID 5300 Turbo B.1
/kernel/drv/sd.conf has entries for extra LUNs:
name="sd" class="scsi"
target=0 lun=0;
target=0 lun=1;
target=0 lun=2;
target=0 lun=3;
After booting with -r ,
I can see LUNs 0 and 1 but not LUN 2:
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <BoxHill-RAID5300Turbo-B.1 cyl 4093 alt 2 hd 16 sec 64>
1. c1t0d1 <BoxHill-RAID5300Turbo-B.1 cyl 24798 alt 2 hd 16 sec
64>
I've also tried to put the entry by hand into /etc/path_to_inst:
and reboot -- -r
but it didn't change anything.
Except for size and LUN, there is no difference -
all three sets are configured in exactly the same way.
Device on LUN=2 is about 6gb, just in case it matters :-)
Does 2.5.1 support LUNs 0 trough 7, anyway?
What am I doing wrong?
Any hints and guesses are welcome.
Thanks,
Andrey
2. /etc/dt/config/Xservers
3. How to decide the number of /dev/cWtXdYsZ under /dev/dsk and /dev/rdsk?
4. Looking for SCSI DAT tape recommedations.
5. tty-dev-number <-> /dev/pts
6. to purify or not to purify?
7. Corrupt label: bad magic number - sd.so(0,0,0)/vmunix: can not open
8. Raw IP Networking FAQ
9. corrupt label : bad magic number - sd.so(0,0,0)/vmunix: can not open
10. MAXIMUM NUMBER OF LUNS
11. What is the highest LUN number for UDWIS cards?
12. Solaris 9: no Serial Number for non SUN sd hardware
13. scsi_id+lun -> /dev/scd??