SVM / SDS device ID conflict situation
Posted: Tue Nov 18, 2008 6:44 pm
We had a power outage at work this past weekend.
I was working extremely hard yesterday to bring all servers up.
One problem I encountered is that the SVM (Solaris Volume Manager, used to be Solstice DiskSuite - SDS) complained about overlaps between 2 HDs (new HDs we purchased from a vendor).
After searching on the internet for some time, I realized it was caused by the identical device ID from these HDs. SUN recognizes its own HD with unique IDs on each HD. The 3rd party HDs are NOT recognized by SUN and have the identical device ID that causes the confusion.
The solution I found is to us "rwdevid" tool.
I then checked with the vendor who sold us the HDs.
They explained and provided a document from SUN.
Basically, the document describes how to make it work (just like how "rwdevid" does it, the vendor said).
First, find HD's vendor and product.
Second, add the following lines in /kernel/drv/sd.conf (make sure to use the right vendor and product number):
Make sure the Vendor occupies the first 8 characters of the total 24 characters in the first pair of "".
Third, reboot (no need for reconfigure).
That should be it.
The disks can be put into mirror again.
Please refer to the document:
I was working extremely hard yesterday to bring all servers up.
One problem I encountered is that the SVM (Solaris Volume Manager, used to be Solstice DiskSuite - SDS) complained about overlaps between 2 HDs (new HDs we purchased from a vendor).
After searching on the internet for some time, I realized it was caused by the identical device ID from these HDs. SUN recognizes its own HD with unique IDs on each HD. The 3rd party HDs are NOT recognized by SUN and have the identical device ID that causes the confusion.
The solution I found is to us "rwdevid" tool.
I then checked with the vendor who sold us the HDs.
They explained and provided a document from SUN.
Basically, the document describes how to make it work (just like how "rwdevid" does it, the vendor said).
First, find HD's vendor and product.
Code: Select all
ols-oradev01:/export/home/hsiaoc1%format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@0,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@1c,600000/scsi@2/sd@1,0
2. c1t2d0 <SEAGATE-ST3146855LC-0003 cyl 65533 alt 2 hd 4 sec 1093>
/pci@1c,600000/scsi@2/sd@2,0
3. c1t3d0 <SEAGATE-ST3146855LC-0003 cyl 65533 alt 2 hd 4 sec 1093> hdd3
/pci@1c,600000/scsi@2/sd@3,0
Specify disk (enter its number): 3
selecting c1t3d0: hdd3
[disk formatted]
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> i
Vendor: SEAGATE
Product: ST3146855LC
Revision: 0003
format> q
Code: Select all
sd-config-list=
"SEAGATE ST3146855LC ", "workaround";
workaround=1,0x8,0,0,0,0,0;
Third, reboot (no need for reconfigure).
That should be it.
The disks can be put into mirror again.
Please refer to the document:
SunSolve206634.pdf- Instruction on how to solve "overlaps with device" error under SDS / SVM
- (144.99 KiB) Downloaded 1263 times