Data already present on disks bought - are they second hand?

Associate
Joined
9 Feb 2016
Posts
14
Has anyone got the 3x3TB WD Red bundle, and was there data on them already? 2 of my 3 had a RAID1 array on it, with a Linux /boot partition and Emby Server data.

Was this done just as a test? SMART info says they only have 10 start_stop_counts - can SMART data be reset? Are these drives second hand?
 
Soldato
Joined
5 Nov 2014
Posts
7,541
disk drives normally come blank and with no data on or partitions active on them at all.

it sounds ;like they have been used for a very short time for something.

did you get them from OCUK? if so put a post in the CS section about it

did they come in a anti static bag at all with seals on?
 
Man of Honour
Joined
13 Oct 2006
Posts
91,040
I've occasionally had a disc turn up with promotional material/extra tools/autorun additions by the drive manufacturer on it but largely they have been empty, anything else sounds like a return.
 
Associate
OP
Joined
9 Feb 2016
Posts
14
Yeah, I'm in contact with support but haven't heard back from my latest message. And I think I know why they had data: building a RAID5 array now, and one of the drives is full of read errors :|

This is so disappointing, I buy all my stuff at OcUK and now they've sent me a returned drive that is defective. Gonna try and reply to the WebNote I created
 
Associate
OP
Joined
9 Feb 2016
Posts
14
What I'm seeing:

[ 1328.515541] md/raid:md0: read error corrected (8 sectors at 74084912 on sde)
[ 1328.515564] md/raid:md0: read error corrected (8 sectors at 74084920 on sde)
[ 1328.515571] md/raid:md0: read error corrected (8 sectors at 74084928 on sde)
[ 1328.515578] md/raid:md0: read error corrected (8 sectors at 74084936 on sde)
[ 1328.515585] md/raid:md0: read error corrected (8 sectors at 74084944 on sde)
[ 1328.515592] md/raid:md0: read error corrected (8 sectors at 74084952 on sde)
[ 1328.515598] md/raid:md0: read error corrected (8 sectors at 74084960 on sde)
[ 1328.515605] md/raid:md0: read error corrected (8 sectors at 74084968 on sde)
[ 1328.515611] md/raid:md0: read error corrected (8 sectors at 74084976 on sde)
[ 1328.515618] md/raid:md0: read error corrected (8 sectors at 74084984 on sde)
[ 1332.007995] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1332.013209] ata6.00: irq_stat 0x40000001
[ 1332.018341] ata6.00: failed command: READ DMA EXT
[ 1332.023449] ata6.00: cmd 25/00:f8:e8:a0:6b/00:01:04:00:00/e0 tag 3 dma 258048 in
[ 1332.023449] res 51/40:f8:e8:a0:6b/00:01:04:00:00/e0 Emask 0x9 (media error)
[ 1332.033751] ata6.00: status: { DRDY ERR }
[ 1332.038881] ata6.00: error: { UNC }
[ 1332.083884] ata6.00: configured for UDMA/133
[ 1332.083967] sd 5:0:0:0: [sde] Unhandled sense code
[ 1332.083976] sd 5:0:0:0: [sde]
[ 1332.083982] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1332.083989] sd 5:0:0:0: [sde]
[ 1332.083994] Sense Key : Medium Error [current] [descriptor]
[ 1332.084003] Descriptor sense data with sense descriptors (in hex):
[ 1332.084007] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 1332.084030] 04 6b a0 e8
[ 1332.084042] sd 5:0:0:0: [sde]
[ 1332.084048] Add. Sense: Unrecovered read error - auto reallocate failed
[ 1332.084056] sd 5:0:0:0: [sde] CDB:
[ 1332.084060] Read(16): 88 00 00 00 00 00 04 6b a0 e8 00 00 01 f8 00 00
[ 1332.084087] end_request: I/O error, dev sde, sector 74162408

(goes on like this for thousands of lines)
 
Associate
Joined
17 May 2013
Posts
1,638
You could open up a thread in the CS section. You might get a quicker response in there.

Sounds like someone may have returned some "unwanted" drives and convincingly sealed up used drives to make them look as if they hadn't been used.
 
OcUK Staff
Joined
31 Jul 2010
Posts
34,426
Location
OcUK HQ
Hi

Can you provide me your order number as per post #7

If the drive was sealed then it has to be new and it would have come from the manufacturer like this

Bailey
 
Back
Top Bottom