The firmware that is supposed to fix the boot-of-death problem on Seagate 7200.11 disks is “In Validation”.
The software and information in this article could be data destructive and/or render your hard drive inoperable if not followed carefully. It is always recommended to keep a backup of critical data.
This article applies to the following models:
Recommended Firmware Update Status
Seagate Barracuda 7200.11
SCSI Enclosure Services, referred as SES or SES-2, depending on the revision level, is a command set that is used to manage and sense the state of the power supplies, cooling devices, displays, indicators, individual drives, and other non-SCSI elements installed in a fibre channel or SAS (host-attached) enclosure. Intelligent enclosures that connect to the host via a SCSI cable will normally speak the SAF-TE protocol.
The command set is defined as an ANSI specification, and utilizes the SCSI commands to obtain configuration information for the enclosure as well as reprogram it to light external indicator LEDs or audible alarms to inform the user about the health and maintenance information for attached RAID controllers and disk drives.
Disk (tape, autochanger, whatever) firmware is intellectual property, and is owned by the manufacturer and/or a particular OEM that purchases the peripheral from the manufacturer.
In general, don’t bother calling Seagate, WD, or any of the other drive vendors and ask them for the firmware update. Unless somebody posts otherwise, it is almost onheard of that they will just send it to you. You typically need to get that from the company that sold you the hardware.
Helpful places to look Read more…
With few exceptions, disk drives are set to 512 bytes per block, and operating systems expect disks to be formatted to 512 bytes per block. In fact, some operating systems and/or disk controllers won’t even “see” disks that aren’t formatted to 512 bytes/block. Certain RAID controllers require disks to be formatted to 520 or 528 bytes/block. EMC, and NetApp are two vendors that format their disks to use these extra bytes. (In case you were wondering, they do this in order to increase data integrity, as the extra bytes are used for ECC.
I have gotten a great deal of calls from people who bought used EMC or NetApp gear Read more…
Disk devices that speak the SCSI protocol (SCSI, SAS, Fibre channel, and even USB memory sticks) have a built-in command designed to specify the drive capacity. The block size and count is defined as mode page settings, so any software product that incorporates a mode page editor has the mechanism to allow you to change the capacity (or block size) of a device.
Why you might want to do this …
- You have some older equipment running an operating system such as VMS, or certain RAID controllers that have an upper limit on the maximum disk size which they support.
- You want to be really sneaky and hide information on a disk drive. (Once you resize the disk, the “hidden” area is hidden from everything, including low-level formats, partition managers, and anti virus software).
- You are trying to mirror disk drives, and while they are both advertised to be 146GB large, they have a slightly different number of total blocks. As such, some RAID software won’t let you mirror the two drives.
Security warning — If you do not want to risk data theft, you should always insure that the disks in your storage farm report 100% of their actual capacity before running software to view the contents, or run a secure erase.