Data ONTAP Discussions

Highlighted

Advanced Drive Partition

Hi people

I have FAS2750 'Ontap 9.7' with 12*900GB SAS disks and I want to create ADP.

 

when I click option 9 in the node 1, I have this error:

 

This node encountered a disk reservations conflict, and might undergo a
coredump: Offset of supplementary header is 0 at index (0)
giveback.  Your boot menu selection, "9", has been cancelled.
coredump: Erasing supplementary header data index (0).
coredump: Offset of supplementary header is 0 at index (1)
coredump: Erasing supplementary header data index (1).
Reservation conflict found on this node's disks!
 
can anyone help-me ?

best regard,

2 REPLIES 2
Highlighted

Re: Advanced Drive Partition

Give this a try:

1) Choose option 5: Maintenance boot mode and unassign all drives from each node.
remove-ownership:
*>disk remove_ownership all
2) Reboot each node, and then choose option 4 – wipeconfig.
3) Once the wipe is finished, then go with option 9,  system will use ADP on the internal drives and be ready to setup.

 

Thanks!

Highlighted

Re: Advanced Drive Partition

Sounds like node 2 is still up.

 

THe fastest/easiest way to get ADP is to to wipe the system. If that is what you want to do (wipe the system, erase all data, no recovery!!) then do this:

 

  1. Either connect to the console of both controllers
    1. Use a Serial cable or SSH to the service-processor of both controllers and do "system console" from the SP
  2. Get both to the "Special Boot Menu"
    1. If the system is running
      • Halt the node(s)
      • If you are in the controller with SSH, exit and SSH to the Service-Processor
        • From the SP, "system power cycle", then "system console"
        • Press "Control-C" when prompted to skip auto-boot
    2. Now the system should be at the LOADER-X> prompt
      1. From the LOADER-X> prompt: boot_ontap menu
      2. Perform on both nodes.
    3. This will boot to the "Special Boot Menu"
    4. From here you can use option 7 to update the ONTAP code
      1. Put the code (9.xPx_image.tgz) on a web server
      2. use the e0M interface when prompted.
      3. DO NOT reboot when prompted, instead say no. It goes back to the boot menu
      4. Choose option 7 again and follow prompts to grab the code and install
      5. Follow prompts and agree to make it stick for next boot
      6. Repeat on both nodes
      7. Note: this may perform a Firmware update on the Nodes. Let it happen
      8. Note: The system will boot and set the image
      9. Note: Let it start to boot. When prompted, press "Control-C" to access the "Special Boot Menu"
      10. Get both nodes to the same state (i.e. at the Special Boot menu)
    5. At the Boot Menu, select option 9 on BOTH nodes.
    6. Wait for the prompt
    7. On node-1, use Option 9a, agree and WAIT FOR IT TO FINISH!
    8. On node-2, use Option 9a, agree and WAIT FOR IT TO FINISH!
    9. Now the important step, repeat #7 and #8:
      1. On node-1, use Option 9a, agree and WAIT FOR IT TO FINISH!
      2. Note the number of drives that it finds. You say you have 12. Make sure it claims 12 during the process.
      3. On node-2, use Option 9a, agree and WAIT FOR IT TO FINISH!
      4. Note the number of drives that it finds. You say you have 12. Make sure it claims 12 during the process.
      5. If it DID NOT find all 12 drives, you will need to go back to the Boot Menu and use Maintenance Mode (option 5)
      6. From Maintenance Mode, you will likely need to use the "disk removeowner" or "disk resassign" command to either remove all other ownerships or reassign to one node. The goal is to get all the drives either assigned to one of the nodes or no owner at all.
    10. If you are here, then 9a should have completed successfully on both nodes and processed all 12 drives
    11. On node-1, use option 9b, agree to continue
    12. This will reboot node-1 and force the partitions to be created. Wait until you see on the console that drives are partitioning. You may continue at this point. It will finish by ending up at the License agreement for ONTAP.
    13. On node-2, use option 9b, agree to continue
    14. This will reboot node-1 and force the partitions to be created. It will finish by ending up at the License agreement for ONTAP.
    15. You should now have an ADP-base FAS2750 with 6 root partitions for each controller and 6 data partitions for each controller.
      1. You have the options of
        1. leaving as is, using RAID_DP and getting a 3D+2P on each controller, leaving 1 spare each
        2. Assign ALL DATA partitions to one node (all 12!)
        3. You can then create a 9D+2P, leaving 1 spare on the controller with the Data Partitions

Hope this helps!

 

Try the NEW Knowledgebase!
NetApp KB Site
Forums