steve1977

Here we go... tower-diagnostics-20220115-0019.zip

I am on Unraid 6.9.2 All dockers show "not available" under docker version. To be precise, all but one docker (one shows up-to-date). I can "force update", but nothing changes. It updates successfully, but still says "not available". I tried "check for updates", but this is also not changing the status. Thoughts?

I got it back. Not sure why and how, but it is back. It may be because I changed the "PCIe ACS override" from downstream to "multi-function", but this could have also been a coincidence...

Ok, this worked. But after reboot, only four of my unassigned devices show up. One got dropped. I refreshed the view, but it is not showing up. Any thoughts? Updated diagnostic log attached. tower-diagnostics-20220114-0030.zip

USB hub

Here we go. The P02509xxxx used to say something else. Plextor_PX-AGxxx is unchanged.

I am facing an issue, which may be related to the UD plugin. See my initial post: What happened is that I replaced my second GPU. Since rebooting, all my UD connected devices have a different name. This leads to my docker and VMs not starting. I could probably change the docker vdisk location to the new name to make it work. However, I am concerned that something else broke and I shouldn't just "fix" it with such work-around. The other thread includes the diagnostic log. Any thought appreciated!

Not sure whether possible to change a header. What happened is that all my UD disks now have a different name. Maybe related to adding a second GPU? Or could be totally unrelated and something else that happened. Any idea why this is the case and what to do to fix this?

Wait... I am not sure whether the NVME dropped or whatever else happened. The issue seems to be though that docker and VM fail to start. No idea why this is the case?

I installed a second GPU. Since doing so, my NVME (mounted in an IDE port) dropped). Any idea based on the diagnostic file what went wrong? tower-diagnostics-20220113-1719.zip

Thanks, I have followed the video and removed the macinabox docker and appdata. How now to install the docker again (step 2)? I already have a Mac VM, which stopped working. So, what do I need to set up to "reactivate" it? Do I need to set a vdisk size? Do I need to change the folders? etc.

Thanks. Can you help with a bit more detail on the steps above? Re "Clean container & data" - Not sure whether I found the right video (first post?) and where this is explained. Does "clean" mean for me to delete the container and also the appdata folder?

How did you swap out opencore? Where is the file located?

Thanks a lot. I was into all of this, but it has been too long, so I forgot. Can you remind me where/how to replace the bootloader file?

Happy new year to all of you! I have pricked my Macinabox VM a few weeks ago and now finding the time trying to fix it. All used to work well. I think I did an attempt for an upgrade and since then pricked and can no longer start. I switched back from GPU to VNC to eliminate one source of failure. Unfortunately, I only get a Mac logo upon start. This stays for over an hour / forever. So, I cannot even start up. Below what I am seeing in the log. Please let me know if anything else I can share for troubleshooting. Thanks! https://pastebin.com/ciUjDKwW

Happy new year! Any new and more thoughts?

root@Tower:~# ls -lah /mnt total 8.0K drwxr-xr-x 21 root root 420 Dec 11 08:02 ./ drwxr-xr-x 20 root root 440 Dec 11 08:02 ../ drwxrwxrwx 4 nobody users 36 Dec 11 08:12 disk1/ drwxrwxrwx 3 nobody users 16 Dec 11 08:12 disk10/ drwxrwxrwx 3 nobody users 20 Dec 11 08:12 disk11/ drwxrwxrwx 3 nobody users 20 Dec 11 08:12 disk12/ drwxrwxrwx 3 nobody users 28 Dec 11 08:12 disk13/ drwxrwxrwx 3 nobody users 20 Dec 11 08:12 disk14/ drwxrwxrwx 4 nobody users 58 Dec 11 08:12 disk15/ drwxrwxrwx 14 nobody users 4.0K Dec 11 08:12 disk2/ drwxrwxrwx 3 nobody users 20 Dec 11 08:12 disk3/ drwxrwxrwx 4 nobody users 43 Dec 11 08:12 disk4/ drwxrwxrwx 7 nobody users 100 Dec 11 08:12 disk5/ drwxrwxrwx 3 nobody users 16 Dec 11 08:12 disk6/ drwxrwxrwx 3 nobody users 20 Dec 11 08:12 disk7/ drwxrwxrwx 3 nobody users 20 Dec 11 08:12 disk8/ drwxrwxrwx 3 nobody users 20 Dec 11 08:12 disk9/ drwxrwxrwt 7 nobody users 140 Dec 11 08:02 disks/ drwxrwxrwt 2 nobody users 40 Dec 11 07:35 remotes/ drwxrwxrwx 3 nobody users 32 Dec 11 08:12 test/ drwxrwxrwx 1 nobody users 36 Dec 11 08:12 user/ root@Tower:~# ls -lah /mnt/test total 0 drwxrwxrwx 3 nobody users 32 Dec 11 08:12 ./ drwxr-xr-x 21 root root 420 Dec 11 08:02 ../ drwxrwxrwx 2 myusername users 37 Dec 11 08:20 Yet\ another\ folder/ root@Tower:~#

Restarting didn't help. Folder is named "Yet another folder". Anything else i can try?

Thanks. Today's update of the plugin fixed it.

I have been successfull using two NVME disks for something around a year. Now they no longer mount. I tried to reboot Unraid, but also no success. Attached the diagnostic log. Any ideas? tower-diagnostics-20211211-0742.zip

Thanks. This one?

I removed the # from the folder names as this seems to have created some confusion? Attached an updated diagnostic log. tower-diagnostics-20211209-1741.zip

Here we go... tower-diagnostics-20211207-2218.zip

I renamed the folder to a totally different name. Unfortunately, the top level folder from the test pool device still does not show up as a user share. Shall I send a new diagnostic or anything else?