jjooee

Did you ever figure out how to get this working? Trying to do the same setup for a lab setup and coming across the same issue.

I used to have everything working perfect with this but an update must have broke things. When using netboot the config seems to be automatically launching the menu from https://boot.netboot.xyz/2.0.69/menu.ipxe rather than using my locally hosted menu. Before the menu loads I can also see "Attempting to retrieve latest upstream version number... https://boot.netboot.xyz/version.ipxe..." Any changes I make to the menu files via the web interface do not apply as it seems the configuration is bypassing any of these settings. This is driving me crazy as this was working and now I'm not able to use any of my custom configs. Is anyone else experiencing this issue and know what to do?

The issue was the Docker Folders plugin. After uninstalling the plugin all buttons under Docker and VM worked properly.

I upgraded to 6.12.0-rc6 and everything is working fine except one odd GUI issue. Docker - When clicking on a container to start it, pressing the start button does nothing. I can click the Logs, Edit, Remove, Project Page, Support, More Info and Donate buttons. For a container that is already running I cannot click Stop, Pause, or Restart. WebUI and Console work too. VMs - When clicking Start on a vm, nothing happens. I can click Start with console(VNC) and it does start the VM and the console window comes up. Edit, Remove VM, and Remove VM & Disks all work. For a running VM, I am unable to click Start, Pause, Restart, Hibernate or Force Stop. VM Console(VNC) does work. Any ideas? I've tried this from another computer that has never accessed the Unraid GUI before. Thanks!

This is a similar use case as to why I would LOVE multi array. I've maxed out my internal 3.5" storage and want to expand to some JBOD solution via SAS. With my setup I would prefer to keep the 8 current 3.5" disks in my main chassis, two being parity and dedicate this storage to my personal/critical data... Then I would want to create a second array with a single (or dual) parity for disks in the DAS/JBOD that would be less critical data. My concern with doing this on a single array is if the JBOD either disconnects or has a power issue it could take my whole array down or throw it out of parity. It would also be nice to expand Unraid past 30 disks by creating multiple arrays. This would be ideal for stacking JBOD enclosures and keeping everything under Unraid. There seems to be a lot of confusion with newer Unraid users in how you can manage cache pools and individual user share settings to tweak where you want your data to be stored in a typical array+cache pool setup. I agree a lot of people's problems could be solved using these settings, but there are definitely some great use cases for multi-arrays.

By this you mean before removing the disk, start in maint. mode and go to the disk and run the XFS repair?

These are the results I get when running -vL against the disk. The disk status is now showing "Unmountable: wrong or no file system"

Diagnostics attached titan-diagnostics-20220909-1303.zip

@JorgeB Here are the attributes for the disk if it helps

After running the check filesystem with -nv I got the attached results. When running the check again with no options I get the following: Considering the disk is showing unmountable, I believe my only option is to run the check with the -vL flag, correct? Thanks again for the help! xfsrepair-nv.txt

Hello - I noticed a few days ago that one of the data disks in my array was forced offline I believe due to too many UDMA CRC error's. I replaced the cables going to that drive as a precaution. I followed the instructions noted here to rebuild the drive onto itself as it appeared the disk was fine just out of sync with the array. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself I did the rebuild process in maintenance mode and it completed successfully. I then stopped the array and started it again in normal mode. After the array started successfully I'm seeing the rebuilt disk show "Unmountable: No file system" Under these circumstances I should I choose to allow the disk to format or not? I just want to make double sure I'm not going to mess up the data on that disk or array since I thought it already rebuilt the disk from parity by following the steps above. Thank you for the help!