Showing results for 
Search instead for 
Do you mean 

PK6 removal problem

Occasional Advisor

PK6 removal problem

Hi,

I have removed PK6 from my DS25 cluster, after removal, I needed to run dn_fix_dat.sh, but system booted itself automatically and I couldn't execute command.

After that system is not booting with the following error:
rm slave: log_rail 0 (size 512 MB), phys_rail 0 (mchan0)
Waiting for Cluster Member Boot Disk to become registered.

I tried to boot in single user mode with boot -fl s, but gives the same error above.

I'll be appreciated if u can share your experience with me.
3 REPLIES
Honored Contributor

Re: PK6 removal problem

can't you run the command from another (still running) node in the cluster ?

or is the whole cluster not booting anymore?
Occasional Advisor

Re: PK6 removal problem

Hi,

I had run dupatch on first node, then on second node. when the one in the second node finished both nodes has been booted and did not come up again as the problem described below
thanks
umit
Occasional Visitor

Re: PK6 removal problem

Hi,

No need to run dupatch on both the nodes
simultaneously. There are few possibilities
for this hang issue:
1. Device is now gone (dead)
2. Fabric is hung.
3. Fabric is having troubles.
Could you please check for (1) and (3)
cases? For further debugging, please
provide binaryerror log file.

Regards,
Shrikant
//Add this to "OnDomLoad" event