Hi Camillo,
a VERY important consideration is, whether the healthy controller took over. If you're in takeover mode, DON'T re-assign disks from maintenance mode! It will mess up your mailbox disks. The new system is probably in a boot loop or 'stuck' but should show you the new Sys-ID in the console messages. Take a note of the new Sys-ID.
Instead go to the controller that took over and type:
* partner /<to switch to the 'virtual' partner>/ * priv set advanced * disk reassign -d <new Sys-ID> * partner
After this is through, the new controller should boot up just fine and be 'waiting for giveback'.
* cf giveback
Done :-)
If you did mess up your mailbox disks, you'll have to go to maintenance mode (option 5 in boot menu) and do
* mailbox destroy local * mailbox destroy partner
on BOTH controllers (to be on the safe side).
Test if your mailbox disks are working OK, by taking over and giving back from BOTH sides.
If the healthy controller did not take over, you're fine to go to maintenance mode and change disk ownership, BTW.
Hope that helps
Sebastian
P.S. no quirks in the 2020, Sys-ID is derived from the serial number of the NVRAM, just like with all the other controllers.
On 10/1/2014 2:42 AM, Camillo Gornati wrote:
When i type disk show, it only shows me 24 disks, which are assigned to controller B, as this is controller A (which has been replaced.
Is this correct?
We have 2 shelves connected to the system.
On Sep 30, 2014, at 7:27 PM, Jeff Cleverley <jeff.cleverley@avagotech.com mailto:jeff.cleverley@avagotech.com> wrote:
Camillo,
I'm not familiar with the 2020 series or quirks it may have. I would have expected the controller personality to transfer with the CF card It sounds like you may be in a
These are the basic steps you need to take.
- Boot the controller connected to the drives to the special boot
menu. There should be a maintenance option, often #5. Select that.
- Once you are in that mode, you can do one of 2 things:
a. remove the ownership of all the drives by running disk remove_ownership all -f b. run sysconfig and get the current system ID. You can then reassign the disks using the disk reassign command.
Once you have done that, you should be able to boot up and it should see the drives.
Jeff
On Tue, Sep 30, 2014 at 3:50 PM, Camillo Gornati <cams1976@gmail.com mailto:cams1976@gmail.com> wrote:
Hi all! In our environment, we have a FAS2020a and a FAS2020. FAS2020a had one controller bad, we installed a replacement we had, installed old the CF CARD, but system won’t boot, it says there is no disks for root volume. That is because all disks are assigned to old controller. How could we assign those disks to new controller without losing any data? Thanks in advance Camillo _______________________________________________ Toasters mailing list Toasters@teaparty.net <mailto:Toasters@teaparty.net> http://www.teaparty.net/mailman/listinfo/toasters-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters