killeriq

Will try , if is there any difference... But I thought such simple process just works and it's few mins task , very naive from me ➗ EDIT: Tried even 7.1.4 zip unpacked to USB, then make bootable and not booting again. Even different setting in Bios, no luck. Very strange

Ok, so i should just migrate to the 16GB USB2.0 which was working and don't bother with getting new USB3.0 different brand? As I was like postponing it for some time, but now I need to always erase PREVIOUS folder to have space to do update (its old USB 2.GB :D ) So i said to my self lets update to latest, faster USB3.0 to have peace for next few years ...

Yesterday i've spend like 2h running up and down to get server working with new USB 3.0 from Backup (my current is only 2gb USB2.0) Thought via app Unraid USB Creator 1.0.1 will be few min tasks. Tried: Sandisk Ultra Fit 32GB ADATA UV128 / 32GB Both are not able to boot into unRAID even in Bios they are the 1st ones, but strangely original USB2.0 have 2 boot options Normal and UEFI After reading boards , guides...seems like I'm not the 1st one having this issue People were suggesting running Unraid USB Creator as admin and then also "make_bootable.bat" also as admin, non of it was working :( Changing USB ports 3.0 to 2.0 and such...no luck Then i've found some older Wintec 16GB USB2.0 and was working right away, even with 2 boot options Normal and UEFI Based on the USB 2.0 vs 3.0 notes, does 3.0 even worth to try (different brand) to get faster read/write speeds? As price for 16-32GB is around 4-7e, no real price difference USB2 vs 3 Boot Issues | Unraid DocsBoot Issues | Unraid DocsPreparing the flash device Where they state: Boot failureThe following are some actions that can be taken to try and identify the cause of a boot failure: If possible use a USB 2.0 port in preference to a USB 3.0 one as they seem to be more reliable for booting purposes. In addition USB 2.0 drives also seem less prone to failure than USB 3.0 ones. Many modern motherboards no longer have USB 2.0 ports directly exposed but there is normally a USB 2.0 header on the motherboard that can be used via an appropriate adapter. USB 3.0 does work with no problems for many people After initial load Unraid runs from RAM so gains no significant performance advantage from using USB 3.0. USB 2.0 drives tend to run cooler than USB 3.0 ones which probably explains why they tend to last longer. USB 2.0 drives are typically cheaper than USB 3.0 ones- so why pay more if not needed

Thanks...changed UMASK to 000, was 022 (or similar...). Will see if helps. I picked ALL in here Thanks for quick help!

Hello, I would like to check how to fix following issue: Each time when the Torrent download (Transmission Docker) is finished (new folder created in Shared folder) seems like the folder do NOT have right permission, so if I want to do something via Windows / SMB , I get error that unable to move/create folder. So I need to go into: Tools - New Permissions and select either all or the affected Disk1 or 2 After is fine again. But it just drives me nuts , that i need to do it manually each time. Please is there any way how to fix it? Thanks! Processing: /mnt/disk1 ... chown -R nobody:users ... chmod -R go-rwx,u-x,go+u ... find -type d -exec chmod 777 {} \; ... sync Processing: /mnt/disk2 ... chown -R nobody:users ... chmod -R go-rwx,u-x,go+u ... find -type d -exec chmod 777 {} \;

Ahh got it working, there needs to be the MQTT server which gets the data, i thought it should be the Zigbee Adapter Then also user / pass had to be added. version: 4 homeassistant: enabled: false frontend: enabled: true mqtt: base_topic: zigbee2mqtt server: mqtt://192.168.10.102:1883 user: XXX password: XXX serial: # Location of SLZB-06Mg24 port: tcp://192.168.10.103:6638 baudrate: 115200 adapter: ember # Disable green led? disable_led: false # Set output power to max 20 advanced: transmit_power: 20 network_key: - 119 - 193 - 155 - 54 - 113 - 239 - 241 - 185 - 191 - 133 - 219 - 138 - 118 - 114 - 49 - 29 pan_id: 44735 ext_pan_id: - 0 - 105 - 120 - 49 - 88 - 159 - 172 - 36

I tried 2 options today When I set: 1. - more errors mqtt: base_topic: zigbee2mqtt server: mqtt://192.168.10.103 Starting Zigbee2MQTT without watchdog. [2025-03-31 14:13:53] info: z2m: Logging to console, file (filename: log.log) [2025-03-31 14:13:53] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #ba337bd329aeb4ca17735c0cf09b31293c8cff06) [2025-03-31 14:13:53] info: z2m: Starting zigbee-herdsman (3.2.7) [2025-03-31 14:13:53] info: zh:ember: Using default stack config. [2025-03-31 14:13:53] info: zh:ember: ======== Ember Adapter Starting ======== [2025-03-31 14:13:53] info: zh:ember:ezsp: ======== EZSP starting ======== [2025-03-31 14:13:53] info: zh:ember:uart:ash: ======== ASH Adapter reset ======== [2025-03-31 14:13:53] info: zh:ember:uart:ash: Socket ready [2025-03-31 14:13:53] info: zh:ember:uart:ash: ======== ASH starting ======== [2025-03-31 14:13:55] info: zh:ember:uart:ash: ======== ASH Adapter reset ======== [2025-03-31 14:13:55] info: zh:ember:uart:ash: ======== ASH starting ======== [2025-03-31 14:13:55] info: zh:ember:uart:ash: ======== ASH connected ======== [2025-03-31 14:13:55] info: zh:ember:uart:ash: ======== ASH started ======== [2025-03-31 14:13:55] info: zh:ember:ezsp: ======== EZSP started ======== [2025-03-31 14:13:57] warning: zh:ember:uart:ash: Frame(s) in progress cancelled in [1ac1020b0a527e] [2025-03-31 14:13:57] error: zh:ember:uart:ash: Received unexpected reset from adapter, with reason=RESET_SOFTWARE. [2025-03-31 14:13:57] error: zh:ember:uart:ash: ASH disconnected: ASH_ERROR_NCP_RESET | Adapter status: ASH_NCP_FATAL_ERROR [2025-03-31 14:13:57] error: zh:ember:uart:ash: Error while parsing received frame, status=HOST_FATAL_ERROR. [2025-03-31 14:13:57] error: zh:ember: Adapter fatal error: HOST_FATAL_ERROR [2025-03-31 14:14:10] error: zh:ember:ezsp: ERROR Transaction failure; status=ASH_ERROR_TIMEOUTS. Last Frame: [FRAME: ID=0:"VERSION" Seq=0 Len=0]. [2025-03-31 14:14:10] error: z2m: Error while starting zigbee-herdsman [2025-03-31 14:14:10] error: z2m: Failed to start zigbee-herdsman [2025-03-31 14:14:10] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-03-31 14:14:10] error: z2m: Exiting... [2025-03-31 14:14:10] error: z2m: Error: ASH_ERROR_TIMEOUTS at Ezsp.ezspVersion (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:1426:19) at EmberAdapter.emberVersion (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1392:63) at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:674:9) at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1536:24) at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29) at Zigbee.start (/app/lib/zigbee.ts:69:27) at Controller.start (/app/lib/controller.ts:142:13) at start (/app/index.js:161:5) ** Press ANY KEY to close this window ** 2. Only 1 error mqtt: base_topic: zigbee2mqtt server: mqtt://192.168.10.103:6638 Starting Zigbee2MQTT without watchdog. [2025-03-31 14:17:03] info: z2m: Logging to console, file (filename: log.log) [2025-03-31 14:17:03] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #ba337bd329aeb4ca17735c0cf09b31293c8cff06) [2025-03-31 14:17:03] info: z2m: Starting zigbee-herdsman (3.2.7) [2025-03-31 14:17:03] info: zh:ember: Using default stack config. [2025-03-31 14:17:03] info: zh:ember: ======== Ember Adapter Starting ======== [2025-03-31 14:17:03] info: zh:ember:ezsp: ======== EZSP starting ======== [2025-03-31 14:17:03] info: zh:ember:uart:ash: ======== ASH Adapter reset ======== [2025-03-31 14:17:03] info: zh:ember:uart:ash: Socket ready [2025-03-31 14:17:03] info: zh:ember:uart:ash: ======== ASH starting ======== [2025-03-31 14:17:05] info: zh:ember:uart:ash: ======== ASH connected ======== [2025-03-31 14:17:05] info: zh:ember:uart:ash: ======== ASH started ======== [2025-03-31 14:17:05] info: zh:ember:ezsp: ======== EZSP started ======== [2025-03-31 14:17:05] info: zh:ember: Adapter EZSP protocol version (14) lower than Host. Switched. [2025-03-31 14:17:05] info: zh:ember: Adapter version info: {"ezsp":14,"revision":"8.0.2 [GA]","build":397,"major":8,"minor":0,"patch":2,"special":0,"type":170} [2025-03-31 14:17:05] info: zh:ember: [STACK STATUS] Network up. [2025-03-31 14:17:05] info: zh:ember: [INIT TC] Adapter network matches config. [2025-03-31 14:17:05] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1246ms until next broadcast. [2025-03-31 14:17:05] info: z2m: zigbee-herdsman started (resumed) [2025-03-31 14:17:05] info: z2m: Coordinator firmware version: '{"meta":{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [GA]","special":0,"type":170},"type":"EmberZNet"}' [2025-03-31 14:17:05] info: z2m: Currently 0 devices are joined. [2025-03-31 14:17:05] info: z2m: Connecting to MQTT server at mqtt://192.168.10.103:6638 [2025-03-31 14:17:07] error: z2m: MQTT failed to connect, exiting... (read ECONNRESET) [2025-03-31 14:17:07] info: z2m: Stopping zigbee-herdsman... [2025-03-31 14:17:07] info: zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json' [2025-03-31 14:17:07] info: zh:ember:uart:ash: ASH COUNTERS since last clear: [2025-03-31 14:17:07] info: zh:ember:uart:ash: Total frames: RX=47, TX=92 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: DATA frames : RX=46, TX=44 [2025-03-31 14:17:07] info: zh:ember:uart:ash: DATA bytes : RX=638, TX=481 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: ACK frames : RX=0, TX=47 [2025-03-31 14:17:07] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: CRC errors : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Comm errors : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Length < minimum: RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Length > maximum: RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Bad controls : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Bad lengths : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Bad ACK numbers : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Out of buffers : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Retry dupes : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: Out of sequence : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: ACK timeouts : RX=0 [2025-03-31 14:17:07] info: zh:ember:uart:ash: ======== ASH stopped ======== [2025-03-31 14:17:07] info: zh:ember:ezsp: ======== EZSP stopped ======== [2025-03-31 14:17:07] info: zh:ember: ======== Ember Adapter Stopped ======== [2025-03-31 14:17:07] info: z2m: Stopped zigbee-herdsman ** Press ANY KEY to close this window ** configuration.yaml version: 4 homeassistant: enabled: false frontend: enabled: true mqtt: base_topic: zigbee2mqtt server: mqtt://192.168.10.103:6638 serial: # Location of SLZB-06Mg24 port: tcp://192.168.10.103:6638 baudrate: 115200 adapter: ember # Disable green led? disable_led: false # Set output power to max 20 advanced: transmit_power: 20 network_key: - 119 - 193 - 155 - 54 - 113 - 239 - 241 - 185 - 191 - 133 - 219 - 138 - 118 - 114 - 49 - 29 pan_id: 44735 ext_pan_id: - 0 - 105 - 120 - 49 - 88 - 159 - 172 - 36

yeah, but you have 8GB. Need to do the same to be in "set and forget" mode for some years again

Did this do i need to change something also here? mqtt: base_topic: zigbee2mqtt server: mqtt://localhost version: 4 homeassistant: enabled: false frontend: enabled: true mqtt: base_topic: zigbee2mqtt server: mqtt://localhost serial: # Location of SLZB-06Mg24 port: tcp://192.168.10.103:6638 baudrate: 115200 adapter: ember # Disable green led? disable_led: false # Set output power to max 20 advanced: transmit_power: 20 network_key: - 119 - 193 - 155 - 54 - 113 - 239 - 241 - 185 - 191 - 133 - 219 - 138 - 118 - 114 - 49 - 29 pan_id: 44735 ext_pan_id: - 0 - 105 - 120 - 49 - 88 - 159 - 172 - 36 Getting this in LOG and not starting yet: Using '/app/data' as data directory Starting Zigbee2MQTT without watchdog. [2025-03-28 14:24:45] info: z2m: Logging to console, file (filename: log.log) [2025-03-28 14:24:45] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #ba337bd329aeb4ca17735c0cf09b31293c8cff06) [2025-03-28 14:24:45] info: z2m: Starting zigbee-herdsman (3.2.7) [2025-03-28 14:24:45] info: zh:ember: Using default stack config. [2025-03-28 14:24:45] info: zh:ember: ======== Ember Adapter Starting ======== [2025-03-28 14:24:45] info: zh:ember:ezsp: ======== EZSP starting ======== [2025-03-28 14:24:45] info: zh:ember:uart:ash: ======== ASH Adapter reset ======== [2025-03-28 14:24:45] info: zh:ember:uart:ash: Socket ready [2025-03-28 14:24:45] info: zh:ember:uart:ash: ======== ASH starting ======== [2025-03-28 14:24:47] info: zh:ember:uart:ash: ======== ASH connected ======== [2025-03-28 14:24:47] info: zh:ember:uart:ash: ======== ASH started ======== [2025-03-28 14:24:47] info: zh:ember:ezsp: ======== EZSP started ======== [2025-03-28 14:24:47] info: zh:ember: Adapter EZSP protocol version (14) lower than Host. Switched. [2025-03-28 14:24:47] info: zh:ember: Adapter version info: {"ezsp":14,"revision":"8.0.2 [GA]","build":397,"major":8,"minor":0,"patch":2,"special":0,"type":170} [2025-03-28 14:24:47] info: zh:ember: [STACK STATUS] Network up. [2025-03-28 14:24:48] info: zh:ember: [INIT TC] Adapter network matches config. [2025-03-28 14:24:48] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1246ms until next broadcast. [2025-03-28 14:24:48] info: z2m: zigbee-herdsman started (resumed) [2025-03-28 14:24:48] info: z2m: Coordinator firmware version: '{"meta":{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [GA]","special":0,"type":170},"type":"EmberZNet"}' [2025-03-28 14:24:48] info: z2m: Currently 0 devices are joined. [2025-03-28 14:24:48] info: z2m: Connecting to MQTT server at mqtt://localhost [2025-03-28 14:24:48] error: z2m: MQTT failed to connect, exiting... () [2025-03-28 14:24:48] info: z2m: Stopping zigbee-herdsman... [2025-03-28 14:24:48] info: zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json' [2025-03-28 14:24:48] info: zh:ember:uart:ash: ASH COUNTERS since last clear: [2025-03-28 14:24:48] info: zh:ember:uart:ash: Total frames: RX=47, TX=92 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: DATA frames : RX=46, TX=44 [2025-03-28 14:24:48] info: zh:ember:uart:ash: DATA bytes : RX=638, TX=481 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: ACK frames : RX=0, TX=47 [2025-03-28 14:24:48] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: CRC errors : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Comm errors : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Length < minimum: RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Length > maximum: RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Bad controls : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Bad lengths : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Bad ACK numbers : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Out of buffers : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Retry dupes : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: Out of sequence : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: ACK timeouts : RX=0 [2025-03-28 14:24:48] info: zh:ember:uart:ash: ======== ASH stopped ======== [2025-03-28 14:24:48] info: zh:ember:ezsp: ======== EZSP stopped ======== [2025-03-28 14:24:48] info: zh:ember: ======== Ember Adapter Stopped ======== [2025-03-28 14:24:48] info: z2m: Stopped zigbee-herdsman ** Press ANY KEY to close this window **

I left all as default. sorry for Noob questions, doing it 1st time Ahh so not "inside docker" it self, but in here : \\UNRAIDTOWER\appdata\zigbee2mqtt\configuration.yaml This is the configuration.yaml content version: 4 homeassistant: enabled: false frontend: enabled: true mqtt: base_topic: zigbee2mqtt server: mqtt://localhost advanced: network_key: - 119 - 193 - 155 - 54 - 113 - 239 - 241 - 185 - 191 - 133 - 219 - 138 - 118 - 114 - 49 - 29 pan_id: 44735 ext_pan_id: - 0 - 105 - 120 - 49 - 88 - 159 - 172 - 36 This is what I found in WebUI, where should i put it configuration.yaml? In the top? or doesn't matter? # Pay attention, if you use the Z2M addon for HA, it is better to edit Z2M addon yaml configuration file directly (Select the 3 dot menu in the upper right corner → "Edit in YAML") serial: # Location of SLZB-06Mg24 port: tcp://192.168.10.103:6638 baudrate: 115200 adapter: ember # Disable green led? disable_led: false # Set output power to max 20 advanced: transmit_power: 20

any guide somewhere how / where is the config in docker? thanks

Hi, Seems like i'm having similar issue as above, but i'm using "SLZB-06Mg24" which is an "network server" not a USB device. https://www.zigbee2mqtt.io/guide/adapters/emberznet.html I should add: "adapter: ember" But not sure where / how to enter the config file Starting Zigbee2MQTT without watchdog. [2025-03-27 13:23:41] info: z2m: Logging to console, file (filename: log.log) [2025-03-27 13:23:41] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #ba337bd329aeb4ca17735c0cf09b31293c8cff06) [2025-03-27 13:23:41] info: z2m: Starting zigbee-herdsman (3.2.7) [2025-03-27 13:23:42] error: z2m: Error while starting zigbee-herdsman [2025-03-27 13:23:42] error: z2m: Failed to start zigbee-herdsman [2025-03-27 13:23:42] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-03-27 13:23:42] error: z2m: Exiting... [2025-03-27 13:23:42] error: z2m: Error: USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration. at discoverAdapter (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/adapterDiscovery.ts:523:15) at processTicksAndRejections (node:internal/process/task_queues:105:5) at Function.create (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/adapter.ts:68:33) at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:132:24) at Zigbee.start (/app/lib/zigbee.ts:69:27) at Controller.start (/app/lib/controller.ts:142:13) at start (/app/index.js:161:5) [2025-03-27 13:23:42] error: z2m: If this happens after updating to Zigbee2MQTT 2.0.0, see https://github.com/Koenkk/zigbee2mqtt/discussions/24364 Using '/app/data' as data directory Starting Zigbee2MQTT without watchdog. [2025-03-27 15:59:12] info: z2m: Logging to console, file (filename: log.log) [2025-03-27 15:59:12] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #ba337bd329aeb4ca17735c0cf09b31293c8cff06) [2025-03-27 15:59:12] info: z2m: Starting zigbee-herdsman (3.2.7) [2025-03-27 15:59:13] error: z2m: Error while starting zigbee-herdsman [2025-03-27 15:59:13] error: z2m: Failed to start zigbee-herdsman [2025-03-27 15:59:13] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-03-27 15:59:13] error: z2m: Exiting... [2025-03-27 15:59:13] error: z2m: Error: USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration. at discoverAdapter (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/adapterDiscovery.ts:523:15) at processTicksAndRejections (node:internal/process/task_queues:105:5) at Function.create (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/adapter.ts:68:33) at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:132:24) at Zigbee.start (/app/lib/zigbee.ts:69:27) at Controller.start (/app/lib/controller.ts:142:13) at start (/app/index.js:161:5) [2025-03-27 15:59:13] error: z2m: If this happens after updating to Zigbee2MQTT 2.0.0, see https://github.com/Koenkk/zigbee2mqtt/discussions/24364 ** Press ANY KEY to close this window **

thanks for tip, I've removed "previous" and it went fine. Let's see what next update brings, but I would need to find some 8GB USB drive to be ready for size upgrade. Just need to check about the "license key" details, how to attach it to new drive.

cleaned some logs ~100mb, now i have around 320mb free space only big is "previous" folder

If I recall right I do not use it for anything else then unraid OS, is there some "cleanup" tool or such? As no clue what can be removed