Disk Read/Write Error

dkwdkw · Post by **dkwdkw** » Tue May 01, 2012 12:46 am

Not what I wanted to hear...

QNAP are you listening? What can be done for those of us that followed the compatibility list but our drives don't work???

jtan · Post by **jtan** » Tue May 01, 2012 8:14 pm

Tried firmware 3.61 and is still having disk read/write problem

jtan · Post by **jtan** » Tue May 01, 2012 8:15 pm

Unit is TS-412 with Seagate ST2000DL003

dkwdkw · Post by **dkwdkw** » Wed May 02, 2012 12:15 am

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

jtan · Post by **jtan** » Wed May 02, 2012 1:47 am

do you mean "Bad Blocks Scan" in Volume Management?

dkwdkw · Post by **dkwdkw** » Wed May 02, 2012 7:12 am

Yes. Got the name wrong since it's not in front of me.

T5000 · Post by **T5000** » Wed May 02, 2012 7:27 am

The Read/Write Error hit me. I have 8 2TB WD2003FYYS HDDs in my 809 Pro. A few Weeks ago the Drive in Bay 3 reported Bad Blocks... i checkt it also on my pc to verify the report which was true. I got a new one (same model) and it was running fine till May 1. now i get Read/Write errors but the SMART test passes with GOOD. And thats again in Bay 3.

I checked the HDD with WD Lifeguard Diagnostics and not only the extended test but also write zeros to the entire HDD passed w/o any errors. So there is clearly something wrong with the Qnap. Everything was running fine for over a year and now it suddenly don't want my disks anymore. The WD2003FYYS was also on the compatibility list.

Since day one i had nothing but trouble with this NAS. First unit had problem even to boot up, second (current) unit had problem with the back FAN (must be replaced) and now with this weird Read/Write Error.

I send this NAS one last time to RMA before it runs out of warranty and then i sell it. I give some other company a try because i don't think it could get any worse...

bazinga · Post by **bazinga** » Thu May 03, 2012 5:13 pm

Disk Read/Write error here also, after only one week of use.

QNAP TS-412
2x3.0TB (Seagate ST3000DM001) on RAID1

The hard drives are found on the hardware compability list: http://www.qnap.com/en/?lang=en&sn=3877

Considering sending the QNAP back to the local retailer.

steffwgnr · Post by **steffwgnr** » Mon May 14, 2012 9:57 pm

Hi,

I got a QNAP 459U RP+ with FW Version: 3.6.1 Build 0302T. Furthermore there are 4 x WDC WD2002FYPS-02W3B04.0 with FW-Version: 04.01G01.

Since tonight i get this Read/Write Error on Disk 4 (Disks are 10 Days old...) and block check of this disk says: Ready
SMART says:

1 Raw_Read_Error_Rate 200 200 051 0 OK
3 Spin_Up_Time 247 240 021 9608 OK
4 Start_Stop_Count 100 100 000 16 OK
5 Reallocated_Sector_Ct 200 200 140 0 OK
7 Seek_Error_Rate 200 200 000 0 OK
9 Power_On_Hours 100 100 000 169 OK
10 Spin_Retry_Count 100 253 000 0 OK
11 Calibration_Retry_Count 100 253 000 0 OK
12 Power_Cycle_Count 100 100 000 15 OK
192 Power-Off_Retract_Count 200 200 000 6 OK
193 Load_Cycle_Count 197 197 000 9188 OK
194 Temperature_Celsius 119 111 000 33 OK
196 Reallocated_Event_Count 200 200 000 0 OK
197 Current_Pending_Sector 200 200 000 1 OK
198 Offline_Uncorrectable 100 253 000 0 OK
199 UDMA_CRC_Error_Count 200 200 000 0 OK
200 Multi_Zone_Error_Rate 100 253 000 0 OK

Nothing red.. but the overall status is NORMAL in yellow. The Disks are all good and i think i would have to upgrade the FW Version of the Disks, although this thread is from 2009 and these HDDs are bought in 2012/04...

I can't format the RAID5 because it is used as LUN target for some VMs.

Help please,
Steffen

schumaku · Post by **schumaku** » Tue May 15, 2012 12:01 am

