we are in progress of testing Scv3020. I initialized the array, I login into Storage center.
But I tried to cleanup drive configuration (I want to configure all from scratch). I released all rotational drives.
Result is that both controllers are orange and I am not able to login to Storage center again. I understanded that there are probably portion of OS on the drives.
And question is easy, how to resolve this. (it seems that on controllers are some services failing, OS itself booted)
I expect that it will require some kind of service login and then array will be completely purged and reverted to default (there are still no data on it so absolutely no problem with this setup)
But how? I didn´t find some service document with these tasks and also service support password. Probably tech-support can do this.
Probably there were two problems, my mistake and then some desynchronisation of both controllers. We must completely purge all configuration from both controllers and reinitialize again.
Co-pilots worked relatively hard but passed. For myself it was some kind of school.
It seems that Compellent IS really different solution. I am in progress of testing features and performance. After this fix I already tested something. And seems interesting.
One reason why you can no longer log into the controllers is that the controllers are not booting into the SCOS operating system. Hence, alternative login procedures will be required.
Have you contacted Co-Pilot support (i.e. Compellent tech support)? I could assist in this, but Co-Pilot should be able to walk you thru the login procedures and fix the controllers; or even factory reset them so you can rediscover them via DSM.
We have sc 8000 and first unit stuck in "Failed controllers, first selection, restart" state. Units are out of warranty so no co-pilot support unfortunately. I wonder if you have any suggestions or alternative login procedure etc to reset the controller etc...
michawel
1 Rookie
•
3 Posts
10507
0
Posted May 14th, 2018 13:00
Probably there were two problems, my mistake and then some desynchronisation of both controllers. We must completely purge all configuration from both controllers and reinitialize again.
Co-pilots worked relatively hard but passed. For myself it was some kind of school.
It seems that Compellent IS really different solution. I am in progress of testing features and performance. After this fix I already tested something. And seems interesting.