ReadyNas Duo - Freezes / Hangup

(a) are you seeing anything in the logs or health? Check the SMART stats for both drives, and also the ethernet stats (network interfaces, show errors).?
(b) have you ever deleted the log files?
(c) do you have ssh access?

(a) are you seeing anything in the logs or health? Check the SMART stats for both drives, and also the ethernet stats (network interfaces, show errors).?
Just the typical "Volume scan found and corrected errors." Everything says and seems "ok".
(b) have you ever deleted the log files?
No, they got back to 2011
(c) do you have ssh access?
I did turn on FTP for the first time in May. Forgot that I did.
I wanted to see if I could make it easier to access from the outside for various projects but I ended up forgetting about it.
I just turned it off. It would be weird that this caused the issue since I have had no problem for a little over a month with FTP turned on.
Anyway, the answer is no.

If you download the logs (Status > Logs > Download all logs) and extract the contents of the zip file what does diagnostics.log look like?

Looks like an A+ ;)
The only other change I have made recently is adding a second media player.
Not sure if having a second media player access the Nas at the same time could cause it to hang up.

In total I have (2) computers, Media Server, (2) Media Players and a PS3 that could all try to access the system.

Again, the only change since 2011 was adding that second Media Player and turning on FTP. All these where done in the last month and this issue started a week ago or so.

Here is the Diagnostics Log:

Disks
-------------------------------
Passed diagnostics.

Memory
-------------------------------
Passed diagnostics.

Network
-------------------------------
Passed diagnostics.

Performance
-------------------------------
* Jumbo frames are disabled on interface 1. If both your switch and clients support jumbo frames, you can enhance your write performance by enabling jumbo frames on this interface.

Volume
-------------------------------
Passed diagnostics.

Have you made any progress with this fault? My Duo is having similar problems. I've had 3 lockups so far, all have occurred when the NAS has been actively copying files either from my PC to the NAS or from the NAS to an externally connected USB drive. I can still see the NAS on my network, but I can't access the shares. The first time this happened I to pulled the plug and on reboot I got errors about the SMART count increasing.....however I think the errors were caused by pulling the plug. The only other error was about loosing power.

The NAS then sat quite happily getting very light/occasional use for about 2 months without any problems until I tried doing another backup from my PC when it locked again about half an hour into the backup. This second lockup left the front view just about accessible but very slow, I was with some patience able to access the reboot command although it took about 90 minutes for the click in the interface to result in an actual reboot!

