[unRAID Server Release 6.0.0-x86_64 Available]

Upgraded from RC3 this morning. All went perfect.

Thank you Lime-technology for delivering us such a great product.

[[SOLVED] Cache drive - read only file system.]

Hello,

RC3 solved the issue for me after applying scrub tools a number of times.

My understanding is that it is a btrfs.img problem related and not the HDD itself.

I would strongly recommend you to upgrade to RC3.

 

Keep us posted on the result please.

Best regards.

[[SOLVED] Cache drive - read only file system.]

Thanks RobJ,

Probably I didn't mentioned that the cache drive itself is RFS formatted and only the docker.img is BTRFS.

I already upgrade to RC-3 and I am closely watching the log.

[[SOLVED] Cache drive - read only file system.]

Dear RobJ,

Thank you very much for your exhaustive comment.

The controller is a Supermicro SASLP-MV8 with LSI cables connected to a Supermicro M35-T cage.

Will upgrade to RC3 as soon as I get back home with a hope to resolve the annoying issue.

Smart (long and short) tests were perform showing no problems with the disk.

Will keep an eye on it and will report what is happening once I upgrade to RC3.

 

Thanks again.

[[SOLVED] Cache drive - read only file system.]

Thanks Jonp for the input.

Could you please elaborate further what test would you like me to perform in order to provide you with additional information?

There are no (obvious) problems neither with the hard-disk nor with the controller.

 

[[SOLVED] Cache drive - read only file system.]

All,

My cache drive has become read-only again. I do not know what is the reason for this but it started to happen after I migrate my server to 6 beta 15.

Every 2 days I need to restart the server because of BTRFS errors. Upgrade to RC3 is still not an option for me.

Please see the system log attached.

 

 

 

syslog.txt.zip

[BTRFS (device loop0): parent transid verify failed on...]

Does it mean it is a bug in beta 15?

Haven't noticed such a behavior of beta 14.

 

Edited:

The problem gets deeper. Now I am unable to use the cache drive as it gets read only almost immediately after a restart and BTRFS-scrub tools are unable to start.

ERROR: scrubbing /var/lib/docker failed for device id 1 (Read-only file system)

scrub canceled for d2d1ad6d-a902-4299-a60c-d4f6a31397ce

scrub started at Thu May 14 09:14:51 2015 and was aborted after 0 seconds

total bytes scrubbed: 0.00B with 0 errors

 

Edited:

Restarted again the whole server and went directly to docker settings. Ran scrub, and here is the output:

ERROR: There are uncorrectable errors.

scrub device /dev/loop0 (id 1) done

scrub started at Thu May 14 09:27:07 2015 and finished after 1 seconds

data_extents_scrubbed: 241775

tree_extents_scrubbed: 25372

data_bytes_scrubbed: 3474448384

tree_bytes_scrubbed: 415694848

read_errors: 0

csum_errors: 2

verify_errors: 0

no_csum: 320

csum_discards: 267533

super_errors: 0

malloc_errors: 0

uncorrectable_errors: 2

unverified_errors: 0

corrected_errors: 0

last_physical: 6480199680

 

[BTRFS (device loop0): parent transid verify failed on...]

Just restarted again and I have a different message in my syslog (attached) this time.

 

May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 40191112 off 13086720 csum 4075985030 expected csum 3722458094

May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 40191112 off 13086720 csum 4075985030 expected csum 3722458094

May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 31910 off 922968064 csum 2992561721 expected csum 3393297930

May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 31910 off 922968064 csum 2992561721 expected csum 3393297930

syslog.zip

[BTRFS (device loop0): parent transid verify failed on...]

Unraid 6 beta 15 here.

Suddenly my all my dockers became offline.

This is the second time it happens for the last 3 days. A restart of the array solves it.

Here is what I had in my log.

 

May 14 00:33:13 UNRAID kernel: BTRFS (device loop0): parent transid verify failed on 1008828416 wanted 178026 found 176354

