| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Problem Resolution Sure Solution 1004033.1 : Clean-Up of disk scanned in on channel 2 and 3 on Sun StorEdge[TM] 3510
PreviouslyPublishedAs 205624 Symptoms If you are using 3.27R or earlier controller firmware it was possible to scan a disk twice on channel 2 and channel 3. The disk is reported twice in sccli show disks. One time on channel 2 and a second time on channel 3. Resolution Verify that the disk has been scanned in twice using the sccli show disks command. Sample output from show disk sccli> show disks Ch Id Size Speed LD Status IDs ---------------------------------------------------------------------- 2 48 68.37GB 200MB NONE NEW SEAGATE ST373307FSUN72G 0207 <= 2 49 68.37GB 200MB ld0 ONLINE SEAGATE ST373307FSUN72G 0207 2 50 68.37GB 200MB NONE NEW SEAGATE ST373307FSUN72G 0207 <= 2 51 68.37GB 200MB NONE NEW SEAGATE ST373307FSUN72G 0207 :::::::: :::::::: 2 58 68.37GB 200MB NONE NEW SEAGATE ST373307FSUN72G 0207 2 59 68.37GB 200MB NONE NEW SEAGATE ST373307FSUN72G 0207 3 48 68.37GB 0MB NONE NEW SEAGATE ST373307FSUN72G 0207 <= 3 50 68.37GB 0MB NONE NEW SEAGATE ST373307FSUN72G 0207 <= In this case disk ID 48 and disk ID 50 are scanned in twice. Sample output from another escalation Vendor: SUN Product: StorEdge 3510 Revision: 327R sccli> show disks Ch Id Size Speed LD Status IDs Rev ------------------------------------------------------------------------ 2 0 68.37GB 200MB ld0 ONLINE SEAGATE ST373307FSUN72G 0207 S/N 3HZ1EN0M00007347 2 1 68.37GB 200MB ld3 ONLINE FUJITSU MAP3735F SUN72G 1501 S/N 000449Q0HGNS ::::::::::::: ::::::::::::: 2 11 68.37GB 200MB GLOBAL STAND-BY FUJITSU MAP3735F SUN72G 1701 <= S/N 000449Q0HGEC 3 11 68.37GB 200MB NONE USED FUJITSU MAP3735F SUN72G 1701 <= S/N 000449Q0HGEC Disk ID 11 was scanned in on channel 2 and 3 The simplest way to remove duplicate entries is to wait for next scheduled down time and to reset the SE 351xx. If the customer is unable to reset the SE 35xx you can use the following procedure to remove duplicate entries. To be able to remove duplicate entries, the affected disks must be moved to an unused status. Steps 1 and 2 of the procedure listed below will move the affected disks to an unused status. This steps are not required if the disk is neither a spare disk nor a member of a LD. Steps 3 trough 7 will clean up the drive list. The final steps 8 and 9 add the disks back to the drive list and complete the procedure. To remove the duplicate entries follow procedure outlined below. This procedure requires one unused drive. 1. If disk is assigned to a LD (logical drive) then view and edit scsi drives -> select drive ch 2 ID xx -> clone Failing drive -> Replace After Clone 2. If disk is used as hot spare then view and edit scsi drives -> select ch2 ID xx -> Delete global / local spare drive 3. Remove disk ch2 ID xx from array (remove disk physically) 4. Add ch2 id xx as global spare while the disk is physically removed view and edit scsi drives -> select ch2 ID xx -> Add global / local spare drive 5. Add ch3 id xx as global spare view and edit scsi drives -> select ch2 ID xx -> Add global / local spare drive ==> this should bring the disk drive ID xx in a failed state on both channels. 6. View and edit scsi drives -> select ch2 ID xx -> clear drive status 7. View and edit scsi drives -> select ch3 ID xx -> clear drive status This should clear the drive status and remove the entries for the disks ch2 ID xx and ch3 ID xx. 8. Insert the disk 9. Rescan the disk if required. This time only on ch2 please. Product Sun StorageTek 3510 FC Array Internal Comments For internal Sun use only. See also Bug ID 4980144 for more details. disk, rescan, scan, twice, sccli, show, disks Previously Published As 85059 Change History Date: 2006-04-27 User Name: 71396 Action: Approved Comment: Performed final review of article. Updated product name and trademarking. Publishing. Version: 6 Date: 2006-04-27 User Name: 71396 Action: Accept Comment: Version: 0 Attachments This solution has no attachment |
||||||||||||
|
||||||||||||