gloworm

Members
  • Posts

    7
  • Joined

  • Last visited

gloworm's Achievements

Noob

Noob (1/14)

2

Reputation

1

Community Answers

  1. I have not experienced any crashes since I temporarily moved my Unraid USB Drive to a different port. Which doesn't make sense. I need to ask this question again, "With the exception of logging to Flash for syslog, does Unraid access the USB and could not being able to access the USB cause a hard crash? (If memory serves, Unraid loads all contents into RAM and runs via RAM; [[[please confirm or deny]])"
  2. To help others that may need it, disabling per USB is not allowed since a kernel came out some time ago disabling that. However one can disable the PCI slot altogether by using the following command: echo 1 > /sys/bus/pci/devices/(Your PCI device here)/remove Use "lspci -vv" To locate your PCI device, mine above was "0000:00:09.0"
  3. The logs are being saved; but the last appendages to the log file are normal outputs. The exception was the most recent crash which the entire log file was lost.
  4. Upon upgrading to 6.12.2/6.12.3, I've begun having hard crashes. 'Nothing on the monitor but a few random characters, no signs of life, but the power is still on' crashes. I did enable logging, but the most recent crash didn't log the data for some reason, and previous crashes nothing is written to the log file, meaning the last lines are normal outputs. This led me down the road of possibly being a hardware issue. The only counter argument I have to that, is that every time it has happened between 1 and 4 am local time. Awfully convenient timing for a hardware issue. At first I thought an IO error of my cache drive could have been causing a freak out. Wiped, stress tested the drives, and rebuilt the cache pool. This morning, I woke up with the crash again. Tried to reboot and it couldn't find my flash drive. Investigated and found contents were fine, temporarily inserted into another port and booted into memtest86 (Going to go ahead and do a RAM check to cover my bases on hardware) I thought about downgrading, but I had the same issue with 6.12.2 although I didn't have in on there for long. 6.11 was my last known 100% config. So my questions are these, 1) With the exception of logging to Flash for syslog, does Unraid access the USB and could not being able to access the USB cause a hard crash? (If memory serves, Unraid loads all contents into RAM and runs via RAM; please confirm or deny) 2) Since I'm not getting software logs as the system crashes and effectively nothing is displayed on the monitor output, what ideas is there to try to resolve the issue? Correct me if I'm wrong, but my next step if the RAM test comes back good would be to start in safe mode, start the array, and see how it performs. Just to rule out a plugin issue. Please give some ideas! P.S. As soon as I get a current log file (post cache rebuild), I'll post it.
  5. As the title says, I'm looking to disable a PCI slot or USB via software because of log pollution. Version: 6.12.3 The log pollution is as follows: kernel: usb usb8-port1: Cannot enable. Maybe the USB cable is bad? Due to the inability to test/remove hardware issues at the present time, I will do whatever necessary via software to stop the messages. Including disabling the individual PCI port altogether (since USB control I've seen is likely impossible). Below is relative hardware info. IOMMU group 23: [1033:0194] 09:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) Bus 007 Device 001 Port 7-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001 Port 8-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Thanks for the help!
  6. I don't know if I'm missing something here, but I can't get dump1090 to show up in Unraid community applications. In the settings, I have told it not to hide anything and show additional results to no avail.
  7. Something about this docker is broken. OP/creator needs to investigate. It creates folders instead of files, does not populate those files as necessary, and I think is even missing files. I have got it partially working by removing the config folders and replacing them with config files, and finding default config file information and placing that inside. It will now stay running but the webgui doesn't work. I think it is missing a file needed.