Seagate Grenada Head 0 can't read user area
December 8th, 2020, 13:45
Hello to all
ST1000DM003-1ER162, 2 heads.
H0 = can read and write all sa sysfiles but return unc errors on all user area sectors (error code = 43110081)
H1 = can read and write both sa and user area
Cloned all sectors from H1 at about 100Mb/s speed
Checked last 32 commands, head resistances seems ok, tried AFH/DAC ajustments, always the same result.
ACE TS told H0 is weak and can't read data in the user area because it have a much higher recording density compared to the service area.
I´d like to try to avoid a head exchange, because data isn't very important and customer isn't be able to afford the cost
Offcourse raw and/or partial recovery from H1 sectors only is possible, but head distribuition is about 60mb/h which results in most large files being bad, also MFT area got 50% read at best
Regarding reading sectors from h0 user area, does anyone have a different suggestion?
(other than head exchange)
i.e. could this problem be related to sa?
Maybe translator broken only for h0 (... i never saw it before)
Maybe MCMT or some other sysfile error?
Hdd is currenyly detecting without knocking, follows terminal log
I noticed one "RECOV Servo Op=0055 Resp=0005" error in terminal log after hdd starts
Thanks to all in advance for any reply / input on this matter
ST1000DM003-1ER162, 2 heads.
H0 = can read and write all sa sysfiles but return unc errors on all user area sectors (error code = 43110081)
H1 = can read and write both sa and user area
Cloned all sectors from H1 at about 100Mb/s speed
Checked last 32 commands, head resistances seems ok, tried AFH/DAC ajustments, always the same result.
ACE TS told H0 is weak and can't read data in the user area because it have a much higher recording density compared to the service area.
I´d like to try to avoid a head exchange, because data isn't very important and customer isn't be able to afford the cost
Offcourse raw and/or partial recovery from H1 sectors only is possible, but head distribuition is about 60mb/h which results in most large files being bad, also MFT area got 50% read at best
Regarding reading sectors from h0 user area, does anyone have a different suggestion?
(other than head exchange)
i.e. could this problem be related to sa?
Maybe translator broken only for h0 (... i never saw it before)
Maybe MCMT or some other sysfile error?
Hdd is currenyly detecting without knocking, follows terminal log
I noticed one "RECOV Servo Op=0055 Resp=0005" error in terminal log after hdd starts
- Code:
Boot 0x40M
Spin Up[LBA=0x000042F9]N0
Trans.
Tech Unlock Handshake: 0x732BC549
Reply:
Spin Up
SpinO
TCC:0022
(P) SATA Reset
RAW OFF
PASS
RECOV Servo Op=0055 Resp=0005
6Gb Max Speed lowered to 3Gb for Intel bug
Send Status: COMRESET seen
ASCII Diag mode
F3 T>
ATA 15 Cmds
Ts(ms) dT(ms) Op Cnt LBA
0 99999999 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
0 0 00 0000 000000000000
RW 32 Cmds
Ts(ms) dT(ms) xT(ms) Type Option Mode St EC Info
9006 99999999 3 02 011201 000000 1 00000080 XFR RD SYS LBA B 000000040649 L 000000000001 BO 000000 BES 022D740.022D77F.022D740
9009 3 9 02 011201 000000 1 00000080 XFR RD SYS LBA B 000000040649 L 000000000001 BO 000000 BES 022D740.022D77F.022D740
9018 9 8 02 028201 000000 1 00000080 XFR WR SYS LBA B 0000000405F8 L 000000000051 BO 000000 BES 0439448.043A887.0439448
9026 8 9 02 028201 000000 1 00000080 XFR WR SYS LBA B 0000000A313A L 000000000051 BO 000000 BES 0439448.043A887.0439448
9035 9 6 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000035814 L 000000000008 BO 000000 BES 006ADE5.006AFE4.006ADE5
9041 6 8 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000098356 L 000000000008 BO 000000 BES 006ADE5.006AFE4.006ADE5
9049 8 0 27 028201 000000 1 00000080 SND_SRV 0C01 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0001 B554 00D0
0F70 0001 0000 0003 0004 0130 F780 DB63
0003 0FE4 0FC2 0FA2 0F8B 0F83 12D2 1002
D3E4 765C 24E8 AA6B FE67 BC15 BD29 7E5D
E8FC 6753 CDD2 CCA2 4F2D B710 3723 C846
9050 1 14 02 011201 000000 0 43110081 XFR RD SYS LBA B 00000003AFBB L 000000000001 BO 000000 BES 006A59E.006A5DD.006A59E
9064 14 3 02 011201 000000 1 00000080 XFR RD SYS LBA B 00000003BA08 L 000000000003 BO 000000 BES 006A5DE.006A69D.006A5DE
9068 4 4 02 011201 000000 1 00000080 XFR RD SYS LBA B 00000002941D L 00000000001D BO 000000 BES 022EC80.022F3BF.022EC80
9077 9 120 02 011201 000000 1 00000080 XFR RD SYS LBA B 0000000377BB L 000000003800 BO 000000 BES 006B025.014B024.006B025
9382 305 2 02 011201 000000 1 00000080 XFR RD SYS LBA B 000000040614 L 000000000002 BO 000000 BES 022D740.022DB3F.022D740
9384 2 9 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000040614 L 000000000002 BO 000000 BES 022D740.022D7BF.022D740
9393 9 8 02 028201 000000 1 00000080 XFR WR SYS LBA B 0000000A3156 L 000000000002 BO 000000 BES 022D740.022D7BF.022D740
9401 8 8 02 011201 000000 1 00000080 XFR RD SYS LBA B 000000040614 L 000000000002 BO 000000 BES 022D740.022DB3F.022D740
9418 17 8 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000040616 L 000000000001 BO 000000 BES 006AAA5.006AAE4.006AAA5
9426 8 8 02 011201 000000 1 00000080 XFR RD SYS LBA B 0000000405FA L 000000000004 BO 000000 BES 022D740.022D83F.022D740
9434 8 8 02 011201 000000 1 00000080 XFR RD SYS LBA B 0000000405FA L 000000000004 BO 000000 BES 022DB40.022DC3F.022DB40
9442 8 9 02 028201 000000 1 00000080 XFR WR SYS LBA B 0000000405FA L 000000000004 BO 000000 BES 022DB40.022DC3F.022DB40
9486 44 1 2B 028201 000000 1 00000080 PES
9498 12 0 2B 028201 000000 1 00000080 PES
9502 4 289 02 011201 000000 2 43110081 XFR RD SYS LBA B 000000036A0F L 000000000001 BO 000000 BES 002B1E0.002B21F.002B1E0
9791 289 1047 02 011201 000000 0 43110081 XFR RD SYS LBA B 000000036A0F L 000000000001 BO 000000 BES 002B1E0.002B21F.002B1E0
10838 1047 19 02 011201 000000 1 00000080 XFR RD SYS LBA B 000000035825 L 000000000800 BO 000000 BES 0439448.0459447.0439448
10865 27 3 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000036A05 L 00000000000A BO 000000 BES 0241E80.02420FF.0241E80
10869 4 8 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000099547 L 00000000000A BO 000000 BES 0241E80.02420FF.0241E80
10891 22 5 02 011201 000000 1 00000080 XFR RD SYS LBA B 0000000373F6 L 000000000001 BO 000000 BES 00670DD.006711C.00670DD
10897 6 8 02 011201 000000 1 00000080 XFR RD SYS LBA B 0000000373F6 L 000000000001 BO 000000 BES 00670DD.006711C.00670DD
10905 8 3 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000035814 L 000000000008 BO 000000 BES 006ADE5.006AFE4.006ADE5
10908 3 8 02 028201 000000 1 00000080 XFR WR SYS LBA B 000000098356 L 000000000008 BO 000000 BES 006ADE5.006AFE4.006ADE5
99659 88751 17 02 011201 000000 0 43110081 XFR RD SYS LBA B 00000002BB11 L 000000000180 BO 000000 BES 0036000.003BFFF.0036000
99677 18 10 02 011201 000000 1 00000080 XFR RD SYS LBA B 00000002BC91 L 000000000100 BO 000000 BES 003C000.003FFFF.003C000
ASCII Diag mode
F3 T>/7X
Head 00 Resistance 015A
Head 01 Resistance 012A
F3 7>
Thanks to all in advance for any reply / input on this matter
Re: Seagate Grenada Head 0 can't read user area
December 8th, 2020, 15:48
ACE TS told H0 is weak and can't read data in the user area because it have a much higher recording density compared to the service area.
This is your problem.
H0 is weak or contaminated. You can't avoid checking the head visually in any case, more precisely you can but with risking drawing nice rings on the surface.
May the head be dirty you can clean it and see if it reads better. If it is clean there is a chance it can be forced to read UA by changing adaptives.
But i don't think this procedure is more simple than a head swap...
could this problem be related to sa?
you were told the answer and still asking such questions...
pepe
Re: Seagate Grenada Head 0 can't read user area
December 8th, 2020, 18:15
Thank you for replying.
I was raised to never stop asking questions and why, not accepting one answer as an inquestionable truth, so I think we can blame that on my parents, teachers and country education system
I recovered data from many situations were ACE said it was weak or bad heads, and head exchange was the only solution, but data was recovered using a completelly different approach. Some examples were fixed using AFH/DAC, which ace strongly doesn't recommend. They surelly have a lot of knowledge and TS support is great, but certainly not to a point that what they say is unquestionable.
I also consider they look at it remotelly and they have a lot of requests, so they have limited time for each case.
What I find strange is that H0 SA is read very fast, without a single bad sector, while user area have all sectors UNC. Hdd is stable, doesn't produce knocking sounds, air filter is clean. Doesn't feel right. If H0 is so weak at least some bad sectors should have appeared in H0 SA read. And even considering the higher UA density, I think at least 1 or 2 sectors should read from UA. I tried 5.000.000+ UA H0 reads, high timeout, single sector read, from different areas of the platter, all UNC.
Maybe there is a fw code that disables H0 if some read/write test does not return 100%. Like windows block all data access if some $mft cannot be fully read. A lot of hdd vendors block all UA data access when g-list overgrows. This is a perfect example of stupid coding. Maybe there is something like this blocking H0 to read UA. But I might be wrong in this feeling. I'm not an expert in this SA, that's why I tried asking here.
And since both head examination and exchange procediments are very intrusive, I think asking before trying that is the best way to go.
So question for me is still open, if anyone have other suggestions please share them here
Otherwise as data is not urgent nor very important and I already have partial results, plan is to examine heads a few days from now and try to clean them if no other non intrusive options are available. Rumors say that next Seagate utility version might allow Seagate hot swap. And it is about to be released soon, so maybe that's a better option before messing with the heads.
Thanks again and best regards
pepe wrote:you were told the answer and still asking such questions...
I was raised to never stop asking questions and why, not accepting one answer as an inquestionable truth, so I think we can blame that on my parents, teachers and country education system
I recovered data from many situations were ACE said it was weak or bad heads, and head exchange was the only solution, but data was recovered using a completelly different approach. Some examples were fixed using AFH/DAC, which ace strongly doesn't recommend. They surelly have a lot of knowledge and TS support is great, but certainly not to a point that what they say is unquestionable.
I also consider they look at it remotelly and they have a lot of requests, so they have limited time for each case.
What I find strange is that H0 SA is read very fast, without a single bad sector, while user area have all sectors UNC. Hdd is stable, doesn't produce knocking sounds, air filter is clean. Doesn't feel right. If H0 is so weak at least some bad sectors should have appeared in H0 SA read. And even considering the higher UA density, I think at least 1 or 2 sectors should read from UA. I tried 5.000.000+ UA H0 reads, high timeout, single sector read, from different areas of the platter, all UNC.
Maybe there is a fw code that disables H0 if some read/write test does not return 100%. Like windows block all data access if some $mft cannot be fully read. A lot of hdd vendors block all UA data access when g-list overgrows. This is a perfect example of stupid coding. Maybe there is something like this blocking H0 to read UA. But I might be wrong in this feeling. I'm not an expert in this SA, that's why I tried asking here.
And since both head examination and exchange procediments are very intrusive, I think asking before trying that is the best way to go.
So question for me is still open, if anyone have other suggestions please share them here
Otherwise as data is not urgent nor very important and I already have partial results, plan is to examine heads a few days from now and try to clean them if no other non intrusive options are available. Rumors say that next Seagate utility version might allow Seagate hot swap. And it is about to be released soon, so maybe that's a better option before messing with the heads.
Thanks again and best regards
Re: Seagate Grenada Head 0 can't read user area
December 8th, 2020, 21:02
Hello,
it is absolutely right right attitude to handle answers with some healthy amount of disbelief. Especially when it comes to TS from ace
I also recovered numerous drives that they deemed unrecoverable for some reason.
So i kind of regret i said that statement.
Anyway, this time they are right about the weak head. Playing with AFH can give you some results however, it can kill head for good as well as the surface if uncontrolled. Check it first under microscope.
Hotswap has been possible for seagates all the time, so they do not really add a lot to this thing. However, hotswap won't help when head is bad/weak, you can easily achieve a discretion, just think about it.
pepe
it is absolutely right right attitude to handle answers with some healthy amount of disbelief. Especially when it comes to TS from ace
I also recovered numerous drives that they deemed unrecoverable for some reason.So i kind of regret i said that statement.
Anyway, this time they are right about the weak head. Playing with AFH can give you some results however, it can kill head for good as well as the surface if uncontrolled. Check it first under microscope.
Hotswap has been possible for seagates all the time, so they do not really add a lot to this thing. However, hotswap won't help when head is bad/weak, you can easily achieve a discretion, just think about it.
pepe
Re: Seagate Grenada Head 0 can't read user area
December 9th, 2020, 0:02
If both you and Ace are right, I agree that hot swap will be of little help here.
This customer is a non profit very small organization that helps homeless persons, so they can not afford a head swap. We took this case for only $50 to help them for humanitary reasons. They already stated data is not very important, also that if we are not able to recover data we can destroy hdd. And unfortunatelly I dont have a donor hdd compatible for this case
With that specific information in mind I was thinking something different as a last resorce if no other better idea comes around: platter side swap
Step 1: open hdd and invert platter sides, hdd has 1 platter only, side0 that was on h0 will be moved to h1 which is good and can read UA data
Step 2: invert RAM logical head in Seagate utility map from 00 01 to 01 00
Step 3: clone platter side0 (was originally on bad h0, now on good h1), but as logical h0 to complete sectors map as original platter side1 has already been fully cloned.
Is this idea totally crazy? Any chances to work, regarding Grenada drives and sa structure?
Note that I have clean room, platter handling tools, experince in head swaps, done platters transplant to another hda before and etc.
But I didn't try platter side swapping on Grenadas yet
And again, this would be used as a last resorce ... because of specific customer total lack of $$$, data low importance, and as a "better than nothing" last chance
This customer is a non profit very small organization that helps homeless persons, so they can not afford a head swap. We took this case for only $50 to help them for humanitary reasons. They already stated data is not very important, also that if we are not able to recover data we can destroy hdd. And unfortunatelly I dont have a donor hdd compatible for this case
With that specific information in mind I was thinking something different as a last resorce if no other better idea comes around: platter side swap
Step 1: open hdd and invert platter sides, hdd has 1 platter only, side0 that was on h0 will be moved to h1 which is good and can read UA data
Step 2: invert RAM logical head in Seagate utility map from 00 01 to 01 00
Step 3: clone platter side0 (was originally on bad h0, now on good h1), but as logical h0 to complete sectors map as original platter side1 has already been fully cloned.
Is this idea totally crazy? Any chances to work, regarding Grenada drives and sa structure?
Note that I have clean room, platter handling tools, experince in head swaps, done platters transplant to another hda before and etc.
But I didn't try platter side swapping on Grenadas yet
And again, this would be used as a last resorce ... because of specific customer total lack of $$$, data low importance, and as a "better than nothing" last chance
Re: Seagate Grenada Head 0 can't read user area
December 9th, 2020, 5:15
Is this idea totally crazy?
yes, it is, just think about it for a moment.
pepe
Re: Seagate Grenada Head 0 can't read user area
December 9th, 2020, 8:21
If you are talking about flipping the platter over, perhaps data recovery is not for you. Basic understanding of hard drive mechanics is more essential in this industry than owning PC3000.
Re: Seagate Grenada Head 0 can't read user area
December 9th, 2020, 9:45
If your understanding say it will not work ... I can only say I've done it on several cases with other brands and have worked well enough to save user´s data. Just have't tried with Grenadas yet. Offcourse there's more stuff to do than the brief summary on my other post.
IMPORTANT: People new to data recovery that read this post please stick to the above advices and DON'T TRY THIS !!! Should know you can lost data forever !!!
I started working with DR probaby long way before you
Thanks for the inputs on this post anyway, always good to hear other people opinions
IMPORTANT: People new to data recovery that read this post please stick to the above advices and DON'T TRY THIS !!! Should know you can lost data forever !!!
lcoughey wrote:If you are talking about flipping the platter over, perhaps data recovery is not for you.
I started working with DR probaby long way before you
Thanks for the inputs on this post anyway, always good to hear other people opinions
Powered by phpBB © phpBB Group.