| 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 Technical Instruction Sure Solution 1018173.1 : Drives may be marked BAD upon upgrade to 4.13 firmware which may be good drives.
PreviouslyPublishedAs 229526 Description If there are any drives that are having status of "NONE USED" and we are on firmware 3.27 or 4.11, if we upgrade to 4.13, this drive will be marked bad by the 4.13 firmware and an amber led will also glow on the drive. This document will clarify why this happens and how can we avoid this problem. Steps to Follow We have seen that occasionally, we end up in a situation where we have drives that have a status of "NONE USED". This is usually due to some hardware/controller problem. The drive will remain in this state unless we clear it. There are a couple of knowledge docs which give some more detail on how to fix this situation. Please see following Problem Resolutions: < Document: 1009137.1 > Sun StorEdge[TM] 3510/3511/3310/:sccli show-disks : disk has NONE USED status by RAID 5 < Document: 1007803.1 > Sun StorEdge[TM] 3510/3511/3310/:sccli show-disks : disk has NONE USED status by RAID 1 If we are at firmware 4.11I or below and if we upgrade to 4.13, the drives with the "NONE USED" status will be marked as "BAD" and an amber led will also be lit on the drive. This change was introduced with 4.13 in trying to fix the two known bugs under both SCSI and FC version of this product (see internal comments). This was to prevent the drives that are marked "NONE USED" to be part of the logical drive again thereby avoiding data integrity and other issues. To avoid this problem, BEFORE we do the upgrade to 4.13, we should ensure that no drives are in the "NONE USED state as below. * disks Ch Id Size Speed LD Status IDs ----------------------------------------------------------------------- 2 16 68.37GB 200MB ld0 ONLINE SEAGATE ST373307FSUN72G 0307 S/N 3HZ7CJB800007443 2 17 68.37GB 200MB NONE USED SEAGATE ST373307FSUN72G 0307 S/N 3HZ7CRRY00007443 2 18 68.37GB 200MB ld0 ONLINE FUJITSU MAP3735F SUN72G 1201 S/N 000409Q08LLB 2 19 68.37GB 200MB ld0 ONLINE FUJITSU MAP3735F SUN72G 1201 S/N 000408Q089W1 Also, if we don't take the above precaution and upgrade to 4.13 and find that the drives have been marked bad, we can do a "dummy-replace" on those drives ie, pull out the drive that is marked "NONE USED" and insert it back. If the state persists, try to clear the "reserved area" by doing the following:- 1. From array cli main menu, select "view and edit scsi Drives" 2. Select the disk showing the status of "NONE USED" or "BAD" 3. Select "disk Reserved space - 256 mb" 4. Select "yes" when prompted to "Remove Disk Reserved Space ?" Product Sun StorageTek 3511 SATA Array Sun StorageTek 3510 FC Array Sun StorageTek 3320 SCSI Array Sun StorageTek 3310 SCSI Array Internal Comments For internal Sun use only. With 4.11, the LD recovery procedure doesn't work if we need to recover the logical drive which has become missing and more than one disk have changed to the state of "NONE USED" A LD recovery procedure is now available with 4.13 firmware but when we upgrade to 4.13 under the above situation, the drives will change status to "BAD" and we may not be able to use this procedure unless we get them back to the "NONE USED" state . here are the two bug references Bug ID 4967518 Firmware doesn't track drive failure and the drive can scan back ok. Bug ID 4967520 Firmware doesn't track drive failure and the drive can scan back ok. 4.11, 3.27, 4.13, minnow, 3310, 3510, 3511, 3320, NONE USED, Drives, BAD Previously Published As 82997 Change History Date: 2005-10-26 User Name: 71396 Action: Approved Comment: Performed final review of article. No changes required. Publishing. Version: 3 Date: 2005-10-26 User Name: 71396 Action: Accept Comment: Version: 0 Attachments This solution has no attachment |
||||||||||||
|
||||||||||||