Unsolved
This post is more than 5 years old
1 Rookie
•
42 Posts
0
8466
March 2nd, 2017 13:00
Removing an offline group member by myself
Is it possible..? I haven't upgraded FW yet to see if the option opens up.. But when I try to remove from GUI it says I need to call support, running member delete in CLI gives me this:
ST-EQ> member delete st-eqex
Deleting an offline member may cause irreversible loss of data. Before the
operation can proceed, contact Dell Customer Support to ensure that this is
an appropriate action. If Dell Customer Support believes that this is the
correct path, they will provide a response to match the following
firmware version and challenge number.
To cancel this operation, press without entering a response.
Firmware version: V6.0.2
Challenge: 2367
Response:
This is old equipment being re-purposed. It does not have a current service contract.
I added it to my group incorrectly- swiftly set it to defaults rather than removing via GUI-- or correcting my slip up.. I mean it literally impacts nothing, just an eye sore in group manager.. I re-added it with a different name and everything is up and running smooth.
nickelob
1 Rookie
•
42 Posts
0
March 2nd, 2017 13:00
...Can I add another array with the same name and remove it? It would certainly have hardware ID's to prevent this right? or would it in a sense, overwrite the original, come online then zing.. I can just ssh in and member delete st-eqex
yay or nay?
so all I do is go get the extra PS6510 I have, put a drive in it, join it to the group as st-eqex, bring it online and delete it the correct way..
Donald, have you seen the movie Inception?
nickelob
1 Rookie
•
42 Posts
0
March 2nd, 2017 13:00
You will have to open a no warranty support case. They will give you the response code to remove it.
--What is the cost? It isn't spitting out email errors so I don't care that much.. just figured you guys might be nice to me here.
The proper way to remove a member is with the member delete option. That will remove it from the database correctly
--yes I discovered that after I reset.... figured my pasted CLI would let you know I made an idiot misclick up front, but thanks for the info.
Are you running VMware against this group?
--The member I need to remove was not configured beyond adding it to the group, no raid cfg, etc. there is no data on it.
nickelob
1 Rookie
•
42 Posts
0
March 2nd, 2017 13:00
...But yes VMware on the group, though this member never had data on it.
nickelob
1 Rookie
•
42 Posts
0
March 2nd, 2017 14:00
That is correct, the other three are way out of contract. I'm now gathering the firmware needed to get them on par.. looks like >6.0.5>7.0.9>up to 7.1.5, I do still have full access to PS firmware/release notes.
?-IO load will do nothing but decrease from now until tomorrow morning, is the FW update disruptive? I will be doing after cob, but just wondering if I should down my environment first, I'd like to avoid an abrupt crash like the one that got me scrambling to add a member in the first place..
?-I did notice that the PS5000's seem to be so old that they actually have standard Seagate OEM drives in them without error.. will upgrading firmware cause a compatibility conflict, or can I assume the legacy hardware will still play fair..?
-It did let me add it to the group with the warning displayed each time I login to the manager, updates planned tonight.
Thank you,
Joe
nickelob
1 Rookie
•
42 Posts
0
March 2nd, 2017 14:00
I'm just going to let it chill, not worried about deleting it anymore.
3 members are running 6.0.2, the array I added this morning is running 7.1.5 ..gives a warning about mixed versions, but seems to allow full functionality- minus stats.. can't get IO stats from the newly added PS6100.
ESXI 5.1 has been working fine for years with 6.0.2..... Is adding the 7.1.5 6100 going to fudge things for me?
Thanks,
JW
nickelob
1 Rookie
•
42 Posts
0
March 3rd, 2017 07:00
Awesome! Looking like weekend maintenance for me 8] but should be quick and clean. Thank you very much, I may continue to post tomorrow morning/afternoon if I run into anything weird, but all in all- thanks to the info you've shared I should be able to handle this without a problem.
-The release notes for 7.1.5 are a little loose, stating anything 6.0.5 or greater will work to go to 7.0.x, I should grab the oldest from the family anyway though.
-I always thought it was a little weird with the OEM drives being found in older EQL sans.. at least I'd find holes in technical info relayed by the same people that were telling me OEM drives shipped in early EQL SANs.
Thank you,
Joe