Our server (ML370G4) running Windows Server 2003 Enterprise with an attached MSA20 crashed (just the OS). We installed Windows Server 2008 Standard on the server. Everything appears fine. We attach the MSA20 and all drives appear, but only the Basic drive is healthy. The other two dynamic drives now appear as foreign.
Does anyone have a method to recover the data from those drives before we convert them to basic?
Thanks for any assistance...
Until that time ... Earl J.
I don't remember being this forgetful when I was younger...
Hello Michael, I have two options in Windows ... convert to basic which kills the data... and now, import ... I'm not sure if that is an available option; I'll check it tomorrow. If I import the drive, will the data come with it - understanding that any data that was open or writing during the crash is now gone... _ _ _ It does appear crazy to me that the program that was used to establish a dynamic drive now can't read it. . . (sigh) _ _ _ Thanks for your help again... until that time ... Earl J.
I don't remember being this forgetful when I was younger...
Okay, I've read the help for the Import Foreign Disks ... it appears that it knows all the disks that are labeled Foreign since when I use the Disks... option, it does correctly identify the three disks we're speaking about here. It also explains in the help about foreign disk import that any volumes that exist among the foreign disks are maintained and become accessible ...
"Here we go. . ."
I'll make one final comment at the conclusion of the import and confirm the results are as expected.
Until that time ... Earl J.
I don't remember being this forgetful when I was younger...
Well, apparently there is a slim chance of a data rescue now. Import Foreign Disk message indicates, "Before using these disks, add them to the system configuration." Checking with the help documentation, both on the computer and online at microsoft, it explains that adding the drives to the system configuration is as simple as using the Import Foreign Disk function...(?) _ _ _
I get to a point just before hitting OK to begin the execution of the Import Foreign Disk function when this warning message appears, "Some volumes will lose data because you have not moved all your disks to this sytem." along with a two item listing indicating that 1 TB will move easily and about 3 TB is corrupted and will lose some data ... (sigh) I'm not sure if all the data is lost or some unknown portion is lost... I can take a chance on some of it being lost - I just don't think all 3 TB is acceptable...
The link: go.microsoft.com/fwlink/?LinkID=64112 indicates the same thing ... _ _ _
Any other ideas about data rescue here? I have until about tomorrow evening to figure something out ... please pass along any ideas or recommendations you might have ... well, other than executing a reliable daily backup... (sigh)
Thanks everyone. . . especially Michael...
Until that time ... Earl J.
I don't remember being this forgetful when I was younger...
as a last resort if you cannot re-install the old OS to the server I have had some success in the past with booting a live Linux distro from CD and mounting external SCSI storage for backup to tape. I last used Ubuntu 10.04 ltsr.
_________________________________________________ How to assign points on this new forum? Click the Kudos Star!
Thanks Greybeard... we'll take a look... I'm over on the Microsoft TechNet trying to get an answer about how much data loss we can expect... We'll reconsider the Windows Server 2003 solution as well... can't hurt to try ...
Until that time ... Earl J.
I don't remember being this forgetful when I was younger...
I've received enough information and advice to close the thread an move on. 1 - We'll look at Server 2003 re-installation again; 2 - We'll wait for feedback from Microsoft forums on how much data we can expect to lose; 3 - We'll consider the Ubuntu solution for capturing the data...
Thanks again to everyone - even if you didn't offer any solutions - for considering our situation and for taking the time to briefly ponder a solution for us.
Until that time ... Earl J.
Please excuse my generous (and erroneous) attitude toward the point system... I'll get better at it... really...
I don't remember being this forgetful when I was younger...
The ML370G4 has been replaced with a DL380G6. We have the proper HP interface card to employ between the HP DL380G6 and our HP MSA20. We eventually had to use File Recovery by LSoft to rescue all our data... it did an excellent job and was very inexpensive. _ _ _ The HP interface card arrived without any drivers. I imagine it will install with the configuration utility. We'll see before long. _ _ _ The plan is to install the card into a DL380G6; connect it to the MSA20; and reconfigure the entire setup before we reinstall the rescued data... I'll come back in a few days with a final wrapup.
Until that time ... Earl J.
I don't remember being this forgetful when I was younger...
Well, never did get a response from MS about how much is "some data loss" ... we went ahead and lost "most" of it... (sigh) we then moved to a rescue operation and found Active@File Recovery from LMSoft most useful for much, much less than we expected to pay for such a wonderful tool. _ _ _ The data is recovered. _ _ _ We moved to the new server HP DL380G6; installed the new HP UltraSCSI interface card that arrived without a driver disk; we connected the HP MSA20 and turned it on first; and then we booted the DL380G6. Nothing happened. The Windows started up and did not recognize the interface card or the MSA20 storage. _ _ _ I used the HP boot disk with the management v. 8.30 software package on it. The ACU does not recognize the card or the MSA20 either. It appears to recognize the riser card and that the slot 2 is occupied, but will not recognize the interface card or the 12 TB MSA20 we have attached through the interface card.
Any suggestions?
Until that time ... Earl J.
I don't remember being this forgetful when I was younger...
Installed the interface card; the DL380G6 will not recognize it... or the MSA20 either. I booted from the HP ACU disk with v. 8.30 of the SmartStart program... will recognize that the controller card (riser card) is populated on slot 2, but will not ID the HP interface card.
I've booted the server with the MSA on and connected to see if it will accept it... nope. I tried turning it off and then back on again to see if the server will recognize it that way... nope.
I guess I'll try HP tech svc on MON...
Until that time ... Earl J.
I don't remember being this forgetful when I was younger...
