Ok, here we go. One of my people has a slave drive that he uses to store archived emails. We normally store them on the network but due to the massive amount of them, someone decided it was a good idea to store them on a sperate local drive and pray it doesn’t die. Well guess what, it died. Upon boot up, it first came up with a “drive[the slave] needs to be checked” prompt. I let it go and that did not complete. I next rebooted and skipped that scan and that’s when Windows froze while trying to boot up. I disconencted the archive drive and Windows came up. I’m now trying to revive the archive drive. I have a 3rd drive identical to the archive and recreated the situation, trying to copy the MBR from the good one to a file and deploy it onto the bad one. While the deploy went ok, the data won’t come back. With the good MBR, the slave will come up in Windows with a drive letter, but says “needs to be formatted” and that would kinda defeat the purpose of recovery efforts. I have stared at this MBR for the past 3 days straight as to why the good drive’s MBR works but not when copied to the slave. Again, they are the exact same model. Searching for backup MBRs with recovery programs finds nothing. I’m starting to think it’s not the MBR at all. Can anyone give me any suggestions?
