Azreal

posted this in general support but no real luck so hopefully find some here, added some additional details also :-). Been having some networking issues off / on since before the 7.0 upgrade, but seems to be worse now. Originally i was having issues connecting to unraid connect, the CA wasn't working properly to detect updates. doing the unraid-api restart command seemed to resolve it sometimes or maybe for 5 minutes then back... my containers all still seemed to work fine and i didn't notice any problems with their connectivity. For the last week or so i've been having issues where the containers are unable to connect to internet. For the ones that have ping command available they show a name resolution error. When this came up last week i found some articles pointing to turn off enable host access to custom network, do a force update, try again. Some variation of that did work for me eventually. I believe the last thing i did was to set them to host networking, spin them up, they connected, set them back to my custom network IP and then start and they all just worked. until last night.... I've done similar steps today, turned off the enable host access to custom network and tried again. no change. set to host network for the container and they work fine, when i go back to my custom network and the designated ip they start up fine but don't connect. i've also wiped out and rebuilt the docker image file with just a handful of the applications restored while i try and work through this, no improvement. I've run this ipvlan network for 2-3 years now mostly without issue once i understood how it worked, not sure what's going on now and how to troubleshoot next. I do run an unbound container to provide dns but as part of the troubleshooting here i pointed all the vlans to just use automatic dns from my net provider and bypass my dns. also have tailscale running on this in case that matters - my primary container i access via tailscale is still accessible remotely so it seems fine high level overview of my network is i have containers on different vlan's - most on the same subnet as the host server (.10.x), i have my omada container on the same vlan as the networking gear (.1.x) I do have 2 nics in the server and one goes to each subnet. Containers on both subnets are having problems. but not all of the containers have this problem... If i set omada to use host network, i can get to internet and it all works, as soon as i set back to custom network it doesn't. diagnostics attached. suggestions appreciated. rlyeh-diagnostics-20250204-1631.zip

yes docker pull works, it's the application in that container that isn't getting out to the internet for some reason. if i set the container to host networking it works, when i set it to my customer ipvlan network ip it won't. ip's for each app on ipvlan network has been my setup for couple of years without any headaches or issues like i'm having now.

Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal. To try something more ambitious, you can run an Ubuntu container with: $ docker run -it ubuntu bash Share images, automate workflows, and more with a free Docker ID: https://hub.docker.com/ For more examples and ideas, visit: https://docs.docker.com/get-started/

Been having some networking issues off / on since before the 7.0 upgrade, but seems to be worse now. Originally i was having issues connecting to unraid connect, the CA wasn't working properly to detect updates. doing the unraid-api restart command seemed to resolve it sometimes or maybe for 5 minutes then back... my containers all still seemed to work fine and i didn't notice any problems with their connectivity. For the last week or so i've been having issues where the containers are unable to connect to internet. For the ones that have ping command available they show a name resolution error. When this came up last week i found some articles pointing to turn off enable host access to custom network, do a force update, try again. Some variation of that did work for me eventually. I believe the last thing i did was to set them to host networking, sping them up, they connected, set them back to my custom network IP and then start and they all just worked. until last night.... I've done similar steps today, turned off the enable host access to custom network and tried again. no change. set to host network for the container and they work fine, when i go back to my custom network and the designated ip they start up fine but don't connect. I've run this ipvlan network for 2-3 years now mostly without issue once i understood how ti worked, not sure what's going on now and how to troubleshoot next. I do run an unbound container to provide dns to my vlans but as part of the troubleshooting here i pointed all the vlans to just use automatic dns from my net provider and bypass my dns. diagnostics attached. suggestions appreciated. rlyeh-diagnostics-20250204-0742.zip

yeah was hoping to understand why it's happening when it didn't for months. however, where would i define it? is it under the go2rtc -> streams? or is it in the camera setup under output_args or inputs? i see it in the reference under the detect stream, but that doesn't sound right to me or i don't think it aligns with what i'm doing anyways. these particular camera are just continuous recording, no object detection or other triggered type events for these.

Wierd live view resizing on the fly. running frigate for a few months w/out issues. couple of weeks ago the live view started acting weird. i have 8 tapo c210's. they always showed the view in a nice widescreen looking sizing, now they randomly resize themselves looks like similar to bouncing from 16:9 to 4:3 - but i never changed any settings. they will just adjust on their own with no visible reason why. screenshots included for reference. A and C are the same cams, B and D are the same cams. You can see the size difference on B and D. they'll just resize seemingly randomly. what is going on here? i think i saw in the config i can specify a size but never had to previously.

installing my newly aqcuired pcie card this week, any specific recommendations / example links re: active cooling?

