TRusselo

hmm.... rebuilding something... but there was nothing when unmounted, no emulated data. still said unmountable... hmm... we'll see what gets written

screw it. mounted, formatting... says data-rebuild paused?? wtf?

pretty sure. disk was installed for couple weeks before i got the error

Sorry for the late replay. busy life. Covid for the past week. couldnt deal with anything. So... unselected disk, array online No emulated data available. fresh diags below. again. i dont care about the missing data. How do i get back to good state? select disk and format? then resync? big-z-diagnostics-20231013-1656.zip

Sorry for the delay. busy life. Reboot, tried to UNSELECT disk 11 to check emulated data. get this warning (see screenshot). sounds bad. reselected the bad disk 11. started array new fresh diags. big-z-diagnostics-20230924-1723.zip

shoulda guessed. here ya go big-z-diagnostics-20230917-1114.zip

ok. new flash built and installed. Disk 10 is rebuilt. what now?

I have not done anything to the flash drive yet. you didnt answer my question if you wanted me to fix that before proceeding, so I assumed no. Ill swap the flash drive after work today, register the new flash drive, after that, rebuild disk 10... (10 tb)... be back in 2 days....

New diags below. big-z-diagnostics-20230913-1834.zip

ok, will be able to try tonight. so busy... thanks again as always. will report back

Long day at work, sorry for the delay, Do you want the new USB drive and rootshare disabled before proceeding to the disk11 issue? And when you say "post new diags after array start", is maintenance mode ok? or reboot without starting array?

rebooted. got a fresh log. big-z-syslog-20230912-0322.zip

woke up the other morning and my docker web guis would not load even though the dockers were running. Rebooted. Disk 11 error - unmountable or no file system found shut down array, started array in maintenance mode disk11 / settings page - no GUI option for xfs repair. (no file system found) terminal - xfs_repair /dev/md11 14 hours later - Sorry could not find valid secondary superblock also... disk 10 is currently emulated, I was about to install the new drive when this all happened. 2 parity drives. not super worried about data on disk 11. just some movies, newest disk. dont know what to do next. would xfs_repair -l do anything? or stop array, un-assign disk 11, check the emulated data? attaching diags thanks in advance~! big-z-diagnostics-20230911-1827.zip

OMG.. THIS THREAD, he narrowed it down and has a quick-fix workaround. tldr; So after an unsafe shutdown, Docker setting "allow host to custom networks" might SAY enabled but isnt. Disable docker, Enable docker.. everything works as it should again. Just worked for me. My home assistant on HOST, can once again see Pi-Hole & diyhue on br0. guac can be accessed from outside network without hard codding the address in swag

I had to edit my xml from ``` <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> ``` to ``` <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> ``` fixed for me

is elevation meters or feet?

i have an idea docker config (your first screenshot) add :/dev/deconz to the end (this sets the mountpoint inside the docker {outside:inside}/ or {host:docker} ) so "/dev/serial/by-id/usb-dresden....97-if00:/dev/deconz" in configuration.yaml change port to serial: port: /dev/deconz

Are you sure? How can i set Eth0 in this screenshot?

try adding :/dev/zigbee to the end of the VALUE /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0:/dev/zigbee

Some outdated info... OP post 1 is missing new webpage https://diyhue.org The Unraid docker "app" support thread link is outdated. Clicking SUPPORT goes to broken forum link https://unraid.net/forums/topic/54183-support-cheesemarathons-repo should be changed to: https://forums.unraid.net/topic/54183-support-cheesemarathons-repo

it would be nice if the plugin could give the device-by-id name of the USB devices to pass thru to dockers eg ls -l /dev/serial/by-id gives usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0 usb-Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_8ad9b0843e67ec119f1fa17089640db2-if00-port0 adding to docker config /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0

for Dockers the best method to passthrough usb to docker is via device by-id open unraid terminal type ls -l /dev/serial/by-id you will get output of your devices with names copy the whole BLUE name of your device go to your docker and edit config add /dev/serial/by-id/ before pasting the name from above. eg /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0 then add :/dev/zigbee to the end - this is the container mount point so you end up with this in your Docker Host config: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0:/dev/zigbee if anywere inside your docker program it asks for the device location you would set it to : /dev/zigbee

the best method to passthrough usb to docker is via device by-id open unraid terminal type ls -l /dev/serial/by-id you will get output of your devices with names copy the whole BLUE name of your device go to your docker and edit config add /dev/serial/by-id/ before pasting the name from above. eg /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0 then add :/dev/zigbee to the end - this is the container mount point so you end up with this in your Docker Host config: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0:/dev/zigbee if anywere inside your docker program it asks for the device location you would set it to : /dev/zigbee

the best method to passthrough usb to docker is via device by-id open unraid terminal type ls -l /dev/serial/by-id you will get output of your devices with names copy the whole BLUE name of your device go to your docker and edit config add /dev/serial/by-id/ before pasting the name from above. eg /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0 then add :/dev/zigbee to the end - this is the container mount point so you end up with this in your Docker Host config: if anywere inside your docker program it asks for the device location you would set it to : /dev/zigbee

the best method to passthrough usb to docker is via device by-id open unraid terminal type ls -l /dev/serial/by-id you will get output of your devices with names copy the whole BLUE name of your device go to your docker and edit config add /dev/serial/by-id/ before pasting the name from above. eg /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0 then add :/dev/zigbee to the end - this is the container mount point so you end up with this in your Docker Host config: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_dcf756dbb712ec118bca20c7bd930c07-if00-port0:/dev/zigbee if anywere inside your docker program it asks for the device location you would set it to : /dev/zigbee