Dysfunctional LSI 9285-8e

auroxin

New Member
Jun 19, 2022
8
1
3
I got a 9285-8e from eBay, but I doesn't work, and I wonder if there is any tool that could diagnose and possibly fix it, instead of sending it back.

Nothing shows up during boot, I can install the driver, but it would not start. I think the hardware ID (DEV_0089) may not be correct, so the card could be defective, or could have some non-standard flash.
 

Attachments

mobilenvidia

Moderator
Sep 25, 2011
1,931
190
63
New Zealand
I'm leaning towards you may have been duped with that card
9285-8e should have 'PCI\VEN_1000&DEV_005B', '0089' does not come up for anything Broadcom/LSI/Avago
Someone possbly trying to flash another card into a 9285, maybe an OEM or even a 9280
Compare yours with a known 9285 and if any differences

Send it back if you can
 

Stephan

Well-Known Member
Apr 21, 2017
484
291
63
Germany
First impulse after googling VEN_1000 and DEV_0089 and finding nothing is to say "send it back".

If you want to go bonkers I just uploaded a PKGBUILD for Archlinux called lsiutil here: Index of /files/lsiutil/

You have to install it with makepkg -Ccfi or similar. Run it, select the card, hit e to enable expert mode and you will get:

Code:
 1.  Identify firmware, BIOS, and/or FCode
2.  Download firmware (update the FLASH)
3.  Upload firmware
4.  Download/erase BIOS and/or FCode (update the FLASH)
5.  Upload BIOS and/or FCode
8.  Scan for devices
801.  Scan for 1 LUN
802.  Scan for 2 LUN's
803.  Scan for 3 LUN's
804.  Scan for 4 LUN's
805.  Scan for 5 LUN's
806.  Scan for 6 LUN's
807.  Scan for 7 LUN's
808.  Scan for 8 LUN's
809.  Scan for 9 LUN's
810.  Scan for 10 LUN's
9.  Read/change configuration pages
10.  Change IOC settings (interrupt coalescing)
13.  Change SAS IO Unit settings
14.  Change IO Unit settings (multi-pathing, queuing, caching)
16.  Display attached devices
17.  Show expander routing tables
18.  Change SAS WWID
19.  Test configuration page actions
20.  Diagnostics
21.  RAID actions
23.  Reset target
24.  Clear ACA
25.  Power Management Control
33.  Erase non-volatile adapter storage
34.  Remove device from initiator table
35.  Display HBA firmware Log entries
36.  Clear (erase) HBA firmware Log entries
37.  Force full discovery
40.  Display current events
42.  Display operating system names for devices
43.  Diagnostic Buffer actions
44.  Program manufacturing information
45.  Concatenate SAS firmware and NVDATA files
46.  Upload FLASH section
47.  Display version information
48.  Display chip VPD information
49.  Program chip VPD information
50.  Dump MPT registers
51.  Dump chip memory regions
52.  Read/modify chip memory locations
54.  Identify FLASH device
55.  Force firmware to fault (with C0FFEE)
56.  Read/write expander memory
57.  Read/write expander ISTWI device
58.  Alta diagnostics
59.  Dump PCI config space
60.  Show non-default settings
61.  Restore default settings
64.  SAS Expander UART Console
65.  SAS UART Debug Console
66.  Show SAS discovery errors
67.  Dump all port state
68.  Show port state summary
69.  Show board manufacturing information
70.  Dump all device pages
71.  Dump all SAS device page 0's
80.  Set SAS phy offline
81.  Set SAS phy online
90.  Send SCSI CDB
95.  Send SATA request
96.  Send SMP request
97.  Reset SAS link, HARD RESET
98.  Reset SAS link
99.  Reset port
e   Disable expert mode in menus
p   Enable paged mode
w   Enable logging

Main menu, select an option:  [1-99 or e/p/w or 0 to quit]
Try options 1, 47, 69 and tell us the output. Sorry, only got it for Archlinux. There could be a windows version of >= 1.70 around somewhere, which is required for the 2xxx chipset series (2008, 2308 etc.).

Edit: I just realized that with that non-standard PCI device ID, chances are Linux will also not load any driver. And lsiutil also will not see the card. Suggest to send it back and buy a working card. Also are you sure you want a Megaraid card and not a plain HBA...
 
Last edited:

mobilenvidia

Moderator
Sep 25, 2011
1,931
190
63
New Zealand
Linux won't load driver but like widow should see it
LSIUtil for windows 1.71 attached may work as Win sees it for what it should be, which must come from somewhere in the Firmware

Possibly use LSIRec (I compiled attached version for Centos7), if this sees the card it can then write a Firmware and/or SBR to it
May attempt a write 9285 SBR to it then flash a suitable firmware

or
Have a looksy here:
Follow instructions
It brings back bricked SAS2208 based cards, may restore it

Just my cup of tea doing the above, but if squeemish you can easily get into a power of trouble but no worse than you are already I suppose
 

Attachments

auroxin

New Member
Jun 19, 2022
8
1
3
Thanks, I'll take a look at those when I get home. The 9285--8E was a good enough deal that I would rather fix it if possible.
 

auroxin

New Member
Jun 19, 2022
8
1
3
I'm leaning towards you may have been duped with that card
9285-8e should have 'PCI\VEN_1000&DEV_005B', '0089' does not come up for anything Broadcom/LSI/Avago
Someone possbly trying to flash another card into a 9285, maybe an OEM or even a 9280
Compare yours with a known 9285 and if any differences

Send it back if you can
I don't think it's a fake card, but it could be defective in a number of ways such as ESD. I don't know how hot they supposed to get, but the heatsink gets a bit hotter than I would consider healthy.

If I can't get it to work within a day or two, I'll start the return process.

Attached are the images of the card in question.
 

Attachments

auroxin

New Member
Jun 19, 2022
8
1
3
Thanks for all the help even though it couldn't do much with the most likely dead card. I filed for return last night and was refunded this morning, and the seller doesn't even wants the card back!!

The card came with a BBU, which is most certainly worth more than the cost of shipping it back.
 

Attachments

  • Like
Reactions: Fritz