• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About indy5

  • Rank


  • Gender

Recent Profile Visitors

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

  1. xfs_repair ended with: ..Sorry, could not find valid secondary superblock Exiting now.
  2. Good day Unraid Community, For, for a bit of background that may have led to my current situation. I have been running a stable system for many years, gone through many drive upgrades, hardware replacements, etc. This past weekend I moved my entire system into a new case, installed a new drive controller (Adaptec 71605). After completing this process, everything was working properly, all drives detected, array started successfully. At some point after things were working, after a reboot, one of my drives went Unmountable. I started the array in maintenance m
  3. I have upgraded to RC2 and am still having issues with this device. Jan 25 09:26:35 kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2 Jan 25 09:26:35 kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
  4. Please let me know if you want to see the full syslog, but here is what I am seeing in mine Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM20702A Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 Jan 22 20:41:54 kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2 Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
  5. +1 Also very interested in this to pass device onto Homeassistant Docker.
  6. I will give this approach a try, thanks! Out of curiosity, how does passing through the controller vs the specific USB device prevent the issue that I have seen? Thanks for your help
  7. I wanted to poll the group on what people are doing passing through USB devices to this container, more specifically the Aeon Labs ZW090 Z Stick. When testing out this installation in the past, I had issues where the USB port for the device would switch after a reboot of the Unraid server (ie ttyACM0 to ttyACM1). This of course, breaks HA's configuration and requires a change to the config files for the device to function again. Is there any kind of more permanent solution to this case? Is there a way, to force the USB device to always use the same port? I have HA running on a
  8. I have followed your guide from the link, but now I am getting only this message in the docker log. Switch to inspect mode. I have altered the path mappings to my own appdata folder that I use for all of my other dockers. Any thoughts? Thanks!
  9. What paths did you set up for the config files?
  10. Has there been any progress on this container? I have been unable to get it started and receive the following in the docker log. I appreciate any help. Traceback (most recent call last): File "/usr/src/app/hapush/", line 347, in <module> main() File "/usr/src/app/hapush/", line 298, in main config = ConfigObj(config_file, file_error=True) File "/usr/local/lib/python3.4/dist-packages/", line 1229, in __init__ self._load(infile, configspec) File "/usr/local/lib/python3.4/dist-packages/", line 1240, in _load raise IOError('Config file not
  11. Thanks, this worked perfectly! You will need to delete your docker image file and recreate it along with your containers. Your appdata for each should be fine, but the containers themselves need to be redownloaded into a complete new docker image file.
  12. I'm getting this error when trying to update Plex Docker as well as CouchPotato Any thoughts?