Seagate 3TB ST3000DM001 and 2TB ST2000DM001 Compatible?

[dkwdkw]

Update on my situation. I did the "search for bad blocks" function (took about 24 hours) and that automatically started rebuilding the array once it finished. That was running about 24 hours too. So, it looks like that is the recovery path? Also, based on some comments about the disk read/write error being caused by a slow startup from sleep mode (I think I saw that?), I have turned off the sleep function on the NAS. Will keep this thread updated....

Dave

[dkwdkw]

Not sure whether to return the qnap or not ...

It's the drives, not the QNAP? Can you exchange them for non "green" drives? That should fix the problem?

[luwak]

Update: The drive failure has returned. I replaced my Drive 1 with a new drive, ran fine for a few weeks and guess what. Got up this morning to the red light flashing, checked sys log and sure enough same symptoms I had prior. Drive 1 has been removed. I am going to try a reformat and redo the RAID again but I have no confidence that it will fix anything. I am really unhappy with this purchase and really do not know where to go. I really do not think it is a drive issue and i guess will have to send to QNAP to fix this issue. Oh and I also disabled the 'Stand By' feature just to see if this would make a difference. I also have placed the previous drive in a PVR which is recording daily and guess what works just fine, another reason I feel that it is not a drive issue. And really if it is THEN TAKE OFF THE ST2000DM001 DRIVES OFF THE COMPATIBILITY LIST.

[bazinga]

I can report problems with ST3000DM001 on the TS-412 as well. Disk Read/Write Error after only one week of use.

[sl1000]

anything interesting at the end of a kernel log dump? (log in via ssh and do:)

Code: Select all

/etc/init.d/klogd.sh dump

[luwak]

So after taking out Drive 1 install in a Windows box, reformat drive and ran check disk and came back clean. I then deleted the volume and reinstalled back into the NAS and allowed the RAID to be rebuilt. Once this was completed I rebooted the NAS and got the same error message as when I first encountered this issue which is [RAID5 Disk Volume: Drive 1 2 3 4] The file system is not clean.

Then I decided to run check disk from the NAS which also completed without any errors and before I left for work started the transfer of 500 GB which completed successfully. BUT now the response of the NAS is really slow and I gave it a reboot.

Now the status light is flashing red and back to square one.

