The LUN's are corrupt from the perspective of the HBA itself (any HBA), Emulex HBAanywhere reports the LUN size to be "Not available" and block size to be "Not available". Restoring from backup was the only workaround. I've not encountered a corruption like this kind before, 6 LUN's got lost in this manner.
Suresh
From: Darren Sykes [mailto:Darren.Sykes@csr.com] Sent: Wednesday, December 23, 2009 2:51 AM To: Michael Schipp; Suresh Rajagopalan; toasters@mathworks.com Subject: RE: Fixing corrupted NTFS LUN's
Hmmm, maybe I hadn't thought that one though - you're right in that you'd need an OS which saw the LUN before attempting to recover the partitions on it - assuming you're booting from iSCSI? If you're not, then my original advice stands.
However, that's not to say you couldn't boot into Windows (by whatever means - another physical disk if necessary) then follow my advice re: FDISK /fixmbr or alternate commercial product.
I wouldn't be too hopeful of Linux fixing it - I'd try Windows tools first as I'd think they'd have a better chance of recovering a Windows file system.
The other option that we've followed in the past is recovering the partition table from a snapshot prior to the corruption, assuming you have one. We booted Linux, mounted the LUNS and literally did a direct copy of the MBR.
From: Michael Schipp [mailto:mschipp@asi.com.au] Sent: 23 December 2009 10:21 To: Darren Sykes; Suresh Rajagopalan; toasters@mathworks.com Subject: RE: Fixing corrupted NTFS LUN's
If the disks (read LUNs) do not appear to windows as a disk then a Windows based disk recover tool will also not see the drive to recover - e.g. for these to work it would need to see a disk drive and see no or corrupt file/partition system to fix it.
Suggest you look at an Linux boot CD/DVD that has iSCSI support to see if it can mount it as a NTFS volume. (follow Darren Sykes advise so as not to break it further)
A quick google for a tool to recover LUNs does not look very promising - good luck and please post back if you do find something.
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Darren Sykes Sent: Wednesday, 23 December 2009 8:51 PM To: Suresh Rajagopalan; toasters@mathworks.com Subject: RE: Fixing corrupted NTFS LUN's
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.
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Suresh Rajagopalan Sent: 23 December 2009 07:26 To: toasters@mathworks.com Subject: Fixing corrupted NTFS LUN's
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
From: Suresh Rajagopalan Sent: Tuesday, December 22, 2009 7:38 PM To: toasters@mathworks.com Subject: Cannot see LUNs after server move
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 https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg== .
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
************************************************************************ ************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************ ************