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
Camillo, You have to go into the boot menu to reassign these. I would strongly suggest that you get netapp on the phone. Once you have done this it's simple but if you have never reassigned disk ownership you really should have some assistance from the pros.
You won't lose data by doing this but you do need to know what is going on. Good luck. Chris
On 09/30/14 16:50, Camillo Gornati 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 http://www.teaparty.net/mailman/listinfo/toasters
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.
1. Boot the controller connected to the drives to the special boot menu. There should be a maintenance option, often #5. Select that.
2. 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 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 http://www.teaparty.net/mailman/listinfo/toasters
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 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 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 http://www.teaparty.net/mailman/listinfo/toasters
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
Disk show -a will show all discs, including those assigned to the previous control ID....
You can then see which ones you need to reassign.
Once re-assigned, reboot the new controller and it should assume the identity of the old controller and boot normally.
Ian.
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Camillo Gornati Sent: 01 October 2014 01:43 To: Jeff Cleverley Cc: Toasters@teaparty.net Subject: Re: Replace controller
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.commailto: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. 1. Boot the controller connected to the drives to the special boot menu. There should be a maintenance option, often #5. Select that. 2. 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.commailto: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.netmailto: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
________________________________
This email and any attachment is for authorised use by the intended recipient(s) only. Its contents may be confidential and/or subject to legal privilege and should be treated as such. It should not be copied, disclosed to, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and then delete this message and any attachments.
Any views or opinions presented are solely those of the author and not those of Phoenix IT Group plc or any of its subsidiaries. This email is not intended to be contractually binding.
Although we have checked this email for viruses, it is your responsibility to scan the message and attachments prior to opening them. We do not take responsibility for loss or damage caused by viruses.
Phoenix IT Group PLC Registered in England no. 03476115 Trend Network Services Registered in England no. 01049704
Registered offices: Technology House, Hunsbury Hill Avenue, Northampton. NN4 8QS.
Phoenix IT Services Limited Registered in England no. 01466217 Phoenix IT Continuity Consulting Limited Registered in England no: 07106472 Phoenix IT Managed Services Limited Registered in England no. 01983540 Phoenix IT Continuity and Resilience Services Limited Registered in England no. 02762460
Registered offices: Lakeside House, The Lakes, Bedford Road, Northampton, NN4 7HD.
For more information about Phoenix IT Group plc please visit our website at http://www.phoenix.co.uk
As a follow-up from the 'Storage Subsystem Technical FAQ:
*HOW DO I PERFORM A CONTROLLER HEAD SWAP WHEN USING SOFTWARE DISK OWNERSHIP? * The recommended method for doing a controller head swap assumes that the other controller head has done a takeover when the broken controller head failed. The user should run the *disk reassign -d old-filersystemid* command in *priv set advanced* mode on the node that is in takeover.
If the other controller head is _*not*_ in takeover mode, then boot the newly swapped head into *maintenance mode* and use the *disk reassign -o old-filername* command. This command determines what the new serial number is and assigns it to the drives. When the node boots, it updates the partner node with the serial number information, provided it is in an HA pair configuration
Sebastian
On 10/1/2014 9:15 AM, Ian Thompson wrote:
Disk show –a will show all discs, including those assigned to the previous control ID….
You can then see which ones you need to reassign.
Once re-assigned, reboot the new controller and it should assume the identity of the old controller and boot normally.
Ian.
*From:*toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] *On Behalf Of *Camillo Gornati *Sent:* 01 October 2014 01:43 *To:* Jeff Cleverley *Cc:* Toasters@teaparty.net *Subject:* Re: Replace controller
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
This email and any attachment is for authorised use by the intended recipient(s) only. Its contents may be confidential and/or subject to legal privilege and should be treated as such. It should not be copied, disclosed to, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and then delete this message and any attachments.
Any views or opinions presented are solely those of the author and not those of Phoenix IT Group plc or any of its subsidiaries. This email is not intended to be contractually binding.
Although we have checked this email for viruses, it is your responsibility to scan the message and attachments prior to opening them. We do not take responsibility for loss or damage caused by viruses.
Phoenix IT Group PLC Registered in England no. 03476115 Trend Network Services Registered in England no. 01049704
Registered offices: Technology House, Hunsbury Hill Avenue, Northampton. NN4 8QS.
Phoenix IT Services Limited Registered in England no. 01466217 Phoenix IT Continuity Consulting Limited Registered in England no: 07106472 Phoenix IT Managed Services Limited Registered in England no. 01983540 Phoenix IT Continuity and Resilience Services Limited Registered in England no. 02762460
Registered offices: Lakeside House, The Lakes, Bedford Road, Northampton, NN4 7HD.
For more information about Phoenix IT Group plc please visit our website at http://www.phoenix.co.uk
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
I believe from the active partner node you could do priv set advanced disk reassign -s [old system id] -d [new system id]
You should get the procedure from Netapp, it also includes running sldiag and I know at least on IBM N series, updating the product ID would could potentially impact your ability to get support.
--Jordan
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Sebastian Goetze Sent: Wednesday, October 01, 2014 7:08 AM To: Ian Thompson; Camillo Gornati; Jeff Cleverley Cc: Toasters@teaparty.net Subject: Re: Replace controller
As a follow-up from the 'Storage Subsystem Technical FAQ:
HOW DO I PERFORM A CONTROLLER HEAD SWAP WHEN USING SOFTWARE DISK OWNERSHIP? The recommended method for doing a controller head swap assumes that the other controller head has done a takeover when the broken controller head failed. The user should run the disk reassign -d old-filersystemid command in priv set advanced mode on the node that is in takeover.
If the other controller head is not in takeover mode, then boot the newly swapped head into maintenance mode and use the disk reassign -o old-filername command. This command determines what the new serial number is and assigns it to the drives. When the node boots, it updates the partner node with the serial number information, provided it is in an HA pair configuration
Sebastian
On 10/1/2014 9:15 AM, Ian Thompson wrote: Disk show -a will show all discs, including those assigned to the previous control ID....
You can then see which ones you need to reassign.
Once re-assigned, reboot the new controller and it should assume the identity of the old controller and boot normally.
Ian.
From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Camillo Gornati Sent: 01 October 2014 01:43 To: Jeff Cleverley Cc: Toasters@teaparty.netmailto:Toasters@teaparty.net Subject: Re: Replace controller
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.commailto: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. 1. Boot the controller connected to the drives to the special boot menu. There should be a maintenance option, often #5. Select that. 2. 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.commailto: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.netmailto: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
________________________________
This email and any attachment is for authorised use by the intended recipient(s) only. Its contents may be confidential and/or subject to legal privilege and should be treated as such. It should not be copied, disclosed to, retained or used by any other party. If you are not an intended recipient please notify the sender immediately and then delete this message and any attachments.
Any views or opinions presented are solely those of the author and not those of Phoenix IT Group plc or any of its subsidiaries. This email is not intended to be contractually binding.
Although we have checked this email for viruses, it is your responsibility to scan the message and attachments prior to opening them. We do not take responsibility for loss or damage caused by viruses. Phoenix IT Group PLC
Registered in England no. 03476115
Trend Network Services
Registered in England no. 01049704
Registered offices: Technology House, Hunsbury Hill Avenue, Northampton. NN4 8QS. Phoenix IT Services Limited
Registered in England no. 01466217
Phoenix IT Continuity Consulting Limited
Registered in England no: 07106472
Phoenix IT Managed Services Limited
Registered in England no. 01983540
Phoenix IT Continuity and Resilience Services Limited
Registered in England no. 02762460
Registered offices: Lakeside House, The Lakes, Bedford Road, Northampton, NN4 7HD.
For more information about Phoenix IT Group plc please visit our website at http://www.phoenix.co.uk
_______________________________________________
Toasters mailing list
Toasters@teaparty.netmailto:Toasters@teaparty.net
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
Great sebastian! I will run those tests as soon as I arrive in the office!
So far so good, cf giveback went ok!
Will test mailboxes and reply soon!
Sent using morse code!
Em 01/10/2014, às 08:02, Sebastian Goetze spgoetze@gmail.com escreveu:
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 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 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 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
-
Blackmor, Chris -
Camillo Gornati -
Ian Thompson -
Jeff Cleverley -
Jordan Slingerland -
Sebastian Goetze