Seagate ST2000DL003?

[nielsgreef]

?

[keithhanlan]

One advantage of the Samsung HD204UI is that it still has a 3 year warranty while the ST2000DL003 is only one year. I must say that I do miss the affordable 5 year warranties. Now they only offer that on their premium drives and the "retail kits" - which amounts to paying $40 or more for the extended warranty. With the damage in Thailand and the consolidation of the industry, it's definitely tough times for the consumer these days.

caveat - the 3 year warranty is what the vendor claims. The information is unavailable on the Seagate/Samsung website. If anybody knows different, please speak up as this is a deciding factor for me.

[Exos]

Been running the debug firmware for two weeks now. Not alot of time i know but compared to previous I haven't had one issue.

Could just be dumb luck, but time will tell.

[Nitro182]

Been running the debug firmware for two weeks now. Not alot of time i know but compared to previous I haven't had one issue.

Could just be dumb luck, but time will tell.

Hi Exos,

How did you get a copy of the debug firmware? I have been complaining about this issue to QNAP since last year, sent them a PM on here with all the details to get a copy of the firmware and it has not been provided to me as promised.

This pretty much sums up my dealing with QNAP, heavily unreliable and don't seem to care a great deal.

Regards,
Adam.

[Exos]

It was emailed to me by Alex on the back of the post he made earlier.

I also have an open ticket regarding the issue.

As an aside, I've had a weekend of power outages to my house and each time it seems to have come up cleanly whereas before I had nothing but issues. I'm not saying the debug firmware is responsible but something appears to definitely be more stable.

Only thing i did notice is that I had the attached error message every 30s for just over 2 hours on the last outage and couldn't access any shares.

2012-04-09 16:11:50 System 127.0.0.1 localhost Stop process rpc.rquotad.

through to:

2012-04-09 18:09:10 System 127.0.0.1 localhost Stop process rpc.rquotad.

[nielsgreef]

So there is a debug firmware already? Strange that qnap did not contact me about it! signed up for it a few weeks ago....
I'm getting the feeling that QNAP will never fix these problems.

[nielsgreef]

Qnap?

[P3R]

So there is a debug firmware already? Strange that qnap did not contact me about it! signed up for it a few weeks ago....

It probably makes more sense communicating by PM directly to the person in question (QNAPAlex) on that matter.
'

[marcovanderheide]

Had a drive Failure 3 months ago while running some qpg packages and all the bells and whistles turned on.
Did a scan and rebuild that fixed the issue.
Turned most things off and just got a different drive fail on me. (same issue, seems that drive gets disconnected and follows with bad scan)
Just finished the scan and rebuilding again.
Hope there is a fix for this soon as cant have two drives failing at once (RAID 5)

[jtan]

Having problem with the same drive model on TS-412, getting disk read/write error and turns out HDD is perfect after doing scans.

[liamf]

Having problem with the same drive model on TS-412, getting disk read/write error and turns out HDD is perfect after doing scans.

Just a thing to check (and I know that it is not related to the topic of this discussion. But I am unlikely to be the only person to get burned by this)

I have a TS-410, same disk types - and also mad that they were on the compatibility list when I bought them, and then disappeared.
But however.

I have recently recovered from a problem where I was getting persistent read/write errors on disk #4 in my 4-disk RAID5 set.
Scans would reveal no issue. Put back in: fail again, read/write error disk #4. Red light on the unit. Kicked out of the array. The usual.

Extensive investigation eventually showed that the problem was that disk #3 was failing. There was nothing wrong with disk #4 at all.
Even though disk #3 showed up a fine in the status, was up to date in RAID events and so on.

I replaced disk #3 and many recovery adventures later, all is again well.

Just a thought. Go scan the other disks in your NAS ....

Liam

[marcovanderheide]

Great QNAP,

After the debacle on the ST2000DL003 (where we are still waiting for a fix on that), now releasing a firmware 3.7 that bricks.
Of course there is a lot of quality assurance and testing done before a new firmware is released, but these kind of bugs need to be picked up.
Sorry but i'm loosing confident in your product and am seriously looking for other alternatives

[schumaku]

After the debacle on the ST2000DL003 (where we are still waiting for a fix on that), now releasing a firmware 3.7 that bricks.

Debacle? In fact, there are very few issues here in the forum on the Samsung F4 HD204UI/Seagate ST2000DL003 - only on some four-bay units. Bet you mix-up something here with the Seagate ST2000DM001/ST3000DM001 now, which was identified to be a signal quality and timing issue, leading to firmware updates on QNAP (3.7) and Seagate side - and even to a hardware revision. I suggest you to contact QNAP support, they can run a check on your system. Don't know - we're running plenty of Samsung F4 HD204UI (aka. Seagate ST2000DL003) without issues.

Of course there is a lot of quality assurance and testing done before a new firmware is released, but these kind of bugs need to be picked up.

Both issues are not systematic - so very hard to catch in test processes.

[xlucas]

I reported drop out on TS 239 Pro with these Seagates ST2000DL003 . It was a few months ago ... I have changed these Seagate's green ** (ST2000DL003) with 3Tb Constellation ST33000650NS - FW 0004 and seems fine. Everything works nice and smooth. In case ST2000DL003 disable stand by helped a lot, however still some drop out happened from time to time.

[P3R]

In fact, there are very few issues here in the forum on the Samsung F4 HD204UI/Seagate ST2000DL003...

As far as I know it's the Seagate ST2000DL004 that is a rebranded Samsung HD204UI (5400 rpm). The Seagate ST2000DL003 that is the focus of this thread is the very problematic Seagate design (5900 rpm).

I think that Seagate abandoning their own model in favor of the Samsung is as close as admitting responsibility for any debacle as you can get...