Tag Info

New answers tagged

0

iMac that spends most of its time reading and swapping files from the 2TB hard drive That sounds like a problem that needs to be addressed. 1) how do you know this is what is happening? 2) How much memory does your computer have? 3) if you are Terminal-fluent, provide the results of ls -l /var/vm


1

As you know with SATA connection you get 3 to 6 Gb/s. With Firewire you get < 1 Gb/s data transfer. To be specific: Firewire 800 is 800 Mbits/s (Mb/s) not 800 Mbytes/s (MB/s) [8 bits in a byte] its a common misconception. so Firewire 800 is rated up to 80 MB/s.


0

Some days ago I discovered that installing an older version of mac is possible, but no one did it. The problem is in the EFI Bootloader Volume, if you have your mac from 2010 you have an EFI Controller Chip with version for example 1.6 (like BIOS in PCs) already installed in the logic board that supports an old System Drivers, but if you have a New Mac so ...


0

I did something similar and ended up incidentally tweaking the partition table from inside of windows. Because of that it wrecked the EFI and GUID and nearly bricked me completely I thought. Start the computer and hit command-r and you should be able to tell where to go from there. I have to warn you though its probably going to involve wiping one or both ...


0

Also make sure that rc.local has the permission to execute, via a sudo chmod 755 /etc/rc.local The LaunchDaemon does not explicitly report an error, so I was bitten by this until I changed permissions.


0

I do not have the Yosemite, but on Mavericks you can turn off the Auto Updates in System Preferences. Open App Store in syst pref and disable the automatically check for update. After restart you can enable it again to see if it is working now as it should. If not use Disk Utility and repair the disk permissions.


-1

I had this: Numlock had been toggled on.


0

Resetting my MacBook's PRAM returned the boot times to normal.


0

I was using those commands for VirtualBox in rc.local, and I ran into the same problem. I don't if this is the right way to do this, but it works for me. I created /Library/LaunchDaemons/local.localhost.startup.plist containing the code below. It runs the rc.local script once at start up. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist ...


0

You can access the backups folders from a working system (at least on Mavericks) as follows. For this example I'm going to use the name "Backups" to represent your Time Machine volume. Here are the steps: From Finder, click on the "Go" menu item. From the drop down list, select the "Go to Folder..." option. Enter the name of the Backup, so for this ...


1

Open up Terminal.app, in /Applications/Utilities, and enter the following: diskutil list It should show both of your drives and give you information about partitions. You may also want to try: diskutil cs list On Yosemite, some of the volumes are defaulting to Core Storage, which can span multiple drives. I'm not saying you did this, in fact I rather ...


0

In an attempt to resolve the issue I would try installing rEFIt which is helpful for inspecting and modifying the regular boot setup. I've used it for doing dual installs of OSX/Linux in the past.


1

Depending on your Macs you might use the FireWire/Thunderbolt target-disk mode. Apple-KB: If you have two Mac computers with FireWire or Thunderbolt ports, you can connect them so that one of them appears as an external hard disk on the other. This is called “target disk mode.” 1. Connect the two computers with a FireWire or Thunderbolt cable. ...


0

If you have access to the hard disk containing your system check that you haven't deleted by mistake mach_kernel located in your root directory. You can do this by booting from an external usb device and mounting your internal hard drive. This happened to me once, after a system error the system rebooted and I was not able to boot again. If this is the ...


0

When your Mac consistently hangs at the loading screen you described (Apple logo with spinning gear) the best advice I can think of is to reboot using verbose mode. To boot into verbose mode, power the Mac on and hold ⌘+V until you see a black screen with lines of text. Verbose mode displays what is happening while the Mac boots, the stuff that is normally ...


0

There could be a number of reasons to cause this: Amount of storage The age torrented applications or files. These are just the main ones, of course there is others. Try cleaning out your mac! Note: I am not accusing you of torrenting application!



Top 50 recent answers are included