Seagate ST2000DL003?

[manuel_]

Two weeks old 219P+ with firmware 3.5.0 Build 0816T
Two new Seagate ST2000DL003 (ST2000DL003-9VT1CC32 Model 9VT166 to be precise)

The system logs says:

2011-09-01 17:54:29 System 127.0.0.1 localhost [Mirror Disk Volume: Drive 1 2] Start rebuilding.
2011-09-01 17:53:07 System 127.0.0.1 localhost [Mirror Disk Volume: Drive 1 2] Drive 2 added into the volume.
2011-09-01 17:53:01 System 127.0.0.1 localhost System started.
2011-08-31 17:16:37 System 127.0.0.1 localhost System was shut down on Wed Aug 31 17:16:37 CEST 2011.
2011-08-31 15:57:11 System 127.0.0.1 localhost [USBDisk1] Device detected. The file system is fat.
2011-08-31 15:56:09 System 127.0.0.1 localhost [Mirror Disk Volume: Drive 1 2] RAID device in degraded mode.
2011-08-31 15:55:59 System 127.0.0.1 localhost System started.

I read that upgrading to 3.4.4 can solve this problem, but I am already on 3.5.0.
Any news for a newbe like me? Thank you.

[MiloW]

"I read that upgrading to 3.4.4 can solve this problem, but I am already on 3.5.0."
There's a special build of 3.4.4 for this specific issue (build 0719)

See this thread:
http://forum.qnap.com/viewtopic.php?f=160&t=47468

You 'upgrade' to that (it sorts out the 'UBOOT' for slow booting drives) then you can go back to 3.5.0

(Thanks go to QNAPAlex for the information).

[hededam]

Just got a new TS-419P+ Installed 4 x Seagate ST2000DL003-9VT1CC32. Set up the raid5. Everyting perfect.
After 4 houers online the dirve 3 failed with read/write error and the raid is in degrade mode.
Newest fimware 3.5.0 Build 0816T.
What is the best solution to this? Is this a bug in the firmware. Do you need any logfiles etc ?

br
jacob

[sl1000]

dit you test the drive already with seagate's test software.... drives do tent to fail most often in the first week of operation...

[manuel_]

@MiloW and sl1000
Thank you for answering. I'll check both and "update" the firmware.

[liamf]

Hmm

Same issue: 4x ST2000DL003 drives in TS-410 , running 3.5.0 Build 0816T, RAID 5 setup and synced.
Brand new system and disks, bought as <ahem> upgrade from old 2-disk NAS.

Set if off copying.

When checked in on it about 24 hours later.

* a disk had dropped out (so this is the "under load" scenario: ~8MBps write, no download), RAID array "degraded"
* although setup to do so, the system did not send me a warning email

Being new and innocent and not having found this thread, I swore a bit, and swapped disks in and out and checked them all for errors and reformatted the array from scratch and so on.
So now it's been reset to factory defaults, HDD sleep mode is turned off, and it's busy synchronising the RAID5 array again, from scratch.

Then I will set it off copying again.

But since I specifically checked the website for compatibility with these disks before buying 4 of them, I am not a happy camper at all that it turns out they are essentially NOT compatible at present.

I note that QNAP support wants files off the NAS in case of this problem reoccurring, and I will provide same when it does. I have 2TB of files to copy onto it, so if it is prone to error under load I fully expect it to do this again.

Unfortunately I will be away from home for a week: is there any way to force the NAS to recognise that it should do a rebuild, without physically removing/replacing the disk? Will a bad block check force this?

[liamf]

Actually, I retract that bit about the warning email.
I setup the account but I could not swear to having the little tick boxes checked on the "alert notification" tab

Now I am sure I do, so I will pay attention to that bit in future ...

[8850]

same problem / running 3.5.0 Build 0816T

2011-09-07 16:16:35 System 127.0.0.1 localhost [Drive 3] Start scanning bad blocks.
2011-09-07 16:15:24 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-07 16:15:22 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 removed.
2011-09-07 16:15:11 System 127.0.0.1 localhost Drive 3 plugged out.
2011-09-07 16:15:01 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 failed.
2011-09-07 16:14:57 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-07 16:14:56 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 removed.

[mzmap]

Just got a new TS-419P+ Installed 4 x Seagate ST2000DL003-9VT1CC32. Set up the raid5. Everyting perfect.
After 4 houers online the dirve 3 failed with read/write error and the raid is in degrade mode.
Newest fimware 3.5.0 Build 0816T.
What is the best solution to this? Is this a bug in the firmware. Do you need any logfiles etc ?

br
jacob

Hi all,

