Alexandro

Upgraded from RC3 this morning. All went perfect. Thank you Lime-technology for delivering us such a great product.

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.

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.

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.

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.

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

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. Edited: Restarted again the whole server and went directly to docker settings. Ran scrub, and here is the output:

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

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. 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.

Would be great. Thanks a lot in advance.

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.

Understood. Thank you for your clean comment.

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.

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

I restarted twice leading to no change.

Thanks for your answer bjp. I am running 6 beta-15. Please kindly find attached the strings.txt file. TIA. strings.txt

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.

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.

dear trurl, the smart report looks absolutely fine. Thank you for your help.

Thank you for your rapid reply, garycase. I will report the outcome of the situation as soon as the rebuild Is done. Best regards.

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?

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...

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

Thank you all for your comments. Best regards.

Thanks BRiT Unfortunately the command doesn't work