-----Original Message-----
From: Linux-PowerEdge <[email protected]> On Behalf Of Klaas
Demter
Sent: Wednesday, November 4, 2020 8:36 PM
To: [email protected]
Subject: Re: [Linux-PowerEdge] iDRAC update failure
[EXTERNAL EMAIL]
we miss the SMINST device, but I don't seem to have encountered that with any
updates since I've been using a dell server. I'll write a note to add it if I
need to touch the multipath file again.
For your more general problem: I once wrote a feature request for dsu to enable
it to work with an enabled multipathd, that would (at least from my point of
view) be the general solution to this problem :)
Greetings
Klaas
On 11/4/20 3:30 PM, Ben Argyle wrote:
> Yes, it turns out this was the one server I'd missed! (-:
>
> So, sort of 50% my fault!
>
> Anyway, here seems to be the definitive list at this point (note that there's
> one more than you have in
> https://github.com/Klaas-/ansible-role-dell-firmware-upgrade/blob/a6a6d1a3c8c18773a5ce3d89f9e68b1693a7d5bd/files/multipath_dell.conf):
>
> device {
> vendor "Linux"
> product "scrtch"
> }
> device {
> vendor "iDRAC"
> product "scrtch"
> }
> device {
> vendor "DELL"
> product "IDSDM"
> }
> device {
> vendor "iDRAC"
> product "MAS022"
> }
> device {
> vendor "iDRAC"
> product "SECUPD"
> }
> device {
> vendor "iDRAC"
> product "SMINST"
> }
> device {
> vendor "Linux"
> product "SECUPD"
> }
>
> Best,
>
> Ben
>
> -----Original Message-----
> From: Linux-PowerEdge <[email protected]> On Behalf Of
> Klaas Demter
> Sent: 04 November 2020 14:16
> To: [email protected]
> Subject: Re: [Linux-PowerEdge] iDRAC update failure
>
>
> [EXTERNAL EMAIL]
>
> Didn't you already notice that 3 months ago? I seem to recall I added
> it to the ansible role because of you :)
>
> https://github.com/CSCfi/ansible-role-dell-firmware-upgrade/pull/31
>
>
>
> Greetings
>
> Klaas
>
>
> On 11/4/20 2:44 PM, Ben Argyle wrote:
>> [EXTERNAL EMAIL]
>>
>> I have this in multipath.conf to ensure the new vendor/product USB device(s)
>> you keep adding aren't caught by multipathd:
>>
>> blacklist {
>> wwid <WWID of internal disk>
>> devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
>> devnode "^hd[a-z]"
>> devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
>> devnode "^asm/*"
>> devnode "ofsctl"
>>
>> device {
>> vendor "iDRAC"
>> product "scrtch"
>> }
>> device {
>> vendor "DELL"
>> product "IDSDM"
>> }
>> device {
>> vendor "iDRAC"
>> product "MAS022"
>> }
>> device {
>> vendor "iDRAC"
>> product "SECUPD"
>> }
>> device {
>> vendor "Linux"
>> product "SECUPD"
>> }
>> }
>>
>> Here's /var/log/messages for an attempt to upgrade the iDRAC from running
>> 'dsu' onwards:
>>
>> Nov 4 13:22:37 server1 yum[228855]: Erased:
>> dsucatalog-20.10.01-3DT6M.noarch Nov 4 13:22:43 server1 yum[228881]:
>> Installed: dsucatalog-20.10.01-3DT6M.noarch Nov 4 13:23:15 server1
>> kernel: usb 1-14.1.2: new high-speed USB device number 32 using
>> xhci_hcd Nov 4 13:23:15 server1 kernel: usb 1-14.1.2: New USB device
>> found, idVendor=0624, idProduct=0250, bcdDevice= 0.00 Nov 4 13:23:15
>> server1 kernel: usb 1-14.1.2: New USB device strings: Mfr=4,
>> Product=5, SerialNumber=6 Nov 4 13:23:15 server1 kernel: usb
>> 1-14.1.2: Product: Mass Storage Function Nov 4 13:23:15 server1
>> kernel: usb 1-14.1.2: Manufacturer: Avocent Nov 4 13:23:15 server1 kernel:
>> usb 1-14.1.2: SerialNumber: 20180726-0 Nov 4 13:23:15 server1 kernel:
>> usb-storage 1-14.1.2:1.0: USB Mass Storage device detected Nov 4 13:23:15
>> server1 kernel: scsi host34: usb-storage 1-14.1.2:1.0
>> Nov 4 13:23:16 server1 kernel: scsi 34:0:0:0: Direct-Access Linux
>> SECUPD 0399 PQ: 0 ANSI: 0 CCS
>> Nov 4 13:23:16 server1 kernel: sd 34:0:0:0: Attached scsi generic
>> sg27 type 0 Nov 4 13:23:16 server1 kernel: sd 34:0:0:0: Power-on or
>> device reset occurred Nov 4 13:23:16 server1 kernel: sd 34:0:0:0:
>> [sdab] 2112 512-byte logical blocks: (1.08 MB/1.03 MiB) Nov 4
>> 13:23:16 server1 kernel: sd 34:0:0:0: [sdab] Write Protect is off Nov
>> 4 13:23:17 server1 kernel: sd 34:0:0:0: [sdab] No Caching mode page
>> found Nov 4 13:23:17 server1 kernel: sd 34:0:0:0: [sdab] Assuming drive
>> cache: write through Nov 4 13:23:17 server1 kernel: sdab:
>> Nov 4 13:23:17 server1 kernel: sd 34:0:0:0: [sdab] Attached SCSI
>> removable disk Nov 4 13:23:17 server1 multipathd: sdab: add path
>> (uevent) Nov 4 13:23:32 server1 kernel: usb 1-14.1.2: USB
>> disconnect, device number 32 Nov 4 13:23:32 server1 multipathd:
>> sdab: remove path (uevent) Nov 4 13:23:32 server1 multipathd: sdab:
>> path already removed Nov 4 13:23:36 server1 kernel: usb 1-14.1.2:
>> new high-speed USB device number 33 using xhci_hcd Nov 4 13:23:36
>> server1 kernel: usb 1-14.1.2: New USB device found, idVendor=0624,
>> idProduct=0250, bcdDevice= 0.00 Nov 4 13:23:36 server1 kernel: usb
>> 1-14.1.2: New USB device strings: Mfr=4, Product=5, SerialNumber=6
>> Nov 4 13:23:36 server1 kernel: usb 1-14.1.2: Product: Mass Storage
>> Function Nov 4 13:23:36 server1 kernel: usb 1-14.1.2: Manufacturer:
>> Avocent Nov 4 13:23:36 server1 kernel: usb 1-14.1.2: SerialNumber:
>> 20180726-0 Nov 4 13:23:36 server1 kernel: usb-storage 1-14.1.2:1.0: USB
>> Mass Storage device detected Nov 4 13:23:36 server1 kernel: scsi host35:
>> usb-storage 1-14.1.2:1.0
>> Nov 4 13:23:37 server1 kernel: scsi 35:0:0:0: Direct-Access Linux
>> SECUPD 0399 PQ: 0 ANSI: 0 CCS
>> Nov 4 13:23:37 server1 kernel: sd 35:0:0:0: Attached scsi generic
>> sg27 type 0 Nov 4 13:23:37 server1 kernel: sd 35:0:0:0: Power-on or
>> device reset occurred Nov 4 13:23:37 server1 kernel: sd 35:0:0:0:
>> [sdab] 2112 512-byte logical blocks: (1.08 MB/1.03 MiB) Nov 4
>> 13:23:37 server1 kernel: sd 35:0:0:0: [sdab] Write Protect is off Nov
>> 4 13:23:37 server1 kernel: sd 35:0:0:0: [sdab] No Caching mode page
>> found Nov 4 13:23:37 server1 kernel: sd 35:0:0:0: [sdab] Assuming drive
>> cache: write through Nov 4 13:23:38 server1 kernel: sdab:
>> Nov 4 13:23:38 server1 kernel: sd 35:0:0:0: [sdab] Attached SCSI
>> removable disk Nov 4 13:23:38 server1 multipathd: sdab: add path
>> (uevent) Nov 4 13:23:52 server1 kernel: usb 1-14.1.2: USB
>> disconnect, device number 33 Nov 4 13:23:52 server1 multipathd:
>> sdab: remove path (uevent) Nov 4 13:23:52 server1 multipathd: sdab:
>> path already removed Nov 4 13:24:32 server1 yum[249182]: Erased:
>> iDRAC-with-Lifecycle-Controller_Firmware_FP2XW_LN_4.22.00.53_A00-4.22
>> .00.53-20.10.01.noarch Nov 4 13:24:59 server1 yum[249651]:
>> Installed:
>> iDRAC-with-Lifecycle-Controller_Firmware_FP2XW_LN_4.22.00.53_A00-4.22
>> .00.53-20.10.01.noarch Nov 4 13:25:26 server1 kernel: usb 1-14.1.2:
>> new high-speed USB device number 34 using xhci_hcd Nov 4 13:25:26
>> server1 kernel: usb 1-14.1.2: New USB device found, idVendor=0624,
>> idProduct=0250, bcdDevice= 0.00 Nov 4 13:25:26 server1 kernel: usb
>> 1-14.1.2: New USB device strings: Mfr=4, Product=5, SerialNumber=6
>> Nov 4 13:25:26 server1 kernel: usb 1-14.1.2: Product: Mass Storage
>> Function Nov 4 13:25:26 server1 kernel: usb 1-14.1.2: Manufacturer:
>> Avocent Nov 4 13:25:26 server1 kernel: usb 1-14.1.2: SerialNumber:
>> 20180726-0 Nov 4 13:25:26 server1 kernel: usb-storage 1-14.1.2:1.0: USB
>> Mass Storage device detected Nov 4 13:25:26 server1 kernel: scsi host36:
>> usb-storage 1-14.1.2:1.0
>> Nov 4 13:25:27 server1 kernel: scsi 36:0:0:0: Direct-Access Linux
>> scrtch 0399 PQ: 0 ANSI: 0 CCS
>> Nov 4 13:25:27 server1 kernel: sd 36:0:0:0: Attached scsi generic
>> sg27 type 0 Nov 4 13:25:27 server1 kernel: sd 36:0:0:0: Power-on or
>> device reset occurred Nov 4 13:25:27 server1 kernel: sd 36:0:0:0:
>> [sdab] 630784 512-byte logical blocks: (322 MB/308 MiB) Nov 4
>> 13:25:27 server1 kernel: sd 36:0:0:0: [sdab] Write Protect is off Nov
>> 4 13:25:27 server1 kernel: sd 36:0:0:0: [sdab] No Caching mode page
>> found Nov 4 13:25:27 server1 kernel: sd 36:0:0:0: [sdab] Assuming drive
>> cache: write through Nov 4 13:25:28 server1 kernel: sdab:
>> Nov 4 13:25:28 server1 kernel: sd 36:0:0:0: [sdab] Attached SCSI
>> removable disk Nov 4 13:25:28 server1 multipathd: sdab: add path
>> (uevent) Nov 4 13:25:28 server1 multipathd: mpathek: load table [0
>> 630784 multipath 1 queue_if_no_path 0 1 1 service-time 0 1 1 65:176
>> 1] Nov 4 13:25:28 server1 multipathd: mpathek: event checker started
>> Nov 4 13:25:28 server1 multipathd: sdab [65:176]: path added to
>> devmap mpathek Nov 4 13:26:30 server1 kernel: usb 1-14.1.2: USB
>> disconnect, device number 34 Nov 4 13:26:30 server1 multipathd:
>> sdab: remove path (uevent) Nov 4 13:26:30 server1 multipathd:
>> mpathek: devmap removed Nov 4 13:26:30 server1 multipathd: mpathek:
>> stop event checker thread (140177298130688) Nov 4 13:26:30 server1
>> multipathd: mpathek: removed map after removing all paths Nov 4
>> 13:26:30 server1 multipathd: dm-28: remove map (uevent) Nov 4
>> 13:26:30 server1 multipathd: dm-28: devmap not registered, can't
>> remove Nov 4 13:26:30 server1 multipathd: dm-28: remove map (uevent)
>> Nov 4 13:26:36 server1 kernel: usb 1-14.1.2: new high-speed USB
>> device number 35 using xhci_hcd Nov 4 13:26:37 server1 kernel: usb
>> 1-14.1.2: New USB device found, idVendor=0624, idProduct=0250,
>> bcdDevice= 0.00 Nov 4 13:26:37 server1 kernel: usb 1-14.1.2: New USB
>> device strings: Mfr=4, Product=5, SerialNumber=6 Nov 4 13:26:37
>> server1 kernel: usb 1-14.1.2: Product: Mass Storage Function Nov 4 13:26:37
>> server1 kernel: usb 1-14.1.2: Manufacturer: Avocent Nov 4 13:26:37 server1
>> kernel: usb 1-14.1.2: SerialNumber: 20180726-0 Nov 4 13:26:37 server1
>> kernel: usb-storage 1-14.1.2:1.0: USB Mass Storage device detected Nov 4
>> 13:26:37 server1 kernel: scsi host37: usb-storage 1-14.1.2:1.0
>> Nov 4 13:26:38 server1 kernel: scsi 37:0:0:0: Direct-Access Linux
>> scrtch 0399 PQ: 0 ANSI: 0 CCS
>> Nov 4 13:26:38 server1 kernel: sd 37:0:0:0: Attached scsi generic
>> sg27 type 0 Nov 4 13:26:38 server1 kernel: sd 37:0:0:0: Power-on or
>> device reset occurred Nov 4 13:26:38 server1 kernel: sd 37:0:0:0:
>> [sdab] 630784 512-byte logical blocks: (322 MB/308 MiB) Nov 4
>> 13:26:38 server1 kernel: sd 37:0:0:0: [sdab] Write Protect is off Nov
>> 4 13:26:38 server1 kernel: sd 37:0:0:0: [sdab] No Caching mode page
>> found Nov 4 13:26:38 server1 kernel: sd 37:0:0:0: [sdab] Assuming drive
>> cache: write through Nov 4 13:26:38 server1 kernel: sdab:
>> Nov 4 13:26:38 server1 kernel: sd 37:0:0:0: [sdab] Attached SCSI
>> removable disk Nov 4 13:26:38 server1 multipathd: sdab: add path
>> (uevent) Nov 4 13:26:39 server1 multipathd: mpathek: load table [0
>> 630784 multipath 1 queue_if_no_path 0 1 1 service-time 0 1 1 65:176
>> 1] Nov 4 13:26:39 server1 multipathd: mpathek: event checker started
>> Nov 4 13:26:39 server1 multipathd: sdab [65:176]: path added to
>> devmap mpathek Nov 4 13:27:40 server1 kernel: usb 1-14.1.2: USB
>> disconnect, device number 35 Nov 4 13:27:40 server1 multipathd:
>> sdab: remove path (uevent) Nov 4 13:27:40 server1 multipathd:
>> mpathek: devmap removed Nov 4 13:27:40 server1 multipathd: mpathek:
>> stop event checker thread (140177298130688) Nov 4 13:27:40 server1
>> multipathd: mpathek: removed map after removing all paths Nov 4
>> 13:27:40 server1 multipathd: dm-28: remove map (uevent) Nov 4
>> 13:27:40 server1 multipathd: dm-28: devmap not registered, can't
>> remove Nov 4 13:27:40 server1 multipathd: dm-28: remove map (uevent)
>> Nov 4 13:27:47 server1 kernel: usb 1-14.1.2: new high-speed USB
>> device number 36 using xhci_hcd Nov 4 13:27:47 server1 kernel: usb
>> 1-14.1.2: New USB device found, idVendor=0624, idProduct=0250,
>> bcdDevice= 0.00 Nov 4 13:27:47 server1 kernel: usb 1-14.1.2: New USB
>> device strings: Mfr=4, Product=5, SerialNumber=6 Nov 4 13:27:47
>> server1 kernel: usb 1-14.1.2: Product: Mass Storage Function Nov 4 13:27:47
>> server1 kernel: usb 1-14.1.2: Manufacturer: Avocent Nov 4 13:27:47 server1
>> kernel: usb 1-14.1.2: SerialNumber: 20180726-0 Nov 4 13:27:47 server1
>> kernel: usb-storage 1-14.1.2:1.0: USB Mass Storage device detected Nov 4
>> 13:27:47 server1 kernel: scsi host38: usb-storage 1-14.1.2:1.0
>> Nov 4 13:27:48 server1 kernel: scsi 38:0:0:0: Direct-Access Linux
>> scrtch 0399 PQ: 0 ANSI: 0 CCS
>> Nov 4 13:27:48 server1 kernel: sd 38:0:0:0: Attached scsi generic
>> sg27 type 0 Nov 4 13:27:48 server1 kernel: sd 38:0:0:0: Power-on or
>> device reset occurred Nov 4 13:27:48 server1 kernel: sd 38:0:0:0:
>> [sdab] 630784 512-byte logical blocks: (322 MB/308 MiB) Nov 4
>> 13:27:48 server1 kernel: sd 38:0:0:0: [sdab] Write Protect is off Nov
>> 4 13:27:48 server1 kernel: sd 38:0:0:0: [sdab] No Caching mode page
>> found Nov 4 13:27:48 server1 kernel: sd 38:0:0:0: [sdab] Assuming drive
>> cache: write through Nov 4 13:27:48 server1 kernel: sdab:
>> Nov 4 13:27:48 server1 kernel: sd 38:0:0:0: [sdab] Attached SCSI
>> removable disk Nov 4 13:27:49 server1 multipathd: sdab: add path
>> (uevent) Nov 4 13:27:49 server1 multipathd: mpathek: load table [0
>> 630784 multipath 1 queue_if_no_path 0 1 1 service-time 0 1 1 65:176
>> 1] Nov 4 13:27:49 server1 multipathd: mpathek: event checker started
>> Nov 4 13:27:49 server1 multipathd: sdab [65:176]: path added to
>> devmap mpathek Nov 4 13:28:51 server1 kernel: usb 1-14.1.2: USB
>> disconnect, device number 36 Nov 4 13:28:51 server1 multipathd:
>> sdab: remove path (uevent) Nov 4 13:28:51 server1 multipathd:
>> mpathek: devmap removed Nov 4 13:28:51 server1 multipathd: mpathek:
>> stop event checker thread (140177298130688) Nov 4 13:28:51 server1
>> multipathd: mpathek: removed map after removing all paths Nov 4
>> 13:28:51 server1 multipathd: dm-28: remove map (uevent) Nov 4
>> 13:28:51 server1 multipathd: dm-28: devmap not registered, can't
>> remove Nov 4 13:28:51 server1 multipathd: dm-28: remove map (uevent)
>> Nov 4 13:28:54 server1 spsetup.sh: Package Release ID=FP2XWA00
>> Package Description=iDRAC with Lifecycle Controller 4.22.00.53, A00
>> Exit code = 0 (Success) Nov 4 13:28:54 server1 root: Update Package:
>> iDRAC with Lifecycle Controller Firmware: Exit code = 0 (Success)
>> Support Log
>> path=/var/log/dell/updatepackage/log/support/iDRAC-with-Lifecycle-Con
>> troller_Firmware_FP2XW_LN_4.22.00.53_A00.log
>>
>> This was a failed attempt.
>>
>> So it looks like you've added ANOTHER vendor/product variant of
>> "Linux/scrtch" to an ever-increasing list. Why do you keep doing this?
>> I've added the below stanza to my /etc/multipath.conf blacklist section:
>>
>> device {
>> vendor "Linux"
>> product "scrtch"
>> }
>>
>> and on re-running 'dsu' the iDRAC update has succeeded.
>>
>> PLEASE, Dell, stick to one set of vendor/product strings! I'd appreciate
>> having a reply that says more than "glad it's working" to explain
>> Engineering's thinking behind changing the vendor/product string, again.
>>
>> Ben
>>
>> -----Original Message-----
>> From: Gore, Santosh <[email protected]>
>> Sent: 04 November 2020 04:46
>> To: Ben Argyle <[email protected]>; [email protected]
>> Subject: RE: [Linux-PowerEdge] iDRAC update failure
>>
>> Hi
>>
>> As part of iDRAC update, the USB drive is exposed from iDRAC to host
>> OS to transfer payload. Please make sure the USB device is not
>> blacklisted on your system and could you please share the OS logs (
>> /var/log/messages) after iDRAC update
>>
>> Thanks
>> Santosh
>>
>> -----Original Message-----
>> From: Linux-PowerEdge <[email protected]> On Behalf Of
>> Ben Argyle
>> Sent: Tuesday, November 3, 2020 9:53 PM
>> To: [email protected]
>> Subject: Re: [Linux-PowerEdge] iDRAC update failure
>>
>>
>> [EXTERNAL EMAIL]
>>
>> Yes. I did a soft reset from the iDRAC web GUI
>> (Maintenance->Diagnostics->Reset iDRAC). I don't want to do a
>> hard/configuration reset and lose IP details, etc. Still no effect:
>>
>> =================> Update Package application started <=============
>>
>> Command:
>> /var/log/dell/updatepackage/log/support/iDRAC-with-Lifecycle-Controll
>> er_Firmware_FP2XW_LN_4.22.00.53_A00.BIN
>> -f -q
>>
>> Date: Tue 3 Nov 16:14:58 GMT 2020
>>
>> =====================================================================
>> ====
>>
>> Release ID: FP2XWA00
>>
>> Update Package version: 20.06.200 (BLD_888)
>>
>> Collecting inventory...
>> <?xml version="1.0"?>
>> <SVMInventory lang="en">
>> <Device componentID="25227" display=" iDRAC">
>> <Application componentType="FRMW" version="4.00.00.00" display="
>> iDRAC"/>
>> </Device>
>> <System systemID="716"/>
>> <OperatingSystem osVendor="Red Hat" osArch="x64" majorVersion="7.0"
>> minorVersion="9" spMajorVersion="0" spMinorVersion="0"/>
>> <Device componentID="159" display="BIOS" impactsTPMmeasurements="TRUE">
>> <Display>BIOS</Display>
>> <Application componentType="BIOS" version="2.8.2" display="BIOS"/>
>> </Device>
>> </SVMInventory>
>> Creating payload file list for UpdRollBack by framework, if needed later.
>> MovePayload: Entry
>> MovePayload: Processing payload directory.
>> MovePayload: Moving firmimgFIT.d9
>> MovePayload: Exiting.
>> Running validation...
>>
>> iDRAC
>> Application: iDRAC
>> Previous version: 4.00.00.00
>> New version: 4.22.00.53
>>
>> The version of this Update Package is newer than the currently installed
>> version.
>> Software application name: iDRAC
>> Package version: 4.22.00.53
>> Installed version: 4.00.00.00
>>
>>
>> Executing update...
>> WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER PRODUCTS WHILE UPDATE IS
>> IN PROGRESS.
>> THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE!
>> Atleast one device updated: Check return 255
>> Device: iDRAC
>> Application: iDRAC
>> Failed to reach virtual device. This could be caused by BitLocker or
>> other security software being enabled. For more information, see the Update
>> Package User's Guide.
>>
>> ============================> Update Result
>> <============================
>>
>> Update complete
>> Application: iDRAC
>> Previous version: 4.00.00.00
>> New version: 4.22.00.53
>> =====================================================================
>> ====
>> Exit code = 0 (Success)
>> Tue 3 Nov 16:18:36 GMT 2020
>>
>>
>> Ben
>>
>> -----Original Message-----
>> From: Linux-PowerEdge <[email protected]> On Behalf Of
>> Patrick Boutilier
>> Sent: 03 November 2020 13:57
>> To: [email protected]
>> Subject: Re: [Linux-PowerEdge] iDRAC update failure
>>
>>
>> [EXTERNAL EMAIL]
>>
>> Have you tried resetting the iDRAC?
>>
>> https://www.dell.com/support/article/en-ca/sln305793/how-to-reset-the
>> -internal-dell-remote-access-controller-idrac-on-a-poweredge-server?l
>> ang=en
>>
>>
>>
>> On 11/3/20 3:50 AM, Ben Argyle wrote:
>>> [EXTERNAL EMAIL]
>>>
>>> Hi All,
>>>
>>> I'm seeing the below in
>>> /var/log/dell/updatepackage/log/support/iDRAC-with-Lifecycle-Controller_Firmware_FP2XW_LN_4.22.00.53_A00.log
>>> when attempting to upgrade the IDRAC from 4.00.00.00 to 4.22.00.53 with
>>> 'dsu'. I thought it was due to having too low a version of the BIOS
>>> (2.4.8), so successfully upgraded that to 2.8.2 and tried again. There was
>>> no change to the logged output other than it registering the newer BIOS
>>> version. I'm _not_ running BitLocker, or anything other than fairly
>>> standard software outside of the OS-supplied (which I hadn't started up
>>> anyway).
>>>
>>> Every other server of this type (R640) has been fine. Thoughts?
>>>
>>> Ben
>>>
>>> =================> Update Package application started <=============
>>>
>>> Command:
>>> /scripts/iDRAC-with-Lifecycle-Controller_Firmware_FP2XW_LN_4.22.00.53_A00.BIN
>>> -f -q
>>>
>>> Date: Tue 3 Nov 07:38:04 GMT 2020
>>>
>>> ====================================================================
>>> ==
>>> ===
>>>
>>> Release ID: FP2XWA00
>>>
>>> Update Package version: 20.06.200 (BLD_888)
>>>
>>> Collecting inventory...
>>> <?xml version="1.0"?>
>>> <SVMInventory lang="en">
>>> <Device componentID="25227" display=" iDRAC">
>>> <Application componentType="FRMW" version="4.00.00.00" display="
>>> iDRAC"/>
>>> </Device>
>>> <System systemID="716"/>
>>> <OperatingSystem osVendor="Red Hat" osArch="x64" majorVersion="7.0"
>>> minorVersion="9" spMajorVersion="0" spMinorVersion="0"/>
>>> <Device componentID="159" display="BIOS" impactsTPMmeasurements="TRUE">
>>> <Display>BIOS</Display>
>>> <Application componentType="BIOS" version="2.8.2" display="BIOS"/>
>>> </Device>
>>> </SVMInventory>
>>> Creating payload file list for UpdRollBack by framework, if needed later.
>>> MovePayload: Entry
>>> MovePayload: Processing payload directory.
>>> MovePayload: Moving firmimgFIT.d9
>>> MovePayload: Exiting.
>>> Running validation...
>>>
>>> iDRAC
>>> Application: iDRAC
>>> Previous version: 4.00.00.00
>>> New version: 4.22.00.53
>>>
>>> The version of this Update Package is newer than the currently installed
>>> version.
>>> Software application name: iDRAC
>>> Package version: 4.22.00.53
>>> Installed version: 4.00.00.00
>>>
>>>
>>> Executing update...
>>> WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER PRODUCTS WHILE
>>> UPDATE IS IN PROGRESS.
>>> THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE!
>>> Atleast one device updated: Check return 255
>>> Device: iDRAC
>>> Application: iDRAC
>>> Failed to reach virtual device. This could be caused by BitLocker or
>>> other security software being enabled. For more information, see the Update
>>> Package User's Guide.
>>>
>>> ============================> Update Result
>>> <============================
>>>
>>> Update complete
>>> Application: iDRAC
>>> Previous version: 4.00.00.00
>>> New version: 4.22.00.53
>>> ====================================================================
>>> ==
>>> ===
>>> Exit code = 0 (Success)
>>> Tue 3 Nov 07:41:43 GMT 2020
>>>
>>> _______________________________________________
>>> Linux-PowerEdge mailing list
>>> [email protected]
>>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>>
>> _______________________________________________
>> Linux-PowerEdge mailing list
>> [email protected]
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>> _______________________________________________
>> Linux-PowerEdge mailing list
>> [email protected]
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>
>> _______________________________________________
>> Linux-PowerEdge mailing list
>> [email protected]
>> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> _______________________________________________
> Linux-PowerEdge mailing list
> [email protected]
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
