Skip to main content
Start a Conversation

Unsolved

S

SPGS

1 Rookie

 • 

15 Posts

30

September 30th, 2023 21:35

ME4024 firmware upgrade = pool lost (model X02SMF040 pn 0HKK8C)

Upgraded in place from GT280R008-04 to GT280R010-01

At the time it was no issue, both pools showed fine

(the unit was not powered off)

Today had site shutdown, so the unit was off (in controlled manner as well as physically)

After power back, the unit's first 12x SAS SSD Dell Enterprise 1.92Tb (HGST HUSMR1619ASS200) disks are fine, but the other 8x 400Gb model PX02SMF040 SAS SSD are all flashing orange right light (left is green) - but ONLY after the OS of the array boots - and the GUI does NOT even show they exist!

When the unit is first starts they have both green.

Looks like the firmware rejects the disks (unsupported?) and that is it

The separate pool that they were used for no longer exists, with all data gone (and I had a couple of files there that I really could do with)

Anybody any ideas?

Seb

SPGS

1 Rookie

 • 

15 Posts

October 10th, 2023 10:51

I get this error for every Dell PX02SMF040 SAS SSD d/pn 0HKK8C drive:

An error was reported by a disk drive. (disk: channel: 0, ID: 16, SN: , enclosure: 0, slot: 16)(Key,Code,Qual,UEC:0x4,0x4C,0xA8,0x0000) 
(CDB:000000000000)(CmdSpc:0x0, FRU:0x0, SnsKeySpc:0x0)(Hardware, no decode for ASC/ASCQ)

To have all EIGHT fail at the same time, would be very unlucky

(edited)

SPGS

1 Rookie

 • 

15 Posts

October 10th, 2023 13:47

Wonder if this has anything to do with my issue....

SPGS

1 Rookie

 • 

15 Posts

October 12th, 2023 18:45

Sadly even if I remove the drives from ME4 & plug into R740 with PERC H730P Adapter I get for each one:

Fault detected on drive x in disk drive bay 1

Controller recognizes them as:

Manufacturing Information 		
Part Number 	Information Not Available
Manufacturer 	TOSHIBA
Non RAID Disk Cache Policy 	Not Applicable
Product ID 	PX02SMF040
Revision 	A3AF
Serial Number 	Information Not Available
Manufactured Day 	Not Applicable
Manufactured Week 	Not Applicable
Manufactured Year 	Not Applicable

but cannot update the firmware, as the SAS-Drive_Firmware_69J5F_WN64_A3B4_A00.EXE claims

This Update Package is not compatible with your system configuration.

(edited)

SPGS

1 Rookie

 • 

15 Posts

October 13th, 2023 11:37

Full upgrade attempt log is here:

https://pastebin.com/UaJi9Fcm

I can hex edit the .fwh file changing the ID and then I get different error (Installed FW version: does not support FW update)

