diyjeff

Members
  • Posts

    11
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Florida

Recent Profile Visitors

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

diyjeff's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. OK, I deleted smart-one.cfg. Went back in to the device, it was set back to the default values(46 & 55C), changed them to 55 & 60C. Just got a yellow warning that it is 48C. So it is still ignoring the settings in smart-one.cfg.
  2. OK. I changed to Celsius and also bumped the warning and critical temperatures by 1 degree C so that smart-one.cfg is: [Samsung_SSD_970_EVO_Plus_1TB_S59ANM0R50XXXXA] hotTemp="55" maxTemp="60" and still get a yellow warning that the device is hot (50C), not when it is >55C. The general disk warning temperature is 46C. Jeff
  3. I am also having the same issue with an unassigned device: Samsung NVME drive. I get the yellow warning at the general warning temperature of 115F, whereas the smart-one.cfg file shows: [Samsung_SSD_970_EVO_Plus_1TB_S59ANM0R50XXXXA] hotTemp="55" maxTemp="60" Jeff
  4. Just an update since originally posting and adding "-i br0" in mid December I still have not observed the problem again. Just to add I have 5 ethernet controllers in use in my server. Two are dedicated and passed through to one VM, 2 more are passed through to a second VM and the third VM uses br0 and the server uses eth0. A sixth controller is currently not used.
  5. bonienl, I tried the "-i br0" and so far the cpu pegging has stopped. I don't know how long it took for the issue to originally appear, but so far so good. Will update tomorrow if it changes. After that it will be weeks before I will be able to check again. Next morning: Still no high cpu usge.
  6. Just noticed that on the Dashboard one cpu at a time goes to 100%. Running top shows wsdd taking 100% (I am assuming that means 100% on one processor). It jumps around to both regular and HT processors, all of which are not pinned to a VM. It does not seem to be impacting any function or performance; I have not seen this before upgrading to 6.8.0. I do not see any issues in the system log.
  7. Update did not show up under plugins initially (even after clicking Check for Updates). Restarted UnRAID, went back to plugins and updates showed up. Before starting array updated unRAID, Dynamix, Fix Common Problems, Preclear Disks and Unassigned devices. Restarted and everything came up. Always like it when things go smoothly.
  8. Solved. I took out a combo 3 port USB3 & Ethernet card. It ends up the Ethernet port appears to be a USB3->Ethernet adapter and that was what was causing the problem. Thanks for the help.
  9. Thanks, I will look at what is attached and see what happens when I detach devices. And yes I do have a USB-Ethernet adapter plugged in to provide access to a different subnet for a VM.
  10. My log size as shown on the dashboard continues to grow. I have updated the firmware on the server to the latest release. The diagnostics log is attached, but here is an example of what repeats over an over every couple of seconds, filling the log. Oct 17 18:42:07 MediaNAS kernel: handle_tx_event: 4 callbacks suppressed Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Successful completion on short TX: needs XHCI_TRUST_TX_LENGTH quirk? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:07 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? Oct 17 18:42:08 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:09 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? Oct 17 18:42:09 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:09 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? Oct 17 18:42:09 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:10 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 1 ep 4 with no TDs queued? Oct 17 18:42:10 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Oct 17 18:42:10 MediaNAS kernel: xhci_hcd 0000:09:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? Everything appears to work. I am not sure if I did not notice this before upgrading to 6.2.1. Any help is appreciated. medianas-diagnostics-20161017-1838.zip
  11. Worked perfectly to add a StarTech USB3 to Ethernet adapter for a 2nd network adapter (Windows 8.1).