You’d think the LUNs are fine (and the fact they’re actually just a file on the Netapp won’t matter as it’s a file system issue).

 

I assume something like fdisk /fixmbr or the recovery console were no use to you (disclaimer: work on a flexclone or at least make sure you have a snapshot before trying that!)?

 

There are commercial products (such as http://www.partition-recovery.com/) but I can’t vouch for their effectiveness.

 

 

 

 

Following up on my post, we had HBA and path issues causing LUN corruption on several NTFS LUN’s on the original host. As a result, we cannot even see a partition table on the LUN’s. 

 

Are there any utilities to manipulate or repair NTFS LUN files (which are visible as flat files via the CIFS share to the volume)? 

 

Thanks

Suresh

 

 

 

We had a bunch of NTFS LUN's on a server that crashed (2003x64/Snapdrive 4.2.1).  We are trying to move the LUNS to another server(Snapdrive 6/Win2k3x64).  To do this we did the following:

 

1) Unmap old initiator from lun

2) Zone new server to the Netapp filer.

3) Try to use connect disk from new server to the lun

4) This gives a error saying drive notification timeout

 

To debug this more, I  opened Disk Management.  The disks do not show up there either.  But they show up as LUNs under Device manager.  Why do the LUN's show up in Device Manager/Disk drives but not in Disk management?     

 

Thanks

Suresh

 

To report this email as spam click here.