EXACTLY the same situation as hededam: same unit, same firmwares (hdd's and nas) same raid setup, same drive failure... Drive 3 failed after about 100 hours in total of operation. The unit had been up for about 2 days, under heavy I/O load while D/L, when the drive dropped. Am currently doing a bad blocks scan, seeing as how removing/inserting drive and restarting does not work. SMART scan finds no errors.


2011-09-08 17:09:58 System localhost [Drive 3] Start scanning bad blocks.
2011-09-08 16:42:37 System localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-08 16:42:14 System localhost System started.
2011-09-08 16:40:11 System localhost System was shut down on Thu Sep 8 16:40:11 CEST 2011.
2011-09-08 16:39:07 admin --- [Power Management] System will be restart now.
2011-09-08 16:37:20 System localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-08 16:37:19 System localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 removed.
2011-09-08 16:37:09 System localhost Drive 3 plugged out.
2011-09-08 16:27:44 System localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-08 16:27:22 System localhost System started.
2011-09-08 16:25:23 System localhost System was shut down on Thu Sep 8 16:25:23 CEST 2011.
2011-09-08 16:24:17 admin --- [Power Management] System will be restart now.
2011-09-08 13:20:07 System localhost [HDD SMART] HDD 3 Full Test result: Completed without error.
2011-09-08 07:54:25 System localhost [HDD SMART] HDD 3 Full Test started.
2011-09-08 07:54:18 System localhost [HDD SMART] HDD 3 Rapid Test was cancelled.
2011-09-08 07:54:06 System localhost [HDD SMART] HDD 3 Rapid Test started.
2011-09-08 06:52:28 System localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 failed.
2011-09-08 06:52:23 System localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-08 06:52:21 System localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 removed.

Thank you for any assistance... and yes, it is kinda irritating to have chosen a compatible drive, only to find it isn't. I hope the issue can be resolved, because I fell in love with my unit ... until the drive failed

[nielsgreef]

Sound familiair, over here the last drop was 2 weeks ago ( 3 in a row) after this i rebuilded the array and let it idle.
It is now idle for 2 weeks and no drops.
This definatly has something to do with the disks on load! in my opnion this is a Error recovery control problem.
i.e. the seagte st2000dl003 firmware does not have the ability to enable error recovery control wich causes mdadm (linux software raid wich qnap uses) to drop the disks when there is a timeout.
the seagate disk timeout is most probaly 20> seconds and the mdadm timeout 8< so when the disk is recovering from read/write erros mdadm with a lower timeout cannot acces the drive and then.... drop!

Qnap is reproducing this problem in their test environment so i hope they come up to a solution wich will solve the problems with the st2000dl003 drives!

[Dreamwatcher]

Hello everyone - going in with the exact same Problem.
-TS419+
-4x Seagate ST2000DL003-9VT1CC32 RAID5
-3.5.0 0816T

NAS was running idle since about a few weeks, yesterday i started moving around files on the NAS, multiple copy jobs to the NAS, all at the same time - so massive load on the NAS. CPU was almost a few hours at 100%.
First Drive 1 failed, got the plugged out message and so on. SMART Check no Error - did a bad block scan - after that the RAID5 got rebuilded an everything was back to normal.
Today, again moving files, massive load on the CPU - Drive 3 failed - same thing as above.
Must be something on QNAPs side, because the HDDs are quite new, only a few weeks old. And seeing a few other People with the exact same problems, i must be something to clear up on the Firmware Side.

Here are some of my Logs, despite they are looking the same as the logs from previous users.

13:23:22 System 127.0.0.1 localhost [Drive 3] Start scanning bad blocks.
2011-09-09 13:23:03 System 127.0.0.1 localhost Network connection resume.
2011-09-09 13:22:29 System 127.0.0.1 localhost [External Drive] Job Serien-->Backup started.
2011-09-09 13:21:45 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-09 13:21:22 System 127.0.0.1 localhost System started.
2011-09-09 13:19:19 System 127.0.0.1 localhost System was shut down on Fri Sep 9 13:19:19 CEST 2011.
2011-09-09 13:18:09 admin 192.168.1.108 --- [Power Management] System will be restart now.
2011-09-09 13:14:25 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-09 13:14:25 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 removed.
2011-09-09 13:14:03 System 127.0.0.1 localhost Drive 3 plugged out.
2011-09-09 13:13:54 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 failed.
2011-09-09 13:13:47 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-09 13:13:46 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 3 removed.


The failed drives only showed up after a restart of the NAS, with the Disk-Write/Read Error.

Also wondering about why the error dont occoured when i was filling the NAS with data for the first time, maybe the thing is about heavy load with multiple files moving around? When i am using my NAS as source for my XBMC HTPC, there never has been an error regarding the drives...

PLEASE QNAP let us know whats going on there, because a rebuild everyday isnt acceptable.

[nielsgreef]

Since not loading my nas with anything no drops......

[eatemalive]

I also just brought a 419+ with these HDDs based on the compatibility list. I also have had two dropout read/write errors.....
I am extremely ** off that i spent $1000 bucks on something that doesn't even work. Can someone from QNAP explain to me why these drives are still on the compatibility list?????? Is there going to be a fix for this? or should i attempt to take the products back?(not that there is anything wrong with the drives). If so how long?

[8850]

Occur twice in a week. The manufacturer should be solved urgently.
This problem occurs with many clients. I do not trust in the product.



Type Date Time Users Source IP Computer name Content
2011-09-14 15:28:31 System 127.0.0.1 localhost [Drive 4] Start scanning bad blocks.
2011-09-14 15:28:09 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-14 15:28:06 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 4 removed.
2011-09-14 15:27:55 System 127.0.0.1 localhost Drive 4 plugged out.
2011-09-14 13:21:34 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 4 failed.
2011-09-14 13:21:30 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] RAID device in degraded mode.
2011-09-14 13:21:28 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 4 removed.
2011-09-14 01:25:21 admin 192.168.0.9 --- [Web Server] Started successfully.

[liamf]

I note that the compatibility list says
"Please update the NAS firmware to V3.4.4 for enhanced compatibility with this hard drive model"

Does that mean that if I downgrade from 3.5.0 to 3.4.4 I will get better compatibility?
Has anyone experienced the disk dropout under load issue with 3.4.4?