-jim

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Male

Recent Profile Visitors

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

-jim's Achievements

Noob

Noob (1/14)

0

Reputation

  1. My Unraid has become a warm brick. Sure that was easy. But then there is a lot of configuration that must be done in other places that is not defined for Unraid.
  2. I too have been unable to run any docker containers for months due to this bug in Unraid and am deeply disappointed there is no apparent documented workable solution. I have dug through 100s of posts looking for a solution and found a lot of contradictions and mostly try this and then that. I have tried 6.10.0-rc2 and still no help. I keep looking at a ipvlan but cannot find how to set this up for my network. So for now, Unriad and all the hardware for me just burn up electricity.
  3. Any updates on this condition? I got this message: Your flash drive is corrupted or offline. Post your diagnostics in the forum for help And when I try to use the Creator: “Unraid USB Creator.app” can’t be opened because Apple cannot check it for malicious software This software needs to be updated. Contact the developer for more information." tower-diagnostics-20211017-0652.zip
  4. While I really appreciate your help, those posts are quite complex with many different steps, many different pages, and no clear answers. I have also spent several minutes exploring how to even find v6.10 to even begin to install with no success. I was expecting more support for a product which requires payment.
  5. Thanks for the help. I have attached the syslog file. syslog-127.0.0.1.log
  6. Been up for 11 days, 1 hour, 20 minutes certainly a record and only as Docker was disabled. Today started docker with no containers running. Appeared anytime Docker Containers were running I would have a UNRAID "Kernel panic not syncing Fatal exception in interrupt" and then this caused an Array Rebuild, that took 33 hours, and this was happening all the time essentially making UNRAID unusable. As some people were pointing to pihole, I uninstalled it from Docker. Have messed with this and read entirely too much and disappointed in UNRAID as I was expecting it to hide these type of complexities. Have made so many changes in network configurations, with no help and admittedly not understanding half of the changes talked bout in several forums in regards to many of the settings. Any ideas? tower-diagnostics-20210807-0736.zip
  7. Had bare binhex-nginx installed and it worked fine. Got to the index.html without issues. Wanted to use let's encrypt and it appears the swag was "the way" forward. Can not get a validation for duckdns.org. always fail at: http-01 challenge for ???.duckdns.org Waiting for verification... Challenge failed for domain ???.duckdns.org No logs are saved in var/log/** nslookup for duckdns.org resolves to my public exposed ip address. Any directions?
  8. I seem to be having similar issues: Mar 1 05:28:57 Tower kernel: usb 1-2: USB disconnect, device number 44 Mar 1 05:28:57 Tower kernel: usb 1-2: new full-speed USB device number 45 using xhci_hcd Mar 1 05:28:57 Tower kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device Mar 1 05:29:01 Tower kernel: usb 1-2: USB disconnect, device number 45 Mar 1 05:29:01 Tower kernel: usb 1-2: new full-speed USB device number 46 using xhci_hcd Mar 1 05:29:01 Tower kernel: cdc_acm 1-2:1.0: ttyACM0: USB ACM device Any Ideas? In my case, this is the ConbeeII (ZigBee Controller) on Unraid: Conbee II - endless connecting/disconnecting loop on USB level CAN'T READ CONFIGURATIONS, ERROR -110 (CONBEE II USB STICK NOT WORKING) Conbee II issues (with Unraid) since last firmware update unRAID - deCONZ - ConBee II I unplugged it and the errors stopped. Still not certain of the solution to fix the issue.
  9. Here is what I know - I plug the device into Windows it works - I plug it into macOS it works - I plug it into unRAID - NOTHING Bought three different devices all with the same results. This is a deal breaker for unRAID. And do not try to tell me it is an authorization thing. "Those users who just want to connect any device without any sort of manual work can add following line to /etc/udev/rules.d/99-local.rules:" ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1" https://www.kernel.org/doc/html/latest/admin-guide/thunderbolt.html
  10. Have a trial license of Version 6.8.3 2020-03-05 and had several issues with several things that were pretty surprising. New Intel NUC 9 NUC9i7QNX 2.6 GHz Intel Core i7-9750H 6-Core processor 32GB RAM Spent a lot of time trying to get the Crucial 2TB P5 NVMe PCIe M.2 Internal SSD CRCT2000P5SS to work be recognized but that appears to be an issue as discussed in So I ordered 2 m.2 1TB and hope that will work. Then I tried a OWC ThunderBay 4-Bay Thunderbolt 3 which works fine on my MAC but it appears to be recognized but does not spin up any drives. Any ideas?
  11. Apparently I am having the same issue with a Crucial P5 2TB PCIe M.2 2280SS SSD. I saw some blurb on the device like: 20-02-2021 15:26 Unraid device nvme0n1 messageNotice [TOWER] - device nvme0n1 returned to normal temperatureCT2000P5SSD8_20362A61D26D (nvme0n1) normal and Feb 20 15:25:30 Tower kernel: nvme nvme0: I/O 41 QID 10 timeout, aborting Feb 20 15:25:47 Tower kernel: nvme nvme0: I/O 1 QID 0 timeout, reset controller Feb 20 15:26:00 Tower kernel: nvme nvme0: I/O 41 QID 10 timeout, reset controller Feb 20 15:26:54 Tower kernel: nvme nvme0: Device not ready; aborting reset Feb 20 15:26:54 Tower kernel: print_req_error: I/O error, dev nvme0n1, sector 0 Feb 20 15:26:54 Tower kernel: nvme nvme0: Abort status: 0x7 Feb 20 15:27:00 Tower kernel: nvme nvme0: Device not ready; aborting reset Feb 20 15:27:00 Tower kernel: nvme nvme0: Removing after probe failure status: -19 Feb 20 15:27:05 Tower emhttpd: error: ckmbr, 2030: Input/output error (5): read: /dev/nvme0n1 Feb 20 15:27:05 Tower emhttpd: import 30 cache device: (nvme0n1) CT2000P5SSD8_20362A61D26D Feb 20 15:27:05 Tower emhttpd: import flash device: sdb Feb 20 15:27:05 Tower kernel: nvme nvme0: Device not ready; aborting reset Feb 20 15:27:05 Tower kernel: Buffer I/O error on dev nvme0n1, logical block 0, async page read Feb 20 15:27:05 Tower kernel: nvme nvme0: failed to set APST feature (-19) So which ones will work? Thanks -jim