Jump to content

jowi

Members
  • Content Count

    1107
  • Joined

  • Last visited

Community Reputation

7 Neutral

About jowi

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So, why can i set all kinds of resolutions in my (spaceinvader inspired) Windows 10 VM, but i can only select 1920x1080 in OSX? (even if i set the clover? bios to 2560x1600) What is the trick for adding more resolutions in OSX? I’m using vm’s through chrome remote desktop btw so remote always.
  2. My background user script just got stopped (by unraid i assume) for no apparent reason, did not do it myself, also wasnt an exception in the python code, because that would send me an email and gets logged. Also, in that case only the python script would get killed not the .sh etc. In this case, the whole user script ‘chain’ was gone from process list. Not sure if there is some syslogging that i could attach for more clarity?
  3. I understand there is no way to respond to a sigkill...
  4. Yeah, i've installed python using nerd/devpack. So that is all ok
  5. Looks like aborting a script does not kill everything. I'm using a user script that 'bashes' a shell script, and that shell script in turn runs a python script: #!/bin/bash #backgroundOnly=true #arrayStarted=true bash /boot/custom/kuroautomode.sh (I don't know how to use bash to call python directly? So this is how i do it. bash is needed, the .sh and .py reside on the usb stick in a subfolder under boot folder) When this is started, proceslist will show 4 processes: root 22117 0.0 0.0 104624 26196 ? SL Aug03 0:00 /usr/bin/php /usr/local/emhttp/plugins/user.scripts/startBackground.php /tmp/user.scripts/tmpScripts/kuroAutoMode/script root 22118 0.0 0.0 3840 2916 ? S Aug03 0:00 sh -c /tmp/user.scripts/tmpScripts/kuroAutoMode/script >> /tmp/user.scripts/tmpScripts/kuroAutoMode/log.txt 2>&1 root 22119 0.0 0.0 3840 2808 ? S Aug03 0:00 /bin/bash /tmp/user.scripts/tmpScripts/kuroAutoMode/script root 22120 0.0 0.0 3840 2916 ? S Aug03 0:00 bash /boot/custom/kuroautomode.sh root 22121 0.0 0.0 18716 14564 ? S Aug03 0:02 /usr/bin/python /boot/custom/kuroautomodecmdline.py Now, when i abort the user script from within unraid, proclist still shows: root 22119 0.0 0.0 3840 2808 ? S Aug03 0:00 /bin/bash /tmp/user.scripts/tmpScripts/kuroAutoMode/script root 22120 0.0 0.0 3840 2916 ? S Aug03 0:00 bash /boot/custom/kuroautomode.sh root 22121 0.0 0.0 18716 14564 ? S Aug03 0:02 /usr/bin/python /boot/custom/kuroautomodecmdline.py So it only aborts the script logging, nothing else. Everything else keeps running. If i restart the user.script, i get everything running 2x, 3x, 4x etc. if i don't manually remove it. Am i doing something wrong or is this an issue?
  6. Is this also true for the seek error rate? I got pretty scared adding my new 16TB seagate to my array, preclearing got the read error rate up and up... luckily i got to this post running the smartctl command shows 0 read errors, but the seek error rate still has high, changing numbers?
  7. Another new & exiting issue. If i start vnc i get the message 'Guest has not initialised the display (yet)"... you know what? I quit. It's just not worth the trouble and frustration.
  8. Again, see my comment above. The resolution there does not seem to matter. Only running vnc fullscreen BEFORE you boot osx, prevents messy video. If i set video in uefi bios to 2560x1600 (native res of monitor) osx still starts up in 1920x1080, and ONLY if i run vnc fullscreen. There also is no option to choose any other resolution in osx other then 1920x1080 regardless what resolution i select in uefi.
  9. Het gaat om de geforceerde kromme vertalingen, welk os het ook is. Vertalen moet als doel hebben om eea duidelijker te maken, en dat gebeurt 9 van de 10 keer niet door dingen domweg geforceerd te vertalen. Vertaal manuals en helpfiles, wiki’s... perfect. Maar de software lekker in het engels laten. Tenzij je chinees of koreaans of islamitisch etc leest en schrijft, dan kan ik me het wel voorstellen. Ik zag laatst ergens “De programmatuur is geüpdatet” voorbij komen. Geen grap. Dat is toch achterlijk. Wel jammer dat je aangevallen voelt. Iedereen moet het voor zichzelf bepalen zeg je terecht, maar mijn beslissing om het niet te willen, val je aan. Bijzonder.
  10. I think you mean that once inside the clovis “menu” you need to select restart clovis, THEN hit F2 to get in the actual bios. That is the only way i can get in some bios and get to set a resolution. But... what resolution i set, if i do NOT run clovis/vnc in full screen mode, the video is messed up. So apparently you must go full screen BEFORE you boot osx. Whatever resolution i choose, if i run vnc in a window, video will be messed up. Second, if i select 2560x1600 (the res of my actual monitor) osx starts in 1920x1080 and i can not select any other resolution in osx. There is 1 option and that is 1920x1080... how do i get to use other resolutions?
  11. What is 'it'? When you start the vm's (clover) bios? F2 doesnt do anything. If you hit enter so OSX boots, F2 also does NOT do anything. Please explain clearly what we need to do?
  12. Oh man... tried everything, other network configs, setting datetimes etc etc. My network runs over a vpn, even disconnected that in case apple did not allow being called from a vpn. Nothing helped. And just now i got another final brainfart, what if... my adblocker is messing things up? I’m running pihole (thanks spaceinvader!) as a docker on unraid, and once i disabled that... the installer now can find what it needs and it is installing Catalina now...
  13. Same problem here. No matter what and how often i try, it just can never contact the recovery server. The (macinabox based) vm has an ip address, i can ping outside and in and even browse from it. But it just NEVER gets to connect... really frustrating.
  14. Doesn’t work for me as well. High Sierra, the share doesn’t show up in timemachine disk select settings. Also tried the fruit option, didn’t work. Editing the avahi services smf file made the share show up in timemachine, but after selecting it, the message showed up that the drive was not capable... this whole timemachine stuff on apple is broken on so many levels, it's not even funny anymore.
  15. Installing the temp plugin on 6.8.3 shows: Unraid version too high, requires at most version 6.7.2... Is this plugin obsolete?