Hello, 

 That means the boot process did not complete.  Are you using the serial port or SSH ? 

 If you are using serial, connect to the other CM, you might be on the passive controller. 

 You can try: 

 CLI>support exec "raidtool"   

  CLI>support exec "uname -a" 

 Copy the text output and paste it here

 Regards,

Don

Try sending them in a private message here. 

Don

@dwilliam62 my replies are going to spam. 

Hi @dwilliam62 I am using SSH.Below are the output from both commands

Hello, 

 That is not a PS6000.   That's either a PS6100 or PS6200. 

 But all those "available" drives means it's not reading the RAID labels on those drives. 

 You can try power down. Remove the active CM partway from the chassis, reseat all the drives, then power back up again.   See if it's a bad controller. 

  Regards, 

Don 

Hello, 

 No. Physical access is going to be needed. 

 Don 

@dwilliam62 sorry, its Ps62110E array, I am working remotely, is there something I can do from CLI to make it work. 

Hello @dwilliam62  How i can Remove the active CM partway from the chassis, reseat all the drives, then power back up again? 

Can you explant that for me? I have the same case.

CLI> support exec diskview -j https://photos.app.goo.gl/D1cpqSiFm9JdMeaz8 

CLI> su exec raidtool -Z https://photos.app.goo.gl/o6QeEBnzMLHTuXKN6 

Disk 0 and 4 are news. 

Send me message 

Hello, 

Only one link worked which showed multiple drives have failed.  Likely your RAIDset is offline as well. 

Please create a new thread, since your issue is not the same as this thread.  even thought the error message is the same.  they have different causes. 

 Most likely you will need to call a data recovery service to try to get those failed drives cloned which will allow the RAIDset to recover. 

 This users problem could be related to a failed controller.  Which is why I suggested removing the active to force a boot up of the secondary. 

 Regards, 

Don 

@dwilliam62 Thank you so much. I'll open another thread.