steve1977

Same issue for me. User scripts didn't install when installing macinabox.

I was lucky not to update the docker. However, I am worried that I will forget one day and update the docker by accident. Would I be safe by changing the repo to linuxserver/musicbrainz:v-2019-08-08-ls6 pro-actively and apply an update. Nothing would change?

Amazing news!!! I am sure this will be one of the most watched videos. So many of us are waiting for it. I currently run a Catalina VM created via the "old" macinabox docker. Is it possible to install the new one and then update to Big Sur? Or do I need to create a new VM from scratch?

Is it possible to mount network disks (connected to my wifi router)? And then could I even include these into an array (without parity drive as this would obviously fail due to network speed).

I don’t think V4 is yet merged?

Great, thanks! Can you let us know in this thread when this happens. I am using the preview tag and would be good once I can drop it from the docker config.

Thanks for your help! I am on X299 platform (Asus X299-A). Yes, XML has been updated for my MacOS. My Windows XML is un-edited (and works). Drivers all up to date. Header is removed. I am thinking to bind my GPU in the vfio-pci settings. Worried it may break Unraid? It used to work, but seems it is recently broken. Not clear though what's different now. Maybe recent Unraid update or MacOS update?

Another thing to watch out with Orico enclosures. The 8-bay ones don't seem to support 18TB disks. No idea why and whether there will be some FW update to solve it.

I am very happy with my Orico enclosures. I have a 5-bay and a 8-bay that work really well together with Unraid. Gives me flexibility and they are surprisingly fast. I know USB in the array is not recommended, but it works well for my use case. I would have preferred to use two 8-bay Orico enclosures, but unfortunately never got this working due to the device ID issue mentioned above. I even bought a different model of the 8-bay (one being USB-B and the other being USB-C), but this didn't work either. It's really a pity that this doesn't work with Unraid, but seems from the responses in this thread that it is just not possible 😞 Hope someone comes up with a work-around.

I seem to face the same issue. But just with one my VMs. I have a Windows VM (with GPU passthrough), which works very well. I also have a MacOS VM (with a different GPU passthrough), which crashes Unraid upon rebooting from within the VM. I don't fully understand what I need to add where to fix this. Any chance you can help elaborate?

Thanks for your helpful reply. I've been thinking about this. What has been holding me back is a few things: (1) If I were to later move from a 2TB to a 4TB NVME (or even to a smaller one), it may just be easier with a vdisk as I just need to copy the disk over, (2) I alrady have the vdisk and it seems quite painful to transit (though not impossible), (3) I have an Intel 760p, so not even sure it is possible to do, (4) There seems to be two views whether it indeed improves performance. Some say that there is no difference. Any thoughts about my question why there are difference sizes displayed and how to size my vdisk to use the full disk?

A few things I am confused about the disk size of my VM. I have my Windows VM vidisk imag on an NVME disk (2TB), which is mounted as an unassigned device. The disk has a folder with two files inside (vdisk and my GPU rom file). Unraid Main UI: Size 2.05 TB, used 1.29 TB Unraid VM UI: 1 vdisk 1 TB, capacity 1B, allocation 1T Windows VM: Local disk 1.16 TB So, it's a bit unclear how my VM setting of 1T in fact seems to have translated into 1.16 or even 1.29 TB space. I'd now like to expand the VM disk. Should be easy by changing the capacity in the Unraid VM UI from 1T to 2T and then expanding the space in the disk manager. I am a bit worried though to do as this may exceed the maximum capacity (1T translated into 1.29 TB used space). Also, i am a bit worried as the GPU rom file is also taking some space. What's the best way to set the vdisk file at the absolute maximum size available on the NVME disk? Don't want to lose any byte

I moved one of the two enclosure to the USB-C port. Some progress! I got the disks to show up on UD. Not sure whether this means progress or just a short-term luck that will go away again? I can actually access the disks that are formatted in NTFS. However, I cannot access the XFS disks. I changed the UIDs to make sure that this isn't causing my issue, but this didn't solve it. Any hope or is this progress mis-leading?

Thanks! The ID cannot be altered by connecting to a different port (e.g., by connecting to USB-C)? Also, will this limitation remain once Unraid will support two arrays in the future?

