EVA

[Sandeep Sanjao Figer]

Hi,

I have HP EVA 5000 with Windows & Linux hosts on it. As my linux waus non production server, I had it on Raid 0 & so it crashed as one of the disk failed in the EVA. This infact has confused me protection level (None, 1,2) concept of EVA as well & raid functionality on EVA as it went into inoperative state. After inserting new Disk & rebuild, I could not access Linux Vdisks which I later deleted of the SAN. I created another same size partition now but on Raid 5. After taking out entry from fstab on linux box for the volume mounted of the earlier SAN crashed disks, I restarted the Red hat Es 3.0 linux server. It gets stuck at the old crashed volume mount & comes at maintenance promptI am not an Linux expert & so not sure how to get rid of this mount. I am okay with no data recovery of the same as I can use the new Vdisk presented for fresh mount. The earlier mount was LVM with two vdisks of the SAN. If i do lssd, i can see one sda entry but not sure what do next & way to mount it for linux & also to take entry out permanently for earlier crashed mount disk. Any help is appreciated.

I have posted the same question on Linux as weel & so hoping to get quick fix.

Thanks,
Sandy

[Uwe Zessin]

Sandy,
unfortunately, there is no 'fix'. The data of the failed disk is gone.

The disk protection level defines how much space is reserved for recovery - think of it as a distributed spare disk.

For VRAID-0, there is simply no redundancy generated, no matter what protection level you use.