January 3, 20233 yr Every once and a while I get this error reported Event: Unraid Cache disk temperature Subject: Alert [TOWER] - Cache disk overheated (84 C) Description: Samsung_SSD_980_1TB_******** (nvme0n1) Importance: alert Then a couple minutes later it returns to normal? I have two nvme disks and I see this (seemingly) random on either one. I don't think I've seen both at the same time. I see one of these every couple of days or so.. I find it hard to believe these are real.. Are they? Are they doing some sort of SSD cleanup? Jim
January 3, 20233 yr See here: https://forums.unraid.net/bug-reports/stable-releases/6103-samsung-980-temp-warning-r2007/?do=findComment&comment=20180
January 3, 20233 yr Author Thanks! That does seem to be the issue. Maybe I'll try to update the FW of the drive(s) if I can figure out how to do it safely. Changing the boot config seems easier though. But updated the FW is probably the better solution?? Jim
January 3, 20233 yr Author For my own benefit and I don't have to find it again. Here is a link on how to update the FW https://blog.quindorian.org/2021/05/firmware-update-samsung-ssd-in-linux.html/ Now I haven't tried it yet...
January 7, 20233 yr Author Well I just, successfully updated the firmware on both drives. Hopefully I won't see any issues with the overtemp any more. I was able to update using the ISO image burned to a flash drive. I got the image from here. It warned about possibly erasing all data but it did not do that for me. My data was intact, thank god! So now we'll see if get those overtemps again! Jim
April 26, 20233 yr @jbuszkie wondering if you ran into the issue since updating the firmware? if not, I'll be updating my firmware too. This has been driving me crazy
April 30, 20233 yr Update for anyone who stumbles across this. I updated both of my samsung 980's at the same time using the ISO samsung provides booted off of a flash drive. This completely fixed the overheating issue for me, I haven't gotten a single warning in a few days when usually I get a few a week. I did run mover first just in case but didn't bother to backup my dockers and took the risk. At first my dockers were broken after rebooting, but I ran mover again, and rebooted again, and they work fine. Seems like no data was lost, but if you have docker data you're not willing to lose then definitely back it up because that first reboot with them broken was a bit scary (they wouldn't launch, and said something about "image couldn't be deleted" if I remember correctly). All in all, fairly painless, and very easy/quick. Edited April 30, 20233 yr by Seltonu
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.