Q. I just cloned my HDD with a Samsung 840 SSD to be used for my HP DM3 Pavilion laptop. After I installed the SSD into my laptop, I checked everything and they seemed to be fine and work faster. One problem I noticed is that now I lose the capability to restore the laptop to its original factory condition with the new SSD. It worked fine with the just removed HDD. When I tried to restore the laptop to its original factory condition, it asked me for some sort of a restore disk, instead of just using drive D: where the original Windows 7 and its operation conditions are located. I appreciate it if anyone knows what the reason is for this. Thank you.
A. Hi..
I have a cloned drive and factory restore work's fine...
I tried several clone applications to get to this point (Norton Ghost etc ) and the manufactures factory restore failed to work...
Easeus Disk Copy worked and all is now fine , it will mean creating a boot disc of the clone application.....
But the free disc copy clone application has no options to resize partitions....
So used another Easeus freebie "Partition magic" (No data loss)....
PS......
For your recovery partitions to work every partition contained on the original drive must be coped !
And if resized must be done with out data loss...(NOT windows disc management )
I have a cloned drive and factory restore work's fine...
I tried several clone applications to get to this point (Norton Ghost etc ) and the manufactures factory restore failed to work...
Easeus Disk Copy worked and all is now fine , it will mean creating a boot disc of the clone application.....
But the free disc copy clone application has no options to resize partitions....
So used another Easeus freebie "Partition magic" (No data loss)....
PS......
For your recovery partitions to work every partition contained on the original drive must be coped !
And if resized must be done with out data loss...(NOT windows disc management )
When SSD or HDD drive get crashed where does data goes?
Q. When SSD or HDD drive get crashed where does data goes? In which part of the drive does those data stays so the recovery softwares can pull them back?? Does the place varies from SDD to HDD?
A. At crash the data can still be somewhere on the drive be lost for good.
If the drive was working when it crashed it's really a crapshoot wheter the data will be lost for good or if it gets dumpled to the folder where it was taken from.
If you're using data recovery SW just scan the whole drive.
If the drive was working when it crashed it's really a crapshoot wheter the data will be lost for good or if it gets dumpled to the folder where it was taken from.
If you're using data recovery SW just scan the whole drive.
Does raid 0 configuration actually increase individual hard drive failure probability?
Q. I know that having two hard drives in raid 0 increases the overall failure rate just because you have two hard drives, of which if one goes down the other is useless, but how often does a hard drive or ssd indovidually actually fail?
Does putting a hdd or ssd in raid 0 or any raid configuration actually increase it's probability of failure?
Does putting a hdd or ssd in raid 0 or any raid configuration actually increase it's probability of failure?
A. SHORT ANSWER:
No, putting a drive into a Raid doesn't increase it's own probability of failure. And while modern drives don't fail frequently, the DO fail. The chances go up the longer you use them, either due to wear-and-tear (HDDs / hybrids), or because eventually the memory cells in SSDs start hitting their maximum wear-level.
LONG ANSWER:
As you probably already know, Raid 0 is striping, meaning that if you write a 100K file to your raid, it "stripes" that file across both drives. 50K on one drive, 50K on the other. Raid 0 does this for every file it stores.
The main advantage to Raid0 is that both drives are involved in reading and writing files, which speeds up reads and writes significantly. It's a Raid configuration designed for speed, not reliability.
The main disadvantage... is that files are always split up onto both drives in stripes. If you lose either drive, then the whole Raid 0 is dead - you just lost ALL of your data, unless you have some pretty-good data-recovery software than can rebuild raids.
A few years back I (stupidly) based my whole computer on a 3-way Raid 0 array, with 3 330GB drives. It ran as fast as lightning (this pretty-much predated SSDs), and for the 2-3 years I ran it, I experienced multiple system crashes, power failures, etc. without the array ever failing. That was probably half luck, and half good quality components (WD black drives, good quality motherboard with reliable bios, etc.).
One day while formatting a new separate drive, I accidentally picked the wrong drive and started formatting part of my Raid 0. I hit the power switch immediately but the damage was done - my Raid 0 was fried. Luckily I was able to manually reconstruct the Raid with a recovery tool ( if you're interested in the tool, see http://www.r-studio.com/ ), and recovered about 75% of my data. But it was a painful, painful process.
Bottom-line: I wouldn't recommend raid-0 unless you're really desperate for speed beyond what SSDs can provide, and you are either prepared to backup your data regularly, or you don't mind taking risks.
Cheers;
Wire
No, putting a drive into a Raid doesn't increase it's own probability of failure. And while modern drives don't fail frequently, the DO fail. The chances go up the longer you use them, either due to wear-and-tear (HDDs / hybrids), or because eventually the memory cells in SSDs start hitting their maximum wear-level.
LONG ANSWER:
As you probably already know, Raid 0 is striping, meaning that if you write a 100K file to your raid, it "stripes" that file across both drives. 50K on one drive, 50K on the other. Raid 0 does this for every file it stores.
The main advantage to Raid0 is that both drives are involved in reading and writing files, which speeds up reads and writes significantly. It's a Raid configuration designed for speed, not reliability.
The main disadvantage... is that files are always split up onto both drives in stripes. If you lose either drive, then the whole Raid 0 is dead - you just lost ALL of your data, unless you have some pretty-good data-recovery software than can rebuild raids.
A few years back I (stupidly) based my whole computer on a 3-way Raid 0 array, with 3 330GB drives. It ran as fast as lightning (this pretty-much predated SSDs), and for the 2-3 years I ran it, I experienced multiple system crashes, power failures, etc. without the array ever failing. That was probably half luck, and half good quality components (WD black drives, good quality motherboard with reliable bios, etc.).
One day while formatting a new separate drive, I accidentally picked the wrong drive and started formatting part of my Raid 0. I hit the power switch immediately but the damage was done - my Raid 0 was fried. Luckily I was able to manually reconstruct the Raid with a recovery tool ( if you're interested in the tool, see http://www.r-studio.com/ ), and recovered about 75% of my data. But it was a painful, painful process.
Bottom-line: I wouldn't recommend raid-0 unless you're really desperate for speed beyond what SSDs can provide, and you are either prepared to backup your data regularly, or you don't mind taking risks.
Cheers;
Wire
Powered by Yahoo! Answers
