Seagate 7200.11

[macman]

Recoveries on these drive with motor seizure. I have recovered from these before. They are easy as long as you know what you are doing. Not for the average computer user.

[Doomer]

for this model it very hard to make DR. What I'm trying to say - if it's seized motor - your data is gone

Are you saying you can't recover from this fault? Or are you saying he can't recover from this fault? Anyway I made a full recovery on on this exact same model with a seized motor a few weeks ago.

Good for you, we have houndreds of them
Statistics shows they not as easy as before

[HDD Spaz]

Your post indicated that you could not recover them. I thought that wasn't correct given you people have inside info . I agree, they are more difficult than the 7200.8,9,10's. The 7200.11 500 GB only has two platters so the data density must make things a little more difficult.

[Doomer]

Your post indicated that you could not recover them.

It's hard but possible. Unfortunately not on all of them

[HDD Spaz]

Your post indicated that you could not recover them.

It's hard but possible. Unfortunately not on all of them

Thats makes me feel good. Maybe I am a guru afterall

Why are these more difficult? Is head alignment an issue with these?

[hddguy]

I am currently recovering a platterswap on a 500GB 7200.11. Only problem is drive has many damaged sectors, and a XFS filesysem and client needs Virtual MAchine VMDK files, around 300GB, so the fat lady aint quite singing yet......

[Doomer]

Why are these more difficult? Is head alignment an issue with these?

They changed SA architecture
It is more like SCSI drives now. If you recovered Seagate SCSI drives before you would know what I mean

[HDD Spaz]

The ones I did done had quite a few bads, i was lucky, I could use data compass to extract what I needed. I take it you are cloning it, what are you using? Might be a good idea to keep some parts on standby. Fingers crossed they won't be needed.

[Doomer]

I am currently recovering a platterswap on a 500GB 7200.11. Only problem is drive has many damaged sectors, and a XFS filesysem and client needs Virtual MAchine VMDK files, around 300GB, so the fat lady aint quite singing yet......

sometimes VM files stored uncompressed and they basically drive images and you still can recover them logically after

[hddguy]

Im pretty sure UFS explorer supports these VMDK files....

[bestvex]

As I don't care to much about the drive or the data on it I went and opened it.
And no surprise, I found the motor seized, but it's completely frozen!
I kept the disks, just in case I'll ever need to recover something...

[HDD Spaz]

you kept the disks? Did you dispose of the rest of the hard drive? Depending on how you answer this question it will have a direct result of the amount of people laughing at you.

[N.C.]

I am currently recovering a platterswap on a 500GB 7200.11. Only problem is drive has many damaged sectors, and a XFS filesysem and client needs Virtual MAchine VMDK files, around 300GB, so the fat lady aint quite singing yet......

XFS is a good recoverable fs.
You should use sparse files for saving xfs_repair changes if you unsure about the result.
This is not a problem, i think...

Regards,
Janos

[bestvex]

I actually disposed the standard answer I have for standard smart arses... not wort it

[hddguy]

I actually disposed the standard answer I have for standard smart arses... not wort it

Now I bet everyone is wondering what that answer is!!

[hddguy]

It is more like SCSI drives now. If you recovered Seagate SCSI drives before you would know what I mean

Are you referring to a translator SCSI issue where capacity is 0? Much the same type of fault as the 7200.11 capacity 0 issue?

[HDD Spaz]

Did you remove the platters from the hard drive? Not being a smart arse, what you said indicated you had and you plan to keep them just in case you want the data. If you have done this.....

1. It was Stupid.
2. Data is Gone For Good.

Why did you open it? You can't RMA it now. That again was stupid if the data is worthless.

[Doomer]

It is more like SCSI drives now. If you recovered Seagate SCSI drives before you would know what I mean

Are you referring to a translator SCSI issue where capacity is 0? Much the same type of fault as the 7200.11 capacity 0 issue?

I'm not reffering only to this but BTW the problem is exactly the same
I'm talking more of internal issues (heads, platters transplants)

[gsustek]

It is more like SCSI drives now. If you recovered Seagate SCSI drives before you would know what I mean

Are you referring to a translator SCSI issue where capacity is 0? Much the same type of fault as the 7200.11 capacity 0 issue?

I'm not reffering only to this but BTW the problem is exactly the same
I'm talking more of internal issues (heads, platters transplants)

Is it some software to repair this 0 LBA for 30 $ or something? like hdd unlock, one time?

[HDD Spaz]

It is more like SCSI drives now. If you recovered Seagate SCSI drives before you would know what I mean

Are you referring to a translator SCSI issue where capacity is 0? Much the same type of fault as the 7200.11 capacity 0 issue?

I'm not reffering only to this but BTW the problem is exactly the same
I'm talking more of internal issues (heads, platters transplants)

Is it some software to repair this 0 LBA for 30 $ or something? like hdd unlock, one time?

In a word...No.