Kavian

--- Solved --- Update 1- Disk1 was completely full with 20kbs of free space. I deleted a couple of files and restarted. Now need to figure out why unraid is not writing elsewhere... I have 1tb+ of free space share in other disks. Update 2- I freed 1gb as pointed out earlier and now unraid is balancing itself. Now, disk1 is showing about 250gbs of free space. Anyway thanks.

Hello eveyone, I need some help please. Yesterday I updated from 7.1.1 to 7.1.2 and ever since my dockers don't start. When I go to Docker's tab I get the following message "Docker Service failed to start" Ive tried to downgrade back to 7.1.1 but didn't resouve the issue and now I've returned to 7.1.2 version. This is something that I'm not sure but going to Setting>Docker> The option "Docker vDisk location: /mnt/user/system/docker/docker.img" which I think this is correct. I did a google search and someone said that it could been changed during the update but for my case I think its correct. However I noticed the option "Docker data-root: btfrs vDisk". I have 6 drives, 5 are set to xfs and cache to zfs. I tried to change that option " Docker data-root: " to " Directory" but didn't help... Ive returned to btfrs Vdisk. Appreciate any help. See the log I get May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709588, rd 0, flush 0, corrupt 0, gen 0 May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1784922112, length 4096. May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709589, rd 0, flush 0, corrupt 0, gen 0 May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1784922112, length 4096. May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709590, rd 0, flush 0, corrupt 0, gen 0 May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1785462784, length 4096. May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709591, rd 0, flush 0, corrupt 0, gen 0 May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1784922112, length 4096. May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3486168 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709592, rd 0, flush 0, corrupt 0, gen 0 May 17 14:37:35 Tower kernel: loop: Write error at byte offset 1785479168, length 4096. May 17 14:37:35 Tower kernel: I/O error, dev loop3, sector 3487264 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 14:37:35 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709593, rd 0, flush 0, corrupt 0, gen 0 May 17 14:37:35 Tower kernel: Initializing XFRM netlink socket May 17 14:38:10 Tower rc.docker: Docker daemon... Failed. May 17 14:38:10 Tower rc.docker: Starting network... May 17 14:38:10 Tower rc.docker: Starting containers... May 17 14:38:11 Tower emhttpd: shcmd (130): umount /var/lib/docker May 17 14:38:11 Tower kernel: BTRFS info (device loop3): last unmount of filesystem 9b7a0bbc-ea2a-41d2-ad03-9577969188bc May 17 14:41:14 Tower ool www[19022]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply' May 17 14:41:14 Tower emhttpd: Starting services... May 17 14:41:14 Tower emhttpd: shcmd (135): /etc/rc.d/rc.samba reload May 17 14:41:15 Tower emhttpd: shcmd (139): /etc/rc.d/rc.avahidaemon reload May 17 14:41:15 Tower avahi-daemon[11986]: Got SIGHUP, reloading. May 17 14:41:15 Tower unassigned.devices: Updating share settings... May 17 14:41:15 Tower unassigned.devices: Share settings updated. May 17 14:41:37 Tower ool www[22621]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply' May 17 14:41:37 Tower emhttpd: Starting services... May 17 14:41:37 Tower emhttpd: shcmd (146): /etc/rc.d/rc.samba reload May 17 14:41:37 Tower emhttpd: shcmd (150): /etc/rc.d/rc.avahidaemon reload May 17 14:41:38 Tower avahi-daemon[11986]: Got SIGHUP, reloading. May 17 14:41:38 Tower unassigned.devices: Updating share settings... May 17 14:41:38 Tower unassigned.devices: Share settings updated. May 17 14:41:38 Tower emhttpd: shcmd (160): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 May 17 14:41:38 Tower kernel: loop3: detected capacity change from 0 to 41943040 May 17 14:41:38 Tower kernel: BTRFS: device fsid 9b7a0bbc-ea2a-41d2-ad03-9577969188bc devid 1 transid 1754631 /dev/loop3 (7:3) scanned by mount (22778) May 17 14:41:38 Tower kernel: BTRFS info (device loop3): first mount of filesystem 9b7a0bbc-ea2a-41d2-ad03-9577969188bc May 17 14:41:38 Tower kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm May 17 14:41:38 Tower kernel: BTRFS info (device loop3): using free-space-tree May 17 14:41:38 Tower kernel: BTRFS info (device loop3): bdev /dev/loop3 errs: wr 709737, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:38 Tower root: Resize device id 1 (/dev/loop3) from 20.00GiB to max May 17 14:41:38 Tower emhttpd: shcmd (162): /etc/rc.d/rc.docker start May 17 14:41:38 Tower rc.docker: Starting Docker daemon... May 17 14:41:39 Tower kernel: lo_write_bvec: 144 callbacks suppressed May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096. May 17 14:41:39 Tower kernel: blk_print_req_error: 42 callbacks suppressed May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: btrfs_dev_stat_inc_and_print: 144 callbacks suppressed May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709738, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785479168, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487264 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709739, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785470976, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487248 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709740, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785487360, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487280 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709741, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709742, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785470976, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487248 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709743, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709744, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785479168, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487264 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709745, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785487360, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487280 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709746, rd 0, flush 0, corrupt 0, gen 0 May 17 14:41:39 Tower kernel: loop: Write error at byte offset 1785466880, length 4096. May 17 14:41:39 Tower kernel: I/O error, dev loop3, sector 3487232 op 0x1:(WRITE) flags 0x800 phys_seg 3 prio class 0 May 17 14:41:39 Tower kernel: BTRFS error (device loop3): bdev /dev/loop3 errs: wr 709747, rd 0, flush 0, corrupt 0, gen 0 May 17 14:42:14 Tower rc.docker: Docker daemon... Failed. May 17 14:42:14 Tower rc.docker: Starting network... May 17 14:42:14 Tower rc.docker: Starting containers... May 17 14:42:15 Tower emhttpd: shcmd (164): umount /var/lib/docker May 17 14:42:15 Tower kernel: BTRFS info (device loop3): last unmount of filesystem 9b7a0bbc-ea2a-41d2-ad03-9577969188bc May 17 14:52:18 Tower emhttpd: spinning down /dev/sdd May 17 14:52:18 Tower emhttpd: spinning down /dev/sde May 17 14:52:18 Tower emhttpd: spinning down /dev/sdb May 17 14:52:18 Tower emhttpd: spinning down /dev/sdc May 17 14:56:49 Tower emhttpd: read SMART /dev/sdd Also attached my Diagnostics tower-diagnostics-20250517-1507.zip

