Disk Read/Write Error

[liuwei]

I upgraded to the 3.4.0 Build 0212T firmware and Enable hard disk standby mode. And again getting de Disk error. Checked the disk and all the disk leds are green again. Now disabled the harddisk standby mode. How can i use the harddisk standby mode without the disk error's ?

[johnnyviper]

Well I'm having the same Read/Write errors on my TS-219P+. When I first noticed the system was in degraded state, I pulled out HD2 and reinserted it. After I reinserted it the RAID 1 array started to rebuild. Once the rebuild was complete, the NAS was unable to find any data on the array. I connected HD1 to a computer, and verified all data was still on the disk. The NAS was then reset to defaults, and updated to 3.4. I installed both drives again and it rebuilt. After the rebuild it still shows that there are ~300 GB of used space on the array, but none of the data is available.

Is there any way to get the NAS to "find" the data on the drives again, or do they need to be formatted?


Thanks

John

[harryfwong]

Have the same problem and the NAS is out of warranty. Reply from QNAP is below. After doing some more research I believe the issue is with the RAID controller that they use. I am currently disappointed that this is a problem with the hardware and yet they fail to own up to it. There should be a recall on all of their NAS devices that use any problematic RAID controllers. Possibly that is the reason their warranty is 1 year vs other major players in the NAS world.

Their applications might be good -- however if the hardware will fail you -- it's quite useless.

Because it's out of warranty
so we will charge for the MB
it will cost 500 USD (without freight and tax)
would you want to buy it?

Should you have any further questions, please kindly let us know.We will be more than happy to assist you right away. Thank you.

Best Regards,
Steve Huang

[maartenb]

Harry,

I agree with you this has nothing to do with warranty. In Europe this is called non-conformity and should be fixed always. Manufactures can't hide behind their warranty. So if you are in the EU you should contact the reseller.

[thecore]

Hi all,

First of all, i just want to say sorry if my english is not good because english is not my native language .

