dlanor15

Hi, my starter license expired while I was using the beta. So does that mean I can't update to the RC, so I have to downgrade back to 7.1.4? I though since I was on the beta for 7.2 then I would still be eligible for 7.2 and 7.2.x updates.

You know I actually didn’t consider that. As a non Linux user, I had forgotten that I can do a tmpfs mount. Thank you. I do have some other use cases where up/down hooks would be nice to have, but those are more like one time setups, so I guess I can live with doing that during initial setup or after disaster recovery.

That's a more of a compose spec question that doesn't have anything to do with this particular plugin. But to help you, you have your restart in the wrong spot, it seems to be with the network config, move it to your service, try putting it below your image setting.

I apologize if this has been asked before. I tried to use the search and didn't see anything about it. @primeval_god Have you considered allowing some hook scripts on up or down. For example for my jellyfin container I like to set the transcode directory to a Ramdisk, however after system restart I have to make sure the directory has the right permissions so the container can write to it. I am currently using the user scripts plugin to execute this on array up. But it would be good to just keep everything in one place. I can probably put together a PR for this, but wanted to make sure it was something you would consider before I spent time on it.

Thank you @JorgeB , shortly after I posted I found an old Ubuntu document that said to do that exact same thing. That got it back to be mountable. So I just made sure all my backups were up to date and I’m planning to just rebuild the cache when I return from work this evening.

Oh, I do have a backup of the boot disk from when the cache was in mirror mode, if that helps in restoring the config without having to format the 2nd cache drive.

My system had some bad RAM which I discovered after my docker containers started crashing. After running a ram test it turns out it was only 1 of the ram sticks that was bad, so I removed that bad one and running single channel at the moment (16GB). Ram test on the single slot passed (4 passes). However after booting back up, my system is not mounting my cache pool. It is telling me it is unmountable, I was following these documentations which tells me I need to do a scrub, however the scrub option is disabled because the drive is not mountable. (I think that doc needs updating). That leaves me with the only option of running a check in maintance mode with the --repair option, which has a huge warning not to do so. What can I do to get my system back up and running? I added my diagnostic files. On another note, I tried to see if removing one of the cache drives pool (the one I was seeing errors on in the logs) would allow me to mount at least one of them and copy some of the data that I have yet to backup. That didnt work, and now when I try to add it backup I get the warning that the drive will be formatted. I though unraid would be smart enough to know that the drive was the same as before and put them back in mirror mode without data lost, sigh. I kept the array stopped for now. Hopefully you all can help me get back into mirror mode and be able to run a scrub, or somehow get them back to mountable state. wanda-diagnostics-20250814-0158.zip

If anyone has any other options other than defaulting to ipvlan. The reason why I don't use ipvlan is because all the containers end up just showing up once on my router's device list since they all share the same Mac-address.