That´s a good call... Infact I didnt remember to stop dockers/VM but at the time of testing the server was idle and it didnt take more than a minute to change settings, reproduce the issue and grab the diagnostis. I promptly reverted to the working settings afterwards, so far didnt notice any file corruption of any sort.

First of all, I want to thank you assistance JorgeB Please see attached.... I embeded 2 diagnoses zip file, first file I didnt change anything... I have SMB working and apps are working as Im currently using no Cache as primary storage but using the "Array" for all Shares. The before running the second diagnose, I changed the Share folder "Data" to use cache as primary storage and array as secondary storage. That was the only change I did. I also simulated SMB access through Windows 11 and see below the error I get. If theres anything else you might need please let me know. Diagnose No cache use.zip Diagnose With cache use.zip

Hello everyone, Long story short, when I added a SSD to Unraid and set Share Folder to use Cache as Primary Storage and Secondary Storrage to Array, Docker Apps such as qtorrent fails to start downloading... Also SMB access becomes read only. If i revert qtorrent returns and Windows user is also able to write and modify Share folder. -- I decided to restart my setup from scrach.. The data I have is not that important. I have 6 Drives, 4 SSDs, 1 HDD and NVME, NO parity and NO Cache drive at this time. I configured few Share Folders and set Unraid to use the appropriate Drive to fit my needs, for example, APPDATA to NVME and Download folders to HDD. SMB works fine, all dockers also working just fine. However, I recently added a SSD and set Unraid to use it as Cache, then, I returned to the Share Folder settings and changed the Primary storage Settings to use Cache and Secondary storage to Array. This config SMB breaks as Windows Users can only read folders, also Download app fails at accessing the Share I assume. While writting this post I noticed that Primary Storage has this nottation "(For new Files and Folders)" by that I assume it has to do with permissions maybe? How can I fix my configuration so that Unraid uses Cache drive primiry and on schedule (move) to the appropriate drive, but SMB works and by dockers and read/write to the drive without issues? Thanks Thanks.

Hello everyone, new to the forum but using Unraid sinse 2017. I´m also having the same issue reported previously by @Marbles_00 Here is screen from the log i have ... This is a infinite loop, and i see that the CPU is working on this process over and over... I want to point out that the docker was working just fine before I just automate the update. I am not sure when it stopped working as i didnt use LMS lately, and sometime from the last time i used to date, I haven't been able to access the Web GUI. The log above is pretty much what I get whenever I try to turn the container on, even after a server reset. I tried to force update LMS (Im on LogitechMediaServer latest -- brench), remove and reinstall LMS and no luck. I also tried to install the other LMS version (not the "latest" brench) and nothing :(. My network type is set to "host". Also the port 5353 (default) was conflicting with Plex so I changed it to 5354. I tried to change the network type to Bridge, didnt work as well. Doxdump replayed Marble_00 post asking to check the folder permission though i'm not sure how to do it, Im pretty good that following guides, though Im not a linux guy. Any idea how to sort this out? All the best,