RimuJim

thanks @James Miller I can confirm that the limine BOOTX64.EFI file and the above config settings fixed this issue for my 2012 Mac mini. I did have the issue that I could not start the array, as Unraid said I was missing a cache pool. I did not have a pool before, but there was an empty reference to one. I deleted it and then all was well. Does anyone know if this workaround will likely break in a future update? Or is it something that might get added to the official release?

@James Miller did you just use the config settings posted above? I have a mini with this issue too.

@JorgeB Do you have any information on how to switch between Legacy boot and EFI boot?

Thanks for giving it a go!

Does anyone know if 7.2.1 fixes this issue?

Thanks. Has this been added a an offical bug report?

I have down-graded to 7.1.3 by copying the bz.* files back to the usb from my back up and everything works as it did before. This is 2012 Mac mini. Does this signal a kernel issue? This is what ChatGPT thinks:It’s almost certainly due to a USB/xHCI initialization regression introduced in Linux 6.10.x — not Unraid-specific code. When enough users report it (and they will — Mac minis, older NUCs, and small-form Intel boards are common Unraid hosts), the Unraid team typically: Either backports the older USB driver behavior, or Adds a boot-time workaround (kernel parameter, delay, or firmware quirk). So once the kernel maintainers fix it upstream, Unraid will inherit the fix.

ok I did all that and still get the same error...

Thanks for that. I will download the current release and copy over the bz* file and then should I run the make bootable script?

I just ran the 7.2 update on this machine and everything went file until the reboot step, then I got this. Does this mean the flash drive is buggered? I have backup of the flash drive made just before I did the upgrade, but I would like to move to 7.2 if possible. thanks!

My Uraid system built in a small form factor case using a Silverstone ST75F-P power supply. From what I can tell this silverstone should be modular, but it will not power up unless I have all the cables plugged into it. The case is very small and it is next to impossible to close with the extra cables that I don’t need. In the attached photo it is the two harnesses plugged into the bottom blue sockets that I don’t need. Is there something I’m missing? What can I do?

That worked! Thanks for your help! Can I assign the same IP address to the wifi interface as I use when the machine is wired? I only occasionally need to use this machine via wifi and it would be nice if it booted up to the same ip address no matter witch connection was being used.

thanks for taking a look diagnostics-20251024-2115.zip

I have Ugreen UG-2020204 Ac650 Usb WIFI stick that stays in disk mode when inserted. I got it to work once in the help of chatGPT, but then I did a reboot and its back to CDROM Mode. Is there an easier way to doe this? Apprent I need usb_modeswitch and their used to be a community app that had that, but I can find it... root@server:~# lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade Bus 001 Device 003: ID 0bda:1a2b Realtek Semiconductor Corp. RTL8188GU 802.11n WLAN Adapter (Driver CDROM Mode) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

I’m just starting with unRAID and I had set up a trail machine using a 2012 Mac mini. I am only using the internal 500gb internal ssd just to test the system. Once I got unRAID installed and setup a share, I copied my music collection into to and it has been happily serving music for a week. Until last night. There must have been a brief power cut in the night, and the mini was off when I woke up. I rebooted it and unRAID started up fine, but then I noticed that my music share was gone. I wasn’t sure what to do, but I could see that unRAID said the ssd had only 200 gb free, suggesting that the files were still there. I then created a new music share hoping that the files would reappear there. Instead the folder remained empty, and a lost&found folder appeared. This folder contains a bunch of randomly named folders (with numbers) and these folders contain the missing files. Some of the original organisation is preserved in the folders but some not. My question is: is this expected behaviour? I assume the power cut happened at a time when the system was writing to the disk index and this was corrupted enough that unRAID lost the location of everything. Is there something in the setup that I could have done to prevent this (aside from a UPS). Is that fact that I was using an ssd a factor? Any insight would be greatly appreciated