Seagate ST2000DL003?

[davep]

I'm fed up with this; I've just wasted another hour of my time trying to fix this.

Does anybody in the UK who is experiencing this problem fancy joining forces to put pressure on QNAP? Perhaps there is scope for some form of legal action or involvement of trading standards - this product is not fit for purpose and we deserve a fix or a refund. PM me if interested.

[mlynchit]

Grow up you people.

[schumaku]

@davep: Have you bought the device from a retailer, distributor or from QNAP? Have you bought both the NAS and the HDD together with the obvious intent to install these HDD in the NAS, or were the even presinstalled? In any case, you closed a contract with the retailer or the distributor - as from what I?m aware QNAP does not sell direct in the UK. Every reseller taking his business seriously, will support you with a replacement or an exchange.

Look, there was a similar issue with the WD Green devices. As long as the drives are healty, and things are well - there wown't be any issues. Even when doing in-depth tests with new HD models or HDD series, it's very unlikley, that something will go wrong in the first hous, days, or weeks. But at that time, the market pressure expects the new disks listed in the compatibility list. It's simply not transparent, what the HDD manufacturers are doing when it comes to surface read/write problems - because the IDE and SATA drive (and their interfaces, hard- and software-wise) are done in a very K.I.S.S. way. What might work in a desktop computer - simply leave the user in a "hung" stat for minutes for example - does badly fail in a NAS. The NAS has to take automated actions when things go wrong, ie. a disk does not come-back to a normal operational mode within reasonable time.

Sorry, that's about the same I had to write in reply to the unlucky early adopters of WD Green desktop drives.

On the other hand, I'm aware of many users out in the market still operating such "questionable" or "removed follwoing bad market experience" HDD aparently in a reliable way and are - beyond the ongoing concens - happy NAS users.

[AlexKe]

Hi folks,

It is few weeks passed since last time we can reproduce the issue with ST2000DL003. We will not be able to debug if the symptom cannot be reproduced by standard process or stress test. To expedite the process, we intend to recruit some volunteers to install the firmware version with debug mode enabled, which might affect the access performance. If you can help to track the issue, please contact us via private message with the following info.

Here is the example.
======================
Subject: Seagate ST2000DL003 issue tracking
NAS model: TS-412
Current firmware version: 3.6.0 build0210
Description:
- what is the date last time HDD dropout?
- how many time it happens since when?
- which services were used when dropout issue occurred on your NAS?
Contact Email address:

[nielsgreef]

Anynews on the debug firmware?

[nielsgreef]

Any news on the debug firmware?

[alexd]

Any updates on this? I have two Qnaps in service with ST2000DL003 and one of them recently developed this issue.

[davep]

any news on the debug firmware?

[gizmotic]

Our QNAP 412 has the same problem.

After searching the web i found this thread and i'm quite astonished that QNAP hasnt released a fix yet.
I've bought these drives because QNAP listed them on the compatibilty list!

So any news?

[davep]

Our QNAP 412 has the same problem.

After searching the web i found this thread and i'm quite astonished that QNAP hasnt released a fix yet.
I've bought these drives because QNAP listed them on the compatibilty list!

So any news?

QNAP do seem to be working on this behind the scenes, but getting an update is like getting blood from a stone.

These problems happen, I've worked in IT long enough to understand that - but the customer service has been shocking, I really don't get the impression they care. You'd think given the length of this forum thread it would be treated like a priority and frequent updates given.

[Scillonian]

These problems happen, I've worked in IT long enough to understand that - but the customer service has been shocking, I really don't get the impression they care. You'd think given the length of this forum thread it would be treated like a priority and frequent updates given.

I had three of these drives in my TS-459 Pro+ but eventually retired them after reading about the problems with them on here and other places. It was an expense I didn't want to incure, especially as I came just as drive prices started to increase, but came to the conclusion that fairly soon one the the drives was going to fail. I'm now glad I did.

I now use them for NAS backups in conjunction with an eSATA enclosure. Two of the drives still work fine but one has recently taken to going offline at random. It can go offline while under load or at idle. The only way to get the drive back online is to power off and on again. (Same effect as pulling the drive and reinserting.)

Out of curiosity I reformated the problem drive to NTFS and started to use it with Windows 7 64-bit with an different eSATA enclosure. Initially it worked fine but soon started to go offline again. I then reformatted the drive back to ext4 and tried it with a Fedora 16 with the same results.

This problem drive passes SeaTools tests and the only anomaly in the SMART data is the Power On Hours that are about three or four times more than they should be. (The Power On Hours on the other two drives are also about three or four times what they should be.)

With the best will in the world I don't see how a NAS firmware update can fix a problem with a drive that takes itself offline at random where the problem is with the drive itself.

[lpb001]

Hi,
I had issues with these drives dropping on reboot a while ago now, then qnap released a firmware specifically for users with these drives.
I installed that firmware which is what i am still currently using
3.4.4 Build 0718T
For months i have had no problems numerous reboots and nas stayed rock solid. In the past month i have had 4 dropouts at random times. when i go into disk managment/volume management the disk which has drooped out says no disk installed. I pull manually pull the disk out and put back in. It then tells me there is a read write error.
I click on bad/blocks scan after that completes disk is back and nas rebuilds.
I have a ts412 running
sab
sickbeard
couchpotato
python
phpmyadmin
have sql server enabled
If there is a log file i can grab and post let me know how i would love this issue to be resolved
I am wondering what could have happened for it to be working for months with out issue then suddenly 4 dropouts in the last month.

[sanke1]

Almost 10 months now and not a single drop out so far.

My config remains same. TS-412 with RAID10 and no QPKG or additional softwares.
Sleep disabled.

Data filled is nearing 1TB out of 4TB.

[anon022]

I've had 1 ST2000DL003 drive in my NAS for half a year now with absolutely no problems (up to 4 months without a reboot). Well, to be honest i had to reboot because it seemed like whole NAS got really slow and i had troubles connecting to it, so i rebooted it and updated from 3.5 to 3.6.1
Yesterday i got 3 more of those hoping to build RAID5 with them. First I could not create RAID5 volume, log error was :
[RAID5 Disk Volume: Drive 2 3 4] Formatting failed.
[RAID5 Disk Volume: Drive 2 3 4] Formatting failed(Cannot unmount disk).
After that i tried to run rapid test but it stopped at 90%.
Finally i started bad block scan on all of the drives and after 5 hours disk 4 dropped out. Bay 4 would not recognize any other drive. Rebooted the device and the disk could be seen again. Atm i'm building RAID5 with drives 2,3,4 and it seems like there are no problems for the moment. I still can not run rapid test on any of the drives (freezes at 10 or 90%).



I'm just wondering if there is any reason to get ST2000DM001 drives instead of ST2000DL003. Should I do that? Send Green drives back, wait few weeks and then get 7200.12 for a little extra. Would they be more stable (not dropping)? From this forum I got the impression that all non-enterprise (I will actually be surprised if enterprise drives do not drop out) seagate and WD drives can not be used in NAS. (ironically, huh?). I would prefer to have 4 "Green" (silent and lower power) drives in my low-end home NAS. But that's not an option as it seems.


I'll wait a week and see how ST2000DL003s will behave. Hope to get some response on ST2000DL003 vs ST2000DM001.
PS: Is there any option to automatically reboot NAS when a disk has dropped? Rebooting seems to help.

UPD: Got Disk Read/Write Error on the same bay (there's got to be a connection, to you QNAP guys). I'm just gonna get Samsung F4 instead.

[nielsgreef]

Any news on the debug firmware yet? it has been more then 2 weeks now and look like absolute radio silence.....