File system check 100% of last 24 hours

I would try booting the NAS with disk 1 replaced with a brand new disk that has no partitions on it.

mdgm wrote:
I would try booting the NAS with disk 1 replaced with a brand new disk that has no partitions on it.

Ok, I did exactly that.

Here is what is going on now. For the first 5-10 minutes, the RAIDar software still shows File System check 100% which happen in a few minutes. All the way to the left, there is a blue dot which is the same as before and both the " Setup and browse" buttons are grayed out. This is exactly the same as before the drive switch.

However, the machine itself has " Drive #1" flashing relatively quickly, the activity light is flashing even quicker than the Drive#1 light and the power light is slowly pulsing between dim and bright for the first 5 minutes. Now the power light is solid.

Both Drive #1 and activity light are flashing.

After the first 5-10 minutes,

RAIDar software, the button all the way to the left has turned " Yellow" the "Volume status" button is blinking green, and the first light on Disk status is blinking green.

*Update, I am now able to access the files and folders. I am also now able to access the web admin screen.
Resync in progress.

When I click on Volume, it said " Status: Resync 1% complete, Time to finish 7470722 hr 55 min, Speed 0 KB/sec"

That is an odd amount of time to complete. Do you think its not actually rebuilding the drive? Maybe its formatting the drive first which is why the resync is currently at " Speed 0 KB/sec"

*Update, now it said " Status: Resync 3% complete, Time to finish 3060215 hr 50 min, Speed 0 KB/sec"
So its becoming more complete even though the speed is still 0KB/sec. I hope this means its formatting the drive before the rebuild.



A quick view of the logs, I think the time stamp may be a little off. : I must say that I am surprised, I did not know this unit had all these alerts. I usually just turn in on once in a blue moon grab a file and turn it off. I am going to need to setup email alerts on all my systems without exception after this incident.

Fri May 22 18:02:07 PDT 2015 System is up.
Wed Jan 1 16:19:42 PST 2003 ATA error count has increased in the last day. Disk 1: Previous count: 0 Current count: 4 Growing SMART errors indicate a disk that may fail soon. If the errors continue to increase, you should be prepared to replace the disk.
Wed Jan 1 16:19:08 PST 2003 Volume C is approaching capacity: 100% used 17G available
Wed Jan 1 16:18:42 PST 2003 RAID sync started on volume C.
Wed Jan 1 12:24:21 PST 2003 RAID sync started on volume C.
Wed Jan 1 12:22:00 PST 2003 Volume scan found and corrected errors.
Wed May 20 19:14:21 PDT 2015 RAID sync started on volume C.
Wed May 20 09:53:34 PDT 2015 RAID sync started on volume C.
Tue May 19 15:45:32 PDT 2015 RAID sync started on volume C.
Tue May 19 15:38:14 PDT 2015 Volume scan found and corrected errors.
Sun Dec 28 01:07:12 PST 2014 System powering off...
Wed Dec 24 23:08:17 PST 2014 A SATA reset has been performed on one or more of your disks that may have affected the RAID parity integrity. It is recommended that you perform a RAID volume resync from the RAID Settings tab ( accessible in the Volumes page => Volume tab in FrontView ). The resync process will run in the background, and you can continue to use the ReadyNAS in the meantime.
Wed Dec 24 23:06:45 PST 2014 System is up.
Fri Dec 19 00:10:21 PST 2014 Powering off device
Fri Dec 19 00:10:21 PST 2014 Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...
Thu Nov 27 09:23:44 PST 2014 System is up.
Tue Aug 12 06:45:00 PDT 2014 Powering off device
Tue Aug 12 06:44:58 PDT 2014 Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...
Mon Jan 13 17:47:10 PST 2003 System is up.
Wed Jun 11 09:51:47 PDT 2014 Powering off device
Wed Jun 11 09:51:46 PDT 2014 Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...
Thu Apr 24 01:42:01 PDT 2014 System is up.
Thu Apr 24 01:40:19 PDT 2014 Volume scan found no errors.
Wed Apr 23 23:25:52 PDT 2014 Rebooting device...
Wed Apr 23 23:25:51 PDT 2014 Please close this browser session and use RAIDar to reconnect to the device. System rebooting...
Wed Apr 23 19:43:25 PDT 2014 System is up.
Tue Dec 31 18:37:26 PST 2002 Volume scan found and corrected errors.
Wed Apr 23 14:31:50 PDT 2014 Powering off device
Wed Apr 23 14:31:49 PDT 2014 Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off...
Wed Apr 23 06:16:00 PDT 2014 RAID sync finished on volume C. The volume is now fully redundant.
Tue Apr 22 20:37:08 PDT 2014 System is up.
Tue Apr 22 12:44:15 PDT 2014 RAID sync started on volume C.
Tue Apr 22 12:43:54 PDT 2014 Volume scan found and corrected errors.
Tue Apr 8 13:29:56 PDT 2014 System is up.

