Disk test running 10 days already

Question

Hello,&nbsp;I'm running a readynas with firmware 6.10.1On august 1 I started a disk test and it is still running now on the 11th.&nbsp;I guess this isn't normal. What should I do? Is it safe to reboot?&nbsp;Kind regardsSteve

stevevandegaer2 · Answer

Last night had to reboot after the device became unresponsive when I activated file search.Should I try the disk test again or do something else first?

StephenB · Answer

stevevandegaer2&nbsp;wrote:
Last night had to reboot after the device became unresponsive when I activated file search.
Should I try the disk test again or do something else first?

One possible reason for the very long test time is that you might have a failing disk.&nbsp; I suggest downloading the log zip file and looking in disk_info.log.&nbsp; Also look for disk related errors in kernel.log
&nbsp;
You might also want to use ssh, and run smartctl -x

stevevandegaer2 · Answer

Not seeing any error in either log file.Started the disk check again, hoping I will get some result this time

stevevandegaer2 · Answer

smartctl -x smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.178.x86_64.1] (local build)Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org&nbsp;ERROR: smartctl requires a device name as the final command-line argument.&nbsp;&nbsp;Use smartctl -h to get a usage summary

StephenB · Answer

stevevandegaer2&nbsp;wrote:
&nbsp;
ERROR: smartctl requires a device name as the final command-line argument.
&nbsp;

Sorry, I assumed more knowledge than you have.
&nbsp;
You need to include the device name for each disk.&nbsp; So for the first disk you use
# smartctl -x /dev/sda
Repeat using sdb for disk 2, and so forth.
&nbsp;
One thing to look for is the "Extended Comprehensive Log" section.&nbsp; Here's a snippet from my own system.&nbsp; "UNC" means "uncorrected error".&nbsp; Not all disks will have this section, but it is helpful when they do.&nbsp;
root@NAS:~# smartctl -x /dev/sdc
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.4.178.x86_64.1] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
...
=== START OF READ SMART DATA SECTION ===
...
SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 12
        CR     = Command Register
        FEATR  = Features Register
        COUNT  = Count (was: Sector Count) Register
        LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
        LH     = LBA High (was: Cylinder High) Register    ]   LBA
        LM     = LBA Mid (was: Cylinder Low) Register      ] Register
        LL     = LBA Low (was: Sector Number) Register     ]
        DV     = Device (was: Device/Head) Register
        DC     = Device Control Register
        ER     = Error register
        ST     = Status register
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 12 [11] occurred at disk power-on lifetime: 36166 hours (1506 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 0c 27 df 40 40 00  Error: UNC at LBA = 0x0c27df40 = 203939648

Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 80 00 c8 00 00 0c 27 df 40 40 08  1d+08:15:46.204  READ FPDMA QUEUED
  60 00 08 00 c0 00 01 06 34 36 98 40 08  1d+08:15:46.163  READ FPDMA QUEUED
  60 00 80 00 b8 00 00 0c 27 e4 40 40 08  1d+08:15:46.146  READ FPDMA QUEUED
  60 00 80 00 b0 00 00 0c 27 e9 40 40 08  1d+08:15:46.123  READ FPDMA QUEUED
  60 00 80 00 a8 00 00 0c 27 ee 40 40 08  1d+08:15:46.094  READ FPDMA QUEUED

Errors in this section might not mean the disk needs to be replaced.&nbsp; But if you are seeing errors that happened during your disk test, then it might help you isolate your problem.&nbsp; If you do see some, the next step is to power down the NAS and test the disk(s) in a Windows PC using vendor tools - lifeguard for Western Digital; seatools for Seagate.&nbsp; If they pass, put them back in to the NAS (in the same slot) before you power it up.
&nbsp;
&nbsp;
&nbsp;
&nbsp;

Forum Discussion

Disk test running 10 days already

10 Replies

Related Content

ReadyNAS Duo still running!

SSD disk failed

Disk Test Status

N204 Remove inactive volumes to use the disk. Disk #1,2,3,4. Firmware 6.10.10

readynas duo v2 disk failed ..

NETGEAR Academy

ProSupport for Business