RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)ĭata 1c.27 1c 1 11 FC:B 0 FCAL 10000 272000/557056000 274845/562884296ĭisk replace: Disk is not being replaced. *** You are about to copy and replace the following file system disk *** No error messages saying it cannot be done. Same size, rpm, Pool, and it's even on the same shelf. 1c.29 is the spare disk I am replacing it with. 1c.27 is the disk that is being replaced.
And no mention of what the proper response to the "really replace disk. I figured it must be rare because I can find very few references to the command actually being used. If it's stuck (For mechanical reasons and cannot be removed), please raise a ticket with NetApp I guess (But again it depends if your Hardware is under the support warranty) Normal = The aggregate and all of its RAID groups are functional.
If you run this command : ĭegraded = The aggregate contains at least one RAID group with single disk failure that is not being reconstructed.Ĭopying = The aggregate is currently the target aggregate of an active copy operation. All you have to do is just replace that faulty disk with the new disk and once assigned to the Node (auto/manual), it will become a new spare. That was my first assumption, now coming to 2nd: If you believe that you have a failed disk '1c.27', then you need not do anything the data will be re-constructed into the new 'spare' disk' (Provided there was a 'spare' available). Disk replace command is not a 'soft signal' to eject a drive ( I am assuming this is what you meant?) Sorry if that's not you meant. Once the data is copied 'old disk' is marked spare. 'Disk replace command' is used to logically copy data from one disk to another disk (Example: To swap out mismatched disks from a RAID group), i.e from the active RAID-GROUP Disk to a spare disk which is already available to System.
0 kommentar(er)
