actonice

I updated the firmware of the cache drive (because i read that there may be a bug that shows this behavior in edge cases) and changed the sata cable, after that i ran multiple extended smart tests without errors. Is there anything else i should do before using it normally again? Update: the crucial mx500 worked fine for 2 days without issue but i decided to just replace both mx500 with 970 evo plus drives. I'll mark this as solved.

Sure thing, here it is.

Hey, this randomly showed up in the syslog spamming for hours, when i tried to shutdown it kept saying target is busy until it did a lazy shutdown. After booting back up i backed up the vms and docker since that is all thats on that cache, smart does not show anything unusal, is that drive dying or could it be a cable? What could be the issue? I updated to 6.12.15 but this does not look like it is related to that?

I updated to 6.12.10 the issue seems to just not happen in this version, so there is nothing in the log that i could post.

Sure, I'll update tmr and then post it Edit: yes UD is updated to the latest version

I tried a few 6.12 versions but the webui kept crashing like others reported, but yes i should try out version 6.12.9 and later and see if it improved since a few people with similar issues and hardware report it is fixed or at least more stable. I guess then there is nothing i can do about this popup on version 6.11.5?

Thanks for the reply I should have mentioned this server is still on version 6.11.5, the PHP option seems to not exist in this version yet?

Hey, i get this popup when i try to mount an external 8tb wd elements drive never got this in the past and in the syslog it also does not show any issues, the drive mounts normal as well as far as i can tell. Reboot does not help. Any idea what might be the cause of this?

Got it, thanks for the advice and explanation of the error.

Oh okay, got it. If it happens again at some point (weeks/months) should I then start swapping parts out, or only if it happens regularly?

Thanks for the reply, the ram-kit is CMW32GX4M2E3200C16 and does not have ECC. Should I still ignore the error for now?

Hey, I randomly checked the syslog and saw this: Nov 16 16:53:38 Smalldata kernel: mce: [Hardware Error]: Machine check events logged Nov 16 16:53:38 Smalldata kernel: [Hardware Error]: Corrected error, no action required. Nov 16 16:53:38 Smalldata kernel: [Hardware Error]: CPU:1 (19:21:0) MC12_STATUS[-|CE|-|-|-|-|UECC|-|Poison|Scrub]: 0x809fef1d3b007f8e Nov 16 16:53:38 Smalldata kernel: [Hardware Error]: IPID: 0x0000000000000000 Nov 16 16:53:38 Smalldata kernel: [Hardware Error]: Bank 12 is reserved. Nov 16 16:53:38 Smalldata kernel: [Hardware Error]: cache level: L2, tx: RESV The server did not crash and I could not notice any strange behavior either, so far this only happend once. I ran a full memtest which finished without any errors, is there anything else I should check? Thanks in advance for any advice.