This morning I updated macOS High Sierra from 10.13.3 to 10.13.4. It appeared to install fine (I got to the login window), so I clicked on 'Shutdown', and when I got to the office, and turned on my Mac, it rebooted into recovery, with the Installer Log open, and a dialog that read, 'The macOS Installation couldn't be completed'. I called Apple and they had me run a check disk, and the boot-up volume didn't have any error. My internal SSD showed up just fine, to this poor chap. Apple also had me try to restart in Safe Mode, but the Apple icon got stuck at 100% progress (3+ minutes waiting). So, since my drive appears to be intact (I used Terminal to browse my data), is it possible to undo the update or reinstall macOS High Sierra and have the system work as it was before the update (apps and data still accessible)? Note, I use Time Machine backups, and I have a 2TB drive with about 40% free space.
Fwd: Aips Installation Question For Macbook Pro
There are lots of 'snapshots' on the volume. Is there a way to recover the system to the Time Machine snapshot? Or, will I need to reinstall macOS High Sierra? Since posting this, Apple called me back and they said that I should be able to reinstall macOS Sierra without formatting the drive and I should be back to the state I was before the failure. I haven't tried this yet as I wanted to see if others have followed this or another procedure to recover from this failure without blowing up the hard drive and starting from scratch.
In the past I have used a procedure for upgrading macOS versions that I had good successes with, especially when discussion groups and news are seeing problematic installs: using a system cleaner. EG using something like Onyx before installing, then a reboot and proceed with the install. Yah, too late now for you but something to consider for the next time. If the restarting in Safe mode doesn't do the trick (it may.) If I were you I would use Recovery Mode and restore from a Time Machine backup. If I remember correctly you have the ability to restore from a specific point in time. Same problem; installation of 10.13.4 failed with 'could not be completed'.
I booted into recovery mode, ran disk utility repair and tried again after restoring from backup. Still no joy, and disk utility is now reporting lots of 'invalid internalflags'. Finally I restored again and I'm sticking with 10.13.3.
Checking the fsroot tree. Warning: inodeval: object (oid 0x5edb): invalid internalflags (0x48000) warning: inodeval: object (oid 0x5edb): invalid pad2 (0x2a). Warning: inodeval: object (oid 0x5ee1): invalid internalflags (0x48000) warning: inodeval: object (oid 0x5ee1): invalid pad2 (0x2a) Checking the snapshot metadata tree. Checking the extent ref tree. Checking the snapshots.
Checking snapshot 1 of 3. Checking snapshot 2 of 3. Checking snapshot 3 of 3. Verifying allocated space. The volume /dev/rdisk1s1 appears to be OK. File system check exit code is 0. Restoring the original state found as mounted.
Operation successful. I got exactly the same problem: after 8-9 minutes got the message to restart because the update didn't work. I had the same with the previous update, but didn't learn my lesson. Then I downloaded the update and with the dmg file managed to update. Mistakenly I didn't this time. So, first I restarted in safe mode, which worked, but when I restarted again back in normal mode, I got the same problem.
Then I restarted with the space bar. Same problem. Then I restarted in recovery mode, and that finally worked. However, regretfully my most recent time machine backup was 2 weeks old (I was traveling), meaning I lost 14 days of work. For the past hour I have been trying to download the dmg file instead of using the update via apple store. First attempt, the download got stuck at 577KB; second attempt stuck at 4.1MB. So, now I decided to wait & see and ignore the apple store message to update, until I read some good news.
ISSUE Users may see issues with fonts when using version 16.9 of Microsoft Word, Excel, Outlook, OneNote and Microsoft PowerPoint on macOS. Symptoms:.
Text appears garbled or in a different font. Fonts not appearing in font picker STATUS: WORKAROUND We recommend you check the installed versions of the font. If you have multiple versions, then make sure the latest version of the font is active. For more information, read about how to fix Need more help? Talk to support.
If you have an Office 365 for home subscription, or you purchased a one-time download of Office 2016, click the Contact Uslink at the bottom of this page. Ask the community Get help from experts in our forums: for Mac users Provide feedback in Office app You can send feedback directly to our Office teams. For Mac users, in Office 2016 for Mac, click the smiley icon in the upper-right corner.
Have a feature request? We love reading your suggestions on new features and feedback about how you use our products! Share your thoughts on the site.
We’re listening.
I want to forward requests from 192.168.99.100:80 to 127.0.0.1:8000. This is how I'd do it in linux using iptables: iptables -t nat -A OUTPUT -p tcp -dport 80 -d 192.168.99.100 -j DNAT -to-destination 127.0.0.1:8000 How do I do the same thing in MacOS X?
Fwd: Aips Installation Question For Mac 2016
I tried out a combination of ipfw commands without much success: ipfw add fwd 127.0.0.1,8000 tcp from any to 192.168.99.100 80 (Success for me is pointing a browser at and getting a response back from a development server that I have running on localhost:8000). I was able to get this working using the ifconfig and pfctl commands on Mac 10.10.2. With the following approach I'm successfully mapping 127.0.0.1:3000 to mydomain.com locally on my machine.
In your command line enter the following two commands to forward connections to 127.0.0.1:3000 to 10.0.0.1: sudo ifconfig lo0 10.0.0.1 alias echo 'rdr pass on lo0 inet proto tcp from any to 10.0.0.1 port 80 - 127.0.0.1 port 3000' sudo pfctl -ef - Then edit your /etc/hosts or /private/etc/hosts file and add the following line to map your domain to 10.0.0.1. 10.0.0.1 mydomain.com After you save your hosts file flush your local DNS: sudo discoveryutil udnsflushcaches Now open mydomain.com in a browser and you'll be seeing the server hosted on your localhost port (i.e. Basically this process maps an: to a new so that you can then map a host that IP. I too had to do a similar thing recently, and in searching came upon this answer. Unfortunately, the answer of Nafe uses ipfw which is now deprecated and unavailable in OSX; and the answer of Kevin Leary is indeed a bit hackish. So I had to make something better (cleaner) and decided to share it here for posterity. This answer is largely based on the approach mentioned at.
As OP mentions, pointing a browser at 192.168.99.100 should get a response from a server at localhost:8000. Adding an alias to ifconfig isn't really necessary, pfctl alone is sufficient: to achieve this the pf.conf file at /etc/pf.conf needs to be modified. First we create (with sudo) a new anchor file (let's call it redirection) at: /etc/pf.anchors/redirection. This is basically a regular text file and contains the following line (just like in the answer of Kevin Leary): rdr pass on lo0 inet proto tcp from any to 192.168.99.100 port = 80 - 127.0.0.1 port 8000. Once the new anchor file has been created, it needs to be referenced within the pf.conf file. Open the pf.conf file with sudo and add rdr-anchor 'redirection' after the last rdr-anchor line (which is rdr-anchor 'com.apple/.'
) and add load anchor 'redirection' from '/etc/pf.anchors/redirection' at the end. Ultimately, this is what the pf.conf file should look like: scrub-anchor 'com.apple/.' nat-anchor 'com.apple/.' rdr-anchor 'com.apple/.' rdr-anchor 'redirection' #added for redirection/port forwarding dummynet-anchor 'com.apple/.' anchor 'com.apple/.' load anchor 'com.apple' from '/etc/pf.anchors/com.apple' load anchor 'pow' from '/etc/pf.anchors/redirection' #added for redirection/port forwarding And that's almost it.
Just restart pfctl by issuing sudo pfctl -d to disable it first and then sudo pfctl -fe /etc/pf.conf to start it again. Now, if you need this happen automatically after every restart, another tiny bit of work needs to be done: the launch daemon for pfctl needs to be updated (the referenced gist mentions that pf is enabled automatically on boot, however this does not seem to be the case from looking at the code). Open (with sudo) System/Library/LaunchDaemons/com.apple.pfctl.plist and look for this: pfctl -f /etc/pf.conf and add the line -e to ultimately make it like this: pfctl -e -f /etc/pf.conf That should do it.
Caveat: Apple no longer allows to change the launch demon files just like that (not with sudo, nor chmod, nor anything else). The only way is to tinker with the settings: boot into recovery mode and launch terminal. Check the SIP status with csrutil status, it should generally be enabled. Disable it with csrutil disable and reboot in normal mode and then do the changes to the plist file as discussed above. Once done, go back to recovery mode and re-enable the protection (it's in place for good reason) by issuing csrutil enable.
Explanation: One can check by issuing the ifconfig command that 127.0.0.1 is already the (default) alias for localhost lo0 - this fact is being used to avoid having to add an extra alias for localhost and to simply use the default address in the pf.conf file. UPDATE: Unfortunately, it seems as though loading the file at startup does not work. I am still trying to get help to have it sorted. Until then, running sudo pfctl -f /etc/pf.conf after starting up does the trick. Your command seems to be missing a rule number; try: ipfw add 100 fwd 127.0.0.1,8000 tcp from any to 192.168.99.100 80 (if you aren't running as root, you'll have to prefix it with sudo). Another thing to check is that the firewall is enabled: sysctl net.inet.ip.fw.enable If it comes back with the value 0 (off), turn it on with: sysctl -w sysctl net.inet.ip.fw.enable=1.
And then arrange for it to get reenabled when the computer reboots. The 'proper' way to do this is probably to create a ( makes this fairly easy). Or just use one of the GUI tools PEra mentioned, and let it take care of the details.
2016-06-17 10:20 GMT+02:00 R-tools Technology Inc.: This is a forwarded message 8.
Hi, I have installed R and being using R for some cDNA analysis. (Mac OSX) I would like to add the Bioconductor in the R I downloaded the bioconductor package and put the folder in the R folder. However, when i type library(vsn), or library(Biobase) in R session R session said can't find these packages. Please kindly advise me how I should do it and I try to use getBioC script to run in the R session. And this time they said my R is not configured to run HTTP.:( so would you mind to advise me how I can solve either of the above or below options? Thank you so much Maggie. Hi, I have installed R and being using R for some cDNA analysis.
(Mac OSX) I will preface this by saying that I'm not very familiar w/ MacOSX and it's installation procedures. I would like to add the Bioconductor in the R I downloaded the bioconductor package and put the folder in the R folder. however, when i type library(vsn), or library(Biobase) in R session R session said can't find these packages. please kindly advise me how I should do it What 'bioconductor package' did you download? The MacOSX package bundle?
and I try to use getBioC script to run in the R session. And this time they said my R is not configured to run HTTP.:( Unless OSX registers as a unix under.Platform$OS, I do not think that OSX will work at all under getBioC.
The other alternative might be to download Jan de Leeuw's Mac OS X R installation from which contains, among some 200-ish other packages, Bioconductor 1.1 On Wednesday, February 19, 2003, at 04:46 PM, Jeff Gentry wrote: Hi, I have installed R and being using R for some cDNA analysis. (Mac OSX) I will preface this by saying that I'm not very familiar w/ MacOSX and it's installation procedures. I would like to add the Bioconductor in the R I downloaded the bioconductor package and put the folder in the R folder. however, when i type library(vsn), or library(Biobase) in R session R session said can't find these packages.
please kindly advise me how I should do it What 'bioconductor package' did you download? The MacOSX package bundle? and I try to use getBioC script to run in the R session.
And this time they said my R is not configured to run HTTP.:( Unless OSX registers as a unix under.Platform$OS, I do not think that OSX will work at all under getBioC. -Jeff Bioconductor mailing list [email protected] Byron Ellis ([email protected]) 'Oook' - The Librarian.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |