indy5

Members
  • Posts

    109
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

indy5's Achievements

Apprentice

Apprentice (3/14)

1

Reputation

1

Community Answers

  1. I just tried it again this morning and the provisioning completed successfully. Thanks for the update!
  2. Still seeing the same results after a reboot. Do you want to see an updated Diagnostics file?
  3. I am experiencing the same issue as described above. Diagnostics are attached. diagnostics-20211207-1033.zip
  4. xfs_repair ended with: ..Sorry, could not find valid secondary superblock Exiting now.
  5. 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 mode, tried running xfs_repair via UI. The repair ran overnight and ended with a message that a Secondary Superblock could not be found. I am not sure what else to do at this point and I want to make sure that I don't disturb anything, if there's a chance I can save the data. I appreciate any help. Diagnostics are attached. diagnostics-20200810-1048.zip
  6. 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
  7. 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
  8. +1 Also very interested in this to pass device onto Homeassistant Docker.
  9. 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
  10. 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 raspberry pi2 at the moment and things are working fine (other than having to use a separate physical device). I would much rather run this app on my Unraid server. I appreciate the feedback and other's experiences.
  11. 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!
  12. What paths did you set up for the config files?
  13. 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/hapush.py", line 347, in <module> main() File "/usr/src/app/hapush/hapush.py", line 298, in main config = ConfigObj(config_file, file_error=True) File "/usr/local/lib/python3.4/dist-packages/configobj.py", line 1229, in __init__ self._load(infile, configspec) File "/usr/local/lib/python3.4/dist-packages/configobj.py", line 1240, in _load raise IOError('Config file not found: "%s".' % self.filename) OSError: Config file not found: "/hapush/hapush.cfg".