New
#11
DATA 400MB volume is ACTIVE and has the bootmgr and bootmenu. I can't see on which physical disk it is!
DATA 400MB volume is ACTIVE and has the bootmgr and bootmenu. I can't see on which physical disk it is!
Drive J 465GB RAW was always 465GB so whole disk? Was it a "basic" disk in working machine? If you put it back to the other machine it works immediately?
What do you mean by "system dies in 29 minutes"? Crashes, reboots... explain.
yes, when I put it back in other machine it works just fine no data loss. No format required works as it should. The originating machine has a different unrelated issue it shuts off as if it is over heating after 20 or so minutes some times less. I have hardware tech looking at that since it is a separate issue. It was supposed to be simple move the disk that contains the data to a different machine and just keep going. So much for things are supposed to be simple.
For now we are going to deal with the broken machine and keep the drive with that machine. I am aware of others having this same issue and like others the hardware is not broken. That is why I think it is something in the software.
Also I have run every test you can run on the hard drive short of over writing the data to test it. And it pass all test without issue. It helps to work for a storage hardware company from time to time.
Last time I ask you: Assume disk has 2 partitions. Do both partitions become RAW, or becomes whole disk 1 big RAW partition?
Assume the volume letter of RAW volume is R
Do it when volume works and when turned RAW. Compare the output. What's different? Run diskpart from an elevated command prompt Elevated Command PromptCode:diskpart select vol R detail vol detail part exit
Thanks for the responses I know I have annoyed some of you a bit. And this post may do that again. The PC, I had that was shutting off after 20 minutes or less has been repaired (new system board). My IT department was able to get a repair person with the part out on a Saturday, sometimes it is good to work for a large organization. This was the reason I had moved my data disk from the Dell (formerly broken) notebook to my Lenovo notebook and to my server. This was a attempt to keep working with the data on that disk. As everyone who has looked at this thread knows by now the disk was showing up as RAW in both the Server and the Lenovo notebook, except it is a properly fine disk formatted with NTFS and 400GB of data on it. Once the Dell notebook was repaired the exact same disk that was showing up as raw in 2 other systems went back into the Dell and is working perfectly fine.
After speaking with my IT department about this they have said they have seen similar things and have recreated the problem. They moved a disk from a Windows 7 Enterprise machine to a Windows 7 Pro machine or the other way around and the disk shows up as RAW in 1 of the 2 machines and is perfectly serviceable in the other. They are opening a ticket with Microsoft since they are planning to move the data disks from our Dell notebooks to our Lenovo Notebooks that we are upgrading too. If they need to do a data copy or restore every time a simple job starts getting a bit larger.
As a summary a disk that shows as raw in one machine and would require formatting for use in that machine works just fine in its original machine. Take the disk from the machine showing needing formatting place it back where it came from and all the data is intact no issues.
In my case the disk had 1 partition only and was formatted for NTFS, I tried different machines (desktop and Lenovo notebook) and different controllers (Intel and Marvel) even recreated the problem with a drive from a different manufacturer (Seagate and Hitachi). I tried different SATA controllers, different SATA speeds SATA II and SATA III. I even tried a LSI mega raid card set as JBOD. No matter what I tried the drive always showed as RAW in these systems, but always worked when put back in the original system. By doing all of these things I was eliminating different points of hardware or firmware as being the issue. The only thing left is software and the common software in this case is Windows 7, that is why my IT department will be opening a ticket with Microsoft.
Thank you to everyone who tried to help, I had been hoping someone had found a way around this issue that did not involve formatting or using data recovery software, it appears no one has. I am always looking for the root cause and just formatting or re-booting is not root cause. I want to know why I have to re-boot or format because if I do not know I should just expect to see this issue again. Once I learn something from my IT department I will post in this thread again.