You are on page 1of 11

How to forcefully reassign assigned disks on a NetApp

Filer
We had to do some emergency maintenance with a new NetApp
shelf a few days ago and found that because we were working with
an older version of the firmware, there were commands that did
not exist on the filer so we ended up using the GUI and CLI to
work around the problem.
Note: Some of the commands may not be necessary but I
wanted to list all the steps we had to take to get this to
work so I’ve highlighted the steps that is possibly not needed
in RED. Please also take note that we had a small window to
work with so the instructions below may not abide by best
practices.
Task: Disks in the new shelf has been assigned to 2 separate
controllers (6 each).
Problem: We could not find the command to unassign the disks in
this version of the firmware so we had to use the combination of
the GUI and CLI to remove the disk from the controller and then
reassign it to another.
NetApp Information
Filer: Some Name
Model: FAS2020
Version: 7.2.6.1
-----------------------------------------------------------------------------------------------------------------------------------------Initiating a disk show shows the following:

login as: root
root@172.20.1.131's password:
login as: root
root@172.20.1.131's password:

17 FAC01 (135048291) Pool0 XX-XXXXX8015493 0b.18 FAC01 (135048291) Pool0 XX-XXXXX8038093 0b.00.00.16 FAC01 (135048291) Pool0 XX-XXXXX7977866 FAC01> .4 FAC02 (135048330) Pool0 4AD7XX4800009928G98U 0c.00.00.FAC01> disk show DISK OWNER POOL SERIAL NUMBER -----------.------------.29 FAC02 (135048330) Pool0 XX-XXXXX8095049 0b.20 FAC01 (135048291) Pool0 XX-XXXXX8039600 0b.9 FAC01 (135048291) Pool0 4AD7XXHG00009928GDQW 0b.6 FAC02 (135048330) Pool0 3QP0ZC2P00009926HBXK 0c.22 FAC01 (135048291) Pool0 XX-XXXXX8095587 0b.00.00.00.19 FAC01 (135048291) Pool0 XX-XXXXX7977641 0b.00.3 FAC01 (135048291) Pool0 4NE20EC100009928G4P0 0c.24 FAC01 (135048291) Pool0 XX-XXXXX8039114 0b.26 FAC01 (135048291) Pool0 XX-XXXXX8039342 0b.0 FAC02 (135048330) Pool0 4AD7XXC900009928PP3P 0c.00.1 FAC01 (135048291) Pool0 3QP0WZT400009926KCBN 0c.00.5 FAC01 (135048291) Pool0 4NE20FK5000099171W7V 0c.25 FAC02 (135048330) Pool0 XX-XXXXX8039954 0b.21 FAC01 (135048291) Pool0 XX-XXXXX7977856 0b.11 FAC02 (135048330) Pool0 4AD7XX3Q00009925DGCC 0c.27 FAC02 (135048330) Pool0 XX-XXXXX8039645 0b.8 FAC01 (135048291) Pool0 3QP0ZRF100009926HEJT 0c.7 FAC01 (135048291) Pool0 4AD7XXEW00009928GNHA 0c.00.00.----------------0c.2 FAC02 (135048330) Pool0 4AD7XX8G00009928PPLH 0c.10 FAC01 (135048291) Pool0 4NE20JG400009926HEZS 0c.28 FAC01 (135048291) Pool0 XX-XXXXX7978194 0b.23 FAC02 (135048330) Pool0 XX-XXXXX8039807 0b.

prepare (quiet) bus for swap unswap .remove a spare disk swap .undo disk swap and resume service scrub { start stop } .lists disks and owners replace {start [-f] [-m] <disk_name> <spare_disk_name>} {stop <disk_name>} .19 and 0b.assign a disk to a filer or all unowned disks by specifying "all" or <count> number of unowned disks show [-o <ownername> -s <sysid> -n -v -a] .17.What we want to do is move disks: ob. A disk ? shows the following: FAC01> disk ? usage: disk <options> Options are: fail [-i] [-f] <disk_name> . we went into the GUI setting them to remove: the replace but found that commands expect you to be pressed for time to get the to offline these disks by .sanitize one or more disks maint { start abort status list} .replace a file system disk with a spare disk or stop replacing zero spares .Zero all spare disks checksum {<disk_name> all} [-c block zoned] sanitize { start abort status release } .run maintenance tests on one or more disks FAC01> We tried the remove option as well as just as the description specifies. As we were disks reassigned. 0b.fail a file system disk remove [-w] <disk_name> .21 off of FAC01 to FAC02.start or stop disk scrubbing assign {<disk_name> all -n <count> auto} [-p <pool>] [-o <ownername>] [-s <sysid>] [-c blockzoned] [-f] . these moving the spares around.

