John_M
Members
-
Joined
-
Last visited
Everything posted by John_M
-
It depends how your current cache disk is formatted and the general health of your server. You won't get any useful answers unless you provide your diagnostics. There's just too much guesswork involved.
-
I haven't done it myself but is this any use to you? https://pimylifeup.com/raspberry-pi-wireguard/
-
I don't know about VMXNET3 - is your Unraid server itself a VM? Regarding the Catalina download,
-
That's not the normal process of adding a new disk to the array. The order of the steps is wrong. You really need to post your diagnostics.
-
If an extended SMART self test takes longer than the configured spin-down delay for the array disk, then the disk spins down and the self test is aborted. This behaviour is different from previous versions, where spin-down was temporarily suspended until after the self-test had completed. The message "SMART self test in progress" appears but the spin-down prevention doesn't operate. pusok-diagnostics-20210120-0317.zip (I know the unassigned Hitachi disk is totally shot!)
-
That's anecdotal. It depends what you do with it. There are real issues with running Big Sur on real Apple hardware that have been confirmed. Some were fixed in the update from 11.0 to 11.1. Others remain and will no doubt be fixed in later updates.
-
This has been mentioned several times already on previous pages. It's clearly a look-up/indexing error causing the wrong macOS product to be selected. An earlier release didn't suffer from this particular issue. If it's any consolation, Big Sur is still very buggy so Catalina might be a better choice for now anyway.
-
If you have problems I suggest you open a thread in the general support area of the board, giving details and including your diagnostics zip file. That will give people something to work with in order to help you. A general moan, like this, serves no useful purpose.
-
My guess is that during the installation is was working as a simple video output device, with no hardware acceleration. Now that you're trying to start the OS for actual use the fact that there's no driver available is causing it to hang.
-
See here for information about Nvidia graphics cards and macOS: https://www.tonymacx86.com/threads/will-my-nvidia-graphics-card-work-with-macos-list-of-desktop-cards-with-native-support.283700/ Edit: Click the "spoiler" button and you'll see that your card isn't supported by Mojave, Catalina or Big Sur.
-
As well as the flashing display in the UD area, a successfully pre-cleared disk no longer shows "pre-cleared" as the FS type (it displays as "-" instead). Other than these minor display issues the plugin seems to be working well at the moment.
-
Even the web browser-based noVNC client supports resolutions higher than 800x600. SpaceInvaderOne recommends Splashtop as a more responsive solution. I haven't used it because it needs you to create an account on a third party server. I have no desire to access my desktops across the Internet. Spreading a desktop across multiple monitors is a different question entirely.
-
There's plenty of third party software that's suitable for viewing a macOS desktop on Windows, as already mentioned. I prefer to use the built-in software if it does what I want though and, since I typically use a MacBook Pro as my daily companion, I use Apple Screen Sharing.
-
No. Just as Windows (well, not the Home edition) comes with an RDP server built in, macOS has Apple Screen Sharing built in. You can view a Windows desktop on another Windows computer using the latter's built in RDP clinet. Similarly you can view a macOS desktop on another Mac. The protocols are not compatible, unfortunately. There is a free Microsoft Remote Desktop client for macOS but no Apple Screen Sharing client for Windows, which is also a shame.
-
That what I do. As you'd expect, it works well, though there's no sound support.
-
Have you made sure the serial number of your VM is not a valid one, as shown in the video? If you mean you don't want to have to press Return at the boot loader screen there's a link on the previous page describing how to do that using the OpenCore Configurator.
-
Maybe not when you're using a virtual Hackintosh but when you're running on bare metal it helps to choose a model that's at least close to your actual hardware. That's the advice I picked up from the TonyMacX86 forum a few years ago, anyway. I simply chose the model I've found to be reliable for a long time but it turned out to be too old for Big Sur. That is to say, it installed OK and ran OK but it didn't recognise the fact that there was an update to 11.1 available. Simply changing the machine type to iMacPro1,1 fixed that.
-
That works a treat. Thanks, David.
-
Does anyone have a recommendation for a good, compatible machine type to choose? I've had good results with "iMac 13,1" in the past but it's too old to run Big Sur officially. Though it works, it won't accept the recent update from macOS 11.0.1 to 11.1.
-
I was having a lot of problems with the newly created VM not appearing on the VMs page of the GUI. I investigated by running tail -f /mnt/user/appdata/macinabox/macinabox/macinabox_Big\ Sur.log in a command window and I saw that the notification from the first user script was popping up before the installer had been completely converted from the .dmg file that's downloaded and the .img file used by Unraid. By ignoring the notification and watching the log to make sure the conversion was complete I then ran the helper script and the new VM appeared as expected.
-
That should be rm -r /mnt/user/appdata/macinabox
-
The error message is, for once, actually quite useful.
-
Tools -> System Log always shows the log from boot time, even if the syslogd has been HUP'd and the syslog is split across multiple files (/var/log/syslog, /var/log/syslog.1, /var/log/syslog.2, etc.) but clicking the Download button downloads a .zip file that contains only the syslog file (the syslog.1, syslog.2, etc. files are missing).
-
When you stop the Docker or VM service nmbd outputs a lot of this to the syslog: Jul 13 12:17:15 Lapulapu nmbd[21118]: Packet send failed to 172.17.255.255(137) ERRNO=Network is unreachable Jul 13 12:17:15 Lapulapu nmbd[21118]: [2020/07/13 12:17:15.221197, 0] ../../source3/nmbd/nmbd_packets.c:1638(retransmit_or_expire_response_records) Jul 13 12:17:15 Lapulapu nmbd[21118]: retransmit_or_expire_response_records: Failed to resend packet id 231 to IP 172.17.255.255 on subnet 172.17.0.1 Jul 13 12:17:15 Lapulapu nmbd[21118]: [2020/07/13 12:17:15.221229, 0] ../../source3/libsmb/nmblib.c:922(send_udp) The network addresses involved are associated with virtual devices, not the LAN. Perhaps it could be made a little quieter?
-
The system/btrfs-usage.txt file contained within the diagnostics zip file only has information about the "cache" pool. Other btrfs pools are omitted.
