did you try this:fk8 wrote: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.
Code: Select all
mdadm --misc --detail /dev/md0Thanks 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..UkPaolo wrote: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...fk8 wrote: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.
Yes, but what should I be looking for?e932 wrote:did you try this:fk8 wrote: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.Maybe this will show some clues?Code: Select all
mdadm --misc --detail /dev/md0
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
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
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.hoonu wrote:**... 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.
To clarify, originally I had two ST3500630NS (500GB). I have now switched one of these with a ST2000DL003 to test with.QNAPAlex wrote:@ 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
Ah... so this is just on Marvell based units? Sorry for my ignorance but the huge thread was a lil daunting.sl1000 wrote: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
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 solvedgkchamp wrote:@ 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?