the lasted frigate UI hits this squarely on the head in my opinion. the scrubbing / review interface is really helpful. bars in the timeline to show if there's movement in those frames, more movemen, bigger bars type of thing. you can see all the cameras in sync while you scrub so if you're tracking something cam to cam you can see all of those feeds at the same time. Curious why you care about the filesize though, that's all managed by the system. Depending on the camera settings and what is going on in the images the file size can vary. I have 8 cams of the same model and each one produces vastly different file sizes, some have very active images some are predominantly static 90%+ of the time. but again, except for managing my storage i don't really care too much about the individual files. you can also configure some pretty simple or pretty complex storage rules depending on your needs. my doorbell cam generates the most storage per day so i keep fewer days of that in long term storage. the rest of my cams i have a longer storage period for. there's a lot to love in the latest frigate even if you're not using or not interested in the various AI type stuff they're investing a lot of work in.

didn't think about the heat sink at all and hadn't seen comments for that elsewhere so thank you!

Mini PCIe Coral Device? https://coral.ai/products/pcie-accelerator 2 Questions: 1. Has anyone used this and how did it perform for them? 2. My machine currently is too old to suppport IOMMU so i can't use the USB version, but assume since that's totally different tech stack i shouldn't need to worry about accessing a mini pcie device right? (if you're wondering my very long in the tooth i7-4770k w/16GB DDR3 RAM) runs well enough but obviously hammering the system using CPU and 9 cameras and 20+ other containers going as well. don't mind investing 25$ for the coral if the feedback on the question above is positive

thank you thank you. don't know my way around the file structures so well yet so didn't know where to find it. appreciate your response.

trying to run the reprocess command after i edited the config.yml to exlude some categories and it errors. did this other day no problem but honestly wouldn't be surprised if i'm doing something wrong. I open console from docker page for the container and shouldn't it just be "bitmagnet reprocess" and enter? I receive "bash: bitmagnet: command not found" i get similar if i try from the unraid console with "docker exec -it binhex-bitmagnet bitmagnet reprocess" returns the following: OCI runtime exec failed: exec failed: unable to start container process: exec: "bitmagnet": executable file not found in $PATH: unknown am i doing it wrong or is there something up wtih the latest image?

Solved it myself.... suddenly dawned on me that i setup Tailscale the other week with spaceinvaderone's video, turned it off and it works now. i got what i was after with that, but apparently needs some additional config to play nice with qbittorrent. fun times incoming. if anyone knows right offhand what to change to allow containers to ignore tailscale or select them individually that would be very helpful. for anyone else's benefit - there's a very simple toggle for using or not using tailscale dns, it even says it will impact server and containers, i'm not sure how it get turned on but turning it off and restarting was all i had to do.

logs below. currently it shows me trying 8.8.8.8,1.1.1.1 but my normal setup is my own isntance of unbound running internally. same errors across the board for all dns i've tried. this has been pretty damn stable for me >1 year. i even tried isntalling another instance side by side under another IP and redoing the config from scratch, same issues. docker run -d --name='binhex-qbittorrentvpn' --net='br0' --ip='192.165.10.8' --pids-limit 2048 --privileged=true -e TZ="xxxxx" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Rlyeh" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'TCP_PORT_6881'='6881' -e 'UDP_PORT_6881'='6881' -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8118'='8118' -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxxxxx' -e 'VPN_PASS'='xxxxxx' -e 'VPN_PROV'='pia' -e 'VPN_CLIENT'='wireguard' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'WEBUI_PORT'='8080' -e 'LAN_NETWORK'='192.165.10.0/24' -e 'NAME_SERVERS'='8.8.8.8,1.1.1.1' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='true' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -v '/mnt/user/media/_torrents/':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' 8b828fa260c27e3c01189c8d3ad72f98e49c7e07ff488205255d1b04ce2706c8 The command finished successfully! 2024-09-03 12:16:46.030435 [info] Host is running unRAID 2024-09-03 12:16:46.058144 [info] System information: Linux 8b828fa260c2 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux 2024-09-03 12:16:46.083214 [info] Image tags: INT_RELEASE_TAG=2024073001,IMAGE_RELEASE_TAG=4.6.6-1-01 2024-09-03 12:16:46.124578 [info] PUID defined as '99' 2024-09-03 12:16:46.154655 [info] PGID defined as '100' 2024-09-03 12:16:46.201928 [info] UMASK defined as '000' 2024-09-03 12:16:46.230146 [info] Permissions already set for '/config' 2024-09-03 12:16:46.255551 [info] Deleting files in /tmp (non recursive)... 2024-09-03 12:16:46.283534 [info] VPN_ENABLED defined as 'yes' 2024-09-03 12:16:46.317664 [info] VPN_CLIENT defined as 'wireguard' 2024-09-03 12:16:46.343950 [info] VPN_PROV defined as 'pia' 2024-09-03 12:16:46.376452 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf 2024-09-03 12:16:46.416228 [info] VPN_REMOTE_SERVER defined as 'ca-vancouver.privacy.network' 2024-09-03 12:16:46.450141 [info] VPN_REMOTE_PORT defined as '1337' 2024-09-03 12:16:46.472329 [info] VPN_DEVICE_TYPE defined as 'wg0' 2024-09-03 12:16:46.497840 [info] VPN_REMOTE_PROTOCOL defined as 'udp' 2024-09-03 12:16:46.528381 [info] USERSPACE_WIREGUARD not defined (via -e USERSPACE_WIREGUARD), defaulting to 'no' 2024-09-03 12:16:46.558654 [info] NAME_SERVERS defined as '8.8.8.8,1.1.1.1' 2024-09-03 12:16:46.604374 [debug] iptables default policies available, setting policy to drop... 2024-09-03 12:16:46.658186 [debug] ip6tables default policies available, setting policy to drop... 2024-09-03 12:16:50.719670 [debug] Having issues resolving name 'ca-vancouver.privacy.network', sleeping before retry... 2024-09-03 12:16:59.767254 [debug] Having issues resolving name 'ca-vancouver.privacy.network', sleeping before retry...

