Re: Hard Drive firmware update issue with DSU

> What really is the technical difference between a Dell-Seagate drive and a generic Seagate drive that have the same model number?
> what is the technical difference between the current firmware from Seagate and the firmware from Dell?

That would be for Dell to answer but I doubt you'll get a comprehensive one.

Stefan

> On Nov 18, 2015, at 5:58 PM, Jeff Boyce <[email protected]> wrote:
> 
> Stefan -
> 
> I had already checked the Seagate site you mention, that is how I knew the firmware version and dates I listed at item #3 in my note below.  So I am quickly concluding that there is not a process to update the firmware on a generic Seagate drive to the firmware version from Dell, as the Dell firmware upgrade process only works on Dell-Seagate drives.  Based on that I will just have to leave things as they are, with mixed firmware versions.
> 
> But I do have one last question, and then I will leave this topic alone.  I have to ask it, because I suspect others following this thread are now thinking the same thing.  What really is the technical difference between a Dell-Seagate drive and a generic Seagate drive that have the same model number?  And furthermore, what is the technical difference between the current firmware from Seagate and the firmware from Dell?  Is the Dell firmware just a repackaged Seagate firmware for deployment on a Dell-Seagate drive, but otherwise the firmware is technically the same?
> 
> Thanks for all your assistance.
> Jeff
> 
> 
> On 11/18/2015 3:58 AM, Stefan M. Radman wrote:
>> Hi Jeff,
>> 
>> You can try to enter the disk's serial number in the Seagate Download Finder to see if there is a firmware update available.
>> 
>> https://apps1.seagate.com/downloads/request.html
>> 
>> For serial numbers of Dell OEM drives this tools redirects to Dell support.
>> 
>> Regards
>> Stefan
>> 
>> On Nov 18, 2015, at 12:08 PM, [email protected]<mailto:[email protected]> wrote:
>> 
>> 
>> Dell - Internal Use - Confidential
>> Hi Jeff,
>> 
>> Thanks for providing the information. The firmware update for hard drives not purchased from Dell is not supported and will not work using the DSU.
>> 
>> Thanks
>> Santosh.
>> 
>> From: K, Muneer
>> Sent: Wednesday, November 18, 2015 4:23 PM
>> To: Jeff Boyce <[email protected]<mailto:[email protected]>>; linux-poweredge-Lists <[email protected]<mailto:[email protected]>>
>> Cc: Ponnandi, Soorej <[email protected]<mailto:[email protected]>>; Gore, Santosh <[email protected]<mailto:[email protected]>>
>> Subject: RE: [Linux-PowerEdge] Hard Drive firmware update issue with DSU
>> 
>> 
>> Dell - Internal Use - Confidential
>> Jeff Boyce,
>> Thanks for the information…
>> 
>> Santosh,
>> Is there anyway Jeff Boyce can update this Hard drive to ES68 version.
>> 
>> Regards
>> Muneer
>> 
>> From: Jeff Boyce [mailto:[email protected]]
>> Sent: Wednesday, November 18, 2015 12:45 AM
>> To: K, Muneer; linux-poweredge-Lists
>> Cc: Ponnandi, Soorej; Gore, Santosh
>> Subject: Re: [Linux-PowerEdge] Hard Drive firmware update issue with DSU
>> 
>> Muneer -
>> 
>>  1.  The drive with ComponentID=00000 was not purchased from Dell, but from a third party retailer.  This was because Dell only had refurbished drives available with a 1-year warranty, while the retailer had new drives available with a full 5-year manufacturer warranty.  The price was the same between the two options.
>> 
>> 2.  The new drive is the exact same make and model as the other drives (Seagate ST3300657SS).  Does the different ComponentID numbers actually make them different drives?
>> 
>> 3.  The Seagate support site identifies the current firmware for the drive as 000B, released on 8/13/2012.  The Dell support site identifies the current firmware for the drive as ES68, released on 6/10/2015.
>> 
>> 4.  I would like to have all drives using the same firmware since they are all the same make and model of drive.  Is that possible?  Is there a way to update this drive with the firmware (ES68) listed on the Dell support site?
>> 
>> Thanks.
>> Jeff
>> On 11/17/2015 5:36 AM, [email protected]<mailto:[email protected]> wrote:
>> 
>> Dell - Internal Use - Confidential
>> Hi Jeff,
>> The Component ID, which has 00000 is from Dell or from some other Vendor?. If it is from some other Vendor then DUP update will not work. Please let us know.
>> 
>> Thanks
>> Muneer
>> 
>> From: Gore, Santosh
>> Sent: Monday, November 16, 2015 10:27 PM
>> To: DUP_FW_IEIC_SCRUM
>> Cc: Ponnandi, Soorej
>> Subject: FW: [Linux-PowerEdge] Hard Drive firmware update issue with DSU
>> 
>> 
>> Dell - Internal Use - Confidential
>> Hi Team,
>> 
>> Please work with “Jeff” to root cause the issue reported with the HDD inventory.   The componentID is incorrect (00000) for one of the drive.
>> 
>> HDD inventory from the system:
>> <Device componentID="20796" enum="CtrlId 0 DeviceId 0" display="ST3300657SS">
>> <Application componentType="FRMW" version="ES68" display="Firmware for - Disk 0 in Backplane 0 of PERC H700 Integrated Controller 0 "/>
>> </Device>
>> <Device componentID="20796" enum="CtrlId 0 DeviceId 1" display="ST3300657SS">
>> <Application componentType="FRMW" version="ES68" display="Firmware for - Disk 1 in Backplane 0 of PERC H700 Integrated Controller 0 "/>
>> </Device>
>> <Device componentID="00000" enum="CtrlId 0 DeviceId 2" display="ST3300657SS">
>> <Application componentType="FRMW" version="000B" display="Firmware for - Disk 2 in Backplane 0 of PERC H700 Integrated Controller 0 "/>
>> </Device>
>> <Device componentID="20796" enum="CtrlId 0 DeviceId 3" display="ST3300657SS">
>> <Application componentType="FRMW" version="ES68" display="Firmware for - Disk 3 in Backplane 0 of PERC H700 Integrated Controller 0 "/>
>> 
>> 
>> Thanks
>> Santosh.
>> 
>> -----Original Message-----
>> From: linux-poweredge-bounces-Lists On Behalf Of Jeff Boyce
>> Sent: Friday, November 13, 2015 10:05 PM
>> To: Ponnandi, Soorej ; linux-poweredge-Lists
>> Subject: Re: [Linux-PowerEdge] Hard Drive firmware update issue with DSU
>> 
>> Soorej -
>> 
>> I have run the inventory report as you requested, and have attached it to this email. I assume it may get stripped off going to the mailing list so I cc'd you directly also. I glanced at the xml file and the only thing that looks like it might be significant is that the replaced disk has a componentID=00000, whereas all the other disks show a componentID=20796. Not sure why, since they are all clearly the same model drives. I hope this help you understand the issue and we can work to resolve it. Thanks.
>> 
>> Jeff
>> 
>> 
>> On 11/12/2015 8:31 PM, [email protected]<mailto:[email protected]> wrote:
>>> Dell - Internal Use - Confidential
>>> Hi Jeff,
>>> 
>>> This could be due to the latest update list (Catalog) not having any updates for Disk 2 componentID. We need the inventory report of the platform for root causing this issue.
>>> 
>>> Please execute the following commands as root user to get inv report.
>>> 
>>> # yum install invcol_V8336_LN64_15.06.00_A00.x86_64
>>> # sh /usr/libexec/dell_dup/invcol_V8336_LN64_15.06.00_A00
>>> -outc=/tmp/inv.xml
>>> 
>>> Send us the inv.xml file from /tmp directory to understand the issue better.
>>> 
>>> Thanks,
>>> Soorej
>>> 
>>> 
>>> 
>>> 
>>> -----Original Message-----
>>> From: linux-poweredge-bounces-Lists On Behalf Of Jeff Boyce
>>> Sent: Wednesday, November 11, 2015 12:16 AM
>>> To: linux-poweredge-Lists
>>> Subject: [Linux-PowerEdge] Hard Drive firmware update issue with DSU
>>> 
>>> Greetings -
>>> 
>>> Well it looks like a recent drive replacement has created a domino effect for me with a firmware update and now an OMSA installation issue. I will hold the OMSA issue for another email, as I am still have a little research to try to identify and resolve the issue.
>>> 
>>> The basics of the firmware update issue that I have is that the DSU inventory identifies that I have drives (same manufacturer and model) showing different firmware, but that running the update does not update the firmware on the drive that is not shown as the current version.
>>> Details of the dsu output are below. My system is a PE T610 and I have
>>> 4 drives installed configured in a RAID 5 (3 active drives and 1 hot
>>> spare) on a PERC H700 Controller. The model of the drive replaced (all drives are the same model) is a Seagate SAS 300GB, ST3300657SS. The Seagate support site identifies the current firmware for the drive as 000B, released on 8/13/2012. The Dell support site identifies the current firmware for the drive as ES68, released on 6/10/2015. The new drive I installed shows a firmware version of 000B, while the firmware of the three original drives is shown as ES68. This is shown in the dsu --inventory results below (all other firmware on the box is up-to-date and is not shown). However when the dsu update is run it only identifies the first drive in the backplane (which has current firmware) and does not make any reference to the other three drives, and in particular the drive that has firmware 000B. So my question becomes, how do I updated the firmware in one specific drive? Is this a bug in the implementation of the dsu utility?
>>> 
>>> Please cc any responses directly to me, as I only receive the daily digest of this mailing list. Thanks.
>>> 
>>> [root@earth ~]# dsu --inventory
>>> Getting System Inventory...
>>> 
>>> 8. Firmware for - Disk 0 in Backplane 0 of PERC H700 Integrated
>>> Controller 0 ( Version : ES68 ) 9. Firmware for - Disk 2 in Backplane
>>> 0 of PERC H700 Integrated Controller 0 ( Version : 000B )
>>> 
>>> [root@earth ~]# dsu
>>> Getting System Inventory...
>>> Determining Applicable Updates...
>>> 
>>> |-----------Dell System Updates-----------|
>>> [ ] represents 'not selected'
>>> [*] represents 'selected'
>>> [-] represents 'Component already at repository version (cannot be selected)'
>>> Choose: q - Quit without update, c to Commit, - To Select/Deselect, a
>>> - Select All, n - Select None
>>> 
>>> [-]6 Firmware for - Disk 0 in Backplane 0 of PERC H700 Integrated
>>> Controller 0 Current Version : ES68 same as : ES68
>>> 
>>> Enter your choice : q
>>> [root@earth ~]#
>>> 
>>> 
>>> --
>>> 
>>> Jeff Boyce
>>> Meridian Environmental
>>> www.meridianenv.com<http://www.meridianenv.com/>
>>> 
>>> _______________________________________________
>>> Linux-PowerEdge mailing list
>>> [email protected]<mailto:[email protected]>
>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>> --
>> 
>> Jeff Boyce
>> Meridian Environmental
>> www.meridianenv.com<http://www.meridianenv.com/>
>> 
>> 
>> --
>> 
>> 
>> 
>> Jeff Boyce
>> 
>> Meridian Environmental
>> 
>> Meridianenv.com<http://meridianenv.com>
>> 
>> _______________________________________________
>> Linux-PowerEdge mailing list
>> [email protected]<mailto:[email protected]>
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>> 
> 
> -- 
> 
> Jeff Boyce
> Meridian Environmental
> www.meridianenv.com
> 
> 

_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge