bogglor

Members
  • Posts

    4
  • Joined

  • Last visited

bogglor's Achievements

Newbie

Newbie (1/14)

2

Reputation

  1. I can't recall precisely, but I seem to remember in a previous SpaceInvaderOne Mac OS X video, the recommended remote desktop software of choice was NoMachine. I am not sure about anybody else, but SplashTop has been complete trash for me. Connecting from a Win10 client to the Mac OS X guest VM, the display is sluggish and corrupts occasionally, the mouse pointer lags horribly, and I'm unable to even get the correct size running. I have none of these problems with NoMachine. Maybe it's ok with the default 1080p setup but it doesn't suffice for high res. Here's what I did to get a high res desktop going: - Boot VM as normal with an Unraid VNC connection - Go get Clover Configurator, mount the EFI partition - Change display resolution to 2560x1600 in Clover (native res of my monitor) - Shut down VM - Went into the VM BIOS and hit F2 a bunch of times, changed display res to 2560x1600 here - Booted the VM, loaded SplashTop - Tried a bunch of stuff to get SplashTop working properly, including changing the NIC to E1000 in the Unraid XML, no love - Installed NoMachine, configured it and have been using it since I also tried TeamViewer, it was comparable to NoMachine once you enable direct connection mode. It's more 'busy' though; prefer the simplicity of NX. Performance in all 3 seemed to be better with the vmxnet3 driver; have not tried iCloud or any other stuff.
  2. I'm having a lot of problems with the preclear plugin and I can't determine whether it's a bug in the script, a problem with the drives or a problem with the SATA cables (which I have swapped out). These drives completed pre-read and zeroing just fine but they fail on post-read around 68% every single time... when done as part of a regular clear operation. They WILL complete an independent "verify all the disk" pass just fine. The preclear signature is written fine to the disks. Attempting to resume the post-read always results in extremely slow 1MB/s rate at the beginning that slowly ramps up before failing again eventually. This is happening on two WD Red 8 TBs ordered direct from the manufacturer. I'm hesitant to put them in the array if they're really erroring out but I can't tell whether this is the preclear bug from earlier and I should just try a different version of the script or what... Log excerpt: May 28 12:09:51 preclear_disk_R6GZ0XBY_16111: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --load-file /boot/config/plugins/preclear.disk/R6GZ0XBY.resume /dev/sdf May 28 12:09:51 preclear_disk_R6GZ0XBY_16111: Preclear Disk Version: 0.9.6-beta May 28 12:09:51 preclear_disk_R6GZ0XBY_16111: Restoring previous instance of preclear May 28 12:09:51 preclear_disk_R6GZ0XBY_16111: S.M.A.R.T. info type: default May 28 12:09:51 preclear_disk_R6GZ0XBY_16111: S.M.A.R.T. attrs type: default May 28 12:09:54 preclear_disk_R6GZ0XBY_16111: Continuing disk read from byte 5396131479552 May 28 12:09:54 preclear_disk_R6GZ0XBY_16111: Post-Read: verifying the beggining of the disk. May 28 12:09:54 preclear_disk_R6GZ0XBY_16111: Post-Read: dd if=/dev/sdf bs=512 count=4095 skip=1 conv=notrunc iflag=direct 2>/tmp/.preclear/sdf/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdf/cmp_out May 28 12:09:54 preclear_disk_R6GZ0XBY_16111: Post-Read: dd pid [18967] May 28 12:09:54 preclear_disk_R6GZ0XBY_16111: Post-Read: verifying the rest of the disk. May 28 12:09:54 preclear_disk_R6GZ0XBY_16111: Post-Read: dd if=/dev/sdf bs=2097152 skip=5396131479552 count=2605431742464 conv=notrunc iflag=nocache,sync,count_bytes,skip_bytes 2>/tmp/.preclear/sdf/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdf/cmp_out May 28 12:09:54 preclear_disk_R6GZ0XBY_16111: Post-Read: dd pid [18983] May 28 12:10:00 preclear_disk_R6GZ0XBY_16111: Post-Read: dd - read 0 of 8001563222016. May 28 12:10:00 preclear_disk_R6GZ0XBY_16111: Post-Read: dd command failed, exit code [141]. May 28 12:10:00 preclear_disk_R6GZ0XBY_16111: Post-Read: dd output -> May 28 12:10:09 preclear_disk_R6GZ0XBY_20407: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --load-file /boot/config/plugins/preclear.disk/R6GZ0XBY.resume /dev/sdf May 28 12:10:09 preclear_disk_R6GZ0XBY_20407: Preclear Disk Version: 0.9.6-beta May 28 12:10:09 preclear_disk_R6GZ0XBY_20407: Restoring previous instance of preclear May 28 12:10:09 preclear_disk_R6GZ0XBY_20407: S.M.A.R.T. info type: default May 28 12:10:10 preclear_disk_R6GZ0XBY_20407: S.M.A.R.T. attrs type: default May 28 12:10:12 preclear_disk_R6GZ0XBY_20407: Post-Read: verifying the beggining of the disk. May 28 12:10:12 preclear_disk_R6GZ0XBY_20407: Post-Read: dd if=/dev/sdf bs=512 count=4095 skip=1 conv=notrunc iflag=direct 2>/tmp/.preclear/sdf/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdf/cmp_out May 28 12:10:12 preclear_disk_R6GZ0XBY_20407: Post-Read: dd pid [23439] May 28 12:10:12 preclear_disk_R6GZ0XBY_20407: Post-Read: verifying the rest of the disk. May 28 12:10:12 preclear_disk_R6GZ0XBY_20407: Post-Read: dd if=/dev/sdf bs=2097152 skip=2097152 count=8001561124864 conv=notrunc iflag=nocache,sync,count_bytes,skip_bytes 2>/tmp/.preclear/sdf/dd_output | cmp - /dev/zero &>/tmp/.preclear/sdf/cmp_out May 28 12:10:12 preclear_disk_R6GZ0XBY_20407: Post-Read: dd pid [23476] May 28 12:13:03 preclear_disk_R5GKH9UV_12442: Post-Read: dd - read 5392956391424 of 8001563222016. May 28 12:13:03 preclear_disk_R5GKH9UV_12442: Post-Read: dd command failed, exit code [141]. May 28 12:13:03 preclear_disk_R5GKH9UV_12442: Post-Read: dd output -> 526+0 records in
  3. I figured out what the problem was. For anyone else that's having issues getting the USB key set up, make sure that you "View All Devices" and select GUID Partition Map when formatting the stick. This did not come up for me when I first tried to build the install key and due to my Mac ignorance I presumed that everything was A-OK if I didn't see the option display. It's not. It uses MBR if you don't specifically install it which leads to a botched Clover installation. After I did this, I followed the rest of the steps and everything came up A-OK. It's somewhat amazing that this works at all. I'm not passing any hardware through at all though since my 2009-era i7 i920 and Nehalem X58 chipset Unraid host doesn't support VT-D. Somewhat surprisingly, the graphics are not a slideshow, either.
  4. I followed this guide pretty closely, including the video on creating the bootable USB stick from a real Mac. Just trying to figure out where I've gone wrong: When I boot the VM, I am dumped right to a UEFI shell. I definitely did install Clover onto the stick. But I don't see the clover bootloader come up at all in the Unraid VM. I don't even see it come up when I use the USB stick itself. This tells me it's probably not installed correctly or I have set something completely wrong. I have no experience with Hackintosh and this is my first attempt so I'm not even sure where to start troubleshooting. I know that I didn't make the boot stick with the 'macdaddy.io' method - I used a generic guide that I found that basically just had me dl the image, run a couple of commands in terminal, then I got down to business, installed Clover, checked the proper options from the video, etc. I don't know if this would have an impact or not, but I might just start over from scratch... Are there any steps of Spaceinvader's guide that are a) different or b) no longer necessary now that it's been a few months? Some questions: - I didn't see the APFS / HFS options present in Clover. Am I right to assume this is all baked in now? - Am I right to assume that if I plug the USB stick into the Mac and attempt to boot from it, I should see Clover come up and not the regular MacOS Utilities / installer? Thanks!