uek2wooF

^p^q

Put back br0, samba is trying to use it May 5 12:51:38 tdm root: /usr/sbin/wsdd2 -d -4 -i br0 May 5 12:51:38 tdm root: Bad interface 'br0' I can't figure out where WSD_OPT is set, but in rc.samba: /usr/sbin/wsdd $WSD_OPT

I have 20 VMs and 20 docker containers. And I plan to run more. I just don't want it to be working too hard I guess.

Awesome. I think I can move off 200 gb to the array and then convert it. Thanks.

Oh it says only for raid pools. So I guess I am out of luck. Maybe I can make a new pool and move everything over.

My existing server is this I had had tons of hardware issues: https://pcpartpicker.com/user/Phah7ahx/saved/GJ3cqs Now I am looking to replace it and I was wondering if someone could take a quick look and see what you think. https://pcpartpicker.com/list/ByMCGL plus 2 of these for the array: https://www.bhphotovideo.com/c/product/1640240-REG/seagate_st8000nm000a_8tb_exos_7e8_7200.html?ap=y&smp=ba_f1_ll&srsltid=AfAwrE698gQRs66VexM-wBx5vQr9RvgnLfXJphoOUQnihWFn1gjtFx1JJ7c Thanks!

I have two 1 TB ssds in a btrfs pool for cache. Both of them are starting to get errors. Can I add 2 more ssds to the pool and then somehow remove the bad ones? Or like one at a time, might be better since I don't have a lot of room for more disks.

shouldn't your guac also be on custdocknet?

Well it has been a while now so I might not remember this perfectly, but: because qemu 5.1.0, which comes with 6.9.2 unraid (which I thought was based on slack 14.2) requires glib 2.48 but slack 14.2 has glib 2.46. So something doesn't add up when I try to rebuild qemu 5.1.0 on slack 14.2 for unraid 6.9.2 since the glib version is too old. None of this matters I guess, I just made a VM which has the qemu emulations I need. It just would be nice to have a short doc on how to compile stuff for unraid.

that question is unrelated to the original question. The original question is basically how to compile stuff for unraid since it does not seem to track the slack version it claims to track.

You added a bunch of emulations, including ppc, but not ppc64? Why not, just to mess with me?

I also had these TCP out of memory errors, turns out there were zillions of processes that looked like "[wget]". Not sure if they were in a docker container or what. Restarting docker did not fix anything though. I killed them off and then everything was fine. I have had these runaway wgets a couple times, not sure what is causing them. I was about to post just that, but then: Haha I just went and looked and guess what, zillions of these: /usr/bin/wget -q -O - -T 20 -U MakeMKV/v1.15.2/linux(x64-release) -o /dev/null http://hkdata.fairuse.org/svq/sdf.dat.gz The weird thing is, I haven't had that MakeMKV container in a while. What could be spawning these??? the parent pid of the wgets is 32120, and look: root 32120 32101 0 Dec18 ? 00:00:00 /usr/bin/python3 -u /sbin/my_init root 32274 32120 0 Dec18 ? 00:00:00 /bin/bash /etc/my_init.d/ripper.sh aha, from docker ps (why so many spaces in there after uptime???): a41e2947de6c rix1337/docker-ripper "/sbin/my_init" 2 years ago Up 45 hours Ripper WTF??? Oh ok: I must have installed this broken Ripper app at some point maybe after I got rid of MakeMKV. I wonder what crap that wget is trying to do. Anyway I will remove this container and hopefully my unraid flakiness goes away.

oh ok well there is a reddit post that says you must format first, going off that. I figured it out and added them. But: The cache is now showing total size. In the spaceinvader video for adding cache disk to a pool it says it defaults to mirror, not JBOD. Why is mine showing total of both?

What were the default FS for array and cache? I am adding disks to both and I can't tell what fs I was using with the array stopped, so I can format the new disks.

Well I was playing with this and got ventura running in qemu in a docker container. On unraid. Not the best thing but at least it will work for what I need I think. https://github.com/sickcodes/Docker-OSX

Is 13 ventura supported yet?

I use the "DockerRegistryDocker" and yes it is running. After "force update" the commands run successfully and it says up-to-date, but then if I check for updates it says "not available" again. I am not sure what is going on behind the scenes so it is hard to troubleshoot this. When you say a template is not needed, are you talking about that registry.xml? Without it I don't get my repo in the private repositories in community apps (6.9.2).

Hmm. It just says version not available in the version column on the docker tab for my qrcode docker.

summed up nicely there

Everything is a big secret on this closed os.

can I pass through a usb disk to a vm (without unraid reboot)? vm reboot is ok

never mind it actually is too big. 5.1 gb oops

I need to burn an iso to dvd. I tried cdrecord from nerdtools but it complains there is not enough room. Something is wrong with it. What else can I use either on unraid or in docker?

never mind I ended up doing this unraid# virsh blockresize FedoraVNC /mnt/user/domains/Fedora/vdisk1.img 60G guest# parted Fix resizepart 3 100% w q guest# pvresize /dev/vda3 guest# lvextend -l +100%FREE /dev/mapper/fedora_localhost--live-root guest# resize2fs /dev/mapper/fedora_localhost--live-root

any updates? need guestfish to increase vm size