All times are UTC - 5 hours [ DST ]


Switch to mobile style


Post new topic Reply to topic  [ 6 posts ] 
Author Message
 Post subject: MHDD regs48 syntax
PostPosted: March 19th, 2015, 5:58 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 14945
Location: Australia
Does anyone know the syntax for the "regs48" batch command? I'd like to write an MHDD script to create a pseudo-uncorrectable sector using the 48-bit WRITE UNCORRECTABLE EXT ATA command.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: MHDD regs48 syntax
PostPosted: March 19th, 2015, 6:10 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
fzabkar wrote:
Does anyone know the syntax for the "regs48" batch command? I'd like to write an MHDD script to create a pseudo-uncorrectable sector using the 48-bit WRITE UNCORRECTABLE EXT ATA command.


Wow !
I was about to ask the same.
You can use the ATA terminal on hdd.exe or HRT.
Syntax for 48 bit ATA is values separated by a comma, example - 00,00
you can use SHT demo as well, mark 48 bit box on ATA terminal, syntax is without comma - example - 0000 . I don't know how to do it with mhdd.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: MHDD regs48 syntax
PostPosted: March 19th, 2015, 7:42 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
Would that WRITE UNCORRECTABLE EXT command cause a drive to log the "error" on it's S.M.A.R.T. error log ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
 Post subject: Re: MHDD regs48 syntax
PostPosted: March 19th, 2015, 15:36 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 14945
Location: Australia
AISI, the standard is a little ambiguous on the question of logging pseudo-uncorrectable errors. Annexes A.4 and A.7 don't make any reference to pseudo-uncorrectable errors, which would suggest that all uncorrectable errors would be logged. However, section 7.71 makes a distinction between pseudo-uncorrectable and "flagged" pseudo-uncorrectable errors. The former are logged but the latter are not.

Quote:
7.71 WRITE UNCORRECTABLE EXT - 45h, Non-Data

7.71.2 Description

7.71.2.1 Overview

The WRITE UNCORRECTABLE EXT command causes the device to report an uncorrectable error when the specified logical sectors are subsequently read.

When the device processes a read command, it shall set the Uncorrectable Error bit to one and the Error bit to one when a pseudo uncorrectable logical sector or flagged uncorrectable logical sector is read. Reading a flagged logical sector or pseudo uncorrectable logical sector may affect the Number of Reallocated Logical Sectors device statistic (see A.5.6.6).

If the device completes a write command to a pseudo uncorrectable logical sector or flagged uncorrectable logical sector without error, then the device:

a) shall write the data to the logical sector;

b) shall only cause the specified logical sectors to become valid;

c) shall not cause any other logical sectors (e.g., other logical sectors in the same physical sector) to become valid;

d) shall clear the pseudo uncorrectable attribute or flagged uncorrectable attribute of the logical sector; and

e) should verify that the logical sector may now be read without error.

The pseudo uncorrectable attribute or flagged uncorrectable attribute of a logical sector shall remain set during the processing of all power and reset events. If the device is unable to process a WRITE UNCORRECTABLE EXT command for any reason the device shall return command aborted.

7.71.2.2 Pseudo Uncorrectable Logical Sectors

When the Feature field (7:0) contains a value of 55h the WRITE UNCORRECTABLE EXT command shall cause the device to indicate a failure when subsequent reads to any of the logical sectors that are contained in the physical block of the specified logical sector are performed. These logical sectors are referred to as pseudo uncorrectable logical sectors. Whenever a pseudo uncorrectable logical sector is accessed via a read command the device shall perform normal error recovery to the fullest extent until:

a) the error recovery process is completed, the Uncorrectable Error bit is set to one, and the Error bit is set to one; or

b) a command time-out that applies to error recovery control occurs before error recovery is completed and an error is reported as a result of the command time-out (see 8.3.3).

When reading a pseudo uncorrectable logical sector, the device shall perform error logging (e.g., SMART, device statistics) in the same manner as an Uncorrectable error (see 6.3.10).

7.71.2.3 Flagged Uncorrectable Logical Sectors

When the Feature field (7:0) contains a value of AAh the WRITE UNCORRECTABLE EXT command shall cause the device to mark the specified logical sectors as flagged uncorrectable. Marking a logical sector as flagged uncorrectable shall cause the device to indicate a failure when subsequent reads to the specified logical sector are processed. When reading a flagged uncorrectable logical sector, the device should not perform error logging (e.g., SMART, device statistics) in the same manner as an Uncorrectable error (see 6.3.10).


Quote:
6.3.10 Uncorrectable Error bit

The Uncorrectable Error bit shall be set to one if the data contains an uncorrectable error.


Quote:
A.4 Comprehensive SMART Error log (Log Address 02h)

A.4.1 Overview

Table A.5 defines the format of each of the log pages that are part of the Comprehensive SMART Error log. The Comprehensive SMART Error log provides logging for 28-bit addressing only. For 48-bit addressing, see A.7. The maximum size of the Comprehensive SMART Error log shall be 51 log pages. Devices may support fewer than 51 log pages. The comprehensive error log data structures:

a) shall include Uncorrectable errors;
b) shall include ID Not Found errors for which the LBA requested was valid;
c) shall include servo errors;
d) shall include write fault errors; and
e) other error conditions.

Comprehensive SMART Error log data structures shall not include errors attributed to the receipt of faulty commands (e.g., command codes not supported by the device or requests with invalid parameters or invalid LBAs).


Quote:
A.7 Extended Comprehensive SMART Error log (Log Address 03h)

A.7.1 Overview

Table A.17 defines the format of each of the log pages that define the Extended Comprehensive SMART Error log. The maximum size of the Extended Comprehensive SMART Error log is 16383 log pages. Devices may support fewer than 16383 log pages. Error log data structures shall include, but are not limited to, Uncorrectable errors, ID Not Found errors for which the LBA requested was valid, servo errors, and write fault errors. Error log data structures shall not include errors attributed to the receipt of faulty commands (e.g., command codes not implemented by the device or requests with invalid parameters or invalid LBAs).

All 28-bit entries contained in the Comprehensive SMART log (see A.4), shall also be included in the Extended Comprehensive SMART Error log with the 48-bit entrie

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: MHDD regs48 syntax
PostPosted: March 19th, 2015, 15:42 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 14945
Location: Australia
Pseudo uncorrectable sectors are added to the Current Pending Sector count whereas flagged uncorrectable sectors are not.

Quote:
A.5.6.6 Number of Reallocated Logical Sectors

The Number of Reallocated Logical Sectors statistic is a counter that records the number of logical sectors that have been reallocated after device manufacture. This statistic shall incremented by one for each logical sector.

Quote:
A.5.6.9 Number of Reallocation Candidate Logical Sectors

A.5.6.9.1 Description

The number of Reallocation Candidate Logical Sectors statistic is a counter that records the number of logical sectors that are candidates for reallocation. A reallocation candidate sector is a logical sector that the device has determined may need to be reallocated. This statistic is incremented by one for each logical sector that is determined to be a candidate for reallocation. The counter shall be decremented by one for each logical sector that is removed from the candidate sector list (e.g., by reallocation, repair, or transient condition). Logical sectors marked as pseudo uncorrectable (see 7.71) shall be considered reallocation candidates. Logical sectors marked as flagged uncorrectable (see 7.71) should not be considered reallocation candidates.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: MHDD regs48 syntax
PostPosted: March 19th, 2015, 15:58 
Offline
User avatar

Joined: December 19th, 2006, 8:49
Posts: 11038
Location: Portugal
Did you have any luck getting the errors to be logged ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 6 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 6 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group