Disk Read/Write Error

[ledf]

I was getting a "Disk Read/Write Error" error message with a 2TB Seagate ST2000DL003-9VT1CC3C in a Raid 5 volume.

I made a bad block SCAN and SMART check, both of them with success.

As I could read this at this forum seagate ST2000DL003-9VT1CC3C is now not recomended by Qnap and some user are experimenting the same issue. So I decided to bought a brand new SAMSUNG HD204UI 1AQ1 but after the replacement I´m still getting the same error with the new one.

Anyone Knows how to procced? I`m waiting for a qnap support response.

[ledf]

Qnap support has wrote me

Please unplug your Samsung HDD and format it by other PC to NTFS. Than hot plug in NAS and try again.

If still fail. It might your drive bay has H/W problem need send back to local reseller for repair.

In a second message, becouse I was pretty sure that it wasn't a problem with the bay and becouse I leave 1500Km away from the local reseller.

If other HDD use the same slot has the problem. That we can confirm drive bay has problem......

I advice you backup data first...that we can try modify RAID setting to make it rebuild to new HDD.

The NTFS format did not fixed the problem.

So I tried to solve my self. I followed the instructions in http://www.penguinpunk.net/blog/qnap-ho ... rokenness/

After that the status Disk change from the "Disk Read/Write Error" to "ready" and the status of the volume still in degraded but with a new message indicating to insert a new disk. Also the "check Now" option was available.

I tried to perform a check, but the process stopped at 68%. So I unplugged the HD with problem and then I hot plugged it in the NAS and the rebuild process began. Now the rebuild is on 8% and I have Read/write access to my content.

Qnap staff, sometimes is better to have no info than wrong info.

[Merlin1300]

This is most definitely a QNAP problem.
I bought a TS419P-II - configured it with 4 Seagate ST3000MD01. After about 25 days – the unit began crashing intermittently - with indications that Drive 3 was faulty. I ran complete SMART testing (4+ hours each drive) on all 4 drives in a separate external enclosure - result ALL tested good !! By this time the QNAP box would NOT EVEN BOOT with Drive 3 in place, however it DID run in RAID degraded mode with the drive removed – so, thinking the drive was faulty – I purchased a NEW drive. The new drive installed fine – and the RAID array rebuilt itself – and worked fine - - for 7 days. Then - - the same problems all over again - - Drive bay 3 came up faulty (red light), and again – the system either crashed every few hours, or would not boot, with drive 3 in place. I removed Drive 3 - it passed a complete 4+ hour SMART test in an external enclosure - the QNAP ran in degraded mode with Drive 3 removed - but crashed intermittently with it installed. Please note - - the drives used (Seagate Barracuda ST3000DM001) ARE certified for use in this device BY QNAP.
.
OBTW - - I have upgraded ALL firmware to Ver 3.6.1 build 0302
.
Fortunately - my hardware vendor has a great return policy - so I returned the 419P-II thinking it might be an incompatibility with the Marvel processor or difficulty keeping up with the SATA-III HDDs. So I bought another QNAP - this time the 459 Pro-II {QNAP sez it has no problems with SATA-III drives}.
.
VERY STRANGE stuff - - installed all 4 drives in the 459 (this uses the Intel Atom processor) - and guess what - - the whole system comes up in degraded mode - has remembered ALL of my settings including passwords etc - - AND drive bay 3 shows the red light with the Drive Read/Write error message. JUST LIKE the 419.
.
Their system MUST store the configuration data SOMEWHERE on the Hard Drive array!! I wouldn't be surprised if it also stored failure data somewhere - and once you get a FAIL - their system doesn't permit any way to fix it ??
.
I certainly wish I had found this forum BEFORE I got the MORE EXPENSIVE 459 - - however - - I will play with it for 2 weeks.
IF I can't get it working reliably BACK IT GOES !!!
Then I'm just gonna buy a small PC motherboard with 5 HDD trays (main drive and 4 for RAID) - install a hardware RAID controller - and be done with this.

[Merlin1300]

Read a bunch of posts - decided to re-initialize.
I think I SHOULD have left the drives out, chosen no array, let the thing reset all, then hot-plugged the drives back in and see if it woulda rebuilt.
.
Unfortunately - there were no instructions on how to do that - so the drives got plugged in too early - and they got wiped.
.
I do have backups - but of course - the thing takes 12 hours to initially synchronize the 12TB array, then I have 2TB data back across a 100 Mbps network - THAT takes 5 days. Thanks QNAP.
.
I wonder if the version of Linux these people are running has the equivalent of Microsoft's "dirty bit" - - something unexpected happens (such as delayed cached data being written at the same time QNAP decides there has been no activity for the specified time so tries to spin the drive down - producing a write error ??) - the 'Dirty Bit' gets set - and (with Winblows) until you run Microsnot's Check-Disk program - there is NO OTHER WAY to clear the 'dirty bit' error setting from the HDD. IF that is the mechanism - or one similar, it would be wise of QNAP to fix it.
.
WHATEVER is wrong with their process - - they better fix it.
.
It would ALSO be nice if their Web File Manager could treat an external drive plugged into the USB or eSATA ports on the back with full file management functionality - so I could transfer my files (entire folders including the sub-folders) using drag 'n Drop back over the high-speed port - instead of having to dribble them across a 100 Mbps network. Nice.

[P3R]

I do have backups - but of course - the thing takes 12 hours to initially synchronize the 12TB array, then I have 2TB data back across a 100 Mbps network - THAT takes 5 days. Thanks QNAP.

I'm confused. Do you hold Qnap responsible for limitations in your infrastructure?

It would ALSO be nice if their Web File Manager could treat an external drive plugged into the USB or eSATA ports on the back with full file management functionality - so I could transfer my files (entire folders including the sub-folders) using drag 'n Drop back over the high-speed port - instead of having to dribble them across a 100 Mbps network. Nice.

I don't understand what it is you can't do but as far as I can remember, in general WFM does have full capabilities on an external disk, as long as the user have sufficient administrative rights. If a normal user need such rights, an administrator needs to apply them.

[Merlin1300]

I'm confused. Do you hold Qnap responsible for limitations in your infrastructure?

No - - I hold them responsible for BUGGY FIRMWARE that causes system downtime and an inability to FIX a problem that has been posted for almost THREE years. And OBTW - the time to transfer I listed is not a limitation, it is standard for a 100 Mbps network. What's your point ??

I don't understand what it is you can't do but as far as I can remember, in general WFM does have full capabilities on an external disk, as long as the user have sufficient administrative rights. If a normal user need such rights, an administrator needs to apply them.

'Skuse me - - do you actually USE this stuff - or are you just a forum troll ?? You post no helpful information. OK - - tell me how, using ANY file manager, to COPY a folder from an external HDD attached to one of the USB ports on the back of the QNAP TO a networked folder ON the QNAP. Step by Step.
.
Also - tell me WHY QNAP hasn't fixed this Drive Read/Write error problem !!

[P3R]

OK - - tell me how, using ANY file manager, to COPY a folder from an external HDD attached to one of the USB ports on the back of the QNAP TO a networked folder ON the QNAP. Step by Step.

You forgot to say please... I owe you nothing and I definately won't comply to any orders but I will give you some help, even if I'm now doubtful that you deserve it.

A networked folder is per definition connected by network so of course there's no way around the data travelling over the network in that scenario.

If you on the other hand means that you want to use a shared folder (or subfolder) as the destination you could simply use copy, as it is described in the documentation for Web File Manager (that was after all what you said you tried to use). Drag and drop are also supported for copy and move in WFM. As long as you don't use the upload or download commands in WFM, actual data isn't copied across the network. Every data transfer is only happening locally on the NAS and only your commands and web interface responses travels over the network connection.

I just tried it and copied a folder (with data in it) from my USB-disk to my Public share in WFM and then back to a different folder on the external disk again. It worked as expected.

Since you're not saying where you fail with the task, I doubt anybody will be able to help you solve your problems with it.

Also - tell me WHY QNAP hasn't fixed this Drive Read/Write error problem !!

I couldn't as I don't know. Furthermore I don't see why I would be expected to answer that. I only commented on what I found confusing and possibly incorrect in your previous post but maybe your extreme anger makes it hard to keep things separated?

[Merlin1300]

OK - - tell me how, using ANY file manager, to COPY a folder from an external HDD attached to one of the USB ports on the back of the QNAP TO a networked folder ON the QNAP. Step by Step.

You forgot to say please... I owe you nothing and I definately won't comply to any orders but I will give you some help, even if I'm now doubtful that you deserve it. A networked folder is per definition connected by network so of course there's no way around the data travelling over the network in that scenario.

Well - P3 - - I apologize for my mischaracterization of you as a potential troll . And although your response is courteous, other than being a reply, it fails to provide any solutions.
Your initial comment suggested there was a way to transfer files from an external HDD attached to the BACK OF THE QNAP to a folder that was ON the QNAP. The COMMANDS would be delivered over the network - however since the Ext HDD and QNAP are connected by USB (Or eSATA) and NOT THE NETWORK, the transfer speeds should be limited by USB or eSATA parameters - NOT the network - and hence MUCH FASTER. SO - - again - - I ask (as I originally posted) it would be nice if their File Manager would permit full access (NOT just 'backup access') to the drives ATTACHED to the back of the QNAP.

I just tried it and copied a folder (with data in it) from my USB-disk to my Public share in WFM and then back to a different folder on the external disk again. It worked as expected.

See above - what you suggest here offers no benefit in transfer speed and doesn't address the original question.

Also - tell me WHY QNAP hasn't fixed this Drive Read/Write error problem !!

I couldn't as I don't know. Furthermore I don't see why I would be expected to answer that. I only commented on what I found confusing and possibly incorrect in your previous post but maybe your extreme anger makes it hard to keep things separated?

First - - yes, I am angry. I have spent over $1500 to build a what was supposed to be a fault-tolerant network array - only to find this company is unable to solve a system critical error that has been in existence for at least 3 years. This is unconscionable and has me re-evaluating my options as to whether I should keep the box - or return it - as it is obviously defective - and simply BUILD my own. I now understand where YOU are coming from - however I do not believe you fully understand the issues involved. And that's OK - but it did cause me to misinterpret the intent of your initial reply, which, instead of providing answers, merely asked lateralizing questions.

While I now appreciate your answers - I am still waiting for someone from QNAP to provide meaningful solutions.

[P3R]

And although your response is courteous, other than being a reply, it fails to provide any solutions.

It's extremely hard to provide a solution if the problem isn't clearly spelled out.

You complained about the network speed being a limitation in a WFM-copy scenario local on the NAS. I claim the network isn't involved and therefore cannot be a limitation. I can even prove my statement to you. Start a large copy, shut the web browser down, disconnect your computer and you'll see that later when you connect, all of your data still have been copied over. Since the task is happening internally on the NAS, it will be completed without a problem despite your workstation being disconnected. No network traffic is involved in such a copy process!

So please, what exactly is the problem?

Your initial comment suggested there was a way to transfer files from an external HDD attached to the BACK OF THE QNAP to a folder that was ON the QNAP.

Yes that was exactly what I did in my example. What is your problem trying to do the same?

The COMMANDS would be delivered over the network - however since the Ext HDD and QNAP are connected by USB (Or eSATA) and NOT THE NETWORK, the transfer speeds should be limited by USB or eSATA parameters - NOT the network - and hence MUCH FASTER.

Transfer speeds aren't limited by the network because the data never even touches the network!

Transfer speeds are limited by whatever bottlenecks are existant in the path from the physical external disk, the USB/eSATA interface, internal bus, SATA 3,0 Gbit/s (SATA II) interface, physical internal disk and all software involved in that data transfer.

The transfer speed will never be even close to the marketing specifications of the respective interface if that is what you expected.

The file system used on the external disk may be a speed limiting factor. I think the native ext4 would probably be the fastest file system.

The Qnap is a bit picky with USB-device compatibility and if your external disk is suffering from short disconnections, that would of course affect your performance drastically.

If it is merely a speed issue then I can provide no solution except for the above general advice. Internal speeds are what they are (but the network isn't a factor) and as long as none of your equipment is defective, it would probably be pretty complicated to change.

SO - - again - - I ask (as I originally posted) it would be nice if their File Manager would permit full access (NOT just 'backup access') to the drives ATTACHED to the back of the QNAP.

When you say "full access" that to me suggests you have some kind of issue with accessing the files at all from WFM or doing something specific with them...?

You may have found a bug that I'm not aware of but unless you tell the forum exactly what it is, nobody will ever be able to provide a solution or even confirm such a bug.

As far as I know, a user with sufficient rights on the external disk (an administrator) does have full access to it!

I can't do anything about the main problem you're having but regarding this WFM-copy issue I fear that you may have misunderstood something. That is what I'm trying to help you clear out but you need to work with me for that to happen.

[Merlin1300]

Well - - P3 - - maybe I'm looking in the wrong place - but I couldn't get the external drive attached to the back of the QNAP to show up using WFM or any other process.
The only place I could find a link to the external drive was in the back-up function.

[schumaku]

Several reports in the forum on USB and/or eSATA drives - plugged, detected according ot the kernel messages, but never made available as a share, for backup, ... automatically. Pitty, nobody eally cares about.

[P3R]

Well - - P3 - - maybe I'm looking in the wrong place - but I couldn't get the external drive attached to the back of the QNAP to show up using WFM or any other process.

Great, then at least finally we know what your issue is!

It should turn up as a share and in WFM automatically. There's plenty of reports about external disks that aren't recognized at all but personally I have never heard of the problem where it is only available for backup.

Some ideas:

• Open a new thread (or find an existing one on the topic) with all the relevant details about your setup and hope for some help there.
• Contact Qnap support about the problem.
• Try to format the external disk from the NAS and then disconnect/connect it again.
• Try a different external disk.

[madhitz]

Trying to revive this thread as I couldn't find a similar recent entry through search. Would be grateful to anyone that can provide assistance or direction.

QNAP, is there any further thought on this disk/unit error and how to correct it? We have recently (less than a month) purchased a new TS-419p II and absolutely love all the functionality. Simply amazing what this little box can do. We have outfitted the device with brand new 2x Seagate ST3000DM001-9YN1CC9C disks and built them up in RAID 1 (with plans to move to a 4x on RAID 5 eventually). We then moved all existing multimedia, backup and personal files onto then. We also have external backup enabled to an attached USB (thank god....). Just today, the "Disk Read/Write Error" error comes up on Disk 2 and no amount of unplugging, reboot, hot-swapping, etc has fixed this issue. Thus, the device is stuck in degraded mode, with seemingly no method (other than additional harddrive purchases) to begin to rectify the issue.

Device is running F/W version 3.6.1 Build 0302T FWIW. QNAP, how do we fix this, or at least identify what the cause is? Warranty periods are slowly ticking by...as is patience and our hope that we don't lose data.

[dkwdkw]

I will also try to restart the thread. Same issue on TS-412. Four Seagate ST2000DM001-9YN1CC47 drives (2gb each) in a RAID6 config. Drive 1 reports as a "Disk Read/Write Error" and RAID is in degraded mode. Unplugged and plugged drive and did "Check Now" from Logical Volume screen. No errors reported. SMART reports no errors. What I'm missing is a clear way to rebuild the RAID to recover from the error.

On the RAID screen, there is a "recover" button, but it is not active?

Firmware Version 3.6.1 Build 0302T
Firmware MD5 Checksum null
System Up Time 24 day 17 Hour 3 Minute(s)
PID VID TS-412 V01
Serial Number Q121I03411


CPU Usage 1.9 %
Total Memory 249.7 MB
Free Memory 107.5 MB
System Temperature 37°C/98°F
HDD 1 Temperature 39°C/102°F
HDD 2 Temperature 40°C/104°F
HDD 3 Temperature 40°C/104°F
HDD 4 Temperature 38°C/100°F



Current Disk Volume Configuration: Physical Disks
Disk Model Capacity Status Bad Blocks Scan SMART Information
Drive 1 Seagate ST2000DM001-9YN1CC47 1863.02 GB Disk Read/Write Error Scan now Good
Drive 2 Seagate ST2000DM001-9YN1CC46 1863.02 GB Ready Scan now Good
Drive 3 Seagate ST2000DM001-9YN1CC46 1863.02 GB Ready Scan now Good
Drive 4 Seagate ST2000DM001-9YN1CC9C 1863.02 GB Ready Scan now Good

Current Disk Volume Configuration: Logical Volumes
Disk/ Volume File System Total Size Free Size Status
RAID 6 Disk Volume: Drive 2 3 4 EXT4 3664.62 GB 3491.82 GB In degraded mode



Hard Disk Model Seagate ST2000DM001-9YN1CC47
Drive Capacity 1863.02 GB
Hard Drive Health Good
Hard Drive Temperature 39 ºCºF
Test Time Sun Apr 29 16:26:24 2012
Test Result Test completed and no errors found (Rapid Test)

[P3R]

This is a thread with more reports about problems. It seems there may be a compatibility issue with those Seagate disks as well...