<Fri Oct 13 01:43:52 PM><Fri Oct 13 01:43:52 PM>DUPWrapper: Begin Device name=<Fri Oct 13 01:43:52 PM>DUPWrapper: checking Device 4 update ctrlid:0 deviceid:7
<Fri Oct 13 01:43:52 PM>DUPWrapper: after setting DeviceID
<Fri Oct 13 01:43:52 PM>SASHardDriveDUPDevice: Enter populateFileVersion
<Fri Oct 13 01:43:52 PM>ImageFiles::getCount count = 1
<Fri Oct 13 01:43:52 PM>getImage: Begin
<Fri Oct 13 01:43:52 PM>getImage: filepattern:*.fwh
<Fri Oct 13 01:43:52 PM>getImage: filename:[<Fri Oct 13 01:43:52 PM>KAI_PM2_Non-SED_A3B4.fwh<Fri Oct 13 01:43:52 PM>]  size<Fri Oct 13 01:43:52 PM>dd680<Fri Oct 13 01:43:52 PM>ImageFiles::DoesFilenameMatchTemplate: Begin
<Fri Oct 13 01:43:52 PM>DoesFilenameMatchTemplate:filename=KAI_PM2_Non-SED_A3B4.fwh filepattern=*.fwh
<Fri Oct 13 01:43:52 PM>DoesFilenameMatchTemplate:lowercase_filename=kai_pm2_non-sed_a3b4.fwh lowercase_filepattern=*.fwh
<Fri Oct 13 01:43:52 PM>ImageFiles:DoesFilenameMatchTemplate: filepattern length = 5
<Fri Oct 13 01:43:52 PM>ImageFiles:DoesFilenameMatchTemplate: wildcard index = 0
<Fri Oct 13 01:43:52 PM>ImageFiles:DoesFilenameMatchTemplate: have last part
<Fri Oct 13 01:43:52 PM>ImageFiles:DoesFilenameMatchTemplate: FPart=
<Fri Oct 13 01:43:52 PM>ImageFiles:DoesFilenameMatchTemplate: LPart=.fwh
<Fri Oct 13 01:43:52 PM>ImageFiles:DoesFilenameMatchTemplate: lowercase_filename.length()18
<Fri Oct 13 01:43:52 PM>ImageFiles:DoesFilenameMatchTemplate: pLPart.length()4
<Fri Oct 13 01:43:52 PM>getImage: End - Found
<Fri Oct 13 01:43:52 PM>SASHardDriveDUPDevice: Online Download Enabled
<Fri Oct 13 01:43:52 PM>m_D_Method = 1
<Fri Oct 13 01:43:52 PM>Image version = A3B4
<Fri Oct 13 01:43:52 PM>Min Image version = A301
<Fri Oct 13 01:43:52 PM>m_ProcessTime(byte) = x
<Fri Oct 13 01:43:52 PM>m_ProcessTime = x
<Fri Oct 13 01:43:52 PM># of devices = 4
<Fri Oct 13 01:43:52 PM>deviceID [0102241
<Fri Oct 13 01:43:52 PM>deviceName [0                              PX02SMF020
<Fri Oct 13 01:43:52 PM>deviceID [1102242
<Fri Oct 13 01:43:52 PM>deviceName [1                              PX02SMF040
<Fri Oct 13 01:43:52 PM>deviceID [200000
<Fri Oct 13 01:43:52 PM>deviceName [2                              PX02SMF080
<Fri Oct 13 01:43:52 PM>deviceID [3102244
<Fri Oct 13 01:43:52 PM>deviceName [3                              PX02SMB160
<Fri Oct 13 01:43:52 PM>SASHardDriveDUPDevice: Image version set: A3B4
<Fri Oct 13 01:43:52 PM>DUPWrapper: populate rc=f
<Fri Oct 13 01:43:52 PM>Comparing device ID:102241 with 00000
<Fri Oct 13 01:43:52 PM>Comparing device ID:102242 with 00000
<Fri Oct 13 01:43:52 PM>Comparing device ID:00000 with 00000
<Fri Oct 13 01:43:52 PM>depCheck: Found matching device
<Fri Oct 13 01:43:52 PM>Comparing device ID:102244 with 00000
<Fri Oct 13 01:43:52 PM>toLowerCase: begin
<Fri Oct 13 01:43:52 PM>toLowerCase: begin
<Fri Oct 13 01:43:52 PM>toLowerCase: begin
<Fri Oct 13 01:43:52 PM>toLowerCase: begin
<Fri Oct 13 01:43:52 PM>depCheck: Installed FW version: does not support FW update
<Fri Oct 13 01:43:52 PM>depCheck: Min required version:A301
<Fri Oct 13 01:43:52 PM>depCheck: Min version check failed
<Fri Oct 13 01:43:52 PM>DUPWrapper: error from depCheck:13
<Fri Oct 13 01:43:52 PM>XMLWriter::addUpdateDeviceInfo: 1
<Fri Oct 13 01:43:52 PM>XMLWriter::addUpdateDeviceInfo: 2
<Fri Oct 13 01:43:52 PM>XMLWriter::addUpdateDeviceInfo: 3
<Fri Oct 13 01:43:52 PM>XMLWriter::addUpdateDeviceInfo: 4
<Fri Oct 13 01:43:52 PM>XMLWriter::addUpdateDeviceInfo: 5
<Fri Oct 13 01:43:52 PM>XMLWriter::addUpdateDeviceInfo: 6
<Fri Oct 13 01:43:52 PM>XMLWriter::addUpdateDeviceInfo: 7
<Fri Oct 13 01:43:52 PM>DUPWrapper:No devicea updated.
<Fri Oct 13 01:43:52 PM>DUPWrapper:Deleting ImageLoader.
<Fri Oct 13 01:43:52 PM>SASHardDriveDUPDevice::~SASHardDriveDUPDevice::Deleting m_PR_stopped
<Fri Oct 13 01:43:52 PM>SASHardDriveDUPDevice::~SASHardDriveDUPDevice::Finished deleting m_PR_stopped
<Fri Oct 13 01:43:52 PM>SASHardDriveDUPDevice::~SASHardDriveDUPDevice::Deleting m_PR_disabled
<Fri Oct 13 01:43:52 PM>ImageFiles::Finished deleting m_PR_disabledr
<Fri Oct 13 01:43:52 PM>swrSASHardDriveDUPDevice::~swrSASHardDriveDUPDevice::Deleting m_BAS_disabled
<Fri Oct 13 01:43:52 PM>swrSASHardDriveDUPDevice::~swrSASHardDriveDUPDevice::Finished deleting m_BAS_disabledr
<Fri Oct 13 01:43:52 PM>swrSASHardDriveDUPDevice::~swrSASHardDriveDUPDevice::Deleting m_config_info
<Fri Oct 13 01:43:52 PM>swrSASHardDriveDUPDevice::~swrSASHardDriveDUPDevice::Finished m_config_info
<Fri Oct 13 01:43:52 PM>DUPWrapper: Checking for process time delay
<Fri Oct 13 01:43:52 PM>DUPWrapper: deviceProcessWaitTime=0
<Fri Oct 13 01:43:52 PM>DUPWrapper: AtLeastOneDeviceUpdatedSuccessfully=0
<Fri Oct 13 01:43:52 PM>DUPWrapper: After takeAction +++++++++++
<Fri Oct 13 01:43:52 PM>DUPWrapper: takeAction complete

(edited)

SPGS

1 Rookie

 • 

15 Posts

October 17th, 2023 10:47

Anybody ANY idea how to force upgrade the firmware?

View More

View All

No Events found!

Top