After experiencing this problem on another Dell system with a different Seagate update it appears to be related to systems with Exchange installed on SBS (Small Business Server) systems.
Taking your I/O comments on board I shut down all services (including Exchange and SQL) and verified from performance monitors that the disks were idle. However the update still failed (on both systems).
I then scheduled the update for a regular patch round, and applied immediately after reboot. It then worked fine on both systems.
Strange given that the I/O on startup was very high as services are starting and the Exchange store is mounting, but the update still completes OK.
Therefore to assist anyone experiencing this issue, it is definitely recommended to take the advice of applying immediately after a restart of the server (regardless of I/O).
The invalid image file error message is misleading, as it implies there is something wrong with the update itself, corruption or otherwise. There does appear to be a correlation with the length of time the server has been running and the failure of the update, regardless of I/O, which a reboot fixes.
Anyway, problem now solved! Hope this helps other people in future.
Could you verify the specific OS that is being used on the T420? Also, could you verify that none of the following conditions is occurring, as this update will not run if any of the following conditions exist
1. Any Virtual Disk that is not optimal. 2. A raid container that is performing a Background Initialization or Consistency Check. 3. A Rebuild, Resync, or copyback function is taking place. 4. A RAID set that is Partially Degraded or in a Degraded state.
Lastly, could you confirm the raid controller, and it's firmware version.
None of those situations are taking place. The firmware update has been attempted several times over the last year at different times, it always says the package is invalid.
The OS is SBS 2011 Standard (based on Server 2008 R2).
Hi, have the labs been able to resolve this situation? I have tried this again today and it still fails with the same error, that the image file is invalid. This would refer to the image within the update yes?
From my understanding, this error is given because ther'es too much I/O on the drives. You can try rebooting the server, then running the update as soon as the server comes back up.
Alternatively, the nautilus tool may work for you. This is a tool to create a bootable USB drive for the sole purpose of updating hard drive firmware.
Walkthroguh:
<ADMIN NOTE: Broken link has been removed from this post by Dell>
APweb
81 Posts
0
May 26th, 2016 11:00
Thanks DerikC :)
After experiencing this problem on another Dell system with a different Seagate update it appears to be related to systems with Exchange installed on SBS (Small Business Server) systems.
Taking your I/O comments on board I shut down all services (including Exchange and SQL) and verified from performance monitors that the disks were idle. However the update still failed (on both systems).
I then scheduled the update for a regular patch round, and applied immediately after reboot. It then worked fine on both systems.
Strange given that the I/O on startup was very high as services are starting and the Exchange store is mounting, but the update still completes OK.
Therefore to assist anyone experiencing this issue, it is definitely recommended to take the advice of applying immediately after a restart of the server (regardless of I/O).
The invalid image file error message is misleading, as it implies there is something wrong with the update itself, corruption or otherwise. There does appear to be a correlation with the length of time the server has been running and the failure of the update, regardless of I/O, which a reboot fixes.
Anyway, problem now solved! Hope this helps other people in future.
DELL-Chris H
Moderator
•
9.7K Posts
0
May 27th, 2015 12:00
ApWeb,
Could you verify the specific OS that is being used on the T420? Also, could you verify that none of the following conditions is occurring, as this update will not run if any of the following conditions exist
1. Any Virtual Disk that is not optimal.
2. A raid container that is performing a Background Initialization or Consistency Check.
3. A Rebuild, Resync, or copyback function is taking place.
4. A RAID set that is Partially Degraded or in a Degraded state.
Lastly, could you confirm the raid controller, and it's firmware version.
Let me know and we can go from there.
APweb
81 Posts
0
May 28th, 2015 03:00
Hi
None of those situations are taking place. The firmware update has been attempted several times over the last year at different times, it always says the package is invalid.
The OS is SBS 2011 Standard (based on Server 2008 R2).
Controller is Perc H710.
H710 packages installed:
SAS-RAID_Driver_XYPYC_WN64_6.803.21.00_A07
SAS-RAID_Firmware_1C4T9_WN64_21.3.1-0004_A06
APweb
81 Posts
0
March 3rd, 2016 02:00
Hi, have the labs been able to resolve this situation? I have tried this again today and it still fails with the same error, that the image file is invalid. This would refer to the image within the update yes?
The problem file is: downloads.dell.com/.../SAS-Drive_Firmware_GXCDR_WN32_PS08_A04.EXE
DerikC
27 Posts
0
March 3rd, 2016 08:00
From my understanding, this error is given because ther'es too much I/O on the drives. You can try rebooting the server, then running the update as soon as the server comes back up.
Alternatively, the nautilus tool may work for you. This is a tool to create a bootable USB drive for the sole purpose of updating hard drive firmware.
Walkthroguh:
<ADMIN NOTE: Broken link has been removed from this post by Dell>
Latest release: www.dell.com/.../DriversDetails