A question

Questions about Arch7 Repair Tool capabilities
Post Reply
CWRU
Posts: 24
Joined: 09 Sep 2013, 17:36

Re: How to open space for mod 04 in Dir

Post by CWRU »

Vlad wrote:Check before, have the SA enough size to hold all modules or no
To avoid surprise)
I did it. There are two big free spaces of about 20MB each...
CWRU
Posts: 24
Joined: 09 Sep 2013, 17:36

Re: How to open space for mod 04 in Dir

Post by CWRU »

The solution came out to be very simple . Just increased the sizes of all regions...
Beamg
Posts: 17
Joined: 05 Jul 2019, 05:52

Question about SelfScan test 34D1 & 34D2 error. Always ends with full head defect list. Why?

Post by Beamg »

Hi,

I've ran some selfscan scripts on a few newer drives and I always end up with a full defect head list.
It's always from the tests 34D1 & 34D2.

I tried the test on 4 different drives. I know the heads are not damaged on any of the drives.
However, they do have some bad sectors.

Models I tried which all produce a full head defect list error with selfscan test 34D1 & 34D2:
WD5000LPCX-60VHAT0
WD10JPVX-08JC3T5
WD10JPVX-22JC3T0
WD40EFRX-68WT0N0

So, if there's anyone out there who has knowledge of this issue, I would appreciate some help.

I tried some selfscan tests on the older WD7500BPVT 750GB models and the scripts seem to work.

Thanks.
User avatar
Vlad
Разработчик
Posts: 5025
Joined: 13 Aug 2013, 07:53

Re: Question about SelfScan test 34D1 & 34D2 error. Always ends with full head defect list. Why?

Post by Vlad »

You can use "Replace 34Dx tests with Dx" option in script from log creation
Beamg
Posts: 17
Joined: 05 Jul 2019, 05:52

Re: Question about SelfScan test 34D1 & 34D2 error. Always ends with full head defect list. Why?

Post by Beamg »

Vlad wrote:You can use "Replace 34Dx tests with Dx" option in script from log creation
Yes, I've actually tried it both ways 00D1 but it still ends with the defect list full. It's also slower.
Any other suggestions?
I'm pretty sure drives are not bad. I know this is a very important test when it comes to fixing the disc surface defects. So, I would like to find a solution. I don't think it has anything to do with the SATA connection used. Since it's an internal command correct?
User avatar
Vlad
Разработчик
Posts: 5025
Joined: 13 Aug 2013, 07:53

Re: A question

Post by Vlad »

if 34Dx and Dx both ends with full log then just head are dead
of cource, if we talking about selfscan on original FW, not on donor or modified in some way FW
Beamg
Posts: 17
Joined: 05 Jul 2019, 05:52

Re: A question

Post by Beamg »

Vlad wrote:if 34Dx and Dx both ends with full log then just head are dead
of cource, if we talking about selfscan on original FW, not on donor or modified in some way FW
So, what I just did was try the test 34D1 & 00D1 on a new Makalu family drive with the original FW. It still failed with a full defect list. :shock: I know this drive has perfect heads. Now, I'm 100% sure it's not dead heads. I made the script from the selfscan log. Maybe I'm doing something wrong? I do have the IDE channel disabled in Device Manager for that particular drive. I don't think that should be a problem.
User avatar
Vlad
Разработчик
Posts: 5025
Joined: 13 Aug 2013, 07:53

Re: A question

Post by Vlad »

Beamg wrote:It still failed with a full defect list. :shock: I know this drive has perfect heads. Now, I'm 100% sure it's not dead heads.
Looks like SelfScan do not agree with you :)
Beamg wrote:I made the script from the selfscan log. Maybe I'm doing something wrong?
"Create script from log" and then "prepare SA and start SelfScan"
Not so many places to do something wrong...

Beamg wrote:I do have the IDE channel disabled in Device Manager for that particular drive.
This is correct
Beamg
Posts: 17
Joined: 05 Jul 2019, 05:52

Re: A question

Post by Beamg »

Vlad wrote:
Beamg wrote:It still failed with a full defect list. :shock: I know this drive has perfect heads. Now, I'm 100% sure it's not dead heads.
Looks like SelfScan do not agree with you :)
Beamg wrote:I made the script from the selfscan log. Maybe I'm doing something wrong?
"Create script from log" and then "prepare SA and start SelfScan"
Not so many places to do something wrong...

Beamg wrote:I do have the IDE channel disabled in Device Manager for that particular drive.
This is correct
:lol:

Yes, the script is easy to create and I know that's not the issue!

