minority

On extracting a copy of the latest rom... I couldn't get it to work. It seems you have to desolder the chip first and then read the rom. My soldering skills are quite poor... so even if I manage to remove the rom chip, it isn't going back on again 😁

I don't think it is as easy as we think - running some software to dump the ROM. Logic dictates it is possible to read the ROM if we can write to it, but this software doesn't exist today. There is something about an SPI ROM programmer being an option. You connect a device to the rom on the board and dump the firmware directly from it. I have one laying around, maybe I give that a go to establish if it is possible.

I would keep the newer firmware, no reported issues with it. There was another poster called Shonk who also received a card with this newer firmware version. I think his goal was to take a backup of it to provide to the rest of us. Maybe something you want to attempt? Or can you say where you bought your card?

It turns out it is because of the Kingston SSD I use. Replaced with a Samsung 980 Pro now, power consumption has dropped. Same experience described here. I also suspect I may have had this issue for longer than I thought, without noticing. I hope you get to the bottom of your issue.

I came across your thread here and your posts in the powertop thread trying to understand my own increase in power consumption that I noticed yesterday. I was running 6.9.X for a long time and decided to upgrade to 6.12.6 after some plugins wouldn’t update some weeks ago. I haven’t checked power consumption in a long time but I was idling at between 42-50 watts and I was surprised it now is around 72 watts. I have two VMs running and some docker containers. I can’t really power things down as it runs the internet here as well 😁 But will try to test over the weekend to see if I can see the same issues as you.

Thanks both for the reply. I will do some reading and some testing, I was hoping for a less manual way (less time consuming) of diagnosing what is causing the issue. Will post at some point once I get to the bottom of it. The second parity-check (without reboot) completed without finding any errors.

Hello JorgeB! Any tips to figure out which of the controllers it is acting up? Everyone else reports great experiences with these controller cards. Kind regards.

Hi! After running with 2 x LSI SAS9217-8i cards flawlessly for some years, I decided to switch to some ASM1166/ASM1064 cards for better power consumption (save on my electricity bill 🙂). It's 2 x ASM 1166 and 1 x ASM 1064 and then eight on-board SATA ports on a Gigabyte C246M-WU4. Unraid 6.9.2. The problem is, now when I run a parity check, I get 5 errors... for some reason on the same sectors. I'm running a second parity check now and the errors haven't come up yet, and I don't think they will. So it seems like it only occurs on a fresh power up (parity check after a restart). I used to have a similar issue with a AOC-SAS2LP-MV8 (at least similar in appearance to me), where errors would always come up on first parity check after powering on - but I'm not sure if with that card it's always the same sectors. Sep 20 03:09:37 nas2015 kernel: md: recovery thread: P corrected, sector=2743151176 Sep 20 03:09:37 nas2015 kernel: md: recovery thread: P corrected, sector=2743151184 Sep 20 03:09:37 nas2015 kernel: md: recovery thread: P corrected, sector=2743151192 Sep 20 03:09:37 nas2015 kernel: md: recovery thread: P corrected, sector=2743151200 Sep 20 03:09:37 nas2015 kernel: md: recovery thread: P corrected, sector=2743151208 Nov 11 02:09:59 nas2015 kernel: md: recovery thread: P corrected, sector=2743151176 Nov 11 02:09:59 nas2015 kernel: md: recovery thread: P corrected, sector=2743151184 Nov 11 02:09:59 nas2015 kernel: md: recovery thread: P corrected, sector=2743151192 Nov 11 02:09:59 nas2015 kernel: md: recovery thread: P corrected, sector=2743151200 Nov 11 02:09:59 nas2015 kernel: md: recovery thread: P corrected, sector=2743151208 I have this feeling that if I switch back to the 9217-8i cards the problem will go away. Diagnostics from both runs is attached. Can someone help explain what is happening? Thanks. unraid-diagnostics-20221112-1319.zip unraid-diagnostics-20220920-1809.zip

Right, it was more of a question as to if anyone else had any problems. I figured out the errors started occurring after running powertop --auto-tune. I had the system running for maybe 12 hours, when I manually ran the command. It seems this gets them into a low power state, and they don't properly come back up (23 disks, 5 were giving read errors)? After rebooting everything is good, no powertop --auto-tune command, running for 3 days 15 hours and counting. I will post a thread when I dare to try again, maybe someone can explain why they act the way they do. After a hike in electricity prices, I've been trying to lower the idle consumption of my server. Inspired by mgutt here and here (powertop --auto-tune). So, with the 2 x 9207's, the whole system idles at 61-62w. No difference if try to optimize power consumption with powertop, like they wouldn't go into a lower power state. With 2 x 1166, 1 x 1064 I am at 42w (23 disks, 8 onboard sata). If I run powertop --auto-tune, the system idles at 31w. I did some tests with the 9207's I had when I was building the new system, to see how much power they consume, and it was far more power than I liked, and I couldn't get them to use less. I believe only CPU+mobo+RAM (bare system, nothing connected) 8w idle. Adding two 9207's, still no disks, total system idle at 24w.

Hi! In trying to lower the power consumption of my unRaid server I decided to replace my 2 x 9207-8i cards with: 2 x ASM1166 PCIe x4 1 x ASM1064 PCIe x1 The 9207’s have been working flawlessly, though a bit power hungry vs the ASMs. On first boot I had issue with the ASM1064. Decided to buy a new one. Same error. Changed PCIe slot with the neighboring Intel NIC. Great. However. That worked for less than 24 hours… now the disk errors are in… but for 5 disks. I’m not sure if the errors were triggered during spinning up and down? Anyone else have similar experiences? I don’t have time to check tonight, will try and investigate tomorrow but I don’t really know where to start.

My Plex broke too as pilgrimHK describes, after updating today. Gonna try the permissions suggestion and see how things go. Edit: Deleting the perms.txt file solved the problem. Name of Plex might have changed, because users suddenly don't have permissions to libraries, corrected that manually.

Whats the not so easy solution?