ha please disregard I did a google image search and see it's on the bottom, the one place I didn't check, thanks :)

thanks so much I will attempt this tomorrow and update - I should mention I was mistaken and it's actually a 6000 with 2 x type 10 controllers, when I was working on this today I remembered something about the CF, silly question where on the type 10 controller is the flash card? I recall briefly looking today and it didn't seem obvious. thanks again.

i will attempt this tomorrow, i should append that its actually a 6000 with type 10 controllers, pulled it put looking for the flash card today, any pointers as to where its located it didnt seem obvious to me for some reason. Thank you

Some progress - (either) single controller and dual controllers both boot and don't crash with no drives - I did a reset command with  no drives, which it took but obviously isn't going to accomplish much -  any drives in any bay causes the same crash loop I pasted , it crashes within 15 seconds (right after drive inserted message) - 1426:79:MgmtExec:23-Jun-2015 12:58:15.160080:emdEcd.cc:107:INFO:7.2.0:Disk 0 has been inserted. - or if I boot with even 1 drive in any bay.

any thoughts on the best way to proceed? I suppose all new drives (the drives are themselves new but obviously have a bad eq config written to them? maybe erase one on a pc?) thanks

also.. running diags with no drives, will see how that goes. thanks

ok so of course the usb adapter we have on hand is SATA only, so will try a sas <-> sata thing on a computer tomorrow will see how it goes - this is a used unit with all brand new out of the box drives... someone else installed them I suspect it was a combo of an old raid config on the controllers + dirty shutdown after drive install == mulch - but yes thankfully no data at all. will update thursday probably, thanks

strange doesn't show my reply, anyway, any drive insertion in any slot crashes the system and it goes into the same reboot loop I originally posted, this afternoon I'm going to erase a drive via a USB<->sata on a computer and see what happens

here is the update - the SATA to SAS adapter I got was actually useless as it required a controller that could talk SAS (which my $20 usb to sata adapter certainly wouldn't) we ordered a single brand new drive of the same model as the others, s soon as we popped in just that drive, the unit crashed as well. so rather stumped, I did find the microSD card that the controller uses, but not sure at this point what would be a erase plan? thanks

I tried a few other things just for curiosity.. putting a clean newest OS on the microSD card.. is there a proper way to actually wipe the nvram on these controllers? this is as close as I got with that experiment:

which makes sense I suppose.

thanks

he nvram version currently running on the array does not match

the version saved in nvram.

             Current version: 16

             Saved version:   12

This situation can occur if the array experienced an abnormal shutdown

during a firmware update.  Contact your customer support provider for

instructions on how to proceed.

The array has been halted.

You can safely power off the array or type any key to restart the array.

did a little more digging in bash mode - seems the controllers are running 5.0.2 if that matters, tried FTPing FROm the array to download a 5.1.2 to update - no dice, never seems to be enough disk space anywhere on the SD card for some reason. anyway I'm stumped - thanks for your help

I got that error message by overwriting I think the current folder with the contents of the kit, copying back 5.0.2 booted fine again (without drives) I guess there is no way to just reset the nvram and start this clean? I guess not.

absolutely, this was a system with brand new drives and no data I was trying to get online - just chasing a lot of ghosts - I also suspect these drives may be too large to be supported by 5.0.2? reading release notes sounds like 5.0 introduced support for sas drives larger than 2tb but I know the early 5 code had some issues. thanks very much for your help on this.

I tried a (single) dell 3tb SAS I had, and some OEM 4tb SAS (which work fine in 2 other 6010 units I have) but those were all at 6.x , I am really leaning towards a backplane failure - I can't definitively find anything saying 3/4 tb drives wouldn't work in 5.0.2 - and certainly not cause the OS to crash, will replace and advise, thanks again.

I have two units that work flawlessly, but both started with 6.x so i'm 50/50 a 5.x issues or backplane, will get a replacement backplane this week it may have just been that.

Thanks for the help, here is the final update: The issue in the end was that it was running 5.0.2 - I put in 8 SATA drives, configured a group, didn't even need to create a raid - did the step by step upgrade to latest 7.x, installed my new drives, all show up fine, had to re-create the group obviously,  built the array and verifying the raid now.