Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Dangers of using N1 command on seagate

November 23rd, 2010, 13:38

dear gurus for drives having large bad sectors is it OK to using N1 command or simply reset smart using seDiv? Can you guide me for any dangers of this and other commands like clearing G list?
Cheers

Re: Dangers of using N1 command on seagate

November 23rd, 2010, 14:29

One danger of N1 is that if you do it at the wrong time you will completely destroy all of the data and essentially erase the firmware

Re: Dangers of using N1 command on seagate

November 23rd, 2010, 15:21

It is certainly important to insure that the heads of the drive are in good enough working condition to be deemed "safe".

If you attempt commands that write to the firmware with a set of bad heads you can end up "up the creek"

Re: Dangers of using N1 command on seagate

November 23rd, 2010, 17:05

in 7200.12 some times after >N1 hdd don't detect

Re: Dangers of using N1 command on seagate

November 23rd, 2010, 17:20

Russwinters wrote:It is certainly important to insure that the heads of the drive are in good enough working condition to be deemed "safe".

If you attempt commands that write to the firmware with a set of bad heads you can end up "up the creek"

How likely is it that the write element of a bad head is faulty? Aren't the vast majority of Seagate / Maxtor head faults due to the read element?

Re: Dangers of using N1 command on seagate

November 23rd, 2010, 17:55

There are MANY circumstances where brutally clearing the G-list will take you in deep shit especially if there was data on the drive. Same for SMART reset if the rest (EVERYTHING) has not properly diagnosed BEFORE.

I see everyday drives where the so-called "internet fix" was applied and the problem was ALSO elsewhere (drive hanging was a consequence) , the result is a mess and is a lot more complicated to get data out of the drive (and it's gonna cost $$$$$ / €€€€€ ).

No wonder, the terminal service on newer drives is no longer available.

Re: Dangers of using N1 command on seagate

November 23rd, 2010, 18:02

fzabkar wrote:
Russwinters wrote:It is certainly important to insure that the heads of the drive are in good enough working condition to be deemed "safe".

If you attempt commands that write to the firmware with a set of bad heads you can end up "up the creek"

How likely is it that the write element of a bad head is faulty? Aren't the vast majority of Seagate / Maxtor head faults due to the read element?



Do you want to take that bet with a customer drive?


I don't take bets. I recover data.

Re: Dangers of using N1 command on seagate

November 23rd, 2010, 18:04

Too easy... :mrgreen:
Post a reply