Gaertner

Open Terminal --> docker rm -f homeassistant Next, select "Add Container" — use the Home Assistant template.

That wasn't directed at the devs—in case you thought it was. What I meant was: what specific combination of circumstances leads to this error occurring? I just want to understand it so that something like this doesn't happen again. However, I suspect that this error was just a one-off.

I understand that much. Perhaps I didn't express myself clearly. It's just that in version 7.3.0, a new feature was added allowing you to change the number of VFs under "PCI Devices and IOMMU Groups" as well. Now there are two places where I can modify these settings: Settings --> Intel Graphics SR-IOV Do you see what I mean now?

That's quite annoying. I just find it strange that it seems to be a small group that has Docker problems. Many apparently had no problems after the update. If there are problems with Docker, e.g. because of a new version. Then a note should have been given that the containers might have to be recreated after the update to 7.3.0. Then you know that you have a bit of work to do afterwards and can plan accordingly. That's why I always wait a few days until I update so that I don't get into a situation like this. But no one had reported Docker issues. I think that many are coming from 7.3.0 beta and possibly many are still on 7.2.6. I would be interested to know what went wrong.

Why are these settings located under "PCI Devices and IOMMU Groups"? What is the difference? In which scenarios should I modify the settings under "PCI Devices and IOMMU Groups" versus "Intel Graphics SR-IOV"? Or does it make no difference where I make the change?

That’s not necessary, as I know how to get everything up and running again. I just have to manually reinstall all the missing Docker containers using the existing template. I just wanted to mention that the update didn't go smoothly for everyone. I actually waited a few days before updating specifically to avoid any potential bugs. There are other users with the same problems. https://www.reddit.com/r/unRAID/comments/1td5v2i/what_the_heck_happened_after_the_update_to_730/?tl=de Update: I have restored the faulty containers. It wasn't exactly easy; I had to manually delete the broken containers via the console. After restarting Unraid, the other containers suddenly appeared broken—even though they had been fine just moments before. Consequently, I had to restore the remaining containers as well. The result: All Docker containers were broken following the update. May 19 04:41:09 BlackBook rc.docker: Docker daemon... Started. May 19 04:41:09 BlackBook rc.docker: Starting network... May 19 04:41:09 BlackBook kernel: Bridge firewalling registered May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container 5224cf2190caab06dc6c89b2e66e289db9995b98ba06daf622e846b5a2eabefb is unexpectedly nil May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container 945827b57775f5fb7b03bca0d00546c8c5d94c4fb3eb2ace0f3159c9bf821351 is unexpectedly nil May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container b51034e4bcbd22ad313a986ecd87055a1db67fc7cd417bba410defc8cc1ef6db is unexpectedly nil May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container da91db5689e801b033fcf9171ce6e0c09d1cac5e0228b0bcbf47fb55de30edc2 is unexpectedly nil May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container d61bc8c7f993e528bfebb9c238d37defb897c0318eeaabfbd7075a7ef2c9ca62 is unexpectedly nil May 19 04:41:09 BlackBook root: Error response from daemon: RWLayer of container f91cf5921bfc56c3798701c7aab1295853fb56b6431f50d74b8987dc45713d9a is unexpectedly nil May 19 04:41:10 BlackBook root: Error response from daemon: RWLayer of container 232b4976213788c52660080005e46c073298bd524db1f396dc638671b122bc6b is unexpectedly nil May 19 04:41:10 BlackBook root: Error response from daemon: RWLayer of container 6837b27979037b099ae7830063657f957501111c95b4fdd05af40d920e78a57c is unexpectedly nil May 19 04:41:10 BlackBook rc.docker: Processing... br0 May 19 04:41:10 BlackBook rc.docker: created network macvlan br0 with subnets: 192.168.178.0/24;

I updated from 7.2.5 to 7.3.0, and now almost all my Docker containers are gone. Why would you release a beta version as a stable release? I am absolutely furious.

Servus, I've just updated to Unraid 7.2.0 and noticed that the settings page looks strange. It needs to be tweaked a bit.

If there is a hardware problem then it must be the ASM1166 card. So far the hard drives connected to the card have been affected. It's just strange that I've only had the errors when I moved files with unbalanced. What errors/causes are there why it suddenly assigns the file with the current date during a read process? Problems with special characters? Access rights?

Hello, I've had a problem several times now. When moving several TB of data, the hard drive from which the data is being read suddenly reports CKSUM errors. The files with the CKSUM error then have a current date (changed) on the reading hard drive. Strangely, the file doesn't seem to be damaged. At the moment it was mkv files that were affected. I can open and play the file. I have to move the file so that ZFS reports everything OK again. It seems that something happened when the file was moved, because the file on the target hard drive also has the changed date. So what is the problem? Hardware? Unbalanced? So far, no use case has had CKSUM errors. Always unbalanced. Oh, the last time the CKSUM error occurred again, a parity check was done beforehand, with no errors. I recently replaced some hard drives with 8 TB. I had the same problems with the old hard drives. The hard drives don't report any errors. Do you have an explanation for my problem? Hardware: Supermicro X13SAE-F Intel i7-13700K Kingston 128GB 4800MT/s DDR5 ECC ASM1166 (6xHDD) Mainboard (8xHDD) 3x WDC WD120EDGZ-11 11x WDC WD80EDAZ-11T Log: command:end:error(exit status 23) command:retcode(0):exitcode(23) Command Finished skipping:deletion:(rsync command was flagged):(/mnt/disk7/******/******)