Disk Read/Write Error

[lifeisfun]

Well, 18 months later and my read/write problem is back exactly the same as before
Very frustrating since there is nothing wrong with those 4 drives in RAID5.
It refuses to rebuild so for the third time I have to beg QNAP to help me
They had it fixed both times before in less then 5 minutes.



2012-06-08
1018 11:15:50 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Rebuilding skipped.
2012-06-08
1017 11:14:42 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Mount the file system read-only.
2012-06-08
1016 11:14:40 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Mount the file system read-only.
2012-06-08
1015 11:14:37 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Mount the file system read-only.
2012-06-08
1014 11:14:32 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 1 added into the volume.
2012-06-08
1013 11:14:17 System 127.0.0.1 localhost System started.
2012-06-08
1012 11:11:31 System 127.0.0.1 localhost System was shut down on Fri Jun 8 11:11:31 EDT 2012.
2012-06-08
1011 11:10:24 admin 192.168.1.4 --- [Power Management] System will be restart now.
2012-06-08
1010 10:42:38 System 127.0.0.1 localhost [HDD SMART] HDD 1 Rapid Test result: Completed without error.
2012-06-08
1009 10:41:35 System 192.168.1.4 localhost [HDD SMART] HDD 1 Rapid Test started.
2012-06-08
1008 10:20:44 System 127.0.0.1 localhost [Drive 1] Bad Blocks Scan completed.
2012-06-08
1007 10:20:39 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Add drive 1 to the volume failed.
2012-06-08
1006 06:07:01 System 127.0.0.1 localhost [Drive 1] Start scanning bad blocks.
2012-06-08
1005 06:06:48 System 127.0.0.1 localhost [HDD SMART] HDD 4 Rapid Test result: Completed without error.
2012-06-08
1004 06:06:48 System 127.0.0.1 localhost [HDD SMART] HDD 3 Rapid Test result: Completed without error.
2012-06-08
1003 06:06:27 System 127.0.0.1 localhost [HDD SMART] HDD 2 Rapid Test result: Completed without error.
2012-06-08
1002 06:06:26 System 127.0.0.1 localhost [HDD SMART] HDD 1 Rapid Test result: Completed without error.
2012-06-08
1001 06:05:43 System 192.168.1.4 localhost [HDD SMART] HDD 4 Rapid Test started.
2012-06-08
1000 06:05:37 System 192.168.1.4 localhost [HDD SMART] HDD 3 Rapid Test started.
2012-06-08
999 06:05:24 System 192.168.1.4 localhost [HDD SMART] HDD 1 Rapid Test started.
2012-06-08
998 06:05:15 System 192.168.1.4 localhost [HDD SMART] HDD 2 Rapid Test started.
2012-06-08
997 06:03:25 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Rebuilding skipped.
2012-06-08
996 06:02:20 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Mount the file system read-only.
2012-06-08
995 06:02:18 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Mount the file system read-only.
2012-06-08
994 06:02:15 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Mount the file system read-only.
2012-06-08
993 06:01:55 System 127.0.0.1 localhost System started.
2012-06-07
992 22:31:07 System 127.0.0.1 localhost System was shut down on Thu Jun 7 22:31:07 EDT 2012.
2012-06-07
991 19:38:54 System 127.0.0.1 localhost [Power Management] Disable schedule shut down.
2012-06-07
990 19:38:54 System 127.0.0.1 localhost [Power Management] Disable schedule shut down.
2012-06-07
989 19:38:53 System 127.0.0.1 localhost [Power Management] Disable schedule startup.
2012-06-07
988 19:38:53 System 127.0.0.1 localhost [Power Management] Disable schedule startup.
2012-06-07
987 19:38:53 admin 192.168.1.4 --- [Power Management] Scheduled power on/off disabled.
2012-06-07
986 18:55:29 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Rebuilding skipped.
2012-06-07
985 18:55:26 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Start rebuilding.
2012-06-07
984 18:55:14 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Error occurred while accessing the devices of the volume in degraded mode.
2012-06-07
983 18:55:11 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Error occurred while accessing Drive 4.
2012-06-07
982 18:54:59 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Error occurred while accessing the devices of the volume in degraded mode.
2012-06-07
981 18:54:56 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Error occurred while accessing Drive 3.
2012-06-07
980 18:54:43 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Mount the file system read-only failure.
2012-06-07
979 18:53:51 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Error occurred while accessing the devices of the volume in degraded mode.
2012-06-07
978 18:53:46 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Error occurred while accessing Drive 2.
2012-06-07
977 18:52:22 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4] Drive 1 added into the volume.
2012-06-07
976 18:51:59 System 127.0.0.1 localhost System started.

[R34GTXT]

Hi there.

I have been reading each and every post on this thread, and I am hopeful somebody can help me.