However, the funny thing is selfscan DOES work for me with only OLDER drives.
Currently testing a WD800BEVT and it seems to be going fine. I also tried a WD7500BPVT and it definitely gets past 00D1 00DB etc.

It seems ALL the NEWER drives which have the test (34D1) are the ones I can't get to work with selfscan correctly. The motherboard I'm using for testing is 11 years old (SATA II). Do you think that could be a problem?
User avatar
Vlad
Разработчик
Posts: 5025
Joined: 13 Aug 2013, 07:53

Re: A question

Post by Vlad »

WD5000L, family: Hubble LT, FW: 06.1TJ, SN: WD-WX81A14E4184, LBA 976773168 - 500Gb

Code: Select all

20.06.2019 2:16:51: Test SelfScan Test ClearIBILogs begin at: 20.06.2019 2:16:51
20.06.2019 2:17:13: Elapsed time 00:00:21
20.06.2019 2:17:13: Test 00/00 begin at: 20.06.2019 2:17:13
20.06.2019 2:17:43: Test SelfScan Test CondServoGain begin at: 20.06.2019 2:17:43
20.06.2019 2:18:01: Elapsed time 00:00:17
20.06.2019 2:18:01: Test SelfScan Test DualBufferWrite begin at: 20.06.2019 2:18:01
20.06.2019 2:19:53: Elapsed time 00:01:52
20.06.2019 2:19:53: Test SelfScan Test jpGTask begin at: 20.06.2019 2:19:53
20.06.2019 2:25:00: Elapsed time 00:05:06
20.06.2019 2:25:00: Test SelfScan Test DualBufferRead begin at: 20.06.2019 2:25:00
20.06.2019 2:26:56: Elapsed time 00:01:55
20.06.2019 2:26:56: Test SelfScan Test DualBufferWriteRetry begin at: 20.06.2019 2:26:56
20.06.2019 2:27:25: Elapsed time 00:00:29
20.06.2019 2:27:25: Test SelfScan Test DualBufferReadRetry begin at: 20.06.2019 2:27:25
20.06.2019 2:28:48: Elapsed time 00:01:23
20.06.2019 2:28:48: Test SelfScan Test Cluster begin at: 20.06.2019 2:28:48
20.06.2019 2:29:50: Elapsed time 00:01:01
20.06.2019 2:29:50: Test SelfScan Test Tlist generation begin at: 20.06.2019 2:29:50
20.06.2019 2:30:20: Elapsed time 00:00:30
20.06.2019 2:30:20: Test SelfScan Test DualBufferWrite begin at: 20.06.2019 2:30:20
20.06.2019 4:19:30: Elapsed time 01:49:09
20.06.2019 4:19:30: Test SelfScan Test jpGTask begin at: 20.06.2019 4:19:30
20.06.2019 4:24:38: Elapsed time 00:05:07
20.06.2019 4:24:38: Test SelfScan Test DualBufferRead begin at: 20.06.2019 4:24:37
20.06.2019 6:18:06: Elapsed time 01:53:28
20.06.2019 6:18:06: Test SelfScan Test DualBufferWriteRetry begin at: 20.06.2019 6:18:06
20.06.2019 6:20:44: Elapsed time 00:02:37
20.06.2019 6:20:44: Test SelfScan Test DualBufferReadRetry begin at: 20.06.2019 6:20:44
20.06.2019 6:24:02: Elapsed time 00:03:18
20.06.2019 6:24:02: Test SelfScan Test RRO begin at: 20.06.2019 6:24:02
20.06.2019 6:24:59: Elapsed time 00:00:57
20.06.2019 6:24:59: Test SelfScan Test TAListGen begin at: 20.06.2019 6:24:59
20.06.2019 6:25:08: Elapsed time 00:00:08
20.06.2019 6:25:08: Test SelfScan Test Cluster begin at: 20.06.2019 6:25:08
20.06.2019 6:25:32: Elapsed time 00:00:24
20.06.2019 6:25:32: Test SelfScan Test Tlist generation begin at: 20.06.2019 6:25:32
20.06.2019 6:26:23: Elapsed time 00:00:51
20.06.2019 6:26:23: Test SelfScan Test PList begin at: 20.06.2019 6:26:23
20.06.2019 6:26:43: Elapsed time 00:00:19
20.06.2019 6:26:43: Test SelfScan Test Format begin at: 20.06.2019 6:26:43
20.06.2019 6:26:51: Elapsed time 00:00:08
20.06.2019 6:26:51: Test 00/00 begin at: 20.06.2019 6:26:51
20.06.2019 6:27:21: Test SelfScan Test ServoRRO begin at: 20.06.2019 6:27:21
20.06.2019 6:28:18: Elapsed time 00:00:56
20.06.2019 6:28:18: Test SelfScan Test PE Scan begin at: 20.06.2019 6:28:18
20.06.2019 6:30:39: Elapsed time 00:02:20
20.06.2019 6:30:39: Test SelfScan Test XMMSResults begin at: 20.06.2019 6:30:39
20.06.2019 6:30:53: Elapsed time 00:00:14
20.06.2019 6:30:53: Test SelfScan Test ClearIBILogs begin at: 20.06.2019 6:30:53
20.06.2019 6:31:00: Elapsed time 00:00:07
20.06.2019 6:31:00: Test 00/00 begin at: 20.06.2019 6:31:00
20.06.2019 6:31:31: Test SelfScan Test HealthMonitor begin at: 20.06.2019 6:31:30
20.06.2019 6:45:29: Elapsed time 00:13:58
20.06.2019 6:45:29: Test SelfScan Test SPT Write All begin at: 20.06.2019 6:45:29
20.06.2019 6:47:18: Elapsed time 00:01:48
20.06.2019 6:47:18: Test SelfScan Test SPT Read All begin at: 20.06.2019 6:47:17
20.06.2019 6:48:53: Elapsed time 00:01:35
20.06.2019 6:48:53: Test SelfScan Test SPT Write All begin at: 20.06.2019 6:48:53
20.06.2019 6:51:04: Elapsed time 00:02:10
20.06.2019 6:51:04: Test SelfScan Test SPT Read All begin at: 20.06.2019 6:51:04
20.06.2019 6:53:02: Elapsed time 00:01:57
20.06.2019 6:53:02: Test SelfScan Test SPT Write All begin at: 20.06.2019 6:53:01
20.06.2019 6:56:22: Elapsed time 00:03:20
20.06.2019 6:56:22: Test SelfScan Test SPT Read All begin at: 20.06.2019 6:56:22
20.06.2019 6:59:44: Elapsed time 00:03:22
20.06.2019 6:59:44: Test SelfScan Test CalDefectSize begin at: 20.06.2019 6:59:44
20.06.2019 7:00:05: Elapsed time 00:00:21
20.06.2019 7:00:05: Test SelfScan Test LBAButterfly begin at: 20.06.2019 7:00:05
20.06.2019 7:01:17: Elapsed time 00:01:11
20.06.2019 7:01:17: Test SelfScan Test XMMSResults begin at: 20.06.2019 7:01:17
20.06.2019 7:01:31: Elapsed time 00:00:14
20.06.2019 7:01:31: Test SelfScan Test SPTReadTime begin at: 20.06.2019 7:01:31
20.06.2019 7:01:34: Elapsed time 00:00:02
20.06.2019 7:01:34: Test SelfScan Test XMMSDRM begin at: 20.06.2019 7:01:34
20.06.2019 7:01:39: Elapsed time 00:00:04
20.06.2019 7:01:39: Test SelfScan Test ClearIBILogs begin at: 20.06.2019 7:01:39
20.06.2019 7:01:46: Elapsed time 00:00:07
20.06.2019 7:01:46: Test 00/00 begin at: 20.06.2019 7:01:46
20.06.2019 7:02:16: Test SelfScan Test LBAZero begin at: 20.06.2019 7:02:16
20.06.2019 7:12:12: Elapsed time 00:09:55
20.06.2019 7:12:12: Test 00/00 begin at: 20.06.2019 7:12:12
20.06.2019 7:12:42: Test SelfScan Test ClearIBILogs begin at: 20.06.2019 7:12:42
20.06.2019 7:12:49: Elapsed time 00:00:07
20.06.2019 7:12:49: Test 00/00 begin at: 20.06.2019 7:12:49
20.06.2019 7:13:19: Test SelfScan Test SPT Write All begin at: 20.06.2019 7:13:19
20.06.2019 7:18:28: P-list read successfully
20.06.2019 7:18:28: PList created.
20.06.2019 7:18:28: Defect log on head 0: 545 defects (540 tracks, 5 sectors ) of 53331 possible
20.06.2019 7:18:28: Defect log on head 1: 445 defects (436 tracks, 9 sectors ) of 53331 possible
But, I run selfscan after ARCO on such drives
I will try to run SelfScan twice on the same drive to test, when have time
SelfScan performed internally, controller, drivers etc, do not affect, after start
Post Reply