been running this container >1 year pretty much no problem. as of last week's appdata backup i noticed on restart it wasn't connecting anymore. I see the following in the debug logs. 2024-09-03 10:47:21.224651 [debug] Having issues resolving name 'ca-vancouver.privacy.network', sleeping before retry. I've tried several endpoints and it just changes the location it says it can't reach. I can hit these end points with the app on my windows 10 vm. i'm using wireguard with port forwarding required. - same type of problem with openvpn too. account is still valid, again i've been able to connect just fine with the application. any suggestions on how to resolve? - i've already removed / reinstalled the container. i setup another instance from scratch just to get same errors. i've changed my name servers from my private ones to public ones. none of these changed things. anyone else having similar issue or have these end points working?

This started sometime within past month using 6.11.11 I made no changes to any settings or config and one day i noticed my docker page doesn't show the assigned ip addresses for many (but not all) of the Arrs, my downloader, jackett. I use custom network with manually assigned IP's on most of my containers and this has never been an issue previously. they still work. I can't use the "webUI" link anymore, otherwise functionality all looks fine. can anyone tell me what happened and is something else likely having issues that i just haven't noticed yet? diag attached if helps rlyeh-diagnostics-20240822-0843.zip

general question around some of the data used by lidarr - walking through my appdata backups and realized my lidarr backup is ~5.5GB which seemed huge to me. digging in i see the MediaCover directory is push 4.5GB. I'm considering excluding this directory from the backups. anyone know if it would cause problems if i did have to restore this backup? is this something it will see is missing and just go redownload or is it not quite that simple?

Thanks i do have that firmware - i ran into issues with that immediately when i set it up and got pointed in the right direction. reading the pooling info now. setup my 240GB as a single cache drive and got everything up and working. setup another cache pool with the 2 1TB drives that started all of this, i've been able to copy large amounts of files over wwithout any errors. left powered on overnight no errors this morning. once my regular scheduled parity check finishes i'm going to try switching back to the drives that started all of this and see how it goes. i'm getting good at tearing it down and spinning it back up at least :).

fwiw i'm thinking of putting cables back since they're newer, then trying to rebuild everything with just a single drive (the newer one) and see what that does or doesn't do... also have a small 240GB drive that's been sitting on shelf for awhile. another option to try with.

Day 3 of errors continuing....diags attached. I have previously erased / formatted the drives and rebuilt docker, restored everything back to where it was - just for the errors to return again overnight. Next step was to wipe the drives / reformat, rinse / repeat same issue while restoring files - have some beefy extra files (~45GB worth) and it never completed restoring it. Ram Memtest for ~1 hour - 2 complete test cycles - no errors. (2*4GB) Base on some other comments i've seen I decided to replace the SATA cables. erase / reformat - in the process of restoring the extra files again and it freezes up. I restart the system and i have CRC errors on one of the drives (had them show up before on the other drive in the pool). but the pool mounts and evertyhing so i'm reinstalling my containers to see what it does or doesn't do. the space used on the pool is in the right range ~137GB out of 1TB. interstingly enough, it's now showing one of these drives as part of the pool and in unassigned devices not mounted. this didn't happen prior to me swapping cables out. one of the ssd's is a little over a year old, the other shows ~2+years powered on. Some of the daily stuff hitting the cache 24*7 would be plex transcode share and my omada SDN working folders. not sure if that would put excessive wear and tear on the drive. I did do SMART tests on both of them when they were working earlier and they both reported no issues. thought or suggestions for next troubleshooting steps? couple of things coming to mind: the cables i used to replace with are "older" but never really used previously. the ones i took out i believe came with my motherboard from a build from last year. (not this pc build - this mb / cpu is ~10yo). i did use the same ports on the board that i've been using for over year now. trying to change just one thing at a time where feasible rlyeh-diagnostics-20240201-1431.zip

woke up to system acting up again. really wanted it to be a one off. didn't get to run memtest due to family obligations etc... but on the to do list. have rebuilt everything like you mentioned above and we'll see how it goes. thanks again. amazing to have accurate help so quickly on a forum. you guys are great.

will do when i get a chance. yeah all my containers came back, several of them live on the cache drive. watching main page shows reads / writes to the pool. will do the memtest this evening once get some time thanks for the assistance, this is my first technical headache in almost a year of 24*7 operation.