I got the same issue on my customer`s NAS, TS-809-URP with 8 x 1.5TB (ST31500341AS), the unit goes to "in degraded mode read only", he touhgt the second disk in the NAS failed, he tried replaced with a new Seagate hdd (ST1500DL003), but the disk status shows "Disk Read/Write" after several minutes he plugged in the new disk . Does anyone can assist me what is the root cause and how to figure out this issue. I would appreciate some advice.

Best Regards,
Thecore

[fk8]

I get the same thing with my ST1500DL003 disk.

Did anyone figure out how to forcefully clear the status or where QNAP user interface get it from?

There seem to be no problem working with the drive manually from the QNAP.

[fk8]

Update: There is really no problems with the drive, only QNAP interface reports there is.

I can manually attach the drive to the mirror, mirror it successfully, detach it from the mirror and then mount it on a separate mount point.

SMART reports no problem. e2fsck and badblocks finished without any issue. Even mounted it on a share and accessed it via SAMBA opening files and playing videos. No problem.

Also..

Killed and restarted /sbin/hd_util as I understand QNAP uses it to get disk information.
Physically ejected and re-inserted the drive.
Physically ejected the drive, rebooted the NAS, and re-inserted it.
Physically ejevted the drive, turned off the NAS, re-inserted it, and booted the NAS back up.

All to no avail.


I'm really at loss where QNAP gets its (incorrect) "Disk Read/Write Error" status from.. anyone having walked down that rabbit hole? or someone from QNAP kind to enlighten?

[gsarbia]

Just to share my experience, I haven't updated anymore the firmware and I keep on using the QNAP with no sleep mode for the HDs. I've never seen again the issue reported in this thread, and the electricity bill is not visibly higher since I disabled the sleep mode.
I'll just use the QNAP as it is now, no more firmware upgrades, and when it will eventually die I'll be happy to buy a NAS from another vendor.
QNAP has a good marketing arm considering the positive reviews they get, but it's not worth the pain inflicted by its products.

[fk8]

Well, the "Disk Read/Write Error" magically cleared itself in the middle of a manually invoked mirror rebuild. (But I don't think that was the trigger since I did several rebuilds before it. What maybe triggered it was that I killed the "hdd_util" process prior to the rebuild. It was re-spawned automatically some time after.)

Before I started the rebuild and after detaching the disk devices from the mirror I did :

Code: Select all

# mdadm --zero-superblock /dev/sdb
# dd if=/dev/sda of=/dev/sdb bs=446 count=1
# fdisk /dev/sdb


(The fdisk-part was basically to set up the partition table to reflect the old drive.)

Then I attached sdb3 to md0 and in the middle of this rebuild the drive status went to "Ready". Still wondering where QNAP gets this status from though..

[fk8]

Just to share my experience, I haven't updated anymore the firmware and I keep on using the QNAP with no sleep mode for the HDs. I've never seen again the issue reported in this thread, and the electricity bill is not visibly higher since I disabled the sleep mode.

I always kept the sleep mode off. In my experience drives live longer when they are allowed to just stand and roll without needing to spin up and down countless of times.

[fk8]

Update: mirror is still up and running since last post and all appears well for now. Will let it run for a week or so and then bump in the other drive and see if I can complete the migration.

I have done some copying back and forth to simulate load but no reboot yet. Still have no idea what made QNAP software out of the blue accept is as OK though.

[fk8]

Update: Came home from holidays and found a red warning light on the QNAP.

Same issue as above.

* SMART status is GOOD

* There is nothing new in any of the logs

* Mirror is OK

Code: Select all

md5 : active raid1 sdb2[1] sda2[0]
      530048 blocks [2/2] [UU]

md13 : active raid1 sdb4[1] sda4[0]
      71808 blocks [2/2] [UU]

md9 : active raid1 sdb1[1] sda1[0]
      530048 blocks [2/2] [UU]

md0 : active raid1 sdb3[1] sda3[0]
      487243328 blocks [2/2] [UU]


* Disk status for drive 2 (ST2000DL003) is marked "Disk Read/Write Error"


I cannot figure out where QNAP software get the "Disk Read/Write Error" status from...

[nosehook]

I just turned on my brand new QNAP TS-412 with 4 x Samsung EcoGreen F2 EG HD154UI, 1.5TB
I got the GUI for first use and selected everything for RAID 5. After 40 mins the system was done and I got the admin page.
After failing to install twonky medio server I checked disk status and noticed all disks have SMART status good, but disk 1 had a read/write fail and the system tells me disk 1,2,3,4, are set for RAID 5, but there is no volume. I tried to let the system setup again for RAID 5, but it fails.
Any suggestions? should I reset to factory default?

I already asked to get a new drive, but still want to set up a degraded RAID 5 with 3 disks, this should be possible right?

[rich1231]

I have the same issue on a brand new TS-412 with 2 brand new of the same drives.

Also ordered a Seagate drive to test with, same issue. Very frustrating.

[colmaclean]

I'm using a new TS412 as a backup solution and it sounds like I've got a similar problem.

Have four 1.5TB disks in the NAS...

1) Seagate Barracuda 7200.11 ST31500341AS
2) Seagate Barracuda 7200.11 ST31500341AS
3) Western Digital WD15EARS-00Z5B1 80.0
4) SAMSUNG HD153WI 1AN1

They were set up as JBOD and formatted as EXT4.

I then set up an RTRR job to copy from my main NAS (TS509) to the 412. This was successful first time, but after that I was seeing this error in the logs:

Code: Select all

[RTRR Job] Job NAS backup failed: Job is aborted because there is an I/O error while accessing the local device!

If I looked at the RTRR log, I could see the file which had the read/write error. I ssh'd onto the 412 and found that I could not read the erroneous file or even delete it. When I attempted to remove the file, the following error showed:

Code: Select all

rm: unable to stat: '<filename>': input/output error

Given that I couldn't delete the files, I decided to format the array and start from scratch. Upon doing this, my third drive (the WD15EARS) showed "DIsk Read/Write Error".

I rebooted the 412 and all drives showed as "Good" again, however the front-end performance was especially sluggish for some reason.

Have attempted another format operation and during this the WD drive was again flagged as "Disk Read/Write Error".

Will remove the WD drive from my array for now and will run diagnostics on it...