20 FAC01 (135048291) Pool0 XX-XXXXX8039600 0b.18 FAC01 (135048291) Pool0 XX-XXXXX8038093 0b.2 FAC02 (135048330) Pool0 4AD7XX8G00009928PPLH 0c.----------------0c.22 FAC01 (135048291) Pool0 XX-XXXXX8095587 0b.17 FAC01 (135048291) FAILED XX-XXXXX8015493 0b.00.1 FAC01 (135048291) Pool0 3QP0WZT400009926KCBN 0c.21 FAC01 (135048291) FAILED XX-XXXXX7977856 0b. a disk show now shows the following: FAC01> disk show DISK OWNER POOL SERIAL NUMBER -----------.00.5 FAC01 (135048291) Pool0 4NE20FK5000099171W7V 0c.6 FAC02 (135048330) Pool0 3QP0ZC2P00009926HBXK 0c.0 FAC02 (135048330) Pool0 4AD7XXC900009928PP3P 0c.00.3 FAC01 (135048291) Pool0 4NE20EC100009928G4P0 0c.00.00.10 FAC01 (135048291) Pool0 4NE20JG400009926HEZS 0c.00.9 FAC01 (135048291) Pool0 4AD7XXHG00009928GDQW 0b.00.00.------------.29 FAC02 (135048330) Pool0 XX-XXXXX8095049 .00.00.24 FAC01 (135048291) Pool0 XX-XXXXX8039114 0b.11 FAC02 (135048330) Pool0 4AD7XX3Q00009925DGCC 0c.After removing these 3 disks from the GUI.4 FAC02 (135048330) Pool0 4AD7XX4800009928G98U 0c.00.7 FAC01 (135048291) Pool0 4AD7XXEW00009928GNHA 0c.8 FAC01 (135048291) Pool0 3QP0ZRF100009926HEJT 0c.00.

Volumes must be taken offline. use them only when directed to do so by Network Appliance personnel. we needed to elevate our privileges to advanced: FAC01> priv set advanced Warning: These advanced commands are potentially dangerous. since option disk.17 Note: Disks may be automatically assigned to this node. Are all impacted volumes offline(y/n)?? y FAC01*> disk remove_ownership 0b. Are all impacted volumes offline(y/n)?? y FAC01*> disk remove_ownership 0b.23 FAC02 0b. since option disk. since option disk.16 FAC01 FAC01> (135048330) (135048291) (135048330) (135048291) (135048291) (135048330) (135048291) Pool0 XX-XXXXX8039807 FAILED XX-XXXXX7977641 Pool0 XX-XXXXX8039645 Pool0 XX-XXXXX7978194 Pool0 XX-XXXXX8039342 Pool0 XX-XXXXX8039954 Pool0 XX-XXXXX7977866 Since the disk reassign command can only be run in maintenance mode or during takeover in advanced mode. Volumes must be taken offline. FAC01*> Then we executed: FAC01*> disk remove_ownership 0b.27 FAC02 0b.0b.25 FAC02 0b.19 Note: Disks may be automatically assigned to this node.auto_assign is on.26 FAC01 0b.21 Note: Disks may be automatically assigned to this node. we executed the disk remove_ownership command but before we can execute that command.auto_assign is on. Are all impacted volumes offline(y/n)?? y FAC01*> The following is the output when we execute a disk show after the above commands were completed: .19 FAC01 0b. Volumes must be taken offline.auto_assign is on.28 FAC01 0b.

