DWomack

I looked at the log and saw references to the GPT on the drives needing to be rewritten. Rebooted the machine. I think I formatted again and things are fine. Unbalanced was still not seeing the pool. I killed removed it and reinstalled and now it works fine. I stopped and started the array multiple times but that didn't fix it. Rebooting was the step I was missing.

You can't see me, but I am about bald from pulling my hair out. I have a 7.2 box that has: 1 zfs ssd cache. 1 zfs mirrored pool of two drives. 3 drives that I am trying to put into a RAID1Z pool. What is the procedure to create the pool of the 3 drives? I have gone round and round. Remove and recreate. Rinse and Repeat. My result is always the same. It looks like the pool is created, but the UI says Unmountable: wrong or no file system. ZFS master will let me see the dataset that was created. I have no I idea what is wrong and how to fix it. Help!!!!

After messing around with the clouflared apps from the Unraid app store with no success, I did the following... I installed the Dockge app. Dockge manages docker compose containers. I had used it before on multiple other machines. Easily manages docker compose containers. In this case you copy the cloudflared docker run command into Dockge and it converts it into docker compose and manages it. Cloudflared shows up in Unraid's docker tab as a 3rd party container, but it works. Easy, Peasy! I have 3 Unraid boxes and each of them is using cloudflared.

I have used Macinabox to create Ventura VMs on 3 different UnRaid boxes. Each VM shows the same Mac Serial number. How can they be changed to be unique? I know that involves changing something in the plist for OpenCore, but I don't know where to look. Is there a mechanism to change this?

Are you referring to the app called... Nacho-Rclone-Native-GUI? If not what's the name of the App?

Switched to Virtio(2D) and that seemed to help. I managed toi get Dropbox working via their web interface. The menu dropdown is still funky.

So, I have now cleaned things up and installed Ventura multiple times via Macinabox on three different unraid servers. An old dog can learn new tricks! My issue now is with the Dropbox app, or rather with its menu icon operation. When I click on the menu icon or try to enter my creds at app installation, the content of the window doesn't show up. Impossible to use. The VM is using the QXL version of VNC. Could that be causing what I am seeing? I am not using a passthrough GPU, so I really can setup otherwise. Any help would be appreciated.

I got it working, but I did two things. Don't know which fixed it. First I deleted a file that said delete me v4. Then I deleted the template in VM create. I shoudn't rush through.

So I am running 7.10 RC-1. When trying to use Macinabox, I get an error message about the Profile. How do I get this to work? I believe I have correctly followed the instructions in the message, but I keep getting the same message. Thanks!

When you create a new VM, say with Win11, the template comes up and you fill out your desired setup. ISOs, cores, memory sizes, etc. It would be really great if there was a button that would create a user readable document for that VM. Preferably a timestamped PDF. It would enable you to track the changes you are making to a VM's configuration. I know this could be done with screen captures, but after all it is a computer. You could just save them in the ISOs directory, because it is always going to be there. Thanks for listening.

I found the problem. Posting back here so it might help someone else. The problem was the setup on the Macs. In File Sharing setup there is an Options button that has to be clicked and SMB access specifically turned on for user(s) creds. It must be for Windows users, because Apple depreciated AFP and uses SMB between Macs now. So how did I find it? I asked Copilot how to set the Mac up to do SMB.

ud_diagnostics-20241120-073645.zip Thank you! Dennis

So, I have 3 UnRaid systems running 7.0.0 b4. I am trying to access shares on multiple Macs running Ventura latest. Using the UnRaid UI>Main>SMB Shares>Add Remote Share Select Windows, select server, username, password, domain=WORKGROUP, select share. OK that works. The share shows on UI>Main. I click mount and it won’t mount. Log shows errors. The shares on the Macs are seen by the other Macs. What am I missing? I did try creating remote shares from another UnRaid box and that works fine. They will mount and can be browsed.

Thanks.

So, I have 3 UnRaid systems running 7.0.0 b4. I am trying to access shares on multiple Macs running Ventura latest. Using the UnRaid UI>Main>SMB Shares>Add Remote Share Select Windows, select server, username, password, domain=WORKGROUP, select share. OK that works. The share shows on UI>Main. I click mount and it won’t mount. Log shows errors. The shares on the Macs are seen by the other Macs. What am I missing? I did try creating remote shares from another UnRaid box and that works fine. They will mount and can be browsed.

https://support.apple.com/en-us/102522

@ZanWhat steps did you go through to get the 2018 mac mini to boot USB flash with Unraid? I have a flash that has been updated to 7.0.0 beta2 and it boots via EFI on a couple of other Unraid systems, so I know that works.

@SpaceInvaderOneThank you for posting a new video. In the video you have “installed” UnRaid on a used 2018 Mac Mini. I have purchased one of those. Can you outline what steps you took to accomplish getting the Mac Mini to boot UnRaid from the usb flash? Thanks for your help.

