Hi,
This is such a strange problem, I just don't know where to start, so I'm really hoping someone out there may have some inspiration .
A friend of mine didn't realise that hard drives go wrong, so he put all his life's photos on his single drive Synology. Now, after seven years of service, it's gone wrong.
It's a Seagate Barracuda ST3000DM001 3TB SATA 3.5", originally sold in a Synology DS112j. In Windows, chkdsk reports it as being 3950MB rather than the 2794GB it should be.
Funnily enough, I also have a Diskstation, four disks, which originally had the same disks in, but one I'd replaced because it was beginning to fail. I thought it seemed like an electronics problem, so swapped over the electronics board of both drives. Here's where the weirdness gets weirder! Now, BOTH drives report a size of 3950MB in chkdsk ! When I swapped the electronics back, it did go back to the original report, his showing 3950MB and mine 2794GB.
I tried Seagate's SeaTool, but it's pretty useless and just fails tests on both disks, whichever electronics they have.
For my next step, I was going to update the firmware, but it's a bit of a stab in the dark.
Any other great ideas out there???
Many, many thanks,
Clive
Seagate Where did my disk go???
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
- cgrenier
- Site Admin
- Posts: 5432
- Joined: 18 Feb 2012, 15:08
- Location: Le Perreux Sur Marne, France
- Contact:
Re: Seagate Where did my disk go???
Try to reset the DCO (Device Configuration Overlay) configuration. You should be able to do it whith seagate tools or with "hdparm --dco-restore" under Linux.
Do you get the correct disk size after that ?
Do you get the correct disk size after that ?
-
- Posts: 2
- Joined: 21 Dec 2018, 15:02
Re: Seagate Where did my disk go???
Hi Christophe,
Many thanks for your reply.
SeaTools was pretty hopeless - only seemed to offer tests, so I followed your advice and switched to Linux, using Knoppix on a USB stick.
First try was through USB/SATA adapter, but I got this error:
I then figured that not all (and especially low-level) commands are supported by USB adapters, so I used the eSATA port on my laptop.
This time I got:
I tried the -N switch as well, but got this:
It still showed up incorrectly.
Here is the response from -I:
I get the strong impression that something inside is damaged and the only way to recover is for a professional to take apart. However, I am interested to know how to decode the response, which I assume is some kind of error that hdparm doesn't know how to interpret?
This is the response for a working drive of the same model:
Regards,
Clive
Many thanks for your reply.
SeaTools was pretty hopeless - only seemed to offer tests, so I followed your advice and switched to Linux, using Knoppix on a USB stick.
First try was through USB/SATA adapter, but I got this error:
Code: Select all
HDIO_DRIVE_CMD(dco_restore) failed: Invalid argument
This time I got:
Code: Select all
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Code: Select all
setting max visible sectors to 5860533168 (permanent)
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 a0 af 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
max sectors = 8089950/1(17?), HPA setting seems invalid (buggy kernel device driver?)
Here is the response from -I:
Code: Select all
ATA device, with non-removable media
Model Number: ST3000DM001
Serial Number: Z1F2A0TJ
Firmware Revision: CC44
Transport: Serial, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x0029)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 8089950
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 3950 MBytes
device size with M = 1000*1000: 4142 MBytes (4 GB)
cache/buffer size = unknown
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Recommended acoustic management value: 254, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
Write-Read-Verify feature set
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* unknown 119[7]
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
Device-initiated interface power management
Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[7]
unknown 206[12] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
210min for SECURITY ERASE UNIT. 210min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c5004fa59688
NAA : 5
IEEE OUI : 000c50
Unique ID : 04fa59688
Integrity word not set (found 0x0000, expected 0x82a5)
This is the response for a working drive of the same model:
Code: Select all
ATA device, with non-removable media
Model Number: ST3000DM001-1CH166
Serial Number: W1F1QVN7
Firmware Revision: CC24
Transport: Serial, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x0029)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 5860533168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 2861588 MBytes
device size with M = 1000*1000: 3000592 MBytes (3000 GB)
cache/buffer size = unknown
Form Factor: 3.5 inch
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = ?
Advanced power management level: 128
Recommended acoustic management value: 208, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
Write-Read-Verify feature set
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
* DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
unknown 206[7]
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
320min for SECURITY ERASE UNIT. 320min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c5005cf95bbc
NAA : 5
IEEE OUI : 000c50
Unique ID : 05cf95bbc
Checksum: correct
Clive
- cgrenier
- Site Admin
- Posts: 5432
- Joined: 18 Feb 2012, 15:08
- Location: Le Perreux Sur Marne, France
- Contact:
Re: Seagate Where did my disk go???
"setting max visible sectors to 5860533168 (permanent)" looks good, the remaining of the message not so good...
Try a cold restart of your computer and see if something has changed.
If it's still bad, you may have to contact a data recovery company.
Try a cold restart of your computer and see if something has changed.
If it's still bad, you may have to contact a data recovery company.