Scrub Volume Command failed

Nice, thank you!
I had scrubbed before and no problems. This last time the only difference is that another user was uploading files while the procedure was started and the NAS lost connection afterward. So I supposed that uploading new data while checking it could have been the cause.
But I'm willing to check the disk integrity of course. Is it possible to look at the SMART status via browser? Or do I need to install RAIDar?

This server wasn't bought in the same place as the hard disk so it would be complicated to relate it to the support which, btw, has been so strongly criticized here and elsewhere that frankly I'm afraid to contact. Thankfully I intend to be a 'light' user :p

Best regards.

The RN102 firmware is still new, so it is possible that something else disrupted the scrub. But it is still good to check.

-You can see the SMART stats from the browser.

(a) Download the logs to your PC and look at volume.log (it is a text file, so notepad will work fine). The stats you care about are reallocated sectors, current pending sector count, and uncorrectable sector count.
(b) Also, hover your mouse over each drive in the RN102 picture in the center of the system/volumes tab. That will show you ATA errors (which are not SMART, but are still useful to see).

Your disk is on the RN102 HCL, and designed for home NAS by WDC - so there should be no problem with either Netgear support or WDC. If the drive is failing, WDC would replace it with a re-certified drive. In my experience most sellers will exchange disks for new ones with no questions asked (within a short window of the purchase date). I only buy disks from sellers that will do that.

Overall, keep in mind that people are more likely to post their complaints about support than praise. I haven't needed to use them myself, but I certainly wouldn't hesitate to do so.

Thank you again, nothing like knowing where to look for!

The stats in the volume.log are all fine, I suppose. Including ATA:

Reallocated Sectors: 0
Reallocation Events: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0

ATA Error: 0

I'll keep an eye on it.

Overall, keep in mind that people are more likely to post their complaints about support than praise. I haven't needed to use them myself, but I certainly wouldn't hesitate to do so.

It makes sense. I shall keep that in mind. No reason to be afraid of support :)

StephenB wrote:
...I've just started a scrub on my RN102 T1832 beta (I have 2 WDC 3 TB Red drives installed)...

These completed. Drive 2 took about 5 hours, drive 1 about 6. These were run in parallel (a bit of a stress test). The drives are jbod (independent volumes).

A few quirks, notably the NAS went briefly non-responsive at the end of the each scrub (UPS communication errors were logged, and the web ui connection was lost for a few seconds). Nothing really horrible though.

I have the same problem (new ReadyNAS 104 fw 6.1.6).
Do you have any idea how to force it to cancel?

root@schemnas:~# btrfs scrub status /data
scrub status for 93255340-2c1f-457a-90ab-8388c735651f
scrub started at Sun Feb 23 21:12:27 2014, running for 873 seconds
total bytes scrubbed: 98.28GiB with 0 errors
root@schemnas:~# btrfs scrub cancel /data
ERROR: scrub cancel failed on /data: not running
root@schemnas:~# btrfs scrub resume /data
ERROR: scrub is already running.
To cancel use 'btrfs scrub cancel /data'.
To see the status use 'btrfs scrub status [-d] /data'.
root@schemnas:~# btrfs scrub start /data
ERROR: scrub is already running.
To cancel use 'btrfs scrub cancel /data'.
To see the status use 'btrfs scrub status [-d] /data'.
root@schemnas:~#

Maciek

I too have exactly the same problem.

root@ReadyNAS:~# btrfs scrub status /data
scrub status for c9439d9b-a5e6-47df-83fe-7988eedca356
scrub started at Thu May 29 10:06:56 2014, running for 6293 seconds
total bytes scrubbed: 384.43GiB with 0 errors
root@ReadyNAS:~# btrfs scrub cancel /data
ERROR: scrub cancel failed on /data: not running
root@ReadyNAS:~# btrfs scrub resume /data
ERROR: scrub is already running.
To cancel use 'btrfs scrub cancel /data'.
To see the status use 'btrfs scrub status [-d] /data'.
root@ReadyNAS:~# btrfs scrub start /data
ERROR: scrub is already running.
To cancel use 'btrfs scrub cancel /data'.
To see the status use 'btrfs scrub status [-d] /data'.
root@ReadyNAS:~#

Fact is, I know that the scrub actually finished. The log shows it finished a day ago.

My guess is that the scrub stat record file is incorrect/damaged/corrupt.
I understand there is an -f option on the btrfs scrub start to overcome a damaged stat record, but this option is not recognised on OS6.1.8.
Is there a way to force a scrub start?

-------
Update:
Found this http://bugzilla.kernel.org/show_bug.cgi?id=66151 which pretty much describes the problem.

Found the offending status file in /var/lib/btrfs.
Checked that no 'btrfs scan' task was running (htop).
(After backing up my data), I deleted the status file. That cleared the 'scrub in progress' status from frontview, and ran a new scrub.
After scrub finished ran 'cat' command on the status file to confirm all was okay.

Black Duck wrote:

I too have exactly the same problem. ------- Update: Found this http://bugzilla.kernel.org/show_bug.cgi?id=66151 which pretty much describes the problem. Found the offending status file in /var/lib/btrfs. Checked that no 'btrfs scan' task was running (htop). (After backing up my data), I deleted the status file. That cleared the 'scrub in progress' status from frontview, and ran a new scrub. After scrub finished ran 'cat' command on the status file to confirm all was okay.

Thanks, this solved the problem in my devicd!

Hi Guys,

I would thanks you for this. Now i restart scrub and hope all goes fine. I had scrub session from almost one year!!!! and i'm not able to install aplications, tranfert was a big trouble. thanks thanks..anyway hope everithing goes wright.....