Logical Unit WWN Device Identifier: 5000c5004fa59688 * SMART Command Transport (SCT) feature setĢ10min for SECURITY ERASE UNIT. * READ_LOG_DMA_EXT equivalent to READ_LOG_EXTĭevice-initiated interface power management *ĝevice Configuration Overlay feature set Recommended acoustic management value: 254, current value: 0ĭMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6Ĭycle time: no flow control=120ns IORDY flow control=120ns R/W multiple sector transfer: Max = 16Ĝurrent = 16 Standby timer values: spec'd by Standard, no device specific minimum Used: unknown (minor revision code 0x0029)ĬHS current addressable sectors: 16514064ĭevice size with M = 1024*1024: 3950 MBytesĭevice size with M = 1000*1000: 4142 MBytes (4 GB)
Seagate disk tools linux update#
I tried Seagate's SeaTool, but it's pretty useless and just fails tests on both disks, whichever electronics they have.įor my next step, I was going to update the firmware, but it's a bit of a stab in the dark.Ĭode: Select all ATA device, with non-removable media 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 thought it seemed like an electronics problem, so swapped over the electronics board of both drives. In Windows, chkdsk reports it as being 3950MB rather than the 2794GB it should be.įunnily 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. It's a Seagate Barracuda ST3000DM001 3TB SATA 3.5", originally sold in a Synology DS112j. Now, after seven years of service, it's gone wrong. Ī friend of mine didn't realise that hard drives go wrong, so he put all his life's photos on his single drive Synology.
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.
0 kommentar(er)
