jowi

ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 016 - 0 2 Throughput_Performance P-S--- 136 136 054 - 80 3 Spin_Up_Time POS--- 149 149 024 - 557 (Average 481) 4 Start_Stop_Count -O--C- 099 099 000 - 5491 5 Reallocated_Sector_Ct PO--CK 100 100 005 - 7 7 Seek_Error_Rate PO-R-- 100 100 067 - 0 8 Seek_Time_Performance P-S--- 114 114 020 - 37 9 Power_On_Hours -O--C- 089 089 000 - 82897 10 Spin_Retry_Count PO--C- 100 100 060 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 140 192 Power-Off_Retract_Count -O--CK 096 096 000 - 5604 193 Load_Cycle_Count -O--C- 096 096 000 - 5604 194 Temperature_Celsius -O---- 230 230 000 - 26 (Min/Max 18/55) 196 Reallocated_Event_Count -O--CK 100 100 000 - 9 197 Current_Pending_Sector -O---K 100 100 000 - 0 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 0 My oldest drive (Hitachi HDS724040ALE640, 4TB) has 7 reallocated sectors, showed up a few days ago. With over 10 years of service, pretty good if it starts to increase, i will replace it with an 8TB one. This is my parity drive btw.

Yes, and thanks again, but i wanted to follow your advice and wait for some more confirmations. But it doesn't look anyone else will respond. I decided to do it anyway. I've backupped the db data just to be sure, and did the update, all looks well.

I have now asked 4 times in the last few weeks if ANYONE has issues after applying the fix a few weeks ago, and applying recent updates. Sadly, no response at all? Really?

How can i find out what exact version is installed anyway? If i know, i could do the update, and if it fails, revert back to my previous (current) version.

Anyone yet that can confirm that updating a previously 'fixed' mariadb (manually fixed to v10.5.12) can be succesfully updated to the latest version?

What i did was set the version manually (i forgot what version exactly) update it, and then set it to 'latest', and get the lastest version. After that, it was working again. As i understand it, that was the fix: 1. update to version x manually, 2: update that to the latest. So, how can i see what the version is i have actually installed? *edit* if i check version in mariadb itself it says : 10.5.12-MariaDB Don't know if the docker version is something else?

But i did the fix, and now there is an update... so it won't let me skip this update. I have to manually do ALL other updates, otherwise if i ' update all' this will update as well... i will wait for confirmation from others that did the fix and applied this latest update.

Unraid tells me there is an update for the mariadb docker, but i'm affraid to install it, since last time everything went wrong. How do i know this update will be ok? Someone tried it? Is there a way to know to what version it will be updated? Is there a way to rollback? Is there a way to exclude a docker from updates? At the moment, i can not update all, since i dont want mariadb to update, so i have to update all others manually one by one...

It has been working good for the last few days. But i'm worried about the next time unraid wants to update mariadb... is there any news if this will continue to be a problem? Or should we export the db etc and install a new, different mariadb docker?

ok, looks like the same issue others are having, i did not recognize it that fast. Did the 'downgrade' (?) to linuxserver/mariadb:110.4.21mariabionic-ls31 and then to latest... as described. Looks like it is functioning again. Now making sure i do have backups of everything that uses mariadb... something i overlooked.

My mariadb no longer works after the last (?) update? If i run 'mysql' i get : Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) Also several website depending on mariadb and my nextcloud is not working. This is bad... How do i fix this? Can i go back to the previous version, and if yes, how?

Ever since i upgraded to unraid 6.9.2, my timemachine stopped working. Had it set up using spaceinvaders tutorial. Now, whatever i do, tm just cant find the disk where the timemachine share is anymore. Even removed my old timemachine share... (nice, no backups anymore...) hoping i could create a new one, or maybe the tm share got to big, but no matter what i do, i just can't get this f-ing thing to work on unraid. It was always a hassle, but this time it looks like it's really broken.

Found the answer on Reddit. Not here. On Reddit. Just upgrade to 6.9.2 and it is fixed.

Doesn't work... after manually forcing all updates, basic mode shows 'up to date', so far so good. But if i now check for updates, everything reverts back to 'not available' again... So, what is the exact solution to this?

Not what i was looking for but i found a tutorial in the french section that had the info i needed: