There are a few options for this. The first thing you should do is open a support ticket but,
1. be sure all IB cables are unplugged
2. what happens when you tell it to continue booting?
either it will come up and continue booting (less likely) or what I assume has happened is that the node simply needs to be reformatted, definitely something support can assist with.
addisdaddy20
65 Posts
0
February 1st, 2016 12:00
There are a few options for this. The first thing you should do is open a support ticket but,
1. be sure all IB cables are unplugged
2. what happens when you tell it to continue booting?
either it will come up and continue booting (less likely) or what I assume has happened is that the node simply needs to be reformatted, definitely something support can assist with.
Roodee Why
2 Posts
1
February 1st, 2016 14:00
1. Unplugged Cables
2. After telling it to continue booting, nothing happens
Ended up reformatting as you mentioned. (Thanks!)
After reformat completed and it rebooted to command prompt, I re-connected cables and joined existing cluster from the list of menu options in CLI.
All looks good now and data is being redistributed across all 4 nodes.
Thanks again.
-Rudy
carlilek
2 Intern
•
205 Posts
0
February 1st, 2016 18:00
I'd pull the cables and then enter recovery shell and do an isi_reformat_node --factory on it. But that's just me.
carlilek
2 Intern
•
205 Posts
0
February 2nd, 2016 04:00
It's nice when things work as intended.
chughh27
39 Posts
0
February 9th, 2016 00:00
Hello,
There are steps to recover journal which only support should run. you need to boot the node in single user mode and then run commands.
I would suggest to involve support and perform the same.
Thanks
Chughh