The third lockup is still in progress, I set off a backup to a USB drive last night and found the whole thing had ground to a halt this morning. I can still see the NAS on the network and I get intermittent access to the front panel, but I get timeouts that stops me from getting to the reboot page :( I'm thinking that the NAS is still working it's just gone into some weird super slow mo mode.

I updated to the latest firmware a few days ago thinking that may help, but lockups are still happening. I replaced a disk (due to increasing SMART errors) back in March...the new one is a 1TB WD Red, the other drive is the original 1TB Seagate.

Is there a sneak way of safely rebooting without pulling the plug? I have the NAS connected to a UPS so I could try to see if disconnecting the UPS from the wall forced a shutdown of the NAS (NAS and UPS are USB connected), but if it takes 90 minutes to respond, my UPS isn’t big enough to support it for that long. Alternately I could put some tape over the power button to see if the 90 minute lag applies to the physical buttons to?

DrC000 - can you tell us the SMART stats? Generally those errors are not caused by pulling the plug.

I'm not sure if I've still got the logs from the last time it hung. I'm at work at the moment so I've left it in it's hung state until I can get some time to look at it later.....If I can successfully reboot it, I'll download the logs and let you know.

The reason I'm thinking the SMART errors were caused by pulling the plug is that the second hang, when I managed to reboot it, did not result in any new SMART errors. Having said that since the hangs have always happened at times of high disk activity it's plausible that it could be caused by a failing disk.

I understand your theory here, but if we are talking about reallocated sectors or pending sectors it is not plausible. ATA errors perhaps.

After trying everything I could think of last night to get the NAS going again, I ended up having to pullthe plug :( It still looked OK this morning and it's curently resyncing. I've pulled the logs and there are quite a few SMART errors for the older seagate disk...

Smart Stats for disk 1:

=== START OF INFORMATION SECTION ===
Model Family: Seagate Pipeline HD 5900.2
Device Model: ST31000322CS
Serial Number: XXXXXXXX
LU WWN Device Id: 5 000c50 01c64db02
Firmware Version: SC13
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Fri Sep 6 00:40:04 2013 WEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

...boring stuff...

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 069 063 006 Pre-fail Always - 72837718
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 037 037 020 Old_age Always - 65535
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 16301554
9 Power_On_Hours 0x0032 079 079 000 Old_age Always - 18547
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 56
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 64718
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 543
190 Airflow_Temperature_Cel 0x0022 066 062 045 Old_age Always - 34 (Min/Max 33/34)
194 Temperature_Celsius 0x0022 034 040 000 Old_age Always - 34 (0 15 0 0 0)
195 Hardware_ECC_Recovered 0x001a 047 042 000 Old_age Always - 72837718
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 36
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 36
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 64718 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 64718 occurred at disk power-on lifetime: 18547 hours (772 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+08:32:05.888 READ DMA EXT
ef 03 45 01 00 00 00 00 5d+08:32:05.866 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 ff 5d+08:32:05.859 NOP [Abort queued commands]
00 00 00 00 00 00 00 ff 5d+08:32:05.848 NOP [Abort queued commands]
25 00 00 ff ff ff ef 00 5d+08:32:03.426 READ DMA EXT

Error 64717 occurred at disk power-on lifetime: 18547 hours (772 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+08:32:03.426 READ DMA EXT
ef 03 45 01 00 00 00 00 5d+08:32:03.404 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 ff 5d+08:32:03.397 NOP [Abort queued commands]
00 00 00 00 00 00 00 ff 5d+08:32:03.386 NOP [Abort queued commands]
25 00 00 ff ff ff ef 00 5d+08:32:00.954 READ DMA EXT

Error 64716 occurred at disk power-on lifetime: 18547 hours (772 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+08:32:00.954 READ DMA EXT
ef 03 45 01 00 00 00 00 5d+08:32:00.932 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 ff 5d+08:32:00.925 NOP [Abort queued commands]
00 00 00 00 00 00 00 ff 5d+08:32:00.914 NOP [Abort queued commands]
25 00 00 ff ff ff ef 00 5d+08:31:58.472 READ DMA EXT

Error 64715 occurred at disk power-on lifetime: 18547 hours (772 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+08:31:58.472 READ DMA EXT
ef 03 45 01 00 00 00 00 5d+08:31:58.450 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 ff 5d+08:31:58.443 NOP [Abort queued commands]
00 00 00 00 00 00 00 ff 5d+08:31:58.432 NOP [Abort queued commands]
25 00 00 ff ff ff ef 00 5d+08:31:56.010 READ DMA EXT

Error 64714 occurred at disk power-on lifetime: 18547 hours (772 days + 19 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+08:31:56.010 READ DMA EXT
ef 03 45 01 00 00 00 00 5d+08:31:55.988 SET FEATURES [Set transfer mode]
00 00 00 00 00 00 00 ff 5d+08:31:55.981 NOP [Abort queued commands]
00 00 00 00 00 00 00 ff 5d+08:31:55.970 NOP [Abort queued commands]
25 00 00 ff ff ff ef 00 5d+08:31:53.549 READ DMA EXT

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

...boring stuff...

SMART stats for disk 2:

=== START OF INFORMATION SECTION ===
Device Model: WDC WD10EFRX-68JCSN0
Serial Number: XXXXXXX
LU WWN Device Id: 5 0014ee 2b29fd71d
Firmware Version: 01.01A01
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Sep 6 00:40:07 2013 WEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

...boring stuff...

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 139 139 021 Pre-fail Always - 4008
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 099 098 000 Old_age Always - 1045
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 6
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 0
194 Temperature_Celsius 0x0022 111 107 000 Old_age Always - 32
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

...boring stuff...

I'd replace the seagate