Scrub Volume Command failed

Got it started again !!

root@readynas:~# btrfs scrub status /data
scrub status for 7c0b297e-1b89-4fbf-8e56-4d4caee95803
scrub started at Wed Jul 3 15:15:10 2013, running for 7586 seconds
total bytes scrubbed: 493.54GB with 0 errors

root@readynas:~# btrfs scrub cancel /data
ERROR: scrub cancel failed on /data: not running

root@readynas:~# btrfs scrub start /data
scrub started on /data, fsid 7c0b297e-1b89-4fbf-8e56-4d4caee95803 (pid=23962)

root@readynas:~# btrfs scrub status /data
scrub status for 7c0b297e-1b89-4fbf-8e56-4d4caee95803
scrub started at Tue Jul 9 10:04:35 2013, running for 45 seconds
total bytes scrubbed: 2.60GB with 0 errors

Greetings,

After months and months of hesitation have I finally chosen the Readynas 102 + 1 WD Red 2TB . And after a day of use I encounter my scrub process locked in 4.24% for hours. Apparently another user was uploading when I command the OS to start scrubbing. Dunno how relevant this info is but I had to physically reset it. And also I don't know if my data is intact. Thus my first post here.

It seems you could discover how to get it started again but frankly I'm not able to understand your explanation. Any tips for a rookie?

Thank you in advance.

wagon wrote:

Greetings, After months and months of hesitation have I finally chosen the Readynas 102 + 1 WD Red 2TB . And after a day of use I encounter my scrub process locked in 4.24% for hours. Apparently another user was uploading when I command the OS to start scrubbing. Dunno how relevant this info is but I had to physically reset it. And also I don't know if my data is intact. Thus my first post here. It seems you could discover how to get it started again but frankly I'm not able to understand your explanation. Any tips for a rookie? Thank you in advance.

Which firmware version are you using?

Jedi Knight wrote:
Which firmware version are you using?

I didn't install RAIDiator, do I need it?
My OS is updated: 6.0.8

Did I answered in a proper way Jedi?

The scrub process stopped in 4.24% for more than a day and the volume write operation in the I/O stats grows continually maybe presenting a risk to the Hard drive(?). I've read in this forum but in no official manual that scrubbing may damage the HD(?).
I decided, after reinstalling the OS, to also boot to Factory default.

Best regards.

wagon wrote:
Jedi Knight wrote: Which firmware version are you using? I didn't install RAIDiator, do I need it? My OS is updated: 6.0.8

You are confusing RAIDiator with RAIDar. OS 6.0.8 is what Jedi Knight wanted to know.

StephenB wrote:
You are confusing RAIDiator with RAIDar. OS 6.0.8 is what Jedi Knight wanted to know.

Thank you Stephen, still getting it. I'm confused quite often in this NAS world :)
Any tips on this situation?
I was finishing a lunch before performing the factory default. Seems to me like the only feasible option.

First I'd run vendor diags (in this case Lifeguard) on the drive. You'd do this in a PC (using a USB enclosure or adapter is fine).

If it passes, I would engage Netgear support (support.netgear.com if your 90 days phone support is up).

If it fails, try returning it to the seller first, since they would exchange it for a new drive. If it is too late for that, contact WDC, they will provide a re-certified replacement.

StephenB wrote:

First I'd run vendor diags (in this case Lifeguard) on the drive. You'd do this in a PC (using a USB enclosure or adapter is fine). If it passes, I would engage Netgear support (support.netgear.com if your 90 days phone support is up). If it fails, try returning it to the seller first, since they would exchange it for a new drive. If it is too late for that, contact WDC, they will provide a re-certified replacement.

Wow your procedures seemed so serious and laborious that a factory reset didn’t sound so drastic anymore to me. So I did it. And it seems ok. No more scrubs there for now. :wink:
Now in a X-Raid disc is it superfluous to use the scrub procedure? And if not, how often?

Thank you again Stephen!

It seems to me that the most likely reason for a scrub to hang is that a disk is failing. So even if the reset resolved your issue, there is still something that needs to be checked out. At the very least look at the SMART stats.

The benefit of scrubbing is that the process reads through all the sectors on the array, so issues are caught sooner rather than later. Most users have a lot of rarely-accessed files on their drives (certainly I do). Though I don't access them often, I do want to know that they still can be read. I recommend running scrubs periodically - on my Pro I schedule them for every 3 months. Monthly is reasonable also, I see no reason to run them more often than that.

I've just started a scrub on my RN102 T1832 beta (I have 2 WDC 3 TB Red drives installed). If it also hangs, I'll post back.