Tonight I had a read write error on BAY 4 of my QNAP ts-459 PRO running RAID 5. I replaced the HDD (Seagate ST32000641AS) as per instructions with an identical brand new HDD. It again showed the red lights and the read write error. So I proceeded to power off the unit and then power back on only to find the QNAP has reset its settings (inlcuding the Network Name I assigned it) and now shows a Config Disk Raid 5 on the LCD Panel of the QNAP.

I have been too frightened to proceed with anything further as the data I have is not backed up and is of extreme personal value (My childrens video/photgraphic memories along with my deceased wifes memories)

The QNAP finder sees the device and it calls it by its default name, however I am unable to connect to the the config menu using my browser. Interestingly, the folders that I have created appear in explorer, however I am unable to access them as it says the path does not exist.

So my questions are:
1.Does this mean that I have lost all my data from the original 3 HDD's?
2. By setting my disk config on the QNAP Panel to to RAID 5, will this format my RAID ARRAY or will it simply try to rebuild it?

THank you all for your time, and I ever hopeful that somebody may be able to help me. I have already submitted a support request to QNAP, but I thought I would also ask "real people" as often they are the ones with real world experience and advice.

Thank you all again.

Peter

[chris-x73]

Hello Peter,

having read your post I would suggest to contact the QNAP support immediately and STOP trying to fix the problem yourself as you have no backup. I had a similar problem but with a RAID1 QNAP TS-219 which made it easy to connect one harddisc to a PC using a SATA/USB adapter and a tool (http://www.ext2fsd.com/) to easily mount the disc. All data were still existing and I was able to backup everything.
I am just not sure if that also works for a RAID5 system - I honestly doubt it.

Good luck!
Best regards,
Christoph

[chris-x73]

Hello Peter again,

sorry - I overread in your post that you already had contacted the QNAP support. Hope they were able to help you.

Regards,
Christoph

[Anata mo]

Remember, that most SATA class disks from WD are NOT to be used in RAID configurations. The even say so on their own site because of the way their errorcorrection and data recovery works. This interfeeres with some RAID controllers and there for fail after some time. I have had plenty of failed WD disks before I was made aware of this.

Up til now I have used Seagate instead, but if you like to stay with WD then use their new RED series. It is made for RAID

Friendly regards
Stefan / Denmark

Quote from WD's site:

From the Western Digital website:

Western Digital manufactures desktop edition hard drives and RAID Edition hard drives. Each type of hard drive is designed to work specifically in either a desktop computer environment or a demanding enterprise environment.

If you install and use a desktop edition hard drive connected to a RAID controller, the drive may not work correctly unless jointly qualified by an enterprise OEM. This is caused by the normal error recovery procedure that a desktop edition hard drive uses.

When an error is found on a desktop edition hard drive, the drive will enter into a deep recovery cycle to attempt to repair the error, recover the data from the problematic area, and then reallocate a dedicated area to replace the problematic area. This process can take up to 2 minutes depending on the severity of the issue. Most RAID controllers allow a very short amount of time for a hard drive to recover from an error. If a hard drive takes too long to complete this process, the drive will be dropped from the RAID array. Most RAID controllers allow from 7 to 15 seconds for error recovery before dropping a hard drive from an array. Western Digital does not recommend installing desktop edition hard drives in an enterprise environment (on a RAID controller).

Western Digital RAID edition hard drives have a feature called TLER (Time Limited Error Recovery) which stops the hard drive from entering into a deep recovery cycle. The hard drive will only spend 7 seconds to attempt to recover. This means that the hard drive will not be dropped from a RAID array. Though TLER is designed for RAID environments, it is fully compatible and will not be detrimental when used in non-RAID environments.

[kozchris]

I'm experiencing the same type of issue on my TS-459, disk was flagged as bad but SMART shows disk as GOOD. Seems like a bug to me that you can't decide to put a disk that appears GOOD back into the raid set easily.

FYI my drive is a WDC WD2002FYPS-01U1B04.0

Does anyone have the steps to reset the status on a drive so it will go back into the array or do i need to contact QNAP support?

[doktornotor]

Does anyone have the steps to reset the status on a drive so it will go back into the array or do i need to contact QNAP support?

Sorry, there is no way to reset a defective drive. Replace it.

[P3R]

Seems like a bug to me that you can't decide to put a disk that appears GOOD back into the raid set easily.

The SMART status is an interpretation of some SMART statistics with fairly liberal tresholds. It's a rather blunt tool, absolutely not able to provide a definitive truth about the disk status.

[baten]

i have a qcrap-ts412 with 4x 3tb seagate/samsung drives. in raid 5.

i got a disc error on disk one. could not get it to go away. so i bought another 3tb drive to copy off most of my data.
i didnt do that though, i upgraded the firmware on all of the seagate/samsung drives and put them back in, still the same error, grrr. so i popped out disc 1 and put in this new disc, and took it back out after a few seconds, it had started rebuilding. then replaced the old disc and it has been okay now for over a month.
now use the spare 3tb disc as a nas back up, for my most valuable data.

hope it helps someone.

[P3R]

...so i popped out disc 1 and put in this new disc, and took it back out after a few seconds, it had started rebuilding. then replaced the old disc and it has been okay now for over a month.

Fantastic machines these Qnaps are, that can still run despite such abuse and awful administration.

To deliberately continue to run on disks that have read/write errors is an accident waiting to happen. This interesting report from Google, claims that a disk that have had a sector reallocation (which is what will eventually happen after a read/write error) is more than 14 times as likely to fail within 2 months compared to a disk without reallocations.

Personally I prefer my data storage to be safe and not a gamble.

[baten]

The disks are less than 2 months old. seagates software said there was nothing wrong with the drive. it was just on the qnap and only disk that 1 disk. and since then no problems at all.
i have replaced all my disks with seagate constellations es.2, just this weekend, and the the other disks are now on a linux machine. the constellations will be going in there too, once i have the new linux machine configured.

yes i agree data should be safe, but the equipment the disks are plugged into shouldnt just display false faults. the hardware is probably good, but the firmware leaves a lot to be desired. although when i did have another problem, qnap support were very good.

this qnap is far too slow and and i dont think they do what say they do, exactly. will probably just keep it for media share, but only vidoes as the amount of music i have puts too many files on there and slows it down far too much.

my message above was to help other people maybe remove the error, if a disk is faulty, it will say so again. but ultimately its up to the owner to decide. not everyone has money to keep buying new disks every 2 months.

[P3R]

yes i agree data should be safe, but the equipment the disks are plugged into shouldnt just display false faults.

The topic of this thread is Disk Read/Write Error. That is not a false fault but a very real one.

A 2 months old disk having read/write errors should really be replaced with a non-faulty product on warranty. But I'm aware of the problem when the disk have later remapped that faulty sector and therefore in testing doesn't reveal any problems. But that issue is not in any way caused by Qnap. It's what (all) disk manufacturers have implemented to buy some time and minimize their cost for warranty replacements.

Yes depending on the importance of your storage and how carefully you manage your backups, you could continue to run the Qnap on such a disk. But every new read/write error means added risk. The safest approach would be to try and stress the disk into producing more errors outside of the Qnap, so that hopefully a warranty claim can be made.

this qnap is far too slow...

Well a TS-412 is the entry-level 4-bay model with a 1.2 GHz ARM CPU and a very modest 256 MB RAM. The whole system is specified as consuming only 26 Watts, with the disks alone probably using at least half of that. No performance miracles can be expected from such low specifications. Qnap currently have a bunch higher specified 4-bay models that all would have been better if great performance is important to you.

my message above was to help other people maybe remove the error...

Okay, I understand that you posted with good intention but pulling a disk that is in an active rebuild is always a very bad thing, no matter how you look at it.

If one wants to achieve what you did, I would recommend to allow the rebuild to finalize and THEN reapply the old disk. After each action (pulling, inserting) one should allow the NAS to react and settle down before doing the next thing.

not everyone has money to keep buying new disks every 2 months.

I agree. I expect 3-5 years out of my disks and most good disks give you that. Out of my 6 Hitachi HDS722020ALA330, 2 have now around the 3 year mark started to have read/write-errors and reallocated sectors. Unfortunately the problems never became severe enough inside of the warranty time. They are now retired to less important duty in test and desktop-computers, where I will squeeze that last lifetime out of them.

[baten]

I agree pulling out while re-biuilding probably wasnt a good idea, but at this point i had about enough. the errors, the slow speed. i wasnt expecting it to be so slow, the site i purchased it from said 70MB/s+ copying, and couldnt get anywhere near it. and since found out it never will. the processor cant cope. but thats another point.

[dkwdkw]

Not sure if this applies, but if these are "green" drives, turn off the QNAP auto-sleep function. With my WD drives this solved the issue. My guess is that the QNAP auto-sleep and the drive auto-sleep fight. The QNAP will send a "wake up" but the drive takes too long to respond so the QNAP isolates the drive as being bad.

Dave

[leobg]

One of my 809U-RP boxes loves to kick drive 3 out. This happens about once every 2-3 weeks, sometimes month+. Always drive 3. Initially I was replacing it with new drives, but last few times I just stared rotating two drives. Drives are all WD RE4, so it should not be them at fault being non-nas use certified. Sure enough all drives are fully tested with WD tools afterwards on a PC and show no defects. First two 'defective' units I still use on my desktop computer for over a year now.
I am thinking the issue is with the QNAP itself. Too bad its been 2+ years since the warranty of this box is over. I'd send it for repair, but I need something to take over this box and its data. I am wondering if QNAP loans devices in situations like that. Of course I do not expect this for free. Anyone with similar experience?