Let me bring this thread up again as it is driving me crazy not being able to connect both of my USB enclosures. Is there absolutely no work-around? What could impact the identifier? Connecting to USB vs USB-C? Using some USB hub in between? Any other creatuve idea how I can use two USB enclosures with Unraid? Any magic appreciated!

Did you ever find a solution to connect both at the same time?

I did a few more round of problem solving what is leading to what issue with various disks and enclosure. A few things I found out: 1) None of my multi-bay USB enclosures supports to run RAID. Only the single-bay enclosure supports it. I don't think that this issue is related to UD, but is more likely a broader Unraid issue (or even a hardware limitation?) 2) The UD issue does not occur after starting Unraid and freshly accessing the disks. It occurs once I unplug the USB enclosure and replace the disks within it. For example, I take out a 2TB disk and replace it instead with a 250GB disk. When I do this, the volume info does not get updated (i.e., 250GB is identified as 2TB disk after mounting). Also, the mount point has a different name rather than the actual mount name. Something like "TO_Exter_nal_USB_3.0". When I reboot Unraid, the mount name shows properly and also the volume info is correct. See below screenshot. The 250GB is wrongly identified as 2TB (previous disk had this volume) and you will also see the wrong mountain name. Both will be fixed when I restart Unraid.

An update on my two issues: 1) SMART test - SMART test only works with my one-bay enclosure. It does not work with my two-bay enclosure. This may be because of the enclosure rather than the UD script? 2) Mounting point - when I freshly boot Unraid, all works fine and the USB is well detected. However, when I turn off the USB, switch the disk and turn it back on, it no longer works. It has a proper mounting point at first. Upon changing the disk, the mounting point shows as "TO_Exter_nal_USB_3.0". I believe this can be fixed with XFS formatted disks by changing the UID in the settings. For NFS disks, there is no option to change it, which may be the cause of this issue?

Yes, thanks. All permanently installed / mounted disks work very well. This includes the NVME disks and also disks that are connected directly to the SATA adapters of my mobo. USB works when starting up Unraid. However, if I turn off / detached the USB enclosure and put in another disks, things go crazy... Below copy & paste from the GUI about disks sdx: sdx nal_USB_3.0_[ID-removed]-4 TB-- 1TO_Exter_nal_USB_3.0MOUNT-0 B-- 2disksMOUNT-0 B-- Both cannot be mounted.

Thanks for your note. The NVME devices are working flawless. So are 2 internal disks. The issue is contained to USB devices (and happens after changing the disk within the USB enclosure). I don't think any of my mount points is called "disks". I think that's part of the issue with the plugin in my use case that makes this to display like that. I will post a screenshot later.

I continue to face issues when switching between disks in my USB enclosure (even with turning it off/on, plugging on/off). What solves it is to restart the Unraid server, but this defeats the purpose. Attached log shows some info on some more issues: 1) Two disks (sdv and sdw) are both connected and seem perfect. However, when I try to run a SMART test, it says that the disks are spun down. Also, it gives a different size. Both are connected via one USB enclosure. 2) One disk (sdx) show non-mountable and shows two parities. I don't think the disk is broken and this one actually ran a successful SMART test. Attached a new diagnostic. tower-diagnostics-20201005-0940.zip

Thanks a lot. The update seems to have fixed (part of) my issue. I am not sure though whether it is fully solved? The disk now mounts and shows two partitions (TO_Exter_nal_USB_3.0 and TO_Exter_nal_USB_3.0-part5). However, there seems to be a third partition (disks). Not sure what this partition does and whether it is a bug of UD or part of the disk? Attached diagnostic log. Thanks for your help! tower-diagnostics-20201005-0910.zip

Oh wow, this is amazing!!! Thanks so much for all you are doing. Will this require a fresh install or will you even allow us to update from Catalina?

Thee issue seems more severe and impacting all UD. I can no longer access "/disks" (where all my UD reside). When trying to access the folder, I am getting the following error message: /bin/ls: reading directory '/mnt/disks': Input/output error

Thanks! Ok, I guess this could have been the case. So, the two issues may well be unrelated?