9 FAC01 (135048291) Pool0 4AD7XXHG00009928GDQW 0b.3 FAC01 (135048291) Pool0 4NE20EC100009928G4P0 0c.26 FAC01 (135048291) Pool0 XX-XXXXX8039342 0b.11 FAC02 (135048330) Pool0 4AD7XX3Q00009925DGCC 0c.00.19 FAC01 (135048291) FAILED XX-XXXXX7977641 0b.00.FAC01> disk show DISK OWNER POOL SERIAL NUMBER -----------.8 FAC01 (135048291) Pool0 3QP0ZRF100009926HEJT 0c.auto_assign is on.00.21 FAC01 (135048291) FAILED XX-XXXXX7977856 0b.5 FAC01 (135048291) Pool0 4NE20FK5000099171W7V 0c.24 FAC01 (135048291) Pool0 XX-XXXXX8039114 0b.7 FAC01 (135048291) Pool0 4AD7XXEW00009928GNHA 0c.22 FAC01 (135048291) Pool0 XX-XXXXX8095587 0b.00. since option disk.00.------------.10 FAC01 (135048291) Pool0 4NE20JG400009926HEZS 0c.00.6 FAC02 (135048330) Pool0 3QP0ZC2P00009926HBXK 0c. Volumes must be taken offline.00.27 FAC02 (135048330) Pool0 XX-XXXXX8039645 0b.16 FAC01 (135048291) Pool0 XX-XXXXX7977866 FAC01> It almost looks like nothing was changed and here’s why: FAC01*> disk remove_ownership 0b.00.00.17 Note: Disks may be automatically assigned to this node.28 FAC01 (135048291) Pool0 XX-XXXXX7978194 0b.00.00.25 FAC02 (135048330) Pool0 XX-XXXXX8039954 0b.17 FAC01 (135048291) FAILED XX-XXXXX8015493 0b.auto_assign is turned on so in order to have these disks remain unassigned.4 FAC02 (135048330) Pool0 4AD7XX4800009928G98U 0c.00. Are all impacted volumes offline(y/n)?? y Notice that the message indicates that disk.20 FAC01 (135048291) Pool0 XX-XXXXX8039600 0b.0 FAC02 (135048330) Pool0 4AD7XXC900009928PP3P 0c.----------------0c.29 FAC02 (135048330) Pool0 XX-XXXXX8095049 0b.23 FAC02 (135048330) Pool0 XX-XXXXX8039807 0b.1 FAC01 (135048291) Pool0 3QP0WZT400009926KCBN 0c. we need to execute the following: .2 FAC02 (135048330) Pool0 4AD7XX8G00009928PPLH 0c.18 FAC01 (135048291) Pool0 XX-XXXXX8038093 0b.

