December 2nd, 2014, 11:39
December 8th, 2018, 17:39
Cris wrote:I wonder if we will start to see hardware imagers supporting this feature.
December 9th, 2018, 11:46
maximus wrote:Cris wrote:I wonder if we will start to see hardware imagers supporting this feature.
It has been 4 years since this post. So do any of the hardware images implement this yet? Might be on my bucket list now
December 9th, 2018, 19:22
December 9th, 2018, 19:31
December 9th, 2018, 20:19
maximus wrote:I could not find any direct evidence that Seagate has actually produced any drives that support this feature ...
December 9th, 2018, 21:00
fzabkar wrote:maximus wrote:I could not find any direct evidence that Seagate has actually produced any drives that support this feature ...
Rebuild Assist appears to be a feature of some Seagate SAS drives. Seagate muddies the waters by calling it "RAID Rebuild", in which case it is also a feature of Exos X12 SATA models.
https://www.seagate.com/files/www-content/datasheets/pdfs/exos-x-12-DS1946-2-1712US-en_US.pdf
Seagate RAID Rebuild and Seagate Secure are either trademarks or registered trademarks of Seagate Technology LLC or one of its affiliated companies in the United States and/or other countries.
December 13th, 2018, 19:14
December 14th, 2018, 16:54
maximus wrote:The drive is HGST Ultrastar 7K6000 HUS726040ALE614 4TB SATA. The SMART is pretty clean, only 11 power on hours. It was sold as "New other, under 100 power on hours". Just curious, how easy and common is it for someone to clear the SMART on these and sell as newer than they really are?
December 16th, 2018, 11:09
fzabkar wrote:maximus wrote:The drive is HGST Ultrastar 7K6000 HUS726040ALE614 4TB SATA. The SMART is pretty clean, only 11 power on hours. It was sold as "New other, under 100 power on hours". Just curious, how easy and common is it for someone to clear the SMART on these and sell as newer than they really are?
AIUI, these models are not yet supported by any data recovery tool. Therefore I doubt that many people would know how to access the SA on these models.
One possible scenario is that your drive was purchased as a RAID spare.
December 16th, 2018, 11:10
December 16th, 2018, 19:14
That is interesting to know.Well ... Thos newer HGST drives still support the old IBM command to access the "SUPER SMART" so most likely the clear SMART command will work as well ... Its just a question of testing that out. Issue the super smart on and the clear S.M.A.R.T. check if it does work ... Most likely it will work even on the latest HGST He filled drives ...
I don't have any firmware tools or chip reader to do that. So unless there is a free firmware tool or VSC you can point me to that can dump the ROM, it won't happen.Also can you please DUMP the ROM content of your flash chip ? I might figure out the Super On VSC from the ROM dump.
December 17th, 2018, 15:24
December 17th, 2018, 15:27
maximus wrote:That is interesting to know.Well ... Thos newer HGST drives still support the old IBM command to access the "SUPER SMART" so most likely the clear SMART command will work as well ... Its just a question of testing that out. Issue the super smart on and the clear S.M.A.R.T. check if it does work ... Most likely it will work even on the latest HGST He filled drives ...
December 17th, 2018, 20:24
The results do show that some smart data is cleared. But the power on hours did not clear. Both outputs are with super smart on.Are you willing to do some testing on your drive ?
http://www.hddoracle.com/viewtopic.php?f=118&t=2171
On the link you have the commands to enable super SMART and then clear SMART. Can you test this and check if it does work with your (modern) HGST drive ?
ID# FLAG VALUE WORST THRESH RAW DATA ATTRIBUTE NAME
1 0x000b 100 100 16 0x00000000000001 Read Error Rate
2 0x0005 135 100 54 0x00000000000070 Throughput Performance
3 0x0007 146 100 24 0x00000801970142 Spin-Up Time
4 0x0012 100 100 0 0x0000000000001f Start/Stop Count
5 0x0033 100 100 5 0x00000000000000 Reallocated Sectors Count
7 0x000b 100 100 67 0x00000000000000 Seek Error Rate
8 0x0005 128 100 20 0x00000000000012 Seek Time Performance
9 0x0012 100 100 0 0x00000000000030 Power-On Hours Count
10 0x0013 100 100 60 0x00000000000000 Spin Retry Count
12 0x0032 100 100 0 0x0000000000001d Power Cycle Count
191 0x000a 100 100 0 0x00000000000000 G-Sense Errors
192 0x0032 100 100 0 0x00000000000020 Power-Off Retract Cycles
193 0x0012 100 100 0 0x00000000000020 Load/Unload Cycles
194 0x0002 253 130 0 0x00003000140016 Temperature
196 0x0032 100 100 0 0x00000000000000 Reallocation Events
197 0x0022 100 100 0 0x00000000000000 Current Pending Sectors
198 0x0008 100 100 0 0x00000000000000 Off-line Uncorrectable
199 0x000a 200 200 0 0x00000000000000 UDMA CRC Error Rate
211 0x0002 100 100 0 0x00007800160195 Vibration During Write
222 0x0012 100 100 0 0x00000000000029 Loaded Hours
223 0x000b 100 100 50 0x00000000000000 Load/Unload Retries
226 0x0007 187 187 40 0x00000000410002 Load-in Time
230 0x0012 94 94 0 0x00000000100001 GMR Head Amplitude
ID# FLAG VALUE WORST THRESH RAW DATA ATTRIBUTE NAME
1 0x000b 100 100 16 0x00000000000000 Read Error Rate
2 0x0005 100 100 54 0x00000000000000 Throughput Performance
3 0x0007 100 100 24 0x00000000000000 Spin-Up Time
4 0x0012 100 100 0 0x0000000000001f Start/Stop Count
5 0x0033 100 100 5 0x00000000000000 Reallocated Sectors Count
7 0x000b 100 100 67 0x00000000000000 Seek Error Rate
8 0x0005 100 100 20 0x00000000000000 Seek Time Performance
9 0x0012 100 100 0 0x00000000000030 Power-On Hours Count
10 0x0013 100 100 60 0x00000000000000 Spin Retry Count
12 0x0032 100 100 0 0x0000000000001d Power Cycle Count
191 0x000a 100 100 0 0x00000000000000 G-Sense Errors
192 0x0032 100 100 0 0x00000000000020 Power-Off Retract Cycles
193 0x0012 100 100 0 0x00000000000020 Load/Unload Cycles
194 0x0002 250 250 0 0x00001900190018 Temperature
196 0x0032 100 100 0 0x00000000000000 Reallocation Events
197 0x0022 100 100 0 0x00000000000000 Current Pending Sectors
198 0x0008 100 100 0 0x00000000000000 Off-line Uncorrectable
199 0x000a 200 200 0 0x00000000000000 UDMA CRC Error Rate
211 0x0002 100 100 0 0x00007800180192 Vibration During Write
222 0x0012 100 100 0 0x00000000000000 Loaded Hours
223 0x000b 100 100 50 0x00000000000000 Load/Unload Retries
226 0x0007 100 100 40 0x00000000000000 Load-in Time
230 0x0012 95 95 0 0x000000000c0004 GMR Head Amplitude
December 17th, 2018, 20:33
December 18th, 2018, 15:55
December 18th, 2018, 19:11
I have been bouncing ideas around in my head on a few different ways to utilize this feature, likely offering options to choose from. And one of those is to image by head. And if errors are encountered, it can move on to the next head, or maybe use some sort of aggressive skipping algorithm to skip out of a potential bad spot. I think the aggressive skipping is the way to go at first, because there is always the possibility of a good head giving errors when one of the heads hits physical media damage. I have seen logs where it looks like one surface had a bad spot, and the other heads also showed signs of reading difficulty when in this area.And asthis is a ATA standard even on modern drives that are fully locked and that tools like PC-3000 can't work with you might be able to "clone by heads" or skip bad heads using this feature ! Very cool.
December 19th, 2018, 14:00
December 25th, 2018, 20:44
Powered by phpBB © phpBB Group.