This seems to work, you guys have comments? I made this an UnRaid User Script: #!/bin/bash #description=This script completely removes all references to the BigSur_VM #foregroundOnly=true #arrayStarted=true #name=remove_macinabox_BigSur_VM # Replace "name_of_VM" with the actual name of your VM echo VM_NAME="Macinabox BigSur" VM_NAME="Macinabox BigSur" echo sleep 2 # Undefine the VM (remove it from libvirt) echo virsh undefine --nvram "$VM_NAME" virsh undefine --nvram "$VM_NAME" echo sleep 2 # Delete the VM's XML configuration file # Navigate to the directory where VM XML files are stored # Usually located at /etc/libvirt/qemu/ # Delete the XML file corresponding to your VM # For example: echo ls -la /etc/libvirt/qemu/ ls -la /etc/libvirt/qemu/ echo # echo rm /etc/libvirt/qemu/"$VM_NAME".xml # rm /etc/libvirt/qemu/"$VM_NAME".xml # echo sleep 2 # Restart the libvirt service # This step ensures that the changes take effect # You can restart the entire server or just the libvirt service # # For example: # systemctl restart libvirtd # # Or since this is Slackware: # /etc/rc.d/rc.libvirt restart echo /etc/rc.d/rc.libvirt restart /etc/rc.d/rc.libvirt restart echo sleep 2 # Optionally, you can also delete the VM's disk image # Locate the VM disk image and delete it # For example: # rm /mnt/user/domains/"$VM_NAME"/disk.img echo rm -r /mnt/user/domains/"$VM_NAME" rm -r /mnt/user/domains/"$VM_NAME" echo sleep 2 echo rm -r /mnt/user/isos/BigSur-install.img rm -r /mnt/user/isos/BigSur-install.img echo sleep 2 echo rm /mnt/user/system/custom_ovmf/* rm /mnt/user/system/custom_ovmf/* echo sleep 2 # Notify any relevant services or users about the VM removal # You can customize this part based on your setup # For example, send a notification using Unraid's built-in notification system: # /usr/local/emhttp/webGui/scripts/notify -i normal -s "VM $VM_NAME removed" # Clean up any other associated files or directories as needed echo rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_vmready_notify rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_vmready_notify echo sleep 2 echo rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_helper rm -r /boot/config/plugins/user.scripts/scripts/1_macinabox_helper echo sleep 2 # Done! The VM traces should now be completely removed. # Remember to make this script executable: # chmod +x /path/to/your/script.sh echo Script complete! Is there a way to script stopping and deleting… the macinabox docker the vm the macinabox docker template If I want to start a fresh, I want to just run a script.

Looking for an annotated user script that will remove all of what Macinabox has touched, so a new macinabox can be created. A script would be much better than touch this, and this, delete this, etc. Maybe the script could remove all VMs and the dockers necessary. Sure I can stumble through all the steps, but a script that always works without mistakes would be much better. Thanks to iamtim2 for posting his guide above.

Have you seen EFI-Agent on GitHub? So, what version of macOS do you have running? I am at Big Sur. When I start the VM it runs thru a bunch of code, which are boot messages from OpenCore? Then it is at an OpenCore picker screen and I pick Big Sur and it boots. How do I get it to go straight to Big Sur? I hope SpaceInvader One is progressing along to the new release of Macinabox. Dennis

Thank you for your help on this New Years Day. Your suggestion above does stop it on the Ubuntu box. Likewise sudo service unifi start will start it back up. I am still having issues with adopting. It doesn’t want to adopt. I think the fly in the ointment is the meshing ability. When it is trying to adopt it is trying to get there through an AP that hasn’t been adopted. How in UniFi can you force wired only? No meshing at all. I know meshing can provide some redundancy if wired fails but this ridiculous. Dennis

I am completely new to running UniFi on Docker, and Docker in Unraid, hence the questions. Do I have to install the Mondo container or is it included in UniFi.Unraid.Reborn? I have run the Cloud Key, and a RaspberryPi as controllers in the past. Currently it is running on a Ubuntu 22.04 box. Short of just shutting down the Ubuntu box, what do I enter at the command line to shut down the running controller?

The older one is an older version back, does that make any difference? When I apt update it complains about the mongo repo. That’s part of the reason for going to yours.

I have a prior version of the UniFi Controller running on a Ubuntu 22.04 box. It is not on docker. I have installed this docker on UnRaid and it runs. I have only two APs running in this home environment. I want to migrate the APs to this new docker based controller. I have tried to move them one at a time. I tell the prior to forget an AP and it does. The new docker controller sees the AP that was forgotten. I tell it to adopt it, but it never does. Adopting…… I tell the prior to adopt it and it does. What am I doing wrong? I even tried hardware reset on the AP but it won’t adopt on the new, but will on the old. Firmware on the AP is the latest. I am stumped. Thanks Dennis