David Bott

Members
  • Posts

    227
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

David Bott's Achievements

Explorer

Explorer (4/14)

5

Reputation

  1. Well it did for me. Not 100% on your issue or hardware. I had the issue with Samsung 980 Pro 1TB NVME drives.
  2. Hi... I added... append initrd=/bzroot pcie_aspm=off ...to the UnRAID OS config area. (Click on Flash Drive to get to the right area.) Add it in as a new line, save and reboot.
  3. Thanks...Ok, did that...Bummer, even after a restart and a rescan, no changes, Still can not see the fans. System temp readings seems to the be the same and the only items I can see.
  4. Greetings.... iPERF3 would be nice. (Unless I totally missed it.)
  5. Might I ask how you installed those drivers so your temp and fans could be seen? Thanks
  6. Sorry, has to be said...Don't you mean "I am not a "FAN" of some the dev.... LOL...At least in my head it was funny. Carry on.
  7. RIGHT on all of the above!!! SOME have been moved to unRAID directly, but where? One of the BIG ONES, one the most people are looking for, are the FAN control which requires being able to read various temp sensors for one, which is missing or not well done or not kept up with the drivers, but then being able to control the fan outputs based on the temps. Heck, I can't even see my fan speeds any more. i can see the temp...But even though I can see the temps, I can't do anything with them. A BIG THING when it comes to running a NAS with many drives. Sorry... I have been an unraid users and promoter from when it 1st started....David Bott - Founder of AVSFroum.com But now I am looking to many to have to move as I get concerns over hardware failures when I can not monitor critical items.
  8. Why has no one realized that this development has just gone away? unRAID, as good as it is, is also only as good as the supporting plugins. In this case, Dynamix was one of the best. Now it seems to be hardly supported. Ugh!
  9. Don't count on much when it comes to a number of Dynamix plugins as it seems development has just dropped off for most of the items. Such a great product at one time.
  10. Totally agree on AER setting ,as I mentioned that before to others who mentioned using it. I sure do not want to suppress all PCI errors just to hide this one that was an actual error, even though it was being corrected, it should not need to be. But hiding all the errors is not not a good idea. I have been looking for weeks and never came across that setting as I had no clue it was a power issue. (Power as in a power saving feature...which like you, surely us not needed in this case. Especially for Cache which is always doing something with Dockers. One setting I did try was the sleep timer setting, set to 5500 or something. It seemed to help, but not fully. I have had no other errors as of yet and my system also just did a fully parity check that runs at the 1st of each month. Though it took 1 day, 5 hours, 21 minute to complete. (I have an 18TB Parity Drive for future upgrades to storage. The four data drives are all 8TB currently....But man, it takes a long time to verify 8TB and then it still continues to scan the Parity drive which is another 10TB above that. Not sure why it does that...but oh well. May need to look to using another method or drive format.) This is all do to my upgrading my Motherboard, processor, and adding two NVMe's for cache (RAID) then the error showed up. I so want to thank you again for your research. So...THANKS!!!! Kudos!!!! Yippee!!! Etc.
  11. Morning...And a good one it is! No errors in the log using pcie_aspm=off Might I ask where you came up with that being likely the issue? Thanks
  12. Hi...Thanks for the idea. I just added it to my Sys Config so it now looks like this... kernel /bzimage append initrd=/bzroot pcie_aspm=off ...saved and rebooted. I will check the log tomorrow morning and see if I have the errors still and report back.
  13. It seems I am on the current FW release... 5B2QGXA7 ... So bummer on that. The good news is that the error shows it is "Corrected", the bad news it has an error at that it needs to correct at all.
  14. Well that did not take long. Sorry to say even with the new Kernel (in the 6.11.0-RC4) still have the error. So I went back to 6.10.3 Aug 31 10:53:52 Server kernel: pcieport 0000:00:1a.0: AER: Corrected error received: 0000:03:00.0 Aug 31 10:53:52 Server kernel: nvme 0000:03:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 31 10:53:52 Server kernel: nvme 0000:03:00.0: device [144d:a80a] error status/mask=00000001/0000e000 Looks like I may have to try a firmware update on the NVMe's. I did find this FWUPDMGR Linux thing that it seems I might be able to run to upgrade the drives. Otherwise, it seems Samsung only support Windows with their software and that would be a pain as I would need to remove the drives and find a Windows machine. UPDATE: It seems that fwupdmgr will not work as it is only for supported products... https://fwupd.org/lvfs/devices/
  15. I just now installed Version: 6.11.0-rc4 and will let it run. As you may have seen by my log times, it is not all the time, so I need to give a number of hours. I will report back. Hi...Do you mean Firmware for the Samsung 980 drive itself? If that is what you mean, no, I have not. I will need to look into a current version and how yo even upgrade it. Removing them from my setup is easy for one and hard for the other. So I hope I could do it in the setup. (Hoping it is a bootable flash or something.) Thanks for the thought as never considered updating the firmware on the drive.