May 14 00:33:13 UNRAID kernel: BTRFS (device loop0): parent transid verify failed on 1008828416 wanted 178026 found 176354

 

The above message was generated million times. What does it mean?

The cache disk where the docker.img resides is RFS formatted.

A smart test was performed showing no issues.

 

Searched the board and couldn't managed to find similar complain from other users. 

 

 

[myMain Support and Information Thread]

Would be great.

Thanks a lot in advance.

[myMain Support and Information Thread]

Dear bjp999, after many restarts and drive cage slot exchange, the situation with the above issue remains unsolved. Do you have any other ideas to try? The issue doesn't hurt but it would be nice if can be cured.

[[DOCKER] kodi isengard headless]

Understood.

Thank you for your clean comment.

 

[[DOCKER] kodi isengard headless]

Could you please enlighten me what is the benefit of running kodi headless on a server?

Is it only for handling the database or it has other advantages?

In case it is only for database sharing how it is better than MySQL sharing?

Thank you in advance for your work and answers.

[[DOCKER] kodi isengard headless]

i'm not letting it loose on my library (7000+ movies)

 

Offtopic: 7000 movies? And I was very proud of my 1000 Blurays.... 

[myMain Support and Information Thread]

I restarted twice leading to no change.

[myMain Support and Information Thread]

Thanks for your answer bjp.

I am running 6 beta-15.

Please kindly find attached the strings.txt file.

 

TIA.

strings.txt

[myMain Support and Information Thread]

Just added another HDD in my system formatted with XFS FS.

As a result, the Mymain is reporting the HDD as "unmounted (non-array) disk".

The disk is in perfect working order, the main menu is reporting it normal just Mymain.

Here are some screenshots.

 

 

[Help with a red ball (triangle)]

Happy to report that the rebuild went successful. No errors have been reported.

A non-corrections parity check is in progress.

Thanks again for your help.

[Help with a red ball (triangle)]

dear trurl,

the smart report looks absolutely fine.

Thank you for your help.

[Help with a red ball (triangle)]

Thank you for your rapid reply, garycase.

I will report the outcome of the situation as soon as the rebuild Is done.

 

Best regards.

[Help with a red ball (triangle)]

Hi guys,

Needed to replace a Supermicro SASLP-MV8 with a DELL Perc H310 controller.

When I started the array disk 2 came with a redball and consequently the Unraid disabled it.

I have opened the case and discovered that the SFF8087 wasn't fitted well into the controller - causing a bad connection to the disabled Disk2.

I need someone to confirm the steps I took in order to resolve the situation.

1. I have stopped the array.

2. Unassigned disk2 and started the array.

3. Stopped the array and assigned the drive again.

4. Started the array.

5. The rebuild have started.

 

Is there something stupid I have done?

 

[unRAID Server Release 6.0-beta14b-x86_64 Available]

Tested this on an Ivy Bridge system (non-Xeon) that we have here and scaling works fine.  Not sure what differences exist between an i5 ivy bridge and xeon ivy bridge that would cause the the scaling issue to occur on one and not the other, but that is the case.

 

Hi jonp,

Please find a screenshot for Xeon E3 1220 V2

Just to clarify that this "bug" is not making me nervous at all.

By the way noticed it a week ago...

 

[unRAID Server Release 6.0-beta14b-x86_64 Available]

My system is an Ivy Bridge i3-3220T and it has not properly throttled since I upgraded to 14b from 5.0.6 about a month ago. It definitely affects Ivy Brudge as well.

 

I have Xeon E3-1220 v2 in my system and I can also confirm the Ivy is affected.

[Syslog stopped logging]

Thank you all for your comments.

Best regards.

[Syslog stopped logging]

Thanks BRiT

Unfortunately the command doesn't work

root@UNRAID:~# /etc/rc.d/syslog restart

-bash: /etc/rc.d/syslog: No such file or directory