RSS
 
 

Xyratex -Autodesk Secrets from the void

26 Jan

I’ve been playing with the Xyratex kit for the past few years, mainly when there is a spare hour or so…
During this time we found any number of really interesting “things” one of which is listed below…

After entering the monitor during boot-up via:

“Press and hold to invoke monitor”

you are presented with a screen showing

“Monitor>”

Entering “?” gives you a list of commands:

and from this list of commands you can do ‘really cool’ things like “upload firmware” or take a look at the temperature…

Lets be honest… it is absolute garbage.. not worth the time of day other than for very basic maintenance….

However
If you enter the command “set debug

now do the command “?”

And suddenly the whole world opens up for you….

Commands you should NEVER EVER do as a newbie…..
“ef”… You will erase the controller firmware…(bye…..)
“sw”… You will completely destroy your controller firmware if not pre-prepared for this action
“go”… If you randomly enter addresses you can jump into the middle of any number of “dangerous” routines….
“fi”… You can destroy critical ram tables as well as writing to the device I/O
“i2w1”. This can destroy critical settings on the i2c buss 1
“i2w2”. This can destroy critical settings on the i2c buss 2
“fwp1”. This can destroy critical settings on the PCI buss 1
“fwp2”. This can destroy critical settings on the PCI buss 2

Those and any command that does a “write” to any address the user can enter…..

Oh… and if you break it.. there is a good chance that a power cycle WILL NOT CORRECT THE ISSUE………..

Anyone who thinks this is bullshit can go try the “SW” command………
What happens.. is a bug….. the internal flash chips are erased.. then it attempts to copy an alternative firmware that is stored in ram…. but it don’t exist… becasue you did not pre-store it.. oh and you cannot load one becasue you don’t know the details of the load file header and validation….. (plus ur running an AD or maybe Xyratex boot monitor)
If it is an AD monitor you are completely fucked.. becasue it will only load “AD” firmware…
and to date I have never seen an “AD” load file…

so you are left with erased flash chips and no real way to recover……… unless you have firmware files

You would have thought they would validate the “alternative ” firmware BEFORE the chip erase… but nope….. Sorry..
There is a firm warning in the “ver” command… if you can spot it.

What is SHOULD look like before doing anything stupid.

As can be seen we have a safety “default” Alternative Operational firmware saved.

same with the “go” command… you can jump right into one of the many “erase chip” functions by accident…

 

Leave a Reply

 

*