Virtual Disk Access

Question

Hi,

I apoligize if I'm posting in the wrong forum, but I am having issues accessing a virtual disk built from a RAID group in my MD3000. I had a nominal amount of free capacity in a RAID group, so I created a virtual disk to access via my Windows host (using the Microsoft iSCSI Initiator built in to Windows 7). I created the mapping (non-shared), presented the LUN to my host, initialized the disk in Windows and created a basic partition formatted with NTFS. This has worked fine until I changed hosts.

Anyway, the hard drive in said host died, so I swapped a new HDD in and rebuilt Windows. I added the new host using the MD Storage Manager, broke the host-to-disk mapping between the original host and virtual disk, and created a new mapping using the 'new' host. I presented the LUN to the new host, but Disk Management sees the drive as un-initialized.

Do I have any shot at recovering the data I stored?

Dev Mgr · Answer

What OS is on the 'new' system that you're trying to connect with?

Also, as you're using desktop OSes, is the new system connecting to the controller that owns the virtual disk? With server OSes (that have the MD3000i multipathing software installed on them), you would connect to both controllers and the server would see the disk through whichever controller owns the disk, but the MPIO driver won't install on desktop OSes, so if your desktop OS is connecting to controller 0, but the virtual disk is currently owned by controller 1, I could see something like this happening.

arcticsnopro · Answer

D'oh! Never thought of that. I connected the initiator to the wrong controller (using Windows 7 on this host, as well). :emotion-10: Thanks, Dev Mgr!

PowerVault

Virtual Disk Access

Was this post helpful?