Here are the details log files if you are interested.

http://1drv.ms/1IQwTaH

I am kind of wondering if I should remove the files from the readynas to keep the CPU space and memory resources freed up on rebuilding the failed drive. Its 4 X 2TB drives in a raid 5 config so it would take days to transfer that off and if another drives breaks during that time, all is lost.

My concern is that its not rebuilding the failed drive cause of the Speed 0 KB/sec. Its at 20% complete but there is no speed on the resync.

My theory is that maybe its formatting the new drive and that is why there is no resync speed yet the % compete is going up.

* Update, its 30% complete at speed 1 KB/sec. 247548 hr 24 min to finish. Maybe its just having issues reading the proper speed for some reason?
*Update, I notice there is conflicting information from what is on the Web based admin page and the RAIDAR software.
If I hover the mouse button over the flashing green light under the volume ICON, its said 28 Hours, 23 minutes until resync at speed 13MB/S which is kind more in the range what I was expecting vs 247548 hr 24 min to complete at a rate between 0 and 1 Kbps.

Is this kind of thing normal or could the firmware be messed up here?

Thanks.

https://onedrive.live.com/redir?resid=f ... 420%211572

*Update, RAIDAar is showing 23MB/s while web admin is showing 3 KB/sec sync speed.

Seems to be a dependency between the 2 methods but the important thing is that the unit is now turning on, booting up, and the files are able to be access as well as the web admin screen. It seem to be on its way to rebuilding the failed green hard drive.
I have it connected to a UPS in case of a power failure.
So I am keeping my fingers crossed that this process completes without incident.

Clear your web browser cache, close your web browser then reopen Frontview.

The disks have to be synced sector by sector. This is at a lower level than the filesystem. The disks have to be synced regardless of whether you have any data on them.

mdgm wrote:
Clear your web browser cache, close your web browser then reopen Frontview. The disks have to be synced sector by sector. This is at a lower level than the filesystem. The disks have to be synced regardless of whether you have any data on them.

Ok, The next morning it shows as complete.

"Configuration: X-RAID (Expandable RAID), 4 disks
Status: Redundant"

Everything is now working and I have full access.

I wonder why the Readynas would start up and basically be frozen instead of allowing me access to the web admin and files using the 3 remaining good drivers.

Is it the way that the Green Drives fail? Basically still spinning up however having damaged on the platters?
Do you think I should update the firmware and maybe it would act better in the future? Its currently on RAIDiator 4.1.8 [1.00a043] however its an old unit so I did not know if it would have trouble with the newer firmware.


I can't believe any Hard drive company would risk such data loss over such a small power difference. This seems insane to me. I don't think a normal person would want to sacrifice their data over a few pennies of power savings a year.



Thank you for helping get the problem solved. That is why I buy so many readynas products because the people actually care about helping you.

I don't recommend green drives in NAS - WDC Red drives are a better choice.

But I don't think the failure you had was specific to green drives either.

StephenB wrote:
I don't recommend green drives in NAS - WDC Red drives are a better choice. But I don't think the failure you had was specific to green drives either.

