MaxwellHouse

Hi all, I now have a bug to upgrade my system one piece at a time. I'm going to start with the parity drive. Currently I have a 4TB HD and want to update to a 12 TB drive. Is there a recommended process to do this? My thought at the moment is to simply replace the drive, reassign as parity and then run the parity check. Please let me know if I'm on the right track! Thanks, Brian

Sorry to hijack the thread but I was hoping to ask about disabling Google Photo Albums backup? I've found that the albums backup creates a soft link to the photo files on my nvme cache drive and mover doesn't move these links to the array device. I've tried to include the "--skip-albums" argument in both the Extra Parameters and Post Arguments in the advanced container setup but it appears as though that command is depreciated. Thanks!

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

What size is your 980? I have a 500 GB drive and noticed that it reports 84C for exactly 30 minutes!

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!

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.

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

No worries! Thank you very much for your suggestions to try to troubleshoot this issue! I upgraded to rc2 and re-ran the random file write. Very interesting results on Sensor 2... see here: There is definitely more of a delta. Incidentally I increased the write command to 2048 counts and the Sensor2 temp peaked at 53.9C. Hmm.... EDIT: After reverting back to rc1 I noticed a delta of 5C increase when writing 2048 counts. root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +30.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +30.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +41.9°C (low = -273.1°C, high = +65261.8°C) root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +47.9°C (low = -273.1°C, high = +65261.8°C) root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +47.9°C (low = -273.1°C, high = +65261.8°C) root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +45.9°C (low = -273.1°C, high = +65261.8°C) root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +44.9°C (low = -273.1°C, high = +65261.8°C) root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +44.9°C (low = -273.1°C, high = +65261.8°C) root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +43.9°C (low = -273.1°C, high = +65261.8°C) root@maxwell:~# sensors | grep nvme-pci-0400 -A 5 nvme-pci-0400 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +81.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +41.9°C (low = -273.1°C, high = +65261.8°C)

Hey, I ran the dd command while monitoring sensors with rc1 and noted that Sensor 2 went up by 1° C during the course of the write. It came back down once the dd command had finished. I'll re-install rc2 and do the same exercise.

Thank you guys for the detailed follow up! I did see issues once again after upgrading to rc2. Same exact issue where it spikes to 84. I've downgraded back to rc1 and haven't had the issue again.

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.

Good call. Been running rc1 again for a while. No issues....... Will update tomorrow morning. Hmmmmmm

I know, it's weird. At first I thought it was a docker container I was trying to install (it's my Docker cache drive) but I still see the issue. You bring up a good point... it is an older NVMe that I had used before. I suppose I could touch it to see for sure! :-) Otherwise it might be time to upgrade to a 1TB drive w/ heatsink!

It usually sits at 31 - 32 C, but then after the rc2 update I've noticed it spiking up to 84C. It's probably a good idea to get a heatsink on it regardless.

Ok, very good. I'll head to the store at some point to get a heatsink. Thanks!