SpaceInvaderOne

Zpools in Unraid can obtain their names in 2 different ways - 1. When you create an independent Zpool in Unraid you name the pool and add the disks. The pool gets its name from what you name it as. 2. However if you format a drive that is part of your array in ZFS format, then that drive, although a part of the array, it is also it's own Zpool. When done this way, the Zpool name is taken from the disk number. So assuming your disk6 is ZFS formatted, it is therefore a Zpool. The pool name being "disk6". A Zpool can contain both regular folders and/or datasets. So the /data in disk6, it could be either a dataset or just a regular folder. But if it is a dataset, then yes, the dataset name would be /data ( a dataset path in ZFS is, poolname/dataset , so your ZFS path would be disk6/data) To see what datasets are in your disk6 (or any other Zpools) install the ZFS master plugin. Then you can see the datasets clearly on the main tab. So if i understand, you say you are using hardlinks. Hard links in ZFS do work but with some limitations. Hard links can only be created within a single dataset but not across datasets. For example, within your disk6/data dataset, hard links can be made between files, functioning just like they would in a traditional filesystem. However hard links cannot span across different datasets in ZFS. This means that you cannot create a hard link between a file in disk6/data and another in disk6/media. This limitation is part of the ZFS design, which emphasizes data integrity and clear boundaries between datasets. Each dataset is basically an isolated filesystem in itself, which has advantages for management, snapshots, and data integrity. But a downside is, it also means that traditional filesystem features like hard links have these constraints. I hope this helps

Hi there. Unfortunately, integrating the ability to install from a usb stick directly into macinabox is not feasible due to the existing mechanisms and how the vm templates are generated. To utilise USB media for installation, a manual edit of a vm template to enable usb passthrough would be necessary. However, a simpler alternative, if you need to install the os from a usb, would be converting your usb media to an image file. This would allow you to utilise an existing image on your usb without requiring direct passthrough of the actual physical device to the VM template.

New Macinabox almost complete. Should be out soon. Hoping for the end of next week or shortly there after Will have a few new features such as Ventura and Sonoma support Also the companion User Scripts will no longer be necessary, the container will do everything itself. Also I plan to add checks so the container can see that your cpu has the correct features to be able to run macOS ie checking for AVX2 etc And a few other new things

Hi. I decided to install Huginn today and was pleasantly surprised to find it readily available in CA in the new apps it had just been added today Thanks so much for this addition I cant wait to start utilizing it. A quick note for anyone installing the Huginn container: you'll need to modify the permissions for the Huginn appdata folder this ensures that Huginn has the necessary permissions (easiest way i find just to use the Unraid file manager plugin to do this) to write in this location for its database etc.

Was working in Unraid 6.10 rc2 but sadely this no longer works in Unraid 6.10 rc3 due to update of either Libvirt to 7.10.0 or QEMU to 6.2.0 This error now happens Also reported here https://www.mail-archive.com/[email protected]/msg1838418.html

This video shows 2 methods to shrink the Unraid array. One method where you remove a drive then rebuild the parity and the second method where the drive is first zeroed then removed preserving the parity.

Ok i think what happened for you is. You uninstalled macinabox and its appdata getting rid of the container and related files. However the vm template was still there. What the helper script does it first checks if a folder called autoinstall in the appdata exists. This contains the newly generated vm xml. If it is present it attempts to define the vm from the template in that folder then deletes the autoinstall folder and exits. So as it said the vm was already present it couldnt define the vm and just exited. It didnt replace your existing template, nether did it run the fixes on it. The reason i think it stops and goes no further on the apple logo is because your existing template was missing this at the bottom Running the helper script a second time would then fix this xml adding it back as the autoinstall folder wouldn't be there now. I hope this makes sense

Do you see the files in your system share?

Catalina xml is now fixed and i have pushed an update. If you update the container and run the Catalina install it should be okay

Um yeah thanks for pointing that out. The problem is, is that Unraid VM manager on an update from making a change in the GUI (not xml edit) will automatically change the nics to be on bus 0x01 hence address to <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> I will take a look at this and perhaps add to the macinabox helper script to fix this.

