Seagate ST2000DL003?

[e932]

So it seems QNAP software tries to be smart. saves the fail information on the drive and gives a rats ** about what is reported by the system and linux raid software. Brilliant.

did you try this:

Code: Select all

mdadm --misc --detail /dev/md0

Maybe this will show some clues?

[fk8]

Still getting the "Disk Read/Write Error" even after manually taking the disk out of the array, restarting the NAS, and re-fitting it.

So it seems QNAP software tries to be smart. saves the fail information on the drive and gives a rats ** about what is reported by the system and linux raid software. Brilliant.

Try running a bad blocks scan - it'll take a few hours and find no problems, but at the end the NAS seems to wake up and realise that the drive is OK after all and initiate a RAID rebuild. Takes far longer than it should but it's the only way I've found that works...

Thanks for the advice but it seems to have fixed itself now... Happened in the middle of the n'th rebuild of the md0 mirror, but I doubt that was the trigger since rebuilding didn't do anything the first 2-3-4 times..

[fk8]

So it seems QNAP software tries to be smart. saves the fail information on the drive and gives a rats ** about what is reported by the system and linux raid software. Brilliant.

did you try this:

Code: Select all

mdadm --misc --detail /dev/md0

Maybe this will show some clues?

Yes, but what should I be looking for?

Before it said:

Code: Select all

# mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Tue May 20 16:44:07 2003
     Raid Level : raid1
     Array Size : 487243328 (464.67 GiB 498.94 GB)
    Device Size : 487243328 (464.67 GiB 498.94 GB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Jul 29 03:18:49 2011
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           UUID : 82c598d6:b9f6cf14:f4ddec3d:b9796114
         Events : 0.2415614

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       0       0        0    28015      removed

But now it seems to have magically fixed itself, so says:

Code: Select all

# mdadm --misc --detail /dev/md0
/dev/md0:
        Version : 00.90.01
  Creation Time : Tue May 20 16:44:07 2003
     Raid Level : raid1
     Array Size : 487243328 (464.67 GiB 498.94 GB)
    Device Size : 487243328 (464.67 GiB 498.94 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Jul 29 09:23:57 2011
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 82c598d6:b9f6cf14:f4ddec3d:b9796114
         Events : 0.2415634

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3

Pretty much as expected in other words. Before it was degraded, now it's not.

But the "Disk Read/Write Error" status was reported even after I detached the drive from the mirror, removed it from the tray and re-inserted it without attaching it to the mirror.

In other words, the "Disk Read/Write Error" status appears independent of the mirror.


I have posted more in this thread http://forum.qnap.com/viewtopic.php?f=2 ... &start=330 as it was more to the point on my problem. I want to avoid double posting and ask to continue discussion there if you have more suggestions. Thanks.

[AlexKe]

@ fk8

It seems you install two 500GB HDD on your TS-209, which is not the same model as Seagate ST2000DL003.
I reply your post here to clarify it is different case as discussion in this thread.
I saw your issue has been fixed by the post here. http://forum.qnap.com/viewtopic.php?f=2 ... 30#p213609

@ gkchamp , fuentesa

About the dropouts during normal use issue, can you suggest which kind of operation can reproduce the symptom? How often it happens on your NAS?
We also need you to provide the system event log and klog for further verification (you can PM me). Thanks

Please login the NAS via SSH (use Putty) and input following commands to get some Linux kernel message.
#/etc/init.d/klogd.sh dump > /share/Public/klogd.txt

[hoonu]

Damn... I'm migrating from a Synology system with a pair of these harddrives and after seeing all the comments here... I'm hesitant to say the least.

[AliceBToklas]

**... I'm migrating from a Synology system with a pair of these harddrives and after seeing all the comments here... I'm hesitant to say the least.

I can't blame you. However, I will say that I have a pair of these in my TS-219P+ and have seen no issues whatsoever. The drive was on the compatibility list when I made my purchase decision and were installed by the reseller. Mind you, I've only had it for a few months and use has been pretty light but it makes me nervous as well hearing about these issues. I'm just keeping my fingers crossed.

[fk8]

@ fk8
It seems you install two 500GB HDD on your TS-209, which is not the same model as Seagate ST2000DL003.
I reply your post here to clarify it is different case as discussion in this thread.
I saw your issue has been fixed by the post here. http://forum.qnap.com/viewtopic.php?f=2 ... 30#p213609

To clarify, originally I had two ST3500630NS (500GB). I have now switched one of these with a ST2000DL003 to test with.

They have similar disk geometry so it was easy enough to build a new partition table using the same start and end cylinders for the partitions. And this configuration is working as I have tested by detaching the 2TB disk from the mirror, mounted each partition to different mount points and attempted to read the data. That worked fine.

The issue is back now, so it was fixed only temporarily. More info under http://forum.qnap.com/viewtopic.php?f=2 ... 30#p213609

[hoonu]

I suppose I should order different drives at this point. Anyone have any recommendations on 2TB drives for a 259 or 459?

[sl1000]

Not really, the intel series nas systems don't have the issue with a drive not recognized at boot time, so you should be fine

[hoonu]

Not really, the intel series nas systems don't have the issue with a drive not recognized at boot time, so you should be fine

Ah... so this is just on Marvell based units? Sorry for my ignorance but the huge thread was a lil daunting.

Thanks

[PANQ212]

I just bought a TS 212 with two ST2000DL003. I am running on the latest firmware. The drives are running as single volumes.
It already happened two times that the first disk dropped out with the message "Drive 1 plugged out." in the logs.

Is there a solution on the way or do I have to return the system?

Thanks

[AlexKe]

Hi PANQ212,

Could you check if the dropout time is during the operation or after NAS reboot in the system event log?
How often it does happen since the TS-212 has upgraded to 3.4.4?

[lpb001]

Hi,
Since upgrading to 3.4.4 My ts 412 has been running fantastic nil dropouts on restart have been running this new firmware since released and seems to have solved my issues thanks.

[UkPaolo]

@ gkchamp , fuentesa

About the dropouts during normal use issue, can you suggest which kind of operation can reproduce the symptom? How often it happens on your NAS?
We also need you to provide the system event log and klog for further verification (you can PM me). Thanks

Please login the NAS via SSH (use Putty) and input following commands to get some Linux kernel message.
#/etc/init.d/klogd.sh dump > /share/Public/klogd.txt

Andy

Have already done this and given you the information months ago. Just go back through the thread and see where you have ignored my messages. How do I RMA for a refund?

You've also had a description of the problem and these logs from me. My messages to QNAP on the subject have also been ignored. It seems I will be forced to look at alternative NAS offerings since the problem has still not been solved

[AlexKe]

Hi UkPaolo,

http://forum.qnap.com/viewtopic.php?f=1 ... 68#p212268

Can you submit the online support form again and PM me your email address? I can help to expedite on it.