Here is some of the dump file,
<4>[ 1418.680000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1418.680000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1449.650000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1450.660000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1462.900000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1462.900000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1462.900000] [1 1] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1462.900000] [1 1] QNAP: Got fake interrupts (HW error).
<5>[ 1474.800000] eth1: stopped
<5>[ 1474.870000] eth1: started
<4>[ 1493.670000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1493.670000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1494.680000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1494.680000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1547.690000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1599.700000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1611.990000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1611.990000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1613.380000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recov
y directory
<6>[ 1613.380000] NFSD: starting 90-second grace period
<4>[ 1643.710000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1644.720000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1655.010000] active port 0 :139
<4>[ 1655.010000] active port 1 :445
<4>[ 1655.010000] active port 2 :20
<6>[ 1657.170000] md: md4: recovery done.
<4>[ 1657.360000] RAID1 conf printout:
<4>[ 1657.360000] --- wd:2 rd:2
<4>[ 1657.360000] disk 0, wo:0, o:1, dev:sda2
<4>[ 1657.360000] disk 1, wo:0, o:1, dev:sdb2
<4>[ 1661.960000] nfsd: last server has exited, flushing export cache
<6>[ 1662.500000] warning: `proftpd' uses 32-bit capabilities (legacy support
use)
<4>[ 1670.240000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1670.240000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1701.730000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1702.740000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1714.900000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running
2fsck is recommended
<4>[ 1719.810000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1719.810000] [1 0] QNAP: Got fake interrupts (HW error).
<6>[ 1719.880000] EXT4-fs (sdt1): mounted filesystem with ordered data mode
<4>[ 1750.750000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1751.760000] ENABLE_WRITE_CACHE (current: enabled).
<6>[ 1766.490000] warning: process `pic_raw' used the deprecated sysctl system
all with 8.1.2.
<4>[ 1770.460000] rule type=2, num=0
<4>[ 1771.790000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running
2fsck is recommended
<4>[ 1772.740000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recov
y directory
<6>[ 1772.740000] NFSD: starting 90-second grace period
<4>[ 1773.730000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1773.730000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1804.770000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1805.780000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1815.260000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1815.260000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1846.790000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1847.800000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1861.310000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1861.310000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1892.810000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1893.820000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1903.340000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1903.340000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1903.450000] active port 0 :139
<4>[ 1903.450000] active port 1 :445
<4>[ 1903.450000] active port 2 :20
<4>[ 1934.830000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1935.840000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1952.370000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 1952.370000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 1983.850000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 1984.860000] ENABLE_WRITE_CACHE (current: enabled).
<6>[ 1995.720000] Loading iSCSI transport class v2.0-871.
<5>[ 1997.160000] iscsi: registered transport (tcp)
<4>[ 2000.550000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 2000.550000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 2031.870000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 2032.880000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 2046.520000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 2046.520000] [1 0] QNAP: Got fake interrupts (HW error).
<4>[ 2077.890000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 2078.900000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 2095.880000] nfsd: last server has exited, flushing export cache
<4>[ 2104.600000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recov
y directory
<6>[ 2104.600000] NFSD: starting 90-second grace period
<4>[ 4350.910000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 4401.920000] ENABLE_WRITE_CACHE (current: enabled).
<4>[ 4414.160000] [1 0] Detect fake interrupts (handleUnrecoverableError).
<4>[ 4414.160000] [1 0] QNAP: Got fake interrupts (HW error).

[luwak]

So my NAS continued to not respond and I was also unable to log into the GUI so I decided to remove all 4 drives and reboot the NAS. This appears to have cleared my slow response; I then re-inserted all the drives and allowed for a re-sync. This has completed and I am again up and running with no issues and no error messages. For how long, only time will tell.

And the output from my latest dump now looks like this.
( What is the command to tail this or be able to dump to a txt file, please and thanks!)
[ 70.640000] kjournald starting. Commit interval 5 seconds
[ 70.670000] EXT3-fs (md9): using internal journal
[ 70.670000] EXT3-fs (md9): mounted filesystem with writeback data mode
[ 70.990000] kjournald starting. Commit interval 5 seconds
[ 71.010000] EXT3-fs (md9): using internal journal
[ 71.010000] EXT3-fs (md9): mounted filesystem with writeback data mode
[ 71.460000] kjournald starting. Commit interval 5 seconds
[ 71.540000] EXT3-fs (md13): using internal journal
[ 71.540000] EXT3-fs (md13): recovery complete
[ 71.540000] EXT3-fs (md13): mounted filesystem with writeback data mode
[ 87.630000] fuse init (API version 7.13)
[ 87.830000] NET: Registered protocol family 5
[ 87.920000] eth0: link down
[ 87.920000] eth0: started
[ 87.990000] eth1: started
[ 88.190000] xor: measuring software checksum speed
[ 88.240000] arm4regs : 1078.000 MB/sec
[ 88.290000] 8regs : 819.200 MB/sec
[ 88.340000] 32regs : 915.600 MB/sec
[ 88.340000] xor: using function: arm4regs (1078.000 MB/sec)
[ 88.440000] eth0: stopped
[ 88.460000] eth0: mac address changed
[ 88.480000] eth0: started
[ 88.550000] eth1: stopped
[ 88.560000] eth1: mac address changed
[ 88.590000] eth1: started
[ 88.830000] raid6: int32x1 84 MB/s
[ 89.000000] raid6: int32x2 116 MB/s
[ 89.170000] raid6: int32x4 122 MB/s
[ 89.340000] raid6: int32x8 114 MB/s
[ 89.340000] raid6: using algorithm int32x4 (122 MB/s)
[ 89.700000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e
ck is recommended
[ 89.760000] md: raid6 personality registered for level 6
[ 89.760000] md: raid5 personality registered for level 5
[ 89.760000] md: raid4 personality registered for level 4
[ 89.810000] device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: d
evel@redhat.com
[ 90.030000] cryptodev: driver 0.9 loaded.
[ 90.110000] usbcore: registered new interface driver usbhid
[ 90.110000] usbhid: USB HID core driver
[ 90.140000] usbcore: registered new interface driver usblp
[ 90.150000] sysinfo: Module loaded.
[ 90.300000] ufsd: module license 'Commercial product' taints kernel.
[ 90.300000] Disabling lock debugging due to kernel taint
[ 90.390000] ufsd: driver U82 (Mar 2 2012 08:58:31) LBD=OFF with ioctl lo
d at bf1f5000
[ 90.390000] NTFS read/write support included
[ 90.390000] Hfs+/HfsX read/write support included
[ 90.550000] Slow work thread pool: Starting up
[ 90.550000] Slow work thread pool: Ready
[ 90.850000] fnotify: Load file notify kernel module.
[ 90.850000] fnotify: Global_Private_Data_List_Init()
[ 90.850000] fnotify: Launch the fnotify thread: 1223
[ 90.860000] fnotify: The fnotify thread starts...
[ 90.880000] lib80211: common routines for IEEE802.11 drivers
[ 90.880000] lib80211_crypt: registered algorithm 'NULL'
[ 90.970000] cfg80211: Calling CRDA to update world regulatory domain
[ 91.080000] Enable WDT...
[ 91.440000] eth0: link up, full duplex, speed 1 Gbps
[ 93.100000] usbcore: registered new interface driver snd-usb-audio
[ 93.160000] usbcore: registered new interface driver snd-usb-caiaq
[ 93.270000] Linux video capture interface: v2.00
[ 93.330000] usbcore: registered new interface driver uvcvideo
[ 93.330000] USB Video Class driver (v0.1.0)
[ 93.600000] kjournald starting. Commit interval 5 seconds
[ 93.610000] EXT3-fs (md9): using internal journal
[ 93.610000] EXT3-fs (md9): mounted filesystem with writeback data mode
[ 94.060000] md: bind<sda1>
[ 94.130000] RAID1 conf printout:
[ 94.130000] --- wd:3 rd:4
[ 94.130000] disk 0, wo:0, o:1, dev:sdc1
[ 94.130000] disk 1, wo:0, o:1, dev:sdb1
[ 94.130000] disk 2, wo:0, o:1, dev:sdd1
[ 94.130000] disk 3, wo:1, o:1, dev:sda1
[ 94.130000] md: recovery of RAID array md9
[ 94.140000] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
[ 94.140000] md: using maximum available idle IO bandwidth (but not more th
200000 KB/sec) for recovery.
[ 94.140000] md: using 128k window, over a total of 530048 blocks.
[ 101.210000] active port 0 :139
[ 101.210000] active port 1 :445
[ 101.210000] active port 2 :20
[ 103.670000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e
ck is recommended
[ 107.830000] md: bind<sda2>
[ 107.830000] raid1: raid set md4 active with 1 out of 1 mirrors
[ 107.830000] md4: detected capacity change from 0 to 542769152
[ 108.000000] md: md0 stopped.
[ 108.030000] md: md0 stopped.
[ 108.080000] md: bind<sdb3>
[ 108.080000] md: bind<sdc3>
[ 108.080000] md: bind<sdd3>
[ 108.080000] md: bind<sda3>
[ 108.080000] raid5: md0 is not clean -- starting background reconstruction
[ 108.080000] raid5: device sda3 operational as raid disk 0
[ 108.080000] raid5: device sdd3 operational as raid disk 3
[ 108.080000] raid5: device sdc3 operational as raid disk 2
[ 108.080000] raid5: device sdb3 operational as raid disk 1
[ 108.100000] raid5: allocated 67488kB for md0
[ 108.100000] 0: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 108.100000] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 108.100000] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 108.100000] 1: w=4 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[ 108.100000] raid5: raid level 5 set md0 active with 4 out of 4 devices, al
ithm 2
[ 108.100000] RAID5 conf printout:
[ 108.100000] --- rd:4 wd:4
[ 108.100000] disk 0, o:1, dev:sda3
[ 108.100000] disk 1, o:1, dev:sdb3
[ 108.100000] disk 2, o:1, dev:sdc3
[ 108.100000] disk 3, o:1, dev:sdd3
[ 108.100000] md0: detected capacity change from 0 to 5996376883200
[ 108.110000] md: delaying resync of md0 until md9 has finished (they share
or more physical units)
[ 108.850000] md4: unknown partition table
[ 109.270000] md0: unknown partition table
[ 111.120000] Adding 530040k swap on /dev/md4. Priority:-1 extents:1 across
0040k
[ 119.750000] md: bind<sdb2>
[ 119.810000] RAID1 conf printout:
[ 119.810000] --- wd:1 rd:2
[ 119.810000] disk 0, wo:0, o:1, dev:sda2
[ 119.810000] disk 1, wo:1, o:1, dev:sdb2
[ 119.820000] md: delaying recovery of md4 until md9 has finished (they shar
ne or more physical units)
[ 119.820000] md: delaying resync of md0 until md4 has finished (they share
or more physical units)
[ 122.090000] md: bind<sdc2>
[ 124.350000] md: bind<sdd2>
[ 131.420000] EXT4-fs (md0): mounted filesystem with ordered data mode
[ 134.550000] Set Adpater:port=1:0 standby to 0 (0 secs).
[ 134.620000] Set Adpater:port=1:1 standby to 0 (0 secs).
[ 134.680000] Set Adpater:port=1:2 standby to 0 (0 secs).
[ 134.740000] Set Adpater:port=1:3 standby to 0 (0 secs).
[ 149.820000] md: md9: recovery done.
[ 149.850000] md: delaying resync of md0 until md4 has finished (they share
or more physical units)
[ 149.850000] md: recovery of RAID array md4
[ 149.850000] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
[ 149.850000] md: using maximum available idle IO bandwidth (but not more th
200000 KB/sec) for recovery.
[ 149.850000] md: using 128k window, over a total of 530048 blocks.
[ 149.930000] RAID1 conf printout:
[ 149.930000] --- wd:4 rd:4
[ 149.930000] disk 0, wo:0, o:1, dev:sdc1
[ 149.930000] disk 1, wo:0, o:1, dev:sdb1
[ 149.930000] disk 2, wo:0, o:1, dev:sdd1
[ 149.930000] disk 3, wo:0, o:1, dev:sda1
[ 155.950000] eth1: stopped
[ 166.160000] md: md4: recovery done.
[ 166.170000] md: resync of RAID array md0
[ 166.170000] md: minimum _guaranteed_ speed: 5000 KB/sec/disk.
[ 166.170000] md: using maximum available idle IO bandwidth (but not more th
200000 KB/sec) for resync.
[ 166.170000] md: Resyncing started: md0
[ 166.170000] md: using 128k window, over a total of 1951945600 blocks.
[ 166.230000] RAID1 conf printout:
[ 166.230000] --- wd:2 rd:2
[ 166.230000] disk 0, wo:0, o:1, dev:sda2
[ 166.230000] disk 1, wo:0, o:1, dev:sdb2
[ 166.650000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recover
irectory
[ 166.650000] NFSD: starting 90-second grace period
[ 170.660000] active port 0 :139
[ 170.660000] active port 1 :445
[ 170.660000] active port 2 :20
[ 178.540000] nfsd: last server has exited, flushing export cache
[ 187.440000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e
ck is recommended
[ 206.790000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recover
irectory
[ 206.790000] NFSD: starting 90-second grace period
[ 207.680000] warning: process `pic_raw' used the deprecated sysctl system c
with 8.1.2.
[ 214.900000] rule type=2, num=0
[ 215.840000] EXT2-fs (mtdblock5): warning: mounting unchecked fs, running e
ck is recommended
[ 222.720000] nfsd: last server has exited, flushing export cache
[ 232.580000] Loading iSCSI transport class v2.0-871.
[ 233.730000] iscsi: registered transport (tcp)
[ 245.720000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recover
irectory
[ 245.730000] NFSD: starting 90-second grace period
[ 263.340000] nfsd: last server has exited, flushing export cache
[ 275.870000] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recover
irectory
[ 275.870000] NFSD: starting 90-second grace period
[ 315.230000] warning: `proftpd' uses 32-bit capabilities (legacy support in
e)
[57656.520000] md: md0: resync done.
[57656.520000] md: Resyncing done: md0
[57656.590000] RAID5 conf printout:
[57656.590000] --- rd:4 wd:4
[57656.590000] disk 0, o:1, dev:sda3
[57656.590000] disk 1, o:1, dev:sdb3
[57656.590000] disk 2, o:1, dev:sdc3
[57656.590000] disk 3, o:1, dev:sdd3
[75772.420000] md0: bitmap file is out of date (0 < 510043) -- forcing full r
very
[75772.420000] md0: bitmap file is out of date, doing full recovery
[75773.930000] md0: bitmap initialized from disk: read 15/15 pages, set 47655
its
[75773.930000] created bitmap (233 pages) for device md0
#

[luwak]

update: Well it did not last very long, one day later and back to square one. I am now calling QNAP to see what my next steps will be, as of right now i just have a big paperweight.

[2000wolf]

Yesterday Qnap updatehd the compatibility list . Now these disks are not recommended!

[mokies]

I can't believe my bad luck, I checked the compatibility list not 4 days ago and purchased 4 x 2TB ST2000DM001 for my 419p II. The 419p II is virtually useless with these drives, they don't even stay online long enough for the NAS to rebuild.

How is QNAP planning to support customers that have been affected by this product defect?

[haty1]

WTF QNAP! I just purchased 2 x 2TB ST2000DM001 Segate drives as they were on your recommended list - a week later a get a read/write error on one of them and now I find out you have changed your mind and removed them from the list. What kind of dodgy testing do you do to certify the drives? This is completely unacceptable and very disappointing. I have been a big fan of your products and have purchased two of them and recommended to several others. Unless you come up with an acceptable solutions (ie. fix issue or provide compensation) I will be telling everyone I can to avoid purchasing your products.

[doktornotor]

Well, as already discussed elsewhere - you come to blame QNAP for something that might very well be just a crappy FW of the Seagate HDDs. There are numerous examples of defective FW e.g. with the "green" drives.

P.S. Any testing done can only be done against a specific QNAP FW version and specific HDD FW version. There is no assurance whatsoever it is going to work with any other combo, sorry. HDD manufacturers need to focus less on marketing **, crippling functionality for "consumer-class" HDDs and way more on standards compatibility. Example: hey, here is the "enterprise" class HDD - we have tweaked the firmware to stop trying to read a bad block endlessly and instead opted to remap it ASAP. Wow, enterprise-class product, exact same components, 100% price premium. Wow!

[chrishugill]

I too had problems with these drives in my 419P II and when I got the first errors I also looked at Seagate's website and Seagate categorically states that these drives should not be used for RAID 5, but they can be used for RAID 0 or 1, so I don't really see it as QNAP's problem. Heeding the information from Seagate advice I switched my 4 drives over to using RAID 10 and I have not had a single problem since, mind you it has only been a month since I made the change.

[doktornotor]

Seagate categorically states that these drives should not be used for RAID 5

Also, they should not be used to store pr0n videos and you should not use filesystem encryption with these drives. They will also explode in fire when some warez bits hit these drives. Oh, and you need to scratch with your left leg behind your right ear at least once a week to keep them stable.

There is absolutely no reason why a standards-compliant drive would work with RAID 0/1/1+0 and would not work with RAID 5/6/whatever else.

People should stop buying products from manufucturers that are trying to avoid responsibility for their crappy products by placing similar ridiculous claims on their websites.

[luwak]

What a joke. So who is going to reinburse me for buying four of these drives? QNAP are you there!!! I only bought them because they were on the list. What kind of QA environment were these tested in. Installed, create Raid 5, all good, done. Maybe you need to investigate your QA folks and see what is actually being done. Not impressed!!!

These drives were on the list for months. They should have been taken off the list once people were complaining. Does anyone that works for QNAP even look at these forums. You cannot blame someone for doing some research making sure you are buying drives that are on a hardware compatibility list.

I guess I am at fault for not searching these forums hard enough but I really did not think I would have had an issue with a drive that is on a COMPATIBILITY from the manufacturer. It was not until I required some help that I realized there were so many issues out there.

Thanks Again I am so glad to be out over $500 bucks!!!!!

OH yea, and if it states on Seagates website that these should not be used for RAID 5 then WHY THE ** DID QNAP HAVE THEM ON THEIR COMPATIBILITY LIST!!!!!!!!!!!!!!!!