Ulf Thomas Johansen Posted November 8, 2021 Share Posted November 8, 2021 Interresting Quote Link to comment
Ulf Thomas Johansen Posted November 8, 2021 Share Posted November 8, 2021 Would this indicate that I should revert back to rc1? Quote Link to comment
MaxwellHouse Posted November 8, 2021 Author Share Posted November 8, 2021 I have reverted and the problem has gone away. If there are any other ideas to try to troubleshoot this I'm very happy to help. -Brian Quote Link to comment
macieksoft Posted November 10, 2021 Share Posted November 10, 2021 I'm having the exact same issue with a z490 and Samsung 980. I have a massive heatsink with thermal bad and the temps go from 39C to 84C randomly. The actually drive is not very hot, so this seems to be an software issue reading the temps. Quote Link to comment
MaxwellHouse Posted November 11, 2021 Author Share Posted November 11, 2021 Hi all. For fun I took the cover off my server and then installed rc2. As soon as I got a notice that the NVMe went to 84C I went to go touch it. I can tell you that it was NOT at 84 (otherwise I'd be in pain!) This seems to point to a sensor read error in rc2. Quote Link to comment
macieksoft Posted November 11, 2021 Share Posted November 11, 2021 I also noticed it stays at 84c for exactly 1 hour. I have Pushbullet send me notifications and it's consistently going from 39c to 84c for 1 hour before dropping back to 39c. Quote Link to comment
Vr2Io Posted November 11, 2021 Share Posted November 11, 2021 31 minutes ago, macieksoft said: I also noticed it stays at 84c for exactly 1 hour. I have Pushbullet send me notifications and it's consistently going from 39c to 84c for 1 hour before dropping back to 39c. Samsung 980 ? Quote Link to comment
macieksoft Posted November 11, 2021 Share Posted November 11, 2021 1 minute ago, Vr2Io said: Samsung 980 ? Ya, the regular 980 (not the pro). Quote Link to comment
DivideBy0 Posted November 11, 2021 Share Posted November 11, 2021 On 11/5/2021 at 10:23 AM, MaxwellHouse said: Well, after reverting I had no issues. So just to make sure I went back to rc2 but this time I ran "Update Assistant" before going from rc1 to rc2. It's been up for about 90 minutes without any issues. Told you Quote Link to comment
MaxwellHouse Posted November 11, 2021 Author Share Posted November 11, 2021 30 minutes ago, johnwhicker said: Told you Yeah, I went back to rc2 and I'm getting the same problem. But, we've determined it's a sensor read error on Samsung 980 NVMe drives. So, for now, I'm ignoring the warning! Quote Link to comment
DivideBy0 Posted November 11, 2021 Share Posted November 11, 2021 41 minutes ago, MaxwellHouse said: Yeah, I went back to rc2 and I'm getting the same problem. But, we've determined it's a sensor read error on Samsung 980 NVMe drives. So, for now, I'm ignoring the warning! You could always cook same eggs Kidding 1 Quote Link to comment
V1per5h0t Posted November 14, 2021 Share Posted November 14, 2021 Just a weigh in that I am having exactly the same issue. RC2, Asus x570 MB, 5700g, NVMe is a Samsung 980. Drive is cool when it is reporting 84 degrees. Drive logs show around 36-38 during this period too. Two (perhaps) differences from my setup to the others in the thread: (1) Have a heatsink on the NVME SSD already. (2) NVMe is being used as a passthrough drive for a VM - it is not assigned to an array or pool. So definitely seems to be an issue with RC2. Quote Link to comment
MaxwellHouse Posted November 15, 2021 Author Share Posted November 15, 2021 On 11/10/2021 at 11:35 PM, macieksoft said: I also noticed it stays at 84c for exactly 1 hour. I have Pushbullet send me notifications and it's consistently going from 39c to 84c for 1 hour before dropping back to 39c. What size is your 980? I have a 500 GB drive and noticed that it reports 84C for exactly 30 minutes! Quote Link to comment
macieksoft Posted November 15, 2021 Share Posted November 15, 2021 9 minutes ago, MaxwellHouse said: What size is your 980? I have a 500 GB drive and noticed that it reports 84C for exactly 30 minutes! I have the 1TB version. Quote Link to comment
V1per5h0t Posted November 15, 2021 Share Posted November 15, 2021 1TB - about 30 mins for the issue sounds about right. Quote Link to comment
V1per5h0t Posted November 26, 2021 Share Posted November 26, 2021 (edited) I have a solve, or at least can point to the cause of this issue. It's something to do with this specific NVMe drive. Not sure if it is the lack of DRAM or the new controller on the 980, but whatever it is, that is what is causing this 30 min period of reported overheating. I just switched out NVME drives (in this case to the 980 Pro) and the issue is gone. No other change in configuration at all. Even using the same M2 slot on the Motherboard. Been running solidly like this over 48 hours now. I'm not sure if this is something that Unraid can fix, or if it will get better with newer releases that deal with this new style of NVMe drive more correctly. One parting thought on this. I don't believe the 980 actually ever got to 84 degrees or that it overheated at all. I think it was just misreporting. I made sure to be there a couple of times when it was reporting the overheating and the drive felt cool to the touch. So I don't think over-time, this problem will cause any issues to the physical drive, but since this was a mission critical drive for me, I didn't like the issue and wanted to be sure to get onto something which works as it should. Edited November 26, 2021 by V1per5h0t Quote Link to comment
MaxwellHouse Posted November 26, 2021 Author Share Posted November 26, 2021 (edited) 2 hours ago, V1per5h0t said: I just switched out NVME drives (in this case to the 980 Pro) and the issue is gone. No other change in configuration at all. Even using the same M2 slot on the Motherboard. Been running solidly like this over 48 hours now. Ok, so you've talked me into it... I just bought a 980 Pro 1TB NVMe. So, what's the best way to replace my 500 Gb NVMe drive? Should I do an rsync to another mount, switch out the drive, let Unraid do it's formatting thing, and then rsync back? I use this guy for all of my Docker containers. EDIT: Never mind, I found this wiki. Thanks! Brian Edited November 26, 2021 by MaxwellHouse Quote Link to comment
[email protected] Posted January 5, 2022 Share Posted January 5, 2022 Wanted to add I have two of the samsung 980 nvme SSDs in an NVME pool on an asus hyper m.2 card and am running the current RC2. The 980s read 84C for 30 minutes then go back to normal. The other two NVME drives on the card are usually at 25-35C even under load. This was never a problem in the several previous versions of unraid. Hopefully this error is fixed in the future. Quote Link to comment
WillPower Posted March 22, 2022 Share Posted March 22, 2022 Just to add, I'm also experiencing this bug in RC2/3/4 with a Samsung 980 1TB. Getting the same as others where it reports 84C for 30 minutes. I'm glad I searched and found this thread, I'm less concerned now and assume it's mis-reporting the value. Quote Link to comment
Schulmeister Posted March 27, 2022 Share Posted March 27, 2022 Same here, I have 4 1TV Samsung 980 nvme in an ASUS Hyper M.2 x16 Gen 4 Card. Massive cooling with fan, so there's no way it could spike to 84°C. I run this set as a btrfs-raid 10 so the likeness that if there's overheating only 1 of the 4 would overheat is very, very low. It must be a software error. I run 6.10rc4 If I switch back to 6.9 no issues. Any suggestions from unraid ? Quote Link to comment
JorgeB Posted March 28, 2022 Share Posted March 28, 2022 15 hours ago, Schulmeister said: Any suggestions from unraid ? It's a problem with the device: https://us.community.samsung.com/t5/Monitors-and-Memory/SSD-980-heat-spikes-to-84-C-183-F/td-p/2002779 1 Quote Link to comment
vyral Posted June 10, 2022 Share Posted June 10, 2022 I am having the exact issue. Exact Quote Link to comment
JorgeB Posted June 10, 2022 Share Posted June 10, 2022 8 hours ago, vyral said: I am having the exact issue. As will everyone using a Samsung 980 NVMe device, until they fix it. 1 1 Quote Link to comment
LukePOLO Posted August 2, 2022 Share Posted August 2, 2022 Reporting same issue , glad to see it seems to be a bug Quote Link to comment
Chr0nic7 Posted August 25, 2022 Share Posted August 25, 2022 Here to report that I am having the same issue and config. Quote Link to comment
Recommended Posts
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.