Finally the new Macinabox is ready. Sorry for the delay work has been a F******G B*****D lately taking all my time. So It also has a new template so please make sure to make sure your template is updated too (but will work with the old template) A few new things added. Now has support for Monterey BigSur Catalina Mojave High Sierra. You will see more options in the new template. Now as well as being able to choose the vdisk size for install you can also choose whether the VM is created with a raw or qcow2 (my favorite!) vdisk The latest version of Open core (OpenCore to 0.7.7.) is in this release. I will try and update the container regularly with new versions as they come. However you will notice a new option in the template where you can choose to install with stock opencore (in the container) or you can use a custom one. You can add this in the folder custom_opencore folder in Macinabox appdata folder. You can download versions to put here from https://github.com/thenickdude/KVM-Opencore/releases Choose the .gz version from here and place in the above folder and set template to custom and it will use that (useful if i am slow in updating !! 🤣) - note if set to custom but Macinabox cant find a custom opencore here to unzip in this folder then it will use the stock one. Also there is another option to delete and replace the existing opencore image that your vm is using. Select this to yes and run the container and it will remove the opencore image from the macos version selected in the template and replace with a fresh one. Stock or custom. By default the NICs for the macOS versions are virtio for Monterey and BigSur. Also vDisk Bus is virtio for these too. HighSierra, Mojave and Catalina use a sata vDisk Bus. They also use e1000-82545em for there NICs. The correct NIC type for the "flavour" of OS you choose will automatically be added. However if for any macOS you want to overide the NIC type and install then you can change the default NIC type in the template from Virtio, Virtio-net, e1000-82545em or vmxnet3 By default the NIC for all vms is on <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> This will make the network adapter seem built in and should help with Apple services. Make sure to delete the macinabox helper script before running new macinabox so the new script is put in as there are some changes in that script too. I should be making some other chnages in the next few weeks soon, but thats all for now

Should be ready I think for wednesday this week

I am in the process of remaking Macinabox & adding some new features and hope to have it finished by next weekend. I am sorry for the lack of updates recently on this container. Thankyou @ghost82 for all you have done in answering questions here and on github and sorry i havent reached out to you before.

reserved

A container to easily download the windows 11 preview iso directly from microsoft and put in the Unraid iso share

I would guess that you removed the disk and when you started the array maybe you had The 'Parity is valid' box checked and then afterwards ran a manual parity check. If so then the parity check will come up with many errors as the orginal parity would be incorrect. I would just stop the parity check. Stop the array then goto tools new configuration. Select preserve all Then click apply This will keep all the disks in the same place. Then go back to the main tab. Double check that the disks there are correct. Then start the array. make sure not to check the 'Parity is valid' box Then a new parity sync should start automatically.

Ah okay zenstates in go isnt necessary for your cpu

What CPU is in your server. If Ryzen do you have the zenstates in your go file?

Its very hard to say without more info. Please post the xml of the vm here. Try a different machine type ie if using i440fx try q35 and vice versa

I thought I had posted here about update a few days ago but it seems i didnt! Well I pushed out a fix for Macinabox over Easter and now it will pull BigSur correctly so if you update the container all should be good. Now both download methods in the docker template will pull Bigsur. Method 1 is quicker as it downloads base image as opposed to method 2 which pulls the InstallAssistant.pkg and extracts that.

here is a guide for setting up Binhex's minecraft container In addition to what I say in this video It actually isn't necessary to use an SRV record to have the connection as minecraft will by default try port 25565 by default. But using an SRV I think is still a good idea especially if you want to use a 'non standard' port for minecraft. Then when using a non standard port you dont have to set the port in the minecraft client. I think it is better not to use the common port for the minecraft server and use an unknown port as this potentially is more secure. Also if you only want people you know to be able to access the server then edit the server properties config file and change whitelist to true. Restart container then Adding and removing players to the accesslist 1. Open webui on the container to see the console. 2. In the console, you will need to type “whitelist add playername”. For example, “whitelist add spaceinvaderone”. 3. After you type this command, you will see a message stating “player added to whitelist”. 4. to remove type “whitelist remove playername”

Here is a guide that i have made showing howto setup Guacamole. Hope its useful.