mason

Sorry somehow i don't seem to get notified by the threat even while subscribed. Was able to update to 2.10.0 but it seems they deprecated the ppa for it. So I need to find another way to integrate it...

just a heads up, you should edit the link on the first post, it throws an 404 error... was able to reinstall the latest from your github release page

Sorry I have no idea how docker on the Synology works... for the normal container you can just start it with: docker run -p 5800:5800 -p 5900:5900 -v /path/to/config/folder:/config/xdg/config/kvibes -v /path/to/media:/movies -e PGID=1000 -e PUID=1000 mediaelch:latest You need to set the options and environments similar to this on the NAS I guess... make sure you have the right user and paths...

Updated to latest MediaElch Version 2.8.18

Upgraded to latest version 2.8.16

yeah i know, but there was nothing running and nothing accessin it afaik. anyway, that rebuild was successfull without any errors now. thanks for the moral and tech support it's weird what issues cabling can cause, you'll never notice until you run something like unraid. so in conlusion: it looks like the issue was caused by a faulty breakout cable

Yeah I know about the inner and outer sectors of a hdd. Right now, it looks like it sorted itself out, array is back to quiet mode and up to the proper speed. Dunno what happend or what might run in the background causing this... *fingerscrossed* Thanks for your reply!

So I replaced the breakout cable and tried another rebuild of disk18, so far it is running. But the speed seems way slower, before maybe 150mb/s compared to 80mb/s now and the array "sounds" different... it "grinds" any idea whats the issue there? could this be the "quality" of the cable?!

of course, but I'm planning on replacing more with 14tb

Rebuild finished with the errors overnight. How do i start another rebuild on that disk? edit: found that part in the docs. Just ordered a new breakout cable for that hba and will rebuild disk18 again I guess. It was replace since it was an old one with some udma errors. and yeah I know, dual parity would be adviced, but there is nothing on that server that is irreplaceable. Also I would need another 14tb disk.

I'm currently in the process of replacing disks in my server. While replacing a 4tb disk18 with a 12tb. Disk3 threw a ton of read errors but stayed online. I had issues with that disk prior to a parity where it would go offiline, after swapping the cable on this one I was able to rebuild disk3 successfull to get it back online with a valid parity. For my understanding right now i can't trust the disk integrity of the rebuld disk18, correct? What would be the proper steps to ensure data integrity there? should i swap back disk18 for the old one, make a new config and replace and rebuild disk3? rebuild didn't finish yet, bit I'm beyond the 4tb mark for the disk i replaced. spacehog-diagnostics-20210918-2210.zip

there was a bugfix release today 2.8.12. .. no issue of the container. image is updated.

Updated to the latest release 2.8.8 also using the version as docker tag to makes things easier Seems like the ppa failed for the base image... need to have a futher look Edit: PPA was fixed and new image pushed

Updated to the latest release 2.8.6

Updated to the latest release 2.8.4