August 26th, 2019, 12:56
August 26th, 2019, 14:45
August 26th, 2019, 15:24
Doomer wrote:There is no media cache(of same use or capacity as on Seagate drives) on WD drives
August 26th, 2019, 15:55
Amarbir[CDR-Labs] wrote:Well,
I Just Solved a Case Today Of a Diablo 3S/3D Which had " Media Cache " Issue .
August 27th, 2019, 15:20
Doomer wrote:Amarbir[CDR-Labs] wrote:Well,
I Just Solved a Case Today Of a Diablo 3S/3D Which had " Media Cache " Issue .
how do you know that the issue was "Media Cache"
August 27th, 2019, 15:30
Amarbir[CDR-Labs] wrote:Well,
Cos Heads And Al Firmware Modules Were Fit And Fine
August 28th, 2019, 1:33
Amarbir wrote:Well,
Cos Heads And Al Firmware Modules Were Fit And Fine
August 28th, 2019, 3:28
Amarbir[CDR-Labs] wrote:Doomer wrote:There is no media cache(of same use or capacity as on Seagate drives) on WD drives
Well,
I Just Solved a Case Today Of a Diablo 3S/3D Which had " Media Cache " Issue . Can You Let Me Know Whats The Use Of It In The WD HDD .I Tried everything On a Case Today And Finally i Got Sector Access By Working On Media Cache . Can You Brief Me About How Its Implemented In HDD And Which Firmware Modules Control It
August 28th, 2019, 13:10
Doomer wrote:Amarbir[CDR-Labs] wrote:Well,
Cos Heads And Al Firmware Modules Were Fit And Fine
I think it was the issue with ignition then
Or maybe you forgot to put fuel in it?
Also check the tire pressure
August 28th, 2019, 13:17
Yustik wrote:Amarbir wrote:Well,
Cos Heads And Al Firmware Modules Were Fit And Fine
sure? how did you check validity of logs?
it looks like you don't understand what are you doing
August 28th, 2019, 13:29
DR-Kiev wrote:Amarbir[CDR-Labs] wrote:Doomer wrote:There is no media cache(of same use or capacity as on Seagate drives) on WD drives
Well,
I Just Solved a Case Today Of a Diablo 3S/3D Which had " Media Cache " Issue . Can You Let Me Know Whats The Use Of It In The WD HDD .I Tried everything On a Case Today And Finally i Got Sector Access By Working On Media Cache . Can You Brief Me About How Its Implemented In HDD And Which Firmware Modules Control It
This is how you solved this case:
August 28th, 2019, 14:05
August 28th, 2019, 14:51
digisupport wrote:Dear Amarbir, in clear language I think all the nice people here are telling you not to gamble with clients data.
You hit a button in your tool without knowing the consequences on a WD drive that you do not know.
In short you screwed up, and the result is that your client has to accept a RAW result, as the consequence of your actions.
Maybe your client does not care, we all make errors from time to time, but using "features" and "hitting random buttons" on a client drive is not one of them.
Maybe good enough for you, but there is space for improvement, right?
The guys you are taking on here has a reputation you can only dream off, has helped so many of us during the years.
Us lower ranking, you included can learn a lot. But sometimes you must admit you screwed up, say you are sorry, it doesn't hurt, try it.
August 28th, 2019, 15:46
Amarbir[CDR-Labs] wrote:So i Though Might Be Its a Media Cache Issue Like Seagate And Bingo It Worked
Amarbir[CDR-Labs] wrote:In Clear Language If You Had The Case You Would Not Be Able To Solve It In The First Place Cos You Too Have ZERO Idea Of The Subject ,But You Are Wanting To Become a Good Boy In The Eyes Of Your Seniors
August 28th, 2019, 18:15
Offset(h) 00 04 08 0C 10 14
00000030 00000000 00806700 00000000 01000000 00000000
00000048 00000000 00000000 01806700 00000000 623B7711 00000000 0x11772B62 x 1
00000060 08000000 00000000 63BBDE11 00000000 623B7711 00000000 0x11772B62 x 1
00000078 10E60000 00000000 C5F65523 00000000 88EDDC45 00000000 0x11772B62 x 4 = 0x45DCED88
00000090 18CC0100 00000000 4DE43269 00000000 88EDDC45 00000000 0x11772B62 x 4
000000A8 20B20200 00000000 D5D10FAF 00000000 88EDDC45 00000000 0x11772B62 x 4
000000C0 28980300 00000000 5DBFECF4 00000000 5364CB68 00000000 0x11772B62 x 6 = 0x68CB044C
000000D8 307E0400 ^^^^^^^^^^^^^^^^^ -----------------
^^^^^^^^ current 08 = previous 08 + previous 10
+ 0xE608
Offset(h) 00 04 08 0C
00000120 00000000 00000000 00000000 D77ACD5D
00000130 01000000 38640500 10270000 581B0000
00000140 20A10700 00000000 00000000 00000000
August 28th, 2019, 19:08
August 29th, 2019, 1:26
pepe wrote:what that button did to 148
August 29th, 2019, 2:27
Yustik wrote:Amarbir[CDR-Labs] wrote:So i Though Might Be Its a Media Cache Issue Like Seagate And Bingo It Worked
Omg what you mean?? Do you clean MC at Seagate drives???Amarbir[CDR-Labs] wrote:In Clear Language If You Had The Case You Would Not Be Able To Solve It In The First Place Cos You Too Have ZERO Idea Of The Subject ,But You Are Wanting To Become a Good Boy In The Eyes Of Your Seniors
You know, until today morning i never used this button in utility and never saw such a problem. But checked this file contents on Diablo, checked behavior with empty and garbage-filled file. And now i know - this is very dangerous to mindlessly modify this file. And it can not be MC.
What did you do? Just tried to press some wrong-named button. Playing with client data. Please, stop it.
August 29th, 2019, 2:32
fzabkar wrote:Well, despite Amarbir's word case annoyances, I analysed module 148h in a Diablo 3D.
AFAICT, the module defines 6 LBA regions, 1 per head (?). I could be seriously wrong, though.
WD30EZRX-00DC0B0, Diablo 3D, mod 148h
- Code:
Offset(h) 00 04 08 0C 10 14
00000030 00000000 00806700 00000000 01000000 00000000
00000048 00000000 00000000 01806700 00000000 623B7711 00000000 0x11772B62 x 1
00000060 08000000 00000000 63BBDE11 00000000 623B7711 00000000 0x11772B62 x 1
00000078 10E60000 00000000 C5F65523 00000000 88EDDC45 00000000 0x11772B62 x 4 = 0x45DCED88
00000090 18CC0100 00000000 4DE43269 00000000 88EDDC45 00000000 0x11772B62 x 4
000000A8 20B20200 00000000 D5D10FAF 00000000 88EDDC45 00000000 0x11772B62 x 4
000000C0 28980300 00000000 5DBFECF4 00000000 5364CB68 00000000 0x11772B62 x 6 = 0x68CB044C
000000D8 307E0400 ^^^^^^^^^^^^^^^^^ -----------------
^^^^^^^^ current 08 = previous 08 + previous 10
+ 0xE608(0x11772B62 x 14) + 0x68CB6453 = 5 860 475 823 LBAs
5860475823 x 512 bytes = 3.00 TB
0xE608 x 6 x 512 bytes = 180.9 MB
0xE608 x 6 x 4096 bytes = 1.45 GB
The current value in column 8 is computed by adding the previous values in columns 8 and 10h.
The current value in column 0 is computed by adding 0xE608 to the previous value.
I don't know how to interpret the following data:
- Code:
Offset(h) 00 04 08 0C
00000120 00000000 00000000 00000000 D77ACD5D
00000130 01000000 38640500 10270000 581B0000
00000140 20A10700 00000000 00000000 00000000
August 29th, 2019, 2:37
pepe wrote:It was 3-4 years ago when i dealt with 148 regarding an issue with building head map in DE. The module is part of the translator and it maps out some LBA regions, but have not really traced it down any further (lack of time, as always). So the exact purpose was not found out that time, but i was able to build correct head map.
Amarbir, you could check what that button did to 148, that might shed some light on what it does.
pepe
Powered by phpBB © phpBB Group.