Here's another one: D1V85 ( http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=D1V85 ) shows as ReleaseID D1V8500.3D.67 instead of just D1V85. Also the filename begins with VRTX_xxxxxx, which is confusing since most recent PSU FW updates start with 'Power_Firmware_xxxx'. Also 'Supported Platforms' is empty. Shouldn't it list the T630, VRTX and other supported platforms? Which might also help get these updates listed in RepoManager (or even in Lifecycle Controller if the catalog.cab would get updated with these changes). Just assuming here though.
On Fri, Jun 16, 2017 at 9:17 AM, Rene Shuster <[email protected]> wrote: > 9CGV6 > > On Fri, Jun 16, 2017 at 9:02 AM, <[email protected]> wrote: > >> >> >> *Dell - Internal Use - Confidential * >> >> Hi Rene Shuster, >> >> Can I know the Dell ID for the last point (* The 11G SAS/SATA FlexBay >> Backplane Firmware Update v1.09 shows 'Supported Platforms' >> "PowerEdge T710", but when you execute it under Linux it will show that >> it's compatible with a T610 and apply the FW update successfully.) >> >> >> >> Regards >> >> Muneer >> >> >> >> *From:* Rene Shuster [mailto:[email protected]] >> *Sent:* Friday, June 16, 2017 2:19 AM >> *To:* K, Muneer <[email protected]> >> *Cc:* linux-poweredge-Lists <[email protected]>; Jana, >> Ananya <[email protected]> >> *Subject:* Re: [Linux-PowerEdge] SAS Drive Firmware annoyances. >> >> >> >> Here are 4 more that I stumbled over while maintaining our FW ISO: >> >> * The latest BIOS for the T630 (DELL ID GK2F7) shows under 'Supported >> Devices' "Server BIOS 12G". >> * All OSC 1.1 FW updates (Dell ID 776YN, 5D53Y, 5W2KP, PWMC8) shows under >> 'Supported Devices' "OS COLLECTOR 2.1" which is obviously contradicting. >> * Backplane 12G SEP (for 8 drives or less) v1.00 (DELL ID 681JN) fails >> Collecting Inventory >> * The 11G SAS/SATA FlexBay Backplane Firmware Update v1.09 shows >> 'Supported Platforms' "PowerEdge T710", but when you execute it under Linux >> it will show that it's compatible with a T610 and apply the FW update >> successfully. >> >> These are all Linux FW updates, I'm not sure if the windows releases are >> also affected. >> >> >> >> On Thu, Jun 15, 2017 at 3:39 PM, Rene Shuster <[email protected]> >> wrote: >> >> The BIOS/UEFI update for the 13th Gen server (Dell Release ID 6YDCM) >> shows 'Supported Platforms' "R730,R730xd,R630", but under 'Supported >> Devices' it shows "Server BIOS 12G" in RepoManager which is confusing. Is >> there a better place to report these issues with the FW DUPs than the Dell >> Linux list? It's a pain to open a ticket for this kind of things. Github >> would be perfect. >> >> >> >> On Thu, Jun 15, 2017 at 10:55 AM, Rene Shuster <[email protected]> >> wrote: >> >> Oh awesome!. Yes, definitely let us know. >> >> >> >> On Thu, Jun 15, 2017 at 8:24 AM, <[email protected]> wrote: >> >> *Dell - Internal Use - Confidential * >> >> Hi Mark, >> >> We got the root cause. We will let You know the Delivery Date once align >> with our Dependent Team. >> >> >> >> Regards >> >> Muneer >> >> >> >> >> >> >> >> *From:* linux-poweredge-bounces-Lists *On Behalf Of *mark >> *Sent:* Friday, April 7, 2017 10:59 PM >> *To:* linux-poweredge-Lists <[email protected]> >> *Subject:* [Linux-PowerEdge] SAS Drive Firmware annoyances. >> >> >> >> dsu fails on several SAS drive firmware updates saying it can't collect >> inventory. >> >> >> >> the fix, after a little debugging... >> >> download the SAS drive firmware bin manually (one way or another), run >> ./SAS-<whatever> --extract=/tmp/mypath >> >> cd /tmp/mypath >> >> mv libstorelibir.so libstorelibir.so.5 >> >> ./spssetup.sh >> >> done. >> >> could anyone comment if they are seeing this and if so what drives ? >> >> so far my list is >> SAS-Drive_Firmware_V38WK_LN_ES68 >> SAS-Drive_Firmware_68NGY_LN_LS0B >> >> there is another segate drive that also fails without some manual work on >> an admin's part , but I can't seem to find it in my notes right now. >> >> anyone else seeing this ? I've seen a few RPM updates to these packages >> but there is no change log on them from the packaging point of view and my >> issue wasn't fixed with it so I have no idea what the change in the >> packaging was that bumped the version number of the rpm packaging as the >> firmware rev was the same. >> >> -Mark >> >> >> >> _______________________________________________ >> Linux-PowerEdge mailing list >> [email protected] >> https://lists.us.dell.com/mailman/listinfo/linux-poweredge >> >> >> >> >> >> -- >> >> Tech III * AppControl * Endpoint Protection * Server Maintenance >> Buncombe County Schools Technology Department Network Group >> ComicSans Awareness Campaign <http://comicsanscriminal.com> >> >> >> >> >> >> -- >> >> Tech III * AppControl * Endpoint Protection * Server Maintenance >> Buncombe County Schools Technology Department Network Group >> ComicSans Awareness Campaign <http://comicsanscriminal.com> >> >> >> >> >> >> -- >> >> Tech III * AppControl * Endpoint Protection * Server Maintenance >> Buncombe County Schools Technology Department Network Group >> ComicSans Awareness Campaign <http://comicsanscriminal.com> >> > > > > -- > Tech III * AppControl * Endpoint Protection * Server Maintenance > Buncombe County Schools Technology Department Network Group > ComicSans Awareness Campaign <http://comicsanscriminal.com> > -- Tech III * AppControl * Endpoint Protection * Server Maintenance Buncombe County Schools Technology Department Network Group ComicSans Awareness Campaign <http://comicsanscriminal.com>
_______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
