ONTAP Hardware
ONTAP Hardware
Hi everyone,
I'm in a big truoble. I've got 4 spare disks, but my raid i degraded. How can I solve this?
I'm using FAS3020 wits system 7.2.6
NETAPP> sysconfig -r
Aggregate aggr0 (online, raid_dp, degraded) (block checksums)
Plex /aggr0/plex0 (online, normal, active)
RAID group /aggr0/plex0/rg0 (normal)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0c.16 0c 1 0 FC:B - ATA 7200 423111/866531584 423889/868126304
parity 0c.18 0c 1 2 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.21 0a 1 5 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.17 0c 1 1 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.28 0c 1 12 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.26 0a 1 10 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.25 0c 1 9 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.24 0c 1 8 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.23 0c 1 7 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.22 0c 1 6 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.20 0c 1 4 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.19 0c 1 3 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.29 0a 1 13 FC:A - ATA 7200 423111/866531584 423889/868126304
RAID group /aggr0/plex0/rg1 (normal)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0a.32 0a 2 0 FC:A - ATA 7200 423111/866531584 423889/868126304
parity 0c.33 0c 2 1 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.34 0c 2 2 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.35 0a 2 3 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0a.36 0a 2 4 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.37 0c 2 5 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.38 0c 2 6 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.39 0a 2 7 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0a.40 0a 2 8 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.41 0c 2 9 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.42 0c 2 10 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.43 0c 2 11 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.44 0c 2 12 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.58 0c 3 10 FC:B - ATA 7200 423111/866531584 423889/868126304
RAID group /aggr0/plex0/rg2 (degraded)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0c.57 0c 3 9 FC:B - ATA 7200 423111/866531584 423889/868126304
parity 0c.49 0c 3 1 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.27 0c 1 11 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.48 0c 3 0 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.60 0c 3 12 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.45 0c 2 13 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.51 0c 3 3 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.50 0c 3 2 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.56 0c 3 8 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.54 0a 3 6 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.52 0c 3 4 FC:B - ATA 7200 423111/866531584 423889/868126304
data FAILED N/A 423111/866531584
Aggregate aggr1 (online, raid_dp) (block checksums)
Plex /aggr1/plex0 (online, normal, active)
RAID group /aggr1/plex0/rg0 (normal)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0c.64 0c 4 0 FC:B - ATA 7200 847555/1735794176 847827/1736350304
parity 0a.70 0a 4 6 FC:A - ATA 7200 847555/1735794176 847827/1736350304
data 0c.75 0c 4 11 FC:B - ATA 7200 847555/1735794176 847827/1736350304
data 0a.68 0a 4 4 FC:A - ATA 7200 847555/1735794176 847827/1736350304
data 0c.67 0c 4 3 FC:B - ATA 7200 847555/1735794176 847827/1736350304
data 0a.72 0a 4 8 FC:A - ATA 7200 847555/1735794176 847827/1736350304
data 0c.65 0c 4 1 FC:B - ATA 7200 847555/1735794176 847827/1736350304
data 0c.76 0c 4 12 FC:B - ATA 7200 847555/1735794176 847827/1736350304
data 0a.69 0a 4 5 FC:A - ATA 7200 847555/1735794176 847827/1736350304
data 0a.74 0a 4 10 FC:A - ATA 7200 847555/1735794176 847827/1736350304
data 0c.73 0c 4 9 FC:B - ATA 7200 847555/1735794176 847827/1736350304
data 0a.66 0a 4 2 FC:A - ATA 7200 847555/1735794176 847827/1736350304
data 0c.71 0c 4 7 FC:B - ATA 7200 847555/1735794176 847827/1736350304
data 0a.61 0a 3 13 FC:A - ATA 7200 847555/1735794176 847827/1736350304
Spare disks
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
Spare disks for block or zoned checksum traditional volumes or aggregates
spare 0a.59 0a 3 11 FC:A - ATA 7200 847555/1735794176 847827/1736350304
spare 0a.77 0a 4 13 FC:A - ATA 7200 847555/1735794176 847827/1736350304
spare 0c.53 0c 3 5 FC:B - ATA 7200 847555/1735794176 847827/1736350304
spare 0c.55 0c 3 7 FC:B - ATA 7200 847555/1735794176 847827/1736350304
Solved! See The Solution
I believe I found it. Replacing 500GB disk with 1TB disk will cause total physical capacity of aggregate to exceed 16TB and this is not allowed in Data ONTAP 7.2 You actually must have seen "The reconstruction cannot start in RAID group [raid group]: Operation would make volume too big" in logs ...
So yes, replacing one of 1TB spare disks with 500GB disk would help in this case. Or you could upgrade to 7.3 which does not count parity disks against total physical capacity ...
I agree with Jeras's assesment.
If this is a HA pair you can check to see if the partner has any of the smaller disks spare and re-assign the disk to the filer in question (providing you are using software based disk ownership)
On the partner you would run:
> disk assign <spare_disk_name> -o <name_of_filer_with_degrated_raid> -f
additionally, if you dont get a disk assigned soon you might want to adjust the options raid.timeout value so your storage system does not halt after 24 hours:
https://kb.netapp.com/support/index?page=content&id=3010870&actp=LIST_POPULAR
Thanks for your answers. Let's see if I understand what I must do:
Firsrt find the broken disk. Not easy, because all lights on netapp are green.....
When I localize them, the commands are like this?
disk assign <0a.50> -o <nnetapp.bdn.....> -f
But when I try to use the comand "disk assign" console says that disk: Did not recognize option "assign".
My netapp version is 7.2.6.1
Thanks.
Disk size is OK in this case - NetApp selects disk of same size or larger as replacement. Given that disk types and RPM seem to match, the only explanation would be different pool. Please, paste output of "disk show -v". Please use CODE tags so it is readable.
Hi again,
Sorry, I don't know what are code tags. What do you mean. I'll help in anything.
Seems that "dsik show -v" doesn't work. I've tried to use "sysconfig -v", and i'll get this.
Options are:
fail [-i] [-f] <disk_name> - fail a file system disk
remove [-w] <disk_name> - remove a spare disk
swap - prepare (quiet) bus for swap
unswap - undo disk swap and resume service
scrub { start | stop } - start or stop disk scrubbing
replace {start [-f] [-m] <disk_name> <spare_disk_name>} | {stop <disk_name>} - 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 } - sanitize one or more disks
maint { start | abort | status | list} - run maintenance tests on one or more disks
NETAPP> sysconfig -v
NetApp Release 7.2.6.1P2: Wed Jan 21 04:38:40 PST 2009
System ID: 0101199841 (NETAPP)
System Serial Number: 2077001 (NETAPP)
System Rev: B1
slot 0: System Board 2797 MHz (NetApp System Board X a2)
Model Name: FAS3020
Part Number: 110-00081
Revision: a2
Serial Number: 0406456
Firmware release: CFE 3.1.0
Agent FW version 15
LCD FW version 1.7
Processors: 2
Memory Size: 2048 MB
slot 0: Dual 10/100/1000 Ethernet Controller VI
e0a MAC Address: 00:a0:98:08:fd:2a (auto-1000t-fd-up)
e0b MAC Address: 00:a0:98:08:fd:2b (auto-unknown-down)
e0c MAC Address: 00:a0:98:08:fd:28 (auto-unknown-down)
e0d MAC Address: 00:a0:98:08:fd:29 (auto-unknown-down)
Device Type: Rev 3
slot 0: FC Host Adapter 0a (Dual-channel, QLogic 2322 rev. 3, 64-bit, L-port, <UP>)
Firmware rev: 3.3.27
Host Loop Id: 7 FC Node Name: 5:00a:098200:01be8e
Cacheline size: 16 FC Packet size: 2048
SRAM parity: Yes External GBIC: No
Link Data Rate: 2 Gbit
ID Vendor Model FW Size
16: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
17: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
18: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
19: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
20: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
21: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
22: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
23: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
24: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
25: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
26: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
27: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
28: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
29: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
32: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
33: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
34: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
35: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
36: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
37: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
38: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
39: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
40: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
41: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
42: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
43: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
44: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
45: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
48: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
49: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
50: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
51: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
52: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
53: HITACHI HDE721010SLA33SX A3BC 847.5GB (1953394092 512B/sect)
54: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
55: HITACHI HDE721010SLA33SX A3BC 847.5GB (1953394092 512B/sect)
56: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
57: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
58: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
59: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
60: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
61: HITACHI HUA722010ALA33SX NA01 847.5GB (1953394092 512B/sect)
64: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
65: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
66: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
67: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
68: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
69: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
70: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
71: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
72: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
73: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
74: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
75: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
76: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
77: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
Shelf 1: AT-FCX Firmware rev. AT-FCX A: 37 AT-FCX B: 37
Shelf 2: AT-FCX Firmware rev. AT-FCX A: 37 AT-FCX B: 37
Shelf 3: AT-FCX Firmware rev. AT-FCX A: 38 AT-FCX B: 38
Shelf 4: AT-FCX Firmware rev. AT-FCX A: 38 AT-FCX B: 38
slot 0: FC Host Adapter 0b (Dual-channel, QLogic 2322 rev. 3, 64-bit, L-port, <OFFLINE (hard)>)
Firmware rev: 3.3.27
Host Loop Id: 0 FC Node Name: 5:00a:098300:01be8e
Cacheline size: 16 FC Packet size: 2048
SRAM parity: Yes External GBIC: No
Link Data Rate: 1 Gbit
slot 0: FC Host Adapter 0c (Dual-channel, QLogic 2322 rev. 3, 64-bit, L-port, <UP>)
Firmware rev: 3.3.27
Host Loop Id: 7 FC Node Name: 5:00a:098000:01be8e
Cacheline size: 16 FC Packet size: 2048
SRAM parity: Yes External GBIC: No
Link Data Rate: 2 Gbit
ID Vendor Model FW Size
16: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
17: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
18: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
19: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
20: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
21: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
22: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
23: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
24: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
25: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
26: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
27: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
28: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
29: NETAPP X267_SGLXY500SSX AQJZ 423.1GB (976642092 512B/sect)
32: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
33: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
34: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
35: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
36: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
37: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
38: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
39: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
40: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
41: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
42: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
43: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
44: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
45: NETAPP X267_HGEMIT50SSX A90A 423.1GB (976642092 512B/sect)
48: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
49: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
50: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
51: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
52: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
53: HITACHI HDE721010SLA33SX A3BC 847.5GB (1953394092 512B/sect)
54: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
55: HITACHI HDE721010SLA33SX A3BC 847.5GB (1953394092 512B/sect)
56: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
57: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
58: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
59: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
60: NETAPP X267_SMOOST50SSX NA01 423.1GB (976642092 512B/sect)
61: HITACHI HUA722010ALA33SX NA01 847.5GB (1953394092 512B/sect)
64: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
65: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
66: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
67: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
68: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
69: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
70: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
71: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
72: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
73: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
74: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
75: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
76: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
77: WDC WD1002FBYS-05ASX NA01 847.5GB (1953394092 512B/sect)
Shelf 1: AT-FCX Firmware rev. AT-FCX A: 37 AT-FCX B: 37
Shelf 2: AT-FCX Firmware rev. AT-FCX A: 37 AT-FCX B: 37
Shelf 3: AT-FCX Firmware rev. AT-FCX A: 38 AT-FCX B: 38
Shelf 4: AT-FCX Firmware rev. AT-FCX A: 38 AT-FCX B: 38
slot 0: FC Host Adapter 0d (Dual-channel, QLogic 2322 rev. 3, 64-bit, L-port, <OFFLINE (hard)>)
Firmware rev: 3.3.27
Host Loop Id: 0 FC Node Name: 5:00a:098100:01be8e
Cacheline size: 16 FC Packet size: 2048
SRAM parity: Yes External GBIC: No
Link Data Rate: 1 Gbit
slot 0: SCSI Host Adapter 0e (Adaptec AIC7892, <ONLINE>)
HW Version 0.0
Ultra160 SCSI, Low Voltage Differential
slot 0: NetApp ATA/IDE Adapter 0f (0x000001f0)
0f.0 NACF1GBJ U-A11 5-04 977MB 512B/sect (STI1J7e607054181221)
slot 1: NVRAM (NetApp NVRAM V)
Revision: B1
Serial Number: 536545
Memory Size: 512 MB
Battery Status: OK (4068 mV)
Charger Status: OFF
Running Firmware: 5 (2.0.0)
Cluster Interconnect Port 1: disconnected
Cluster Interconnect Port 2: disconnected
Commands do not work because you have hardware based disk ownership, so disk assignment is moot. This is single node system so pool should not really matter either. Did you try manually starting "disk replace" for failed disk?
Unfortunately to say anything one would need to fetch logs and analyze them. I suggest you open case with NetApp to investigate.
Hi,
Netapp only helps with my Fas2240 (I've two netapp series) ,but with FAS3020 they said is too old for opening a case. I'll try this, but I need some help:
replace {start [-f] [-m] <disk_name> <spare_disk_name>}
Spare disk name is easy, but:
How can I know wich one is the falied disk? I'm not able to find this one i my system.
Thanks again.
Indeed. You have 56 good disks (including spares) and one "broken". Do you have ASUP from the time before disk failure?
Yes, I've got ASUP before disk failure but not right now. I've got ASUP actually with my FAS2240, but not with that one.
What will happen if I'll try this:
aggr0 has no spare disks. Can I try to add spare disks to the Volume where aggr0 is found, and then add a disk to aggr0?
How can I add a disk to a volume?
or
How can I force a spare disk on an aggr0?
Does sysconfig -r not show you "Broken Disks"?
No, only saiysfailed disk as you can see, but no info about which one
RAID group /aggr0/plex0/rg2 (degraded)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0c.57 0c 3 9 FC:B - ATA 7200 423111/866531584 423889/868126304
parity 0c.49 0c 3 1 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.27 0c 1 11 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.48 0a 3 0 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.60 0c 3 12 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.45 0a 2 13 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.51 0c 3 3 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0a.50 0a 3 2 FC:A - ATA 7200 423111/866531584 423889/868126304
data 0c.56 0c 3 8 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.54 0c 3 6 FC:B - ATA 7200 423111/866531584 423889/868126304
data 0c.52 0c 3 4 FC:B - ATA 7200 423111/866531584 423889/868126304
data FAILED N/A 423111/866531584
There is usually another section (before "Spare Disks" if memory serves) called Broken Disks which would contain the disk id.
Do you have a copy of the ASUP that was generated, if not try looking through the message log to see if it stated which disk failed
rdfile /etc/messages
Try aggr status -f to see if the failed disk shows there with the disk ID.
Ken
Just says empty
NETAPP> aggr status -f
Broken disks (empty)
😞
aggr0 has no spare disks.
spares are always global; they do no belong to aggregate.
How can I force a spare disk on an aggr0?
You can't add disk to aggregate as spare. You can add disk as additional data/parity, but that does not help in this case. Looking at logs (starting) at the time of disk failure may give some hints.
I beg to differ. The size of the disk is NOT ok in this case. The RAID group with the failed disk has smaller disks than the size of the spares. Data ONTAP will not automatically grab a larger spare drive to replace a failed smaller disk because it would result in the larger spare disk being downsized in this case. You have to manually force the swap. If the dual parity disk was at the same size as the larger spare, then the larger spare disks would be grabbed automatically. That's not the case here. The error message that ONTAP is displaying in this case is because it is looking for the same size disk as a spare and there are none and it won't use the larger spares automatically because it will result in the disk being downsized.
Ken
Data ONTAP will not automatically grab a larger spare drive to replace a failed smaller disk because it would result in the larger spare disk being downsized in this case.
Yes. And where is the problem? https://kb.netapp.com/support/index?page=content&id=3013616&locale=en_US
I believe I found it. Replacing 500GB disk with 1TB disk will cause total physical capacity of aggregate to exceed 16TB and this is not allowed in Data ONTAP 7.2 You actually must have seen "The reconstruction cannot start in RAID group [raid group]: Operation would make volume too big" in logs ...
So yes, replacing one of 1TB spare disks with 500GB disk would help in this case. Or you could upgrade to 7.3 which does not count parity disks against total physical capacity ...
You're right!!!
I've replaced one of 1TB spare disks with 500GB disk and it works. Now netapp is rebuilding..
Thanks
Martí.