June 25, 201610 yr I retested this several times and the same thing happened without fail. Drive is a Seagate Archive 8TB (the SMR one), mounted via Unassigned Device When my VM extracts an archive to the HDD, the partition would "drop" within a few minutes / seconds with errors usually associated with a bad SATA cable (please see syslog). Note that only the partition drops, the drive itself still shows up. A restart is required for things to return to normal. However, it would NEVER drop if I transfer files from the VM to the HDD or via mc. I have tried gigabytes of data and nothing happened. Smart reports before the crash and after reboot were ok - NOT even an increase in UDMA-CRC-Error-Count as would usually happen with a bad SATA cable. However, right after the crash, the smart report says this: smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: /2:0:0:0 Product: User Capacity: 600,332,565,813,390,450 bytes [600 PB] Logical block size: 774843950 bytes scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46 >> Terminate command early due to bad response to IEC mode page A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I tested the drive separately on my workstation and everything is fine. No data loss, no file system corruption. New data can be added and verified fine. Old data can be extracted and md5 check is ok. It's as if the particular write from VM to the drive just simply failed to happen and somehow triggers the entire partition to fail or something. It's very weird. This only started to happen since I configured my VM to extract archives automatically to the Unassigned Device share. It did not happen at all before that (despite gigabytes of data transfer) and would not recur until I start an archive extraction from the VM. syslog.zip
June 25, 201610 yr Author Ok, the Seagate Archive drive has now developed End-to-end error which smartctl reports as FAILING NOW. Googling says it's generally associated with a dying cache. I think this kinda explains why it fails under a certain workload. The extraction must have "overuse" the cache or something while normal high speed copying uses less of it. Anyway, I am initiating a warranty replacement. Just keep this thread here in case anyone else may have the same issue.
Archived
This topic is now archived and is closed to further replies.