not what i was looking to hear after all the other @#$ i been dealing with last two days. seems like stuff is working fine at the moment. I have not done memtest or any other adminstrative type stuff on this because until it wasn't stable all of a sudden, it's been stable :-). ssd pool appears to be working at the moment though......... or is this one bad drive and other picking up the slack? or drives fine and contents are what's hosed? guess i'm trying to understand corrupt...i.e. hardware or conent?

Afrer about 12 hours of troubleshooting my network infra and finally resetting it all to default and reconfiguring Omada I finally got evertying back up and running. Couple hours later containers have died and a few won't start - error 403 coincidently on omada and pihole containers... Logs not full as i saw info suggesting online. Pulled diagnostic and found this in the syslog. This machine has been pretty solid the past 9 months or so, only downtime is for system upgrades. Other issues were self-inflicted learning events. never any hardware. should i treat this as a one off (unless it keeps coming back) or does this warn of other issues to come. I finally just did a reboot and all seems to "ok?" for now. Don't think it matters but i've restarted this machine numerous times in the last 24 hours, always clean and came back no problem. Screwing with network interface a lot. turn off / back on docker dozens of times. nothing that i think "should" cause an issue, but yeah asking here. Drive passes a SMART test. SATA SSD ~2.5 years worth of powered on but little endurance used. ***End of Syslog.txt below*** Jan 30 15:06:53 Rlyeh kernel: BTRFS critical (device sdc1): corrupt leaf: root=7 block=853895479296 slot=2, bad key order, prev (18446744073709551606 128 855491284992) current (18413108958147612918 255 855491321856) Jan 30 15:06:53 Rlyeh kernel: BTRFS info (device sdc1): leaf 853895479296 gen 1042007 total ptrs 192 free space 383 owner 7 Jan 30 15:06:53 Rlyeh kernel: item 0 key (18446744073709551606 128 855491264512) itemoff 16267 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 1 key (18446744073709551606 128 855491284992) itemoff 16231 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 2 key (18413108958147612918 255 855491321856) itemoff 16215 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 3 key (18446744073709551606 128 855491338240) itemoff 16155 itemsize 60 Jan 30 15:06:53 Rlyeh kernel: item 4 key (18446744073709551606 128 855491403776) itemoff 16143 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 5 key (18446744073709551606 128 855491416064) itemoff 16103 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 6 key (18446744073709551606 128 855491457024) itemoff 16071 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 7 key (18446744073709551606 128 855491489792) itemoff 16055 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 8 key (18446744073709551606 128 855491506176) itemoff 16007 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 9 key (18446744073709551606 128 855491559424) itemoff 15991 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 10 key (18446744073709551606 128 855491575808) itemoff 15971 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 11 key (18446744073709551606 128 855491596288) itemoff 15879 itemsize 92 Jan 30 15:06:53 Rlyeh kernel: item 12 key (18446744073709551606 128 855491690496) itemoff 15835 itemsize 44 Jan 30 15:06:53 Rlyeh kernel: item 13 key (18446744073709551606 128 855491739648) itemoff 15779 itemsize 56 Jan 30 15:06:53 Rlyeh kernel: item 14 key (18446744073709551606 128 855491796992) itemoff 15739 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 15 key (18446744073709551606 128 855491837952) itemoff 15707 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 16 key (18446744073709551606 128 855491874816) itemoff 15619 itemsize 88 Jan 30 15:06:53 Rlyeh kernel: item 17 key (18446744073709551606 128 855491964928) itemoff 15559 itemsize 60 Jan 30 15:06:53 Rlyeh kernel: item 18 key (18446744073709551606 128 855492026368) itemoff 15531 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 19 key (18446744073709551606 128 855492055040) itemoff 15475 itemsize 56 Jan 30 15:06:53 Rlyeh kernel: item 20 key (18446744073709551606 128 855492116480) itemoff 15463 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 21 key (18446744073709551606 128 855492136960) itemoff 15439 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 22 key (18446744073709551606 128 855492165632) itemoff 15423 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 23 key (18446744073709551606 128 855492182016) itemoff 15391 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 24 key (18446744073709551606 128 855492218880) itemoff 15363 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 25 key (18446744073709551606 128 855492247552) itemoff 15339 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 26 key (18446744073709551606 128 855492272128) itemoff 15279 itemsize 60 Jan 30 15:06:53 Rlyeh kernel: item 27 key (18446744073709551606 128 855492333568) itemoff 15251 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 28 key (18446744073709551606 128 855492362240) itemoff 15199 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 29 key (18446744073709551606 128 855492415488) itemoff 15123 itemsize 76 Jan 30 15:06:53 Rlyeh kernel: item 30 key (18446744073709551606 128 855492493312) itemoff 15099 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 31 key (18446744073709551606 128 855492526080) itemoff 15083 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 32 key (18446744073709551606 128 855492546560) itemoff 15039 itemsize 44 Jan 30 15:06:53 Rlyeh kernel: item 33 key (18446744073709551606 128 855492595712) itemoff 15011 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 34 key (18446744073709551606 128 855492624384) itemoff 14983 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 35 key (18446744073709551606 128 855492661248) itemoff 14943 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 36 key (18446744073709551606 128 855492702208) itemoff 14867 itemsize 76 Jan 30 15:06:53 Rlyeh kernel: item 37 key (18446744073709551606 128 855492780032) itemoff 14847 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 38 key (18446744073709551606 128 855492812800) itemoff 14807 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 39 key (18446744073709551606 128 855492861952) itemoff 14759 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 40 key (18446744073709551606 128 855492911104) itemoff 14739 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 41 key (18446744073709551606 128 855492935680) itemoff 14699 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 42 key (18446744073709551606 128 855492976640) itemoff 14687 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 43 key (18446744073709551606 128 855492988928) itemoff 14659 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 44 key (18446744073709551606 128 855493021696) itemoff 14647 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 45 key (18446744073709551606 128 855493033984) itemoff 14611 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 46 key (18446744073709551606 128 855493070848) itemoff 14563 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 47 key (18446744073709551606 128 855493120000) itemoff 14531 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 48 key (18446744073709551606 128 855493156864) itemoff 14491 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 49 key (18446744073709551606 128 855493197824) itemoff 14439 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 50 key (18446744073709551606 128 855493255168) itemoff 14295 itemsize 144 Jan 30 15:06:53 Rlyeh kernel: item 51 key (18446744073709551606 128 855493402624) itemoff 14255 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 52 key (18446744073709551606 128 855493447680) itemoff 14243 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 53 key (18446744073709551606 128 855493459968) itemoff 14211 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 54 key (18446744073709551606 128 855493492736) itemoff 14175 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 55 key (18446744073709551606 128 855493529600) itemoff 14163 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 56 key (18446744073709551606 128 855493541888) itemoff 14127 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 57 key (18446744073709551606 128 855493578752) itemoff 14115 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 58 key (18446744073709551606 128 855493591040) itemoff 14099 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 59 key (18446744073709551606 128 855493611520) itemoff 14039 itemsize 60 Jan 30 15:06:53 Rlyeh kernel: item 60 key (18446744073709551606 128 855493677056) itemoff 14007 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 61 key (18446744073709551606 128 855493709824) itemoff 13971 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 62 key (18446744073709551606 128 855493746688) itemoff 13959 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 63 key (18446744073709551606 128 855493779456) itemoff 13923 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 64 key (18446744073709551606 128 855493820416) itemoff 13891 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 65 key (18446744073709551606 128 855493857280) itemoff 13879 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 66 key (18446744073709551606 128 855493869568) itemoff 13851 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 67 key (18446744073709551606 128 855493902336) itemoff 13839 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 68 key (18446744073709551606 128 855493918720) itemoff 13831 itemsize 8 Jan 30 15:06:53 Rlyeh kernel: item 69 key (18446744073709551606 128 855493926912) itemoff 13719 itemsize 112 Jan 30 15:06:53 Rlyeh kernel: item 70 key (18446744073709551606 128 855494041600) itemoff 13691 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 71 key (18446744073709551606 128 855494070272) itemoff 13619 itemsize 72 Jan 30 15:06:53 Rlyeh kernel: item 72 key (18446744073709551606 128 855494144000) itemoff 13599 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 73 key (18446744073709551606 128 855494168576) itemoff 13575 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 74 key (18446744073709551606 128 855494193152) itemoff 13563 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 75 key (18446744073709551606 128 855494217728) itemoff 13515 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 76 key (18446744073709551606 128 855494266880) itemoff 13503 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 77 key (18446744073709551606 128 855494291456) itemoff 12911 itemsize 592 Jan 30 15:06:53 Rlyeh kernel: item 78 key (18446744073709551606 128 855494897664) itemoff 12599 itemsize 312 Jan 30 15:06:53 Rlyeh kernel: item 79 key (18446744073709551606 128 855495221248) itemoff 12491 itemsize 108 Jan 30 15:06:53 Rlyeh kernel: item 80 key (18446744073709551606 128 855495331840) itemoff 12427 itemsize 64 Jan 30 15:06:53 Rlyeh kernel: item 81 key (18446744073709551606 128 855495401472) itemoff 12387 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 82 key (18446744073709551606 128 855495442432) itemoff 12227 itemsize 160 Jan 30 15:06:53 Rlyeh kernel: item 83 key (18446744073709551606 128 855495606272) itemoff 12187 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 84 key (18446744073709551606 128 855495647232) itemoff 12123 itemsize 64 Jan 30 15:06:53 Rlyeh kernel: item 85 key (18446744073709551606 128 855495716864) itemoff 12087 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 86 key (18446744073709551606 128 855495753728) itemoff 12055 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 87 key (18446744073709551606 128 855495786496) itemoff 12015 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 88 key (18446744073709551606 128 855495827456) itemoff 11947 itemsize 68 Jan 30 15:06:53 Rlyeh kernel: item 89 key (18446744073709551606 128 855495897088) itemoff 11883 itemsize 64 Jan 30 15:06:53 Rlyeh kernel: item 90 key (18446744073709551606 128 855495966720) itemoff 11875 itemsize 8 Jan 30 15:06:53 Rlyeh kernel: item 91 key (18446744073709551606 128 855495974912) itemoff 11799 itemsize 76 Jan 30 15:06:53 Rlyeh kernel: item 92 key (18446744073709551606 128 855496052736) itemoff 11775 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 93 key (18446744073709551606 128 855496077312) itemoff 11751 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 94 key (18446744073709551606 128 855496101888) itemoff 11663 itemsize 88 Jan 30 15:06:53 Rlyeh kernel: item 95 key (18446744073709551606 128 855496200192) itemoff 11655 itemsize 8 Jan 30 15:06:53 Rlyeh kernel: item 96 key (18446744073709551606 128 855496208384) itemoff 11539 itemsize 116 Jan 30 15:06:53 Rlyeh kernel: item 97 key (18446744073709551606 128 855496327168) itemoff 11443 itemsize 96 Jan 30 15:06:53 Rlyeh kernel: item 98 key (18446744073709551606 128 855496425472) itemoff 11403 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 99 key (18446744073709551606 128 855496474624) itemoff 11391 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 100 key (18446744073709551606 128 855496486912) itemoff 11363 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 101 key (18446744073709551606 128 855496519680) itemoff 11327 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 102 key (18446744073709551606 128 855496556544) itemoff 11315 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 103 key (18446744073709551606 128 855496593408) itemoff 11143 itemsize 172 Jan 30 15:06:53 Rlyeh kernel: item 104 key (18446744073709551606 128 855496769536) itemoff 11095 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 105 key (18446744073709551606 128 855496818688) itemoff 11071 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 106 key (18446744073709551606 128 855496843264) itemoff 11007 itemsize 64 Jan 30 15:06:53 Rlyeh kernel: item 107 key (18446744073709551606 128 855496908800) itemoff 10991 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 108 key (18446744073709551606 128 855496925184) itemoff 10843 itemsize 148 Jan 30 15:06:53 Rlyeh kernel: item 109 key (18446744073709551606 128 855497076736) itemoff 10827 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 110 key (18446744073709551606 128 855497101312) itemoff 10807 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 111 key (18446744073709551606 128 855497121792) itemoff 10763 itemsize 44 Jan 30 15:06:53 Rlyeh kernel: item 112 key (18446744073709551606 128 855497166848) itemoff 10703 itemsize 60 Jan 30 15:06:53 Rlyeh kernel: item 113 key (18446744073709551606 128 855497232384) itemoff 10575 itemsize 128 Jan 30 15:06:53 Rlyeh kernel: item 114 key (18446744073709551606 128 855497367552) itemoff 10555 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 115 key (18446744073709551606 128 855497392128) itemoff 10503 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 116 key (18446744073709551606 128 855497449472) itemoff 10471 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 117 key (18446744073709551606 128 855497490432) itemoff 10383 itemsize 88 Jan 30 15:06:53 Rlyeh kernel: item 118 key (18446744073709551606 128 855497580544) itemoff 10355 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 119 key (18446744073709551606 128 855497609216) itemoff 10323 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 120 key (18446744073709551606 128 855497641984) itemoff 10275 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 121 key (18446744073709551606 128 855497691136) itemoff 10231 itemsize 44 Jan 30 15:06:53 Rlyeh kernel: item 122 key (18446744073709551606 128 855497736192) itemoff 10187 itemsize 44 Jan 30 15:06:53 Rlyeh kernel: item 123 key (18446744073709551606 128 855497781248) itemoff 10067 itemsize 120 Jan 30 15:06:53 Rlyeh kernel: item 124 key (18446744073709551606 128 855497912320) itemoff 10007 itemsize 60 Jan 30 15:06:53 Rlyeh kernel: item 125 key (18446744073709551606 128 855497973760) itemoff 9987 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 126 key (18446744073709551606 128 855497998336) itemoff 9947 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 127 key (18446744073709551606 128 855498043392) itemoff 9871 itemsize 76 Jan 30 15:06:53 Rlyeh kernel: item 128 key (18446744073709551606 128 855498121216) itemoff 9835 itemsize 36 Jan 30 15:06:53 Rlyeh kernel: item 129 key (18446744073709551606 128 855498166272) itemoff 9811 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 130 key (18446744073709551606 128 855498194944) itemoff 9779 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 131 key (18446744073709551606 128 855498227712) itemoff 9767 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 132 key (18446744073709551606 128 855498244096) itemoff 9695 itemsize 72 Jan 30 15:06:53 Rlyeh kernel: item 133 key (18446744073709551606 128 855498321920) itemoff 9647 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 134 key (18446744073709551606 128 855498371072) itemoff 9635 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 135 key (18446744073709551606 128 855498387456) itemoff 9619 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 136 key (18446744073709551606 128 855498407936) itemoff 9599 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 137 key (18446744073709551606 128 855498440704) itemoff 9583 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 138 key (18446744073709551606 128 855498481664) itemoff 9559 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 139 key (18446744073709551606 128 855498506240) itemoff 9543 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 140 key (18446744073709551606 128 855498522624) itemoff 9515 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 141 key (18446744073709551606 128 855498551296) itemoff 9487 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 142 key (18446744073709551606 128 855498596352) itemoff 9431 itemsize 56 Jan 30 15:06:53 Rlyeh kernel: item 143 key (18446744073709551606 128 855498670080) itemoff 9243 itemsize 188 Jan 30 15:06:53 Rlyeh kernel: item 144 key (18446744073709551606 128 855498862592) itemoff 8971 itemsize 272 Jan 30 15:06:53 Rlyeh kernel: item 145 key (18446744073709551606 128 855499141120) itemoff 8955 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 146 key (18446744073709551606 128 855499165696) itemoff 8935 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 147 key (18446744073709551606 128 855499194368) itemoff 8867 itemsize 68 Jan 30 15:06:53 Rlyeh kernel: item 148 key (18446744073709551606 128 855499264000) itemoff 8651 itemsize 216 Jan 30 15:06:53 Rlyeh kernel: item 149 key (18446744073709551606 128 855499493376) itemoff 8483 itemsize 168 Jan 30 15:06:53 Rlyeh kernel: item 150 key (18446744073709551606 128 855499665408) itemoff 8431 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 151 key (18446744073709551606 128 855499718656) itemoff 8411 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 152 key (18446744073709551606 128 855499739136) itemoff 8399 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 153 key (18446744073709551606 128 855499751424) itemoff 8383 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 154 key (18446744073709551606 128 855499792384) itemoff 8351 itemsize 32 Jan 30 15:06:53 Rlyeh kernel: item 155 key (18446744073709551606 128 855499825152) itemoff 8299 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 156 key (18446744073709551606 128 855499878400) itemoff 8291 itemsize 8 Jan 30 15:06:53 Rlyeh kernel: item 157 key (18446744073709551606 128 855499886592) itemoff 8263 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 158 key (18446744073709551606 128 855499923456) itemoff 8243 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 159 key (18446744073709551606 128 855499948032) itemoff 8227 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 160 key (18446744073709551606 128 855499964416) itemoff 8151 itemsize 76 Jan 30 15:06:53 Rlyeh kernel: item 161 key (18446744073709551606 128 855500046336) itemoff 8127 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 162 key (18446744073709551606 128 855500070912) itemoff 8087 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 163 key (18446744073709551606 128 855500111872) itemoff 8071 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 164 key (18446744073709551606 128 855500128256) itemoff 8043 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 165 key (18446744073709551606 128 855500156928) itemoff 8003 itemsize 40 Jan 30 15:06:53 Rlyeh kernel: item 166 key (18446744073709551606 128 855500197888) itemoff 7927 itemsize 76 Jan 30 15:06:53 Rlyeh kernel: item 167 key (18446744073709551606 128 855500283904) itemoff 7871 itemsize 56 Jan 30 15:06:53 Rlyeh kernel: item 168 key (18446744073709551606 128 855500341248) itemoff 7859 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 169 key (18446744073709551606 128 855500353536) itemoff 7811 itemsize 48 Jan 30 15:06:53 Rlyeh kernel: item 170 key (18446744073709551606 128 855500402688) itemoff 7747 itemsize 64 Jan 30 15:06:53 Rlyeh kernel: item 171 key (18446744073709551606 128 855500468224) itemoff 7735 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 172 key (18446744073709551606 128 855500480512) itemoff 7715 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 173 key (18446744073709551606 128 855500500992) itemoff 7647 itemsize 68 Jan 30 15:06:53 Rlyeh kernel: item 174 key (18446744073709551606 128 855500574720) itemoff 7631 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 175 key (18446744073709551606 128 855500599296) itemoff 7567 itemsize 64 Jan 30 15:06:53 Rlyeh kernel: item 176 key (18446744073709551606 128 855500713984) itemoff 7547 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 177 key (18446744073709551606 128 855500754944) itemoff 7491 itemsize 56 Jan 30 15:06:53 Rlyeh kernel: item 178 key (18446744073709551606 128 855500812288) itemoff 7463 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 179 key (18446744073709551606 128 855500849152) itemoff 7443 itemsize 20 Jan 30 15:06:53 Rlyeh kernel: item 180 key (18446744073709551606 128 855500873728) itemoff 7399 itemsize 44 Jan 30 15:06:53 Rlyeh kernel: item 181 key (18446744073709551606 128 855500926976) itemoff 7375 itemsize 24 Jan 30 15:06:53 Rlyeh kernel: item 182 key (18446744073709551606 128 855500967936) itemoff 7363 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 183 key (18446744073709551606 128 855500980224) itemoff 7291 itemsize 72 Jan 30 15:06:53 Rlyeh kernel: item 184 key (18446744073709551606 128 855501053952) itemoff 7239 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 185 key (18446744073709551606 128 855501119488) itemoff 7227 itemsize 12 Jan 30 15:06:53 Rlyeh kernel: item 186 key (18446744073709551606 128 855501135872) itemoff 7211 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 187 key (18446744073709551606 128 855501152256) itemoff 7195 itemsize 16 Jan 30 15:06:53 Rlyeh kernel: item 188 key (18446744073709551606 128 855501168640) itemoff 7167 itemsize 28 Jan 30 15:06:53 Rlyeh kernel: item 189 key (18446744073709551606 128 855501213696) itemoff 7115 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 190 key (18446744073709551606 128 855501266944) itemoff 7063 itemsize 52 Jan 30 15:06:53 Rlyeh kernel: item 191 key (18446744073709551606 128 855501320192) itemoff 5183 itemsize 1880 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device sdc1): block=853895479296 write time tree block corruption detected Jan 30 15:06:53 Rlyeh kernel: BTRFS: error (device sdc1) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Jan 30 15:06:53 Rlyeh kernel: BTRFS info (device sdc1: state E): forced readonly Jan 30 15:06:53 Rlyeh kernel: BTRFS warning (device sdc1: state E): Skipping commit of aborted transaction. Jan 30 15:06:53 Rlyeh kernel: BTRFS: error (device sdc1: state EA) in cleanup_transaction:1992: errno=-5 IO failure Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 20758528, length 4096. Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 40544 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 1139044352, length 4096. Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 2224696 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7335411712, length 4096. Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7066976256, length 4096. Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7335280640, length 4096. Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7066845184, length 4096. Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7335100416, length 4096. Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7066664960, length 4096. Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7334969344, length 4096. Jan 30 15:06:53 Rlyeh kernel: loop: Write error at byte offset 7066533888, length 4096. Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 14326976 op 0x1:(WRITE) flags 0x1800 phys_seg 40 prio class 2 Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 13802688 op 0x1:(WRITE) flags 0x1800 phys_seg 40 prio class 2 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 14326720 op 0x1:(WRITE) flags 0x1800 phys_seg 24 prio class 2 Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 13802432 op 0x1:(WRITE) flags 0x1800 phys_seg 24 prio class 2 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 14326368 op 0x1:(WRITE) flags 0x1800 phys_seg 40 prio class 2 Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 13802080 op 0x1:(WRITE) flags 0x1800 phys_seg 40 prio class 2 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 14326112 op 0x1:(WRITE) flags 0x1800 phys_seg 16 prio class 2 Jan 30 15:06:53 Rlyeh kernel: I/O error, dev loop2, sector 13801824 op 0x1:(WRITE) flags 0x1800 phys_seg 16 prio class 2 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:06:53 Rlyeh kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Jan 30 15:06:53 Rlyeh kernel: BTRFS info (device loop2: state E): forced readonly Jan 30 15:06:53 Rlyeh kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. Jan 30 15:06:53 Rlyeh kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure Jan 30 15:06:55 Rlyeh kernel: veth4c50b97: renamed from eth0 Jan 30 15:06:55 Rlyeh kernel: veth96888d8: renamed from eth0 Jan 30 15:06:55 Rlyeh kernel: vethb3198ca: renamed from eth0 Jan 30 15:07:14 Rlyeh kernel: lo_write_bvec: 9 callbacks suppressed Jan 30 15:07:14 Rlyeh kernel: loop: Write error at byte offset 20758528, length 4096. Jan 30 15:07:14 Rlyeh kernel: blk_print_req_error: 9 callbacks suppressed Jan 30 15:07:14 Rlyeh kernel: I/O error, dev loop2, sector 40544 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jan 30 15:07:14 Rlyeh kernel: btrfs_dev_stat_inc_and_print: 9 callbacks suppressed Jan 30 15:07:14 Rlyeh kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 20, rd 0, flush 0, corrupt 0, gen 0 Jan 30 15:07:19 Rlyeh kernel: loop: Write error at byte offset 1138503680, length 4096. Jan 30 15:07:19 Rlyeh kernel: I/O error, dev loop2, sector 2223640 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jan 30 15:07:19 Rlyeh kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 21, rd 0, flush 0, corrupt 0, gen 0 rlyeh-diagnostics-20240130-1510.zip

very long shot here, came across this troubleshooting my own inability to map network drive or access shares on my unraid from a particular windows 10 client i have. i have 2 win 10 machines, my main one is working just fine according to the configuration i have setup. my other machine is not and it's been driving me crazy - this box is what unraid has replaced in many ways, plex server - downloader machine - omada controller etc... - and i haven't used it for much of anything since getting comfortable with unraid and getting it stable. today decided to try and start cleaning up the music library and trying out musicbrainz picard so i need to grab a subset of media off the unraid share and wasn't able to. i finally (couple hours effort and lots of tweaks and adjustments per the various suggestions in this threa and others) happened to notice the Private internet access icon in the systray - despite setting it to allow lan traffic, once i turned this off everything appears and shows up properly - prior to that i could ping the server but i couldn't see ANY shares. private, public, etc... turned off PIA and now we're good to go. incredibly frustrating oversight on my end. hopefully you have something similar and same oversight? if not, sorry and good luck! i understand your comment about not changing anything and it was working but now isn't just throwing it otu there just in case.