I currently have 14 RAID system active, 2 are 6 drive systems are 4 drive systems.

So 60 hard drives with a majority of them not being green drives.

I would say that every single time with the exception of 1 time I have had a hard drive fail in my array, it has been a Green drive.

My understanding is that a green drive does certain things to save power that results in the drive being damaged in the process. The power savings are laughable between a green drive vs a normal drive.

In the Readynas software, I can shut down all the drives after 60 minutes of inactivity. I sometimes will shut down a raid system completely if the files don't have to be accessed that often. I can basically do my own power saving management without compromising the data integrity.

Back in the day, the data systems were SCSI hard drives which started out as the best of the best of the regular hard drives before the upgrades to SCSI . Basically like the navy seals of hard drives, the best of the best. The SCSI drives and hardware were extremely expensive however the idea for RAID( redundant array of inexpensive disks or redundant array of independent disks) is that you could use a normal hard drive not have to be forced to buy a special SCSI drive or " RED" drive.
RAID is suppose to allow for a normal average joe hard drive not a special VIP " RED" edition hard drive. It kind of goes against the theory behind raid. If the Red drive is good, then all their hard drives should be made like the red. When you go on an airlines, you don't have to specify that you want a flight that won't crash. They are all not suppose to crash.

The problem from my experience in these green drives are like engineered to be guaranteed defective. I don't know if WD takes the rejected drives and turned them into the green drive or if the mechanical on constantly stopping the hard drive and starting it again over and over again that is causing these defects but these drives in my humble opinion are absolutely insanity to use.

Does it make sense to risk losing all your data over a few cents in power a year? Heck, those Comcast Cable boxes use like 32 watts on and 30 watts off and we are forced to have them on every TV.

My car has a green technology in which it will turn off the car completely if I stop at a red light or in traffic too long. Very annoying since the car's battery can only power the AC for a few seconds before needing to power on again. I don't think its good for my car to keep starting and stopping to I shut that feature off. The point is that this " green" craze that some people are doing is risking to seriously damage people equipment and data for almost zero savings in energy.

After this latest scare, I think I may have to write a letter to the president of WD about the real cost of their " green" drives which are a ticking time bomb of data loss. Thank goodness for RAID technology and the wonderful people on this message board who care enough to help others.

May I ask why you don't think my issue was specific to green drives?

Thanks.

miogpsrocks wrote:
My understanding is that a green drive does certain things to save power that results in the drive being damaged in the process. The power savings are laughable between a green drive vs a normal drive.

My understanding is quite different. A green drives runs at a lower spindle rate. It also parks the heads when the drive is not being accessed. The standard tuning for head parking is set up for the Windows OS - but under linux/raid the heads park too quickly - creating a lot of load cycles very quickly. There are tools available to reset the threshold so drive does not have rapid load cycles.

If you have other information on this, please post it.

miogpsrocks wrote:
May I ask why you don't think my issue was specific to green drives?

Because I have seen a similar failure which did not involve a green drive.

I am a home NAS user, with 16 drives running in various ReadyNAS - 4 of which are old green drives (WD20EARS). These have ~42000 power-on hours with the out-of-the-box settings with no problems. I have another 5 green drives running in various desktop PCs. Overall, the failure rates I have seen with green drives is lower than what I've seen with ordinary consumer drives. I don't use enterprise drives, so I don't have any personal experience with their failure rates.

Today I am deploying WDC Red drives instead of WDC Green (and 4 of the PC green drives were originally in my ReadyNAS). The Red drives are intended for NAS use (and the WD specifically does not recommend their Green drives for NAS). That simplifies any warranty issues, and avoids the need to adjust head-parking thresholds. The Reds also run at less then 7200 rpm, and have similar power use to the Greens. My oldest Red drives have ~23000 power-on-hours.

Whether power savings are "laughable" or not depends on point of view I guess. For me, the main gain is the lower operating temperatures I see in the ReadyNAS enclosures (not the savings on my electricity bill).