ignite 发表于 2012-02-01 14:12

EVA8000磁盘损坏，但不在upgroup中

EVA8000磁盘损坏，但不在upgroup中，重启SMA也没有用，cmv中是failed的状态，ungroup中没有出现该盘，能直接拔出更换吗？

lbseraph 发表于 2012-02-01 20:58

看对应的disk group是否还有该盘，没有的话就可以拔掉更换~如果那个disk group还在做reconstruction的话，需要等它做完之后才能更换~

ignite 发表于 2012-02-06 10:51

disk group中坏盘还在，只是状态为failed，打个红X，好几天了，重构应该做完了，记得以前重启一下cmdview就可以在ungroup中看到，这回居然不行，郁闷。

chinadns 发表于 2012-02-07 15:50

Check the controller log and SSSU to find out why the migration is blocked. Make sure there is enough free space available to perform the migration. If there is, see if the failing drive is logging the following error:

3/11/00 FRU=81 Physical disk drive: 2000001d387a67340000000000000000; Port ID: DP-1B; Enclosure: 8.; Bay: 2.; AL_PA: 0x00bc; Sense Key: 3 (MEDIUM ERROR); ASC: 0x11 ASCQ: 0x00 (Unrecovered read error); FRU Code: 0x81

If the drive you are trying to ungroup is logging the unrecovered read errors, that is what is blocking the migration. The data cannot be migrated off of this drive since the data cannot be read. To recover from this, you must pull this drive. Pulling the drive will cause a reconstruct to start. The reconstruct will recreate the data from parity.

Due diligence must be preformed before you pull a drive from a disk group. You must make sure that there are no Raid 0 vdisks, and that no reconstruct, migration or reverting is in progress on the disk group containing the failing drive. If there is any question about this please engage EVA support before pulling the drive.


ignite 发表于 2012-02-07 16:02

没有去看控制器的日志，会不会因为这个disk group只有8块盘，EVA要求最小配置的原因而导致无法ungroup？

chinadns 发表于 2012-02-07 16:54

8块盘的DG可以坏到6块

lbseraph 发表于 2012-02-07 20:16

不是所有情况都可以看到坏盘被踢出来放在Ungrouped disks的文件夹里的，要确认的话用SSSU查一下该盘还有没有数据在上面，如果是0%的话那么可以直接拔掉该盘正常换就行~

ignite 发表于 2012-02-09 11:02

本帖最后由 ignite 于 2012-02-09 11:03 编辑

谢谢各位的解答。
页: [1]
查看完整版本: EVA8000磁盘损坏，但不在upgroup中