Impossible to say what went wrong with that disk. worth reviewing # dmesg .... or check the kernel messages collected in /mnt/HDA_ROOT/.logs/kmsg for some insight.

A disk operational for just ten days, and already down from Good to Normal status in S.M.A.R.T. - considering this is the disks own information?

steffwgnr · Post by **steffwgnr** » Tue May 15, 2012 1:24 am

schumaku wrote:Impossible to say what went wrong with that disk. worth reviewing # dmesg .... or check the kernel messages collected in /mnt/HDA_ROOT/.logs/kmsg for some insight.

A disk operational for just ten days, and already down from Good to Normal status in S.M.A.R.T. - considering this is the disks own information?

This is the information i get from SMART of Qnap.. from shell and WI. We will see if its a HW fault or something else.. i just hope that the 3 other HDDs keep alive

)

clickright · Post by **clickright** » Sat Jun 02, 2012 11:58 am

Add me to the list!

I've got a brand new Qnap TS419 P11 with 2x WD WD2003FYYS Enterprise drives. So far it's always drive 2. I replaced it right away thinking it was DOA. Got a new replacement, installed it and let the RAID rebuild. Ran a volume scan and it passed. Then I ran a Complete HDD test. About 15% in there was a Read Write error on Drive 2 and my RAID array is degraded. The scan is still in progress 70% so it hasn't even failed or completed yet.

Will try and update with what happens. However given the amount of issues in the thread and lack of response from Qnap and the headache I've been through already I will probably just return the unit to my supplier and get a more reliable unit of another brand.

sl1000 · Post by **sl1000** » Sun Jun 03, 2012 6:15 am

@clickright: swapt bay one with bay two and try again. if agian there are issue with "drive 2" you can be anfry with qnap. if now the first drive is bad you've been send a bad replacement. that happens..

clickright · Post by **clickright** » Sun Jun 03, 2012 7:02 am

sl1000 wrote:@clickright: swapt bay one with bay two and try again. if agian there are issue with "drive 2" you can be anfry with qnap. if now the first drive is bad you've been send a bad replacement. that happens..

Complete test passed fine overnight. Bad block scan came up clean. RAID rebuilt this afternoon. I am returning the NAS unit to my supplier. I'm 99% sure both drives are fine, however I am running WD lifeguard tools now. Looking on the forms the sudden dropping of good drives seems to happen all too often. Of course a failing disk can & WILL happen, however I don't believe that it the issue here.

it.manager@maf · Post by **it.manager@maf** » Mon Jun 04, 2012 12:53 pm

Am also having the same error come regularly:

QNAP 459 Pro
3 x Seagate ST1000DM003-9YN1CC4C and 1 x Seagate ST31000340AS SD04
RAID 5
3.6.1 Build 0302T
Hard Disk Standby - OFF
Replaced 3 of the 4 original disks - (although I think that probably only one of them actually needed replacing)
SMART is "Good" on all disks
TWONKY enabled (but only after this started happening)
No QPKG Enabled

The problem only seems to come when I am doing a backup from the system to somewhere else - either across my network or to a connected USB drive.

Run the "Scan Now" on the "failed" drive - no bad blocks found and RAID rebuilds

Until about 2 weeks ago - NO problems at all with the unit - it has been running fine for 18 months.

There is an error when shutting down:

The system is unable to save your settings (file = [/etc/config/uLinux.conf], section = [TFTP Server], field = [Enable], value = [FALSE]) due to insufficient ramdisk space. If restarting the server does not solve the problem please contact support for further assistance.

Output of df:

[~] # df
Filesystem Size Used Available Use% Mounted on
/dev/ramdisk 139.5M 104.6M 34.9M 75% /
tmpfs 64.0M 308.0k 63.7M 0% /tmp
/dev/sda4 310.0M 191.4M 118.6M 62% /mnt/ext
/dev/md9 509.5M 122.1M 387.4M 24% /mnt/HDA_ROOT
/dev/md0 2.7T 538.3G 2.2T 20% /share/MD0_DATA
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
/dev/sdu1 931.5G 311.7G 619.8G 33% /share/external/sdu1

Don't know if that has anything to do with it

What gives guys? Firmware bug?

QNAP NAS Community Forum