auto_assign changed on one cluster node..change:warning]: Option disk. FAC02*> Now in order to reassign these disks. This value must be the same in both cluster members prior to any takeover or giveback.unfail.auto_assign which applies to both members of the cluster in takeover mode.options.17.17 disk unfail: unfailing disk 0b.19 disk unfail 0b.auto_assign changed on one cluster node.17 disk unfail0b.change:warning]: Option disk. FAC01*> Sun Sep 26 21:28:16 EST [FAC01: raid. or that next takeover/giveback may not work correctly.auto_assign which applies to both members of the cluster in takeover mode.disk.17 Shelf 1 Bay 1 [WDC .FAC01*> options disk.reassim:info]: Disk 0b.cf. or that next takeover/giveback may not work correctly.21 Here’s what the SSH session looks like: FAC01*> disk unfail 0b. we had to unfail it with the command: disk unfail <disk name> disk unfail 0b.options.. Sun Sep 26 21:25:53 EST [PHMSFAC01: reg.cf.auto_assign off You are changing option disk. This value must be the same in both cluster members prior to any takeover or giveback.auto_assign off You are changing option disk. Sun Sep 26 21:25:53 EST [PHMSFAC01: reg. FAC01*> FAC02*> options disk.

00.9 FAC01 (135048291) Pool0 3QP0YVHG00009928GDQW .unfail.------------.----------------0c.. and is now being reassimilated Now that we’ve unfailed the disks as well as turned off disk. FAC01*> Sun Sep 26 21:28:23 EST [FAC01: raid.19 disk unfail: unfailing disk 0b.00.disk.auto_assign.00..17 Volumes must be taken offline. we can execute the remove_ownership command again: FAC01*> disk remove_ownership 0b.00.00.21 disk unfail: unfailing disk 0b.10 FAC01 (135048291) Pool0 3QP10JG400009926HEZS 0c.WD1002FBYS-05ASX NA01] S/N [WD-WMATV8015493] was unfailed.reassim:info]: Disk 0b. Are all impacted volumes offline(y/n)?? y FAC01*> disk remove_ownership 0b.. and is now being reassimilated disk unfail 0b. Are all impacted volumes offline(y/n)?? y FAC01*> disk remove_ownership 0b.0 FAC02 (135048330) Pool0 3QP0YVC900009928PP3P 0c.21 Shelf 1 Bay 5 [WDC WD1002FBYS-05ASX NA01] S/N [WD-WMATV7977856] was unfailed.4 FAC02 (135048330) Pool0 3QP0YV4800009928G98U 0c. Are all impacted volumes offline(y/n)?? y FAC01*> disk show DISK OWNER POOL SERIAL NUMBER -----------.00.00.19 Volumes must be taken offline.reassim:info]: Disk 0b.3 FAC01 (135048291) Pool0 3QP10EC100009928G4P0 0c.21.19.21 Volumes must be taken offline.00.5 FAC01 (135048291) Pool0 3QP10FK5000099171W7V 0c.2 FAC02 (135048330) Pool0 3QP0YV8G00009928PPLH 0c. and is now being reassimilated disk unfail 0b.7 FAC01 (135048291) Pool0 3QP0YVEW00009928GNHA 0c.11 FAC02 (135048330) Pool0 3QP0YV3Q00009925DGCC 0c..00. FAC01*> Sun Sep 26 21:28:27 EST [FAC01: raid.8 FAC01 (135048291) Pool0 3QP0ZRF100009926HEJT 0c.19 Shelf 1 Bay 3 [WDC WD1002FBYS-05ASX NA01] S/N [WD-WMATV7977641] was unfailed.disk.6 FAC02 (135048330) Pool0 3QP0ZC2P00009926HBXK 0c.00.unfail.00.00.1 FAC01 (135048291) Pool0 3QP0WZT400009926KCBN 0c.

27 FAC02 (135048330) Pool0 WD-WMATV8039645 0b.16 FAC01 (135048291) Pool0 WD-WMATV7977866 NOTE: Currently 3 disks are unowned.28 FAC01 (135048291) Pool0 WD-WMATV7978194 0b.19 (S/N WD-WMATV7977641) from unowned (ID -1) to FAC02 (ID 135048330) FAC02*> disk assign 0b.17 Sun Sep 26 21:39:34 EST [FAC02: diskown.22 FAC01 (135048291) Pool0 WD-WMATV8095587 0b.25 FAC02 (135048330) Pool0 WD-WMATV8039954 0b. Posted by Terence Luk at 6:07 PM Email ThisBlogThis!Share to TwitterShare to Facebook Labels: NetApp . The final step is to hop over to the controller that you want to assign the disks and execute the following: FAC02*> disk assign 0b.20 FAC01 (135048291) Pool0 WD-WMATV8039600 0b.21 Sun Sep 26 21:39:43 EST [FAC02: diskown. Sorry about the extra steps I included so they may or may not be required to change assigned disks from one controller to the other.23 FAC02 (135048330) Pool0 WD-WMATV8039807 0b.changingOwner:info]: changing ownership for disk 0b.26 FAC01 (135048291) Pool0 WD-WMATV8039342 0b.29 FAC02 (135048330) Pool0 WD-WMATV8095049 0b.17 (S/N WD-WMATV8015493) from unowned (ID -1) to FAC02 (ID 135048330) FAC02*> disk assign 0b.0b.24 FAC01 (135048291) Pool0 WD-WMATV8039114 0b.18 FAC01 (135048291) Pool0 WD-WMATV8038093 0b.changingOwner:info]: changing ownership for disk 0b. Use 'disk show -n' for additional information. FAC02*> disk assign 0b.21 (S/N WD-WMATV7977856) from unowned (ID -1) to FAC02 (ID 135048330) FAC02*> A disk show now shows the 3 disks being assigned to the other active controller.19 Sun Sep 26 21:39:39 EST [FAC02: diskown.17 disk assign: Assign failed for one or more disks in the disk list.changingOwner:info]: changing ownership for disk 0b. FAC01*> Notice how there are 3 disks stated as being unowned now.

Thanks! -f solved the issue for me after receiving a refurbished disk that we couldn't get to be owned by our systems.5 comments: Anonymous said.. I don't remember whether we tried the command but will definitely try it in the future. Try: FAC01> options disk. Rather fraught way of going about it.. .LMS July 24.19 0b. It was helpful to me. January 26.17 0b. Charlie October 14. But extra typing is one way to keep fingers warm in a data center lol..17 0b.19 0b..21 Done.auto_assign off FAC01> disk assign 0b... Thanks Charlie. Whew. 2013 at 10:36 AM Anonymous said.. .. October 14.. 2010 at 1:37 AM Terence Luk said. Thank you for the post..21 -s unowned -f FAC02> disk assign 0b.. 2012 at 11:25 AM Anonymous said.. 2010 at 9:03 AM Jertek said.

September 30. 2013 at 3:17 AM .