search

Seagate / openSeaChest

Cross platform utilities useful for performing various operations on SATA, SAS, NVMe, and USB storage devices.
Other
471 stars 61 forks source link

Using CFS file results in segfault #151

Open reb00tz opened 3 weeks ago

reb00tz commented 3 weeks ago

Attempting to update firmware on Seagate Exos X18 16TB (ST16000NM000J-2TW103) fails.

Using CFS file results in segfaults.

Tried different variations of commands used (including invalid --downloadMode attempts). Used both RAID and Non-RAID versions.

Attached are the -v3 logs and output, including system and drive information *_system_drive_info.txt along with the two RAID/Non-RAID scripts used to generate them.

More platform information as follows:

run_fwupgrade_RAID.tar.gz run_fwupgrade_Non-RAID.tar.gz

config_segfault.tar.gz

vonericsen commented 3 weeks ago

@reb00tz,

Thank you for reporting this. I will debug it to figure out what is causing the segmentation fault to fix that.

Starting in the Dec 1, 2023 release support for the CFS was dropped for a new format. Was this the version of SeaChest_Firmware included with the firmware package from Seagate.com? As I recall there should have been a version of SeaChest included with that package that supports the CFS file.

reb00tz commented 3 weeks ago

The files in OP were from the SeaChest Utilities straight from Seagate's website.

It appears that you are correct; using the CFS file, it reports "Model matched but the current Firmware version does not match available updates.".

If this drive has a firmware that somehow is unable to be flashed with the latest bug-fixed firmware, what is my next step? Since the release notes for the latest SN05 is not available, I do not know if the drive will fail prematurely.

packaged.zip

vonericsen commented 3 weeks ago

If this drive has a firmware that somehow is unable to be flashed with the latest bug-fixed firmware, what is my next step? Since the release notes for the latest SN05 is not available, I do not know if the drive will fail prematurely.

I will look into this to see if I can find out some more information on why it would not match as expected.

I am getting close to ready for a new software release, so I definitely want to fix the segfault and provide a better error message for this case.