Showing posts with label macbook. Show all posts
Showing posts with label macbook. Show all posts

Friday, September 16, 2022

Expelling demons from 2020 Air: when Disk Utility says to run against the Container (and more)

If you have to maintain a modern Mac, it helps to be retired. How else would I have hours to spend one Friday pm?

The 2020 Air I inherited from my daughter had met with a beverage at a bad time. We paid a third party to resurrect it (Apple doesn't touch wet stuff) but the machine seemed quirky in a software way. Maybe related to the T2 chip and doing the battery swap and then (mistake) Migration Assistant from my ancient Air.

First I had to fix the VoiceTrigger bug, but the machine was slow and I kept running into weird sh*t, like being unable to enable the default App Expose gesture.

So I decided to cleanup by removing files on that machine (they are still on my working Air) and also clean up the user library. I removed a lot of 2007 and earlier items, including a RAZR plug-in. Maybe did nothing but didn't take long.

Then I ran Onyx and it complained the disk was corrupted. When I tried to run Disk Utility I ran into the SMC reset bug.

Once I fixed that Disk Utility would run, but it complained about a corrupt snapshot on my Data drive. Deleting the snapshot didn't fix the error though, so it's likely a red herring. The message said to run fsck on the Container, but I didn't see how to do that. Running it on the Volume didn't help.

The Disk Utility directions were, of course, wrong. As were various web sites that said to try fsck in single user mode (is single user even possible in Monterey?).

Eclectic Light had the best guidance, but the real missing piece was telling Disk Utility to show everyone, not just Volumes. That showed me the Container so I could run DU there; the details console shows it's running fsck_apfs -y -x /dev/disk0s2. It ran against all the /dev/disk* things and fixed them all, exiting successfully. My App Expose gesture returned.

I think the demons are purged for now. macOS is pretty damn fragile these days ...

Saturday, August 27, 2022

Using Apple's USB-C to T2 adapter: not for video but still good

My 2015 MacBook Air uses Thunderbolt 2; it was connected to an elgato T2 hub (reliable for over 6 years) with a few USB and Firewire 800 peripherals. That Air is in for a battery swap after which it will be primarily an Aperture machine with some portable use. At the moment I'm sharing my son's 2020 Air; there may be a Pro or M2 Air ahead.

To reduce costs and hassles I decided to try Apple's T3/USB-C to T2 adapter. It costs around $45. Everything works for now -- except my external HDMI monitor. It flickers on and off. I might play with it a bit but for now I have it connected directly to the laptop via a compact Anker USB-C hub [1]. Apple tells us that "This adapter does not support DisplayPort displays...". I wonder if the HDMI display connected to a Hub with a DisplayPort/T2 cables affected by this limitation.

Overall it's worth the money, even though I'm likely to switch everything to a USB-C or better hub eventually. The single remaining Firewire 800 device can be retired.

- fn -

[1] When I disconnect the laptop I have to pull two cables! Oldness helps with the indignity.

Sunday, February 20, 2022

1Password WiFi broke with my new iPhone - how I fixed it (for now)

I pay about $4 or so every month to 1Password because I have not yet been able to replace it. Reason enough to dislike them, but there's worse. 

We use 1Password's legacy WiFi sync with 1Password 7. It dates from the days that 1PW was merely mediocre. It was flaky and annoying but it mostly worked. We didn't have to put our lives into the hands of company that could be hacked or acquired at any time (China, Russian ... who wouldn't want those yummy credentials?). Even now that we pay monthly (not yearly, because I plan to leave) we still use WiFi sync.

Every so often we get this:

WiFi sync is deprecated and unsupported now, but there is still a troubleshooting page. Check WiFi, restart everything, restart router, toggle WiFi sync on/off, etc. That usually works, but this time was different. Nothing worked.

I'd just replaced my iPhone 8 with an iPhone 13 Pro, so I had a hunch what was wrong. [1] There was something broken in the authentication process between my phone and the MacBook running the desktop version of 1Password. I needed a button that said "reset authentication" -- but that doesn't exist. I could delete 1Password and reinstall, but it had been a few weeks since my last sync. Who knows what I'd changed. I didn't want to lose everything.

This is what I did:
  1. I saved copies of things I knew I'd changed to a local text file
  2. I discovered iOS 1Password has a backup/restore feature and I could transfer that to a Mac by iTunes. You can actually unzip the backup and browse it in SQLite, including the database schema (I think passwords are encrypted though).
  3. After I saved my backup to my Mac I deleted and reinstalled 1Password. As I'd guessed this allowed me to sync again. (Bad Bug 1Password Inc. But you don't care.)
  4. I then went back to my Mac, copied the backup using iTunes back to my iPhone, then did a restore on the iPhone
  5. I then did sync again.
It's not quite as simple as that. I had to quit and restart 1Password a few times. At one point 1PW for iOS was only showing me sync options for Dropbox! Somehow, after some restarts and tweaks it seemed to sync. Did it all sync properly? I have no idea. For now it's no worse than it ever was.

Once Apple Passwords get the notes feature (holds secret questions) we'll migrate to a hacked together approach of Apple Passwords and a shared Secure Note and I'll finally be done with 1Password.

Update: looks like the process lost my authenticator codes.

[1] I dread iPhone swaps. I try to do them no more than every 5 years. All kinds of pain happens.

Saturday, February 05, 2022

Relentless beeping when plug iPhone into MacBook USB port: reset iPhone Location and Privacy

Solved 9/12/2022

I wrote the post below when I used an iPhone 8. When I went to an iPhone 13 it seemed to resolve, but today I tried charging my iPhone from my Air and it was beeping again.

I didn't have time to waste so I switched to a normal charger, but later it occurred to me that there might be a way to reset the trust relationship.

There is, but it's not on the iTunes side. It's on the iPhone side.

If you don't want to trust a computer or other device anymore, change the privacy settings on your iPhone, iPad, or iPod touch. Go to Settings > General > Transfer or Reset [Device] > Reset > Reset Location & Privacy. Now when you connect to formerly trusted computers, the Trust alert will ask you whether you trust that computer. 

I did the reset on my iPhone and next time I plugged it in to my Mojave Air I got the "do you want to trust" dialog. I accepted it and now the phone charges without beeping. I suspect the problem will recur based on the notes below however.

--

When I plug my iPhone 8 into my MacBook Air's USB port I get relentless beeping and the iPhone power icon flashes. Sometimes iTunes throws up a "received an unexpected response" error. I'm on Mojave iTunes.

I figured this was a bad USB cable or bad port or bad connection, but it's both ports and all cables and the phone connection is good. More importantly, I rebooted with no peripherals connected and switched to my admin account. Then every beep was associated with a new iTunes dialog asking me (yet again, and again, this is such a pain) to authenticate. When the dialogs ended the beeping stopped.

Stack Exchange has an article on this, but that's definitely connection issue related. This Apple tech article seems closest; but they also focus on cable issues.

I'm not entirely sure it's not something hardware related on my Air, but I think there's an iTunes component too.

The console shows:

I see: usbmuxsd errors, HandleUSMMuxConnect, iTunes Helper, MobileDeviceUpdater, "no such device". So iTunes is causing the beeps (though the underlying issue could be hardware).

From those clues I found these posts:

  • https://discussions.apple.com/thread/251691536: kill usbmuxsd related processes
  • https://discussions.apple.com/thread/6611777?answerId=27079314022#27079314022 - a bug in usbmuxsd that Apple may have fixed in later releases
  • https://discussions.apple.com/thread/6728641?answerId=6728641021#6728641021 has a discussion:
It's an iTunes 12 bug... Not sure who's responsible for usbmuxd at Apple, but they should be fired! This was extensively discussed and worked out here: itunes 12 will not recognize iphone

All credit to oskapt, who's post detailed the entire issue. The short version is a recent version of usbmuxd has a programming error that leads it to never close any connection. At the same time, it's constantly making new connections too. The end result is this background process actually hits the built-in UNIX limit on open connections by a single process (to prevent bugs like this from ultimately crashing an entire computer), and is blocked by design from functioning after that point. Once usbmuxd fails, iTunes can't see your iOS devices.

The fix is to quit usbmuxd, either via Activity Monitor or Terminal. It will automatically relaunch, and work again until it hits the limit. That thread has several suggestions for automated scripts to run every 24-48 hours to prevent this.

Update 2/20/22: I never solved this problem, but I did get a new phone and the beeping is gone. So either a connection problem with the old iPhone or a bug with the "trust relationship" between iPhone and MacBook.

Update 3/5/2022: In the process of cleaning out old iPhones I tried various iPhones and I tried iPhones that beeped on my Mojave iTunes machine on a different machine. I think it's a bug with establishing a Trust relationship. Probably fixed in later versions of iTunes.

Sunday, January 24, 2021

Saturday, January 23, 2021

Don't blame your hub when your USB Flash (thumb) drive disconnects from your Mac

I tried using a SanDisk USB Flash ("thumb") drive as an alternative Time Machine backup device on my daughter's 2020 Intel MacBook Air (Catalina) and my 2020 Apple Silicon MacBook Air (Big Sur). It worked when directly connected to a 2011 MacBook Air (High Sierra), but when connected to an Anker USB-C hub it kept disconnecting:


I was pretty annoyed with the Anker hub and decided to return it, but then I tried it on my 2016 MacBook Air (Mojave) with a rock solid old Elgato Thunderbolt 2 Hub. The same thing happened there!

So I can't blame the Anker hub too much. I canceled my Amazon return. The bug is probably some mixture of faults in macOS, the processor in Flash drives, and some global Hub/USB flaw. 

It would be interesting to test Apple's hub-equivalent dongle -- the USB-C Digital AV multiport adapter.

Migrating from 9yo 11" High Sierra MacBook Air to 2021 Big Sur M1 Air

I replaced Emily's 8-9 yo MacBook Air 11" running High Sierra with Apple's latest (M1) Air (Big Sur). A few notes for others who might be facing migrations....

  1. I used Migration Assistant over WiFi but I didn't migrate any applications. Apps have changed to much, better to install from source. Pay CLOSE ATTENTION when they tell you to write down the user passwords! (I took a photo). Migration Assistant brings over a lot of old junk but it also saves a lot of time; it's a pain to migrate mail archives without it.
  2. Only 1Password needed Rosetta so far. As I write Office 365 is installing.
  3. Citrix Workspace for Apple Silicon worked! That was biggest risk.
  4. I couldn't get Carbon Copy Cloner email notifications working. I contacted vendor. The app works for back up though.
  5. I didn't want to use the iCloud Document sync feature and Migration Assistant did preserve my High Sierra settings.
  6. You need to open Photos and let it update before reenabling iCloud photo sync. There's no error message -- it just won't work.
  7. For multiple users I couldn't update the User Profile Login picture from the user account, I had to do it from my Admin account in Users and Groups preferences. (Needed update for Retina images)
  8. I did better skipping iCloud setup initially then doing it from each User account separately.
  9. I had to reenable Fast User Switching on 1-2 accounts.

Overall I ran into a few bugs and glitches but High Sierra is 3 releases from Big Sur so that's a hard jump. Really wasn't terrible so far. 

The new Air is rather faster than the 9yo 11" Air, but not amazingly faster than my 5yo MacBook Air (Best Computer Ever Made). Most delays are waiting for servers, so local speedups don't make a ton of difference.

Update 4/2/2021: Alas, it turned into a bit of a disaster.

Saturday, February 09, 2019

MacBook Air shutdowns - it was the battery

My 2015 Air shut down suddenly two weeks ago. The battery was at about 80%. When I got it home and plugged it in it showed classic bad SMC behavior — the power diode didn’t light. 

I did an SMC reset and it worked, but a week later it did the same thing. I did an SMC reset again, but without checking if it was necessary.

It happened yet again. This time it worked fine as a soon as I plugged it in. That gave me hope that it was a battery issue, even though system info showed only 80 or so cycles. It’s an old battery.

After doing the usual 3 backups-to-current-state-prior-to-repair (one update to my Carbon Copy non-bootable clone backup, one fresh full bootable clone, and one Time Machine backup) I brought it in. It failed the diagnostic test with a big red dead battery note.

So $140 when the part comes in, which is a nice relief. If it had been the motherboard that would be $340 and I’d have a machine with a 4yo battery and a 4yo SSD. Might be better to just buy new.

Tuesday, May 17, 2016

Yosemite, Fusion 7, Windows 10, Office 365: experience

I am a bit freaked out about how painless this was. The experience was surreal to someone of my vintage.

My primary machine is a 10 month old MacBook Air with 8GB of RAM, 1.6GHz i5 and a 256GB internal SSD running Yosemite. A Thunderbolt 2 Hub connects an USB 3 external 1TB SSD and an old Firewire 800 3TB external drive and separate 3TB backup cradle. All pretty generic stuff.

For work reasons I bought Office 365 Mac. I thought I might be able to avoid Windows entirely, but a new contract meant I couldn’t escape.

So I installed my Fusion VM 7.x and an old XP image with Office 2007. The image is stored on my external SSD. That went disturbingly well, so I downloaded the Windows 10 ISO (64 bit) and asked Fusion to create a new image from the ISO. That also went disturbingly well. The only glitch was it hung during VMWare Tools installation. I had to restart the VM and I reinstalled the tools.

Then, hey, what the hell, I installed Office 365 too. The usual 365 license covers several machines, both Windows and Mac. Yeah, same thing. No problem.

The image on the external SSD took 12.6GB with just Windows 10 Pro, 14.45 after Office 365 installed. Heck, I’ll probably move it back to my primary SSD.

The performance of my very generic low end MacBook Air is excellent. Modern SSDs are a miracle.

Very. Strange.

Saturday, October 25, 2014

Adventures in using Migration Assistant to move one User from a Lion Mac to a Mavericks Mac

When my G5 iMac finally died (1995-2014) I first thought we’d need another machine - like Apple’s top-secret max value DVD containing laptop. As it turned out, we didn’t, which is probably not great news for Apple. I did have to reconfigure our existing devices and order an external display, but we ended up with a better hardware distribution than we started with.

The reconfiguration did require migrating a user from an older machine running Lion to a Mavericks machine [1]. That’s what this post is mostly about, so feel free to skip the hardware refactoring discussion.

The hardware refactoring

Before the G5 iMac (2005-2014) died our family of five (not counting Kateva) had 1 iPhone apiece, no iPads, a 2009 27” iMac [2], a 2006 MacBook Core 2 Duo (Lion) [3], a 2011 11” MacBook Air [4] and, of course the G5. (And two of the kids are getting school iPads in a few weeks.)

Each machine had its constituency. 

The SSD revitalized 2009 iMac is our family server and my personal machine — thanks to its 1TB Samsung SSD power I’d need to spend $2,800 to replace it with a better machine. The 2005 G5 iMac was used by the boys for writing and light web browsing, and it was a DVD playing / iTunes streaming entertainment center. The Air has always been sadly underutilized — it’s my laptop but I usually travel with a corporate winter thing. The 2006 MacBook (Lion) is the main homework machine and my wife’s laptop [5].

We played around with a few options, most of which involved spending about $1,600 and dealing with the pain of a new Mac [6], but we realized that we actually had everything we needed. 

So the 2009 iMac stays where it is, the 2011 Air will become Emily’s primary workstation (hence the account migration need), and the 2006 MacBook with its DVD player will get a $240 external 27” display with integrated speakers. It  will become the DVD/iTunes streaming media center and, with the new external display, a much improved homework machine [7].

All the hardware gets used, we save about $1,300 and weeks of pain (burning coals, pins in eyes, etc). 

Moving the user - quirks of Migration Assistant

I wanted to move Emily’s data from the MacBook (Lion) to the Air (Mavericks) and I remembered that Migration Assistant can move a single user account (or much more) [8]. So I hooked up the two machines with an ethernet cable and … it didn’t work. The User Accounts from the MacBook didn’t show up — only apps and config data appeared.

I did, however, see that I could move Emily’s data from the MacBook backup on Time Capsule. I hadn’t known that was possible. (Turns out this is also a way to restore User data to a new machine from the backup of a defunct device.)

Google told me the missing User option can be a permissions issue, so I did a safe boot (power up while holding shift key). That runs a number of cleanups including permissions repair and disk utility repair. 

Then I turned WiFi off - to reduce any network confusion.

This time it seemed to work — until it hung with the dreaded “Less than a minute remaining” message.

From my reading it looks like this might be related to disk issues, or file corruption, or the fact that computers hate us (it’s mutual). There are a few options:

  1. Run Disk Utility repair or Disk Warrior or equivalent, seeking the bad file. (I’d already done the safe boot, which I believe runs Disk Utility repair.)
  2. Wait overnight. Sometimes many hours later, the process may complete.
  3. Force quit Migration assistant on the sending machine.
  4. Use Time Capsule instead. (Yay!)

I decided to let it run overnight and try a force quit in the morning… but the MacBook closed its session. I noticed it was repeatedly trying to logout, and in user preferences security was set to logout after 8 minutes of inactivity. I wonder if the logout attempts were causing the problem. I ran fsck -fy in single user mode but the MacBook seemed fine.

So rather than try again I switched to Time Capsule using a direct ethernet connection. It took 16 min to move the data over. I ran into 1 (replicable) UI bug that’s hard to explain. If you don’t see a “continue” prompt, click somewhere else.

Then I tried email - and saw nothing. As I submit this post it appears emails are streaming in from Google - NOT from the backup. I may be running into Mavericks Gmail problems, compounded by a migration from Lion. I think that’s going to be a different post. (At least I have the original machine to work with!)

PS. The Air has an encrypted drive; Mavericks Migration Assistant does not automatically enable migrated non-admin users to unlock the drive on startup. That has to be done in security settings from an admin account.

- fn -

[1] I’m waiting a bit longer before going to Yosemite.

[2] Which, like the G5 iMac, had a troublesome youth, multiple hardware issues, and display discoloration — but has settled into a reliable middle-age. People wonder why I hate buying new Macs.

[3] Suffered from plastic case disintegration syndrome — I missed the recall notice for that one. Has had off-kilter hinges and 1 dead drive, easily replaces because it’s freakily easy to service. Yeah, I hate buying new Macs.

[4] Aside from the early demise of the power supply (replaced by Apple) this machine has been insanely trouble free. Reminds me of the remarkably reliable machines before Jobs and Ives. I can’t explain why the Air actually seems to work.

[5] She likes it, and she doesn’t like dealing with unreliable machines.

[6] Typically something between needles in the eyes and walking on hot coals.

[7] If the drive falters I can put in 250GB SSD for $120 or so and it will be supercharged. This was one of the last of the truly serviceable Macs.

[8] If an account of the same name already exists on the target machine Migration Assistant will help, but I prefer to delete the target machine account if, as is usually the case, it’s not worth keeping.

Saturday, April 19, 2014

Why the low end MacBook Pro is the best family computer

First of all, the best family computer is still a Mac. ChromeBooks will be a good option when prices fall below $180 for reasonable build quality, but they’re not there yet.

So which Mac?

Until today I’d have said a Mac Mini or a 13” MacBook Air. The combination of bundled display, internal hard drive, and difficult repair rules out the iMac, and most of the MacBook Pro lineup is too expensive for a family machine.

Today though timely app.net advice [1] persuaded me that the education market legacy non-retina 13” MD101LL MacBook Pro is the right choice. It’s inexpensive by Mac standards ($1,185 and no tax via Amazon), it’s the only Mac notebook with a DVD player, and it comes with plenty of storage (500GB hard drive). Best of all, but the pathetic standards of the modern Mac, it’s relatively serviceable.

Which is why geek parents like this 2012 era MacBook. Buy it cheap and when the warranty expires a year later, put in 4GB RAM and a 500GB/1TB SSD. Now you’ve got a performance machine with a seven year lifespan. [2]

Yeah, the non-Retina MB Pro is, you know, non-Retina. But that makes it faster and the battery lasts longer. Sure it’s heavier than the new generation, but it’s a family device. You’re not globetrotting with it. And a DVD is still a handy thing to have. Best of all it’s an old design — all of the manufacturing glitches have been fixed by now.

It’s the best family computer. Too bad it’s going to disappear soon … 

- fn - 

[1] Advice sought because of a humiliating blunder that I just figured out as I was writing this post. Excuse me while I bang my head against the table.

It began when our family computer, a 2006 Core 2 Duo MacBook, stopped charging. At first the power adapter glowed green and powered the computer, but a day or so later the adapter light went out entirely. An SMC reset didn’t help. Since the power adapter was a shiny 8 month old modern L-connector Apple Store replacement I was sure the old logic board had died. Hence my app.net inquiry.

I ran to the U of MN Apple store to get a new machine, but, of course, I brought my adapter along to check it worked. And there they told me that it was a 45W adapter! Wow, amazing it worked at all! How could that Apple Genius have given me the wrong adapter! What an idiot! (wait for it)

So I gave ‘em my 45W adapter to throw out and went home. Later, when writing this blog, I confirmed the MacBook needs a 60W adapter, whereas my MacBook Air uses a 45W adapter (wait for it) which … come to think of it … looks a lot … like the one … I just bought …

Yeah. Somehow we’d switched adapters. The 60W is fine for the Air (though unnecessarily bulky) 

Although you should always use the proper wattage adapter for your Apple notebook, you can use an adapter of a higher wattage without issue.

But the 45W failed the MacBook. I’m surprised it worked at all. The whole mess was a series an Einstellung effect cognitive blunders. I assumed I had the right adapter, I assumed it had to be the logic board …

Sigh. Now I have to take my new 60W adapter back to the Apple Store and exchange it for a new 45W adapter …

- fn -

[1] Scotch tape over chipping top case plastic, congenitally crummy hinges but with one huge, killer feature — it’s serviceable. Anyone can easily upgrade RAM or replace the hard drive. And so it delivered great value. Apple has forgotten what made it loved…

[2] Extra credit feature: The University of Minnesota Apple Store will add memory at time of purchase (non-soldered!). They’ll even do the SSD update. Now that our beloved First Tech is gone, I’ll be relying on them more …

See also

Sunday, October 14, 2012

Working with a MacBook Air 11" - Tips

I don't  use my MacBook Air that often, since I usually travel with a corporate behemoth and I'm otherwise home bound or occupied. So it's taken me  a while to figure out how to make best use of the 11" screen. Here are some tips I've picked up:

  • Apple made full screen mode for this device. Forget the stories about it being iOS-lite; you need full screen.
  • Mountain Lion full screen works (Lion was awkward) thanks to the the 3 finger mission control gesture.
  • You can move mission control screens around, so you can arrange the full screens in a common sequence that makes it easier to navigate them.
  • Browser tabs now make sense. Each browser gets its own window (full screen), but tabs work within a screen. (There are some odd things with Chrome, full screen, and app switching, but not enough to make me displace Chrome as my full-time non-iOS browser).
  • Sparrow for OS X is essential for a Gmail user, esp. now that Google's UIs waste vast amounts of screen real estate. Sadly it's in minimal maintenance mode (at best) since the team left for Google. It doesn't, for example, support Google two-factor verification; you have to use one of Google's security-annihilating not-really-application-specific passwords. I hope some other team will replicate Sparrow. If the Sparrow team/Google were honorable, they'd open source this app. $10 on the app store for ad-free, and worth it for however long it lasts. Since the data lives on Google there's no harm in using it for now. [1]
  • I need something like Sparrow for Google Calendar -- we are cursed by Google's miserable space-wasting UI [2]. I may try OS X Calendar.app again, too bad Fantastical isn't a native extension to Google Calendar (it works through iCal). BusyCal is $50; if it were $20 I'd try the free trial. [3]

[1] Mail.app IMAP syncs too much data locally, and Apple is incompetent at delivering net services like email and calendaring. I only need my full multi-GB email repository on my home server.
[2] Apple can't do net services, Google can't do UIs. Sigh.
 

Thursday, July 05, 2012

Don't try converting a MacBook Core Duo to Lion

We converted our 2006 MacBook Core 2 Duo dual USB to Lion a few weeks ago.

Don't bother; the MacBook isn't up to it. It's too slow.

I suspect more memory or an SSD drive would help, but, really, six years is a long time for a laptop.

I think we're due for a new machine. When we get one I'll wipe this machine and revert it to Snow Leopard. That would mean no more iCloud, which is, at this point, a feature.

Incidentally, it has the flaking plastic border problem that's common with older plastic MacBooks. It started doing it four years ago and has been stable since; we use scotch tape to close the gaps. A friend tells me Apple will replace the broken plastic for free, even on quite old devices. The hassle isn't worth it for us, but it would be nice if that were true.

Saturday, June 16, 2012

Notes on converting a MacBook Core 2 Duo dual USB to Lion

Our vintage 2006 MacBook Core 2 Duo can, in theory, run Lion [1]. I just upgraded it from Snow Leopard, which it ran reasonably well albeit with lots of fan activity.

I didn't upgrade happily. There's a reason I've waited this long. I wanted to stay with Snow Leopard, but Apple's MobileMe migration was going to cause problem for Emily's Address Book/iPhone Contact sync. Yes, that was the primary reason. Sad.

I upgraded all the apps we use, said farewell to AppleWorks and many games the kids no longer use, removed all PreferencePanes and extensions, unplugged all cables, did a safeboot cleanup and two completely independent backups (one a clone). Then I upgraded.

It seemed to go well enough once Spotlight rebuilt its indices and I refreshed everyone's account. it does take a very long time to log out; Lion is saving a lot of state information and the MacBook doesn't like that.

It went well enough, that is, until my old account. Then things got slow. Even though I'd updated VMWare Fusion to the final "Lion Compatible" 3.x version, I suspected it was the problem. I tried running my VM -- that was a disaster. After power down and a safe boot I uninstalled VMWare 3 per directions.

That helped a great deal. In fact, the laptop is quieter than it used to be. I suspect Fusion has been causing problems for a while [3].

So will I try Fusion 4?

No, not on this old machine. I really don't use my VM's very often, and neither Parallels nor Fusion are sold through the App Store. To do their magic without Apple's help they must be hacking the underlying OS; and OS X is increasingly hard to safely hack.

For now the MacBook seems to have survived Lion - albeit at the cost of a little used VM I'm probably better off without and a dozen or so older games -- and AppleWorks.

So far, better than it could have been. I am, however, regretting obeying Lion's command to update my Airport firmware [2]. 

[1] That's almost six years ago! I'd forgotten how old it really was. Maybe I shouldn't be too upset it can't run Mountain Lion. [2] Lion really wanted me to undo my Time Capsule firmware regression, so I did. Now I'm seeing more problems with losing connectivity, i saw a -1 error again, and I'm again having to rebuild Spotlight indices of the backups. I have a strong feeling I'll be reverting again. I seem to be the only one with this problem though. [3] My best Fusion experience was version 2 with a Windows 2000 VM -- on that old MacBook probably with Leopard (10.5). It's never worked as well since. 

Update 6/17/2012: Logging out and user switching is much slower. It takes about 20-30 seconds to log out and 15-20 to switch. I think it's because of all the context saving Lion does; this old machine can't handle it. There are ways to disable saving of application states, but I'm going to wait a while on this one. Otherwise things aren't too bad. The machine is quieter than it has been for years, the fan no longer roars. I suspect that's due to uninstalling Fusion 3.x, but it could be a Lion improvement.

Update 6/17/2012: I went through each user account and turned off 'save and restore windows' in system preferences. Then I logged out and unchecked the restore windows on login option shown there. No logout and login is back to Snow Leopard times. Now I have to figure out what to do about #$@$ Google Software Update. it keeps popping up in managed accounts that don't have privileges to run it.

Sunday, January 22, 2012

My MacBook fan was roaring. Again. Time Capsule edition.

My MacBook fan was roaring. Again.

This time, however, activity monitor didn't show much going on. It wasn't a Flash ad running in another user account. I didn't have a print job stuck in the bowels of Apple's dysfunctional printing framework.

It had been doing it for weeks. Sluggish performance, slow fan pinup, then continuous running. Something was draining performance and making heat -- and it wasn't showing up in Activity Monitor.

Or, at least, it wasn't obvious in Activity Monitor. I did see something called fsck_hfs using up 10% or so CPU.

To make a long story short - the problem was a defective Time Capsule backup. My MacBook was running fsck_hfs, a utility that "verifies and repairs standard HFS and HFS+ file systems". When I saw this I thought there was something wrong with my system drive - but it tested out fine.

A SuperUser tip clued me in. My MacBook was trying to verify the integrity of my 150GB backup -- over a WiFi connection. This is a singularly ineffective strategy, it would have taken days to complete. The laptop never ran continuously for that long; and there is something about this process that makes a MacBook run hot [3]

If I'd known what to look [1] for I'd have seen something like this:

Screen shot 2012 01 21 at 10 53 54 PM

Except it would have shown 2-4%. It only got to 92% when I connected the laptop to my TC via wired ethernet. It got to 92% then stuck there. The backup was toast.

I then disconnected all users and tried deleting the .img file for my MacBook from TC. That failed because the Finder can't handle TB scale image files [2]. I then used AirPort Utility's very confusing Time Capsule UI to erase the entire drive and started the slow, painful, recreation of my backups.

My MacBook is quiet and responsive again, and fsck_hfs free.

That was painful.

Backup is an unsolved problem.

See also:

[1] I wasn't so direct, instead I wandered about searching Console error messages. There I found:
search console for com.apple.backupd (all messages)
Attempting to mount network destination using URL: afp://;AUTH=No%20User%20Authent@Molly.local/Molly_Internal
Backup failed with error: 21
Error writing Time Machine Information file: /Volumes/Molly_Internal/Stanford_MacBook_0017f2f04828.sparsebundle/com.apple.TimeMachine.MachineID.plist
Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Input/output error
Event store UUIDs don't match for volume: Escanaba
While plumbing Console I discovered an unrelated error that distracted me for a while - a pile of errors like this:
Jul 20 18:27:55 localhost com.apple.launchd[1] (com.apple.SystemStarter): Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
Googling on this one I discovered this is an old OS X bug, one some systems a routine update deleted this folder. I recreated it using terminal:
cd /System/Library
sudo mkdir StartupItems
That cleared up a bunch of Console error messages, but it didn't fix my real problem.
[2] Kind of amazing, but there you go. Apparently they can be deleted via terminal, but erasing through TC is safer. You can only erase the internal drive, if you want to erase a TC mounted external drive you need to move it to a Mac and erase it there.
[3] The MacBook runs hot whenever it does an 802.11n TC backup. I wonder how much of this is heat output from the WiFi/encryption systems.

Wednesday, February 16, 2011

My MagSafe adapter light goes out periodically

My T-Connector style MagSafe LED (green light) goes off periodically. Disconnecting and reconnecting the T connector will turn it back on.

This Apple support note was written for people like me...

Apple Portables: Troubleshooting MagSafe adapters

...Whether your product is in or out-of-warranty, you can take your adapter to an Apple-Authorized Service Provider or Apple Retail Store for evaluation and replacement if necessary. You may be eligible for a replacement adapter free of charge provided there are no signs of accidental damage...

I've inspected and cleaned the connector. For now I live with it, but if it gets worse I'll have it replaced. Sounds like an understated semi-recall ...

Update 3/6/11: It seems to be fixed, or at least a lot better. I guess it just needed to be cleaned.

Monday, December 13, 2010

Troubleshooting MacBook wake from sleep problems

Our 3 yo Dual USB MacBook (Intel dual core) is having intermittent wake from sleep problems. It's on a WiFi network and running Leopard - 10.5. On lifting the lid it spins up then hangs with a faint blue screen. There's no cursor.

I haven't found a fix yet, but here's a list of what I've tried [4]. They're listed in the order I'd suggest. Of course the first thing to do with any ill-behaved machine is to check that your backups are good...

  1. Run Safe Mode start, (aka Safe Boot) then restart [2]
  2. Remove share mounts
  3. Login items - remove all
  4. Clean out list of remembered WiFi networks - Network:AirPort:Advanced. [5]
  5. Do not inactivate the ethernet port - even if you don't use it. Delete all Locales. [6]
  6. Disable Bluetooth
  7. Update Flash (or consider removing it forever)
  8. Input Managers - remove all. They are Satan's tool.
  9. StartupItems - remove all from Library\StartupItems and ~\Library\StartupItems if it exists. Do not mess with System\Library.
  10. Onyx: check corrupted preferences, check disk, delete caches including font caches
  11. Onyx: Repair Permissions :-) [1]
  12. Install disk, run disk utility check disk
  13. Reset SMC [3]
  14. Zap PRAM [2]
  15. Run hardware test in loop mode on install DVD
  16. Remove or update any low level software
    1. Look in /System/Library/Extensions for ideas, but dont' mess with /System. Look in Library/Extensions.
    2. Cisco VPN for example - uninstall requires terminal
    3. Retrospect Client [7]
    4. Fusion is another - it loads early. Update it.
  17. Console.app: Look for messages on startup. Unfortunately Console captures a vast number of warnings and error messages even in a "healthy" system.
  18. Disable Safe Sleep (more a Leopard than Snow Leopard option?)
  19. Look for more ideas here: Tutorial: Dealing with Wake-from-sleep issues | MacFixIt - 2006
  20. Reinstall OS X (desperation move). If you're on Leopard, might as well upgrade to Snow Leopard.
  21. Send out for repairs - likely a hardware issue. Bad memory can do this and problems may not show up in the hardware test.

I'll update this post with the eventual outcome. As of this moment I'm trying Permissions [1] and SMC reset (more likely to help) and I'll try run the hardware test tonight in loop mode.

Update 12/18/10: The hardware test worked. The problem is much better. I wouldn't say it is perfect, but clearly some of the above measures helped. The two I'd most favor are "clean out list of remembered WiFi networks" and "reset SMC". I suspect this problem is less common with 10.6 and that, at least with 10.5, there are many contributing factors to "wake from sleep" failure. The fixes I made reduced the frequency, but it will still occur.

By way of comparison, there were NEVER any issues with the pre-hibernate sleep mode of 10.3 and MacOS Classic, but XP sleep mode is completely unusable. (I've no experience with Win 7 sleep.)

Update 6/17/11: This problem resolved. I think it was finally fixed in 10.6

See also:

-- footnotes

[1] OS X has reams of permission related issues. I have never, however, seen repair permissions help with any of them, much less anything else. It always finds things to "repair", but the "repairs" fix nothing. Repair Permissions is the OS X equivalent of a disconnected thermostat. It's there to distract the customer. Still, when all else fails, I suppose it's worth trying. Onyx will conveniently run Repair Permissions.

[2] Safe Boot, loop mode hardware test and zap PRAM all need a wired keyboard. There are terminal workarounds for Safe Boot.

[3] An Apple identified cause of wake from sleep issues - Intel-based Macs: Resetting the System Management Controller (SMC): "A portable Mac doesn't appear to respond properly when you close or open the lid." I have noted that sometimes the green light on my magsafe connector doesn't come on ...

[4] An infamous Discussion thread on MacBook Pro problems is a good source of ideas.

[5] I had at least 20-30 in my machine. I removed every one.

[6] I have done this in the past, but not on this machine.

[7] I had a leftover version from when I used a Win XP Retrospect Pro backup server. I had to find an old installer to safely uninstall this low level app that runs on startup.

Wednesday, October 27, 2010

Why didn't the MacBook Air ship with USB 3?

I'm halfway to buying a MacBook Air, but I'm sticking with Gordon's rules of acquisition. I'm good with #2-#4, but working on really, really wanting it three separate times.

Thanks to the joy of a nearby Apple Store I've touched the 11". I am infected now. I verified that my 51 yo eyes can read the screen -- that was my main concern. I've also confirmed that it's no bigger than an iPad.

My decision would be easier if the Air had shipped with USB 3. That would more than compensate for the lack of Firewire or ethernet ports.

So why doesn't the lovely 11" come with USB 3? Will there be a USB 3 version out this fall?

This Wikipedia article explains ...
... Intel will not support USB 3.0 until 2011 ... These delays may be due to problems in the CMOS manufacturing process ... .... or a tactic by Intel to boost its upcoming Light Peak interface... Current AMD roadmaps indicate that the new southbridges released in the beginning of 2010 will not support USB 3.0...
This looks ominous. I'd be surprised to see USB 3 in an Apple product before mid-2011. I wouldn't be surprised if they took another path entirely.

Bottom line: USB 3 isn't ready now, isn't likely to be ready for a year, and may yet go the way of Bluetooth (basically dead).

PS. Incidentally, I tested in the Apple store. The MacBook's USB port has enough juice to charge an iPad.

Tuesday, August 17, 2010

Airport Extreme 802.11n range: better at 2.4 than 5

The last time I messed with my home wireless network I jumped through hoops to connect an old 802.11b iBook (yes, the computer, not the app) to an early 2009 Time Machine. A few weeks after I bought that Time Machine Apple revved the line.

Now that I've replaced the Airport Express that now powers my mother's iPad with a new one, I'm sure Apple will rev it along with the upcoming iTV.

In the meantime, I've made one new discovery. In my home, 802.11N 2.4 GHz has significantly greater range than 802.11N 5 GHz. Apparently this is not uncommon.

When I configured the Express to WDS Extend it worked well in our dining room, but it couldn't connect in the living room. I brought it back to the dining room and manually switched the WDS setting from the original 5GHz network I'd selected to the standard 802.11N network [2]. (Time Machine broadcasts both plus 802.11G and 802.11B.) It then connected from the dining room. I repeated this to confirm it wasn't a chance glitch.

So our current (all wireless [1]) home network looks like this:
  • Time Machine: 802.11 n/g/b with 802.11n 5GHz and 2.4Ghz
  • Airport Express: Extends Time Machine, WDS connection is 802.11n 2.4 GHz
  • iMac i5: 802.11n 5 GHz (it's about 10 feet directly below the Time Machine)
  • iMac G5: 802.11g
  • MacBook Intel: 802.11n 5GHz at the moment, but I bet I have to switch it back to 802.11N 2.4 GHz to get more range
  • iPhone 4: 802.11n 2.4 GHz
  • iPhone 3G and 3GS: 802.11g
  • iPhone 3 (used as iTouch): 802.11g
  • iBook: would be 802.11b but I've retired it. It wasn't getting any use in the iPhone era.
Note Apples says the Airport Express will connect up to 10 clients, and the Airport Extreme will connect up to 50 users (I'm not sure where my older Time Machine sits). With our iPhones and guest devices it's not hard to get near to the Express limits.

See also:
[1] I thought the "all wireless" setup would be temporary following some home reconfiguration, but it's worked so well I've stayed with it. I'm surprised.
[2] From Airport Utility select Airport Express. Choose Manual setup, then Wireless. Select the non-5GHz or 5GHz through Wireless Network Name.

--My Google Reader Shared items (feed)

Friday, March 05, 2010

Little Snitch exposes network killing MobileMe behavior

My mothers modem lights were flickering madly -- but I couldn't see why. All was quiet.

It wasn't just the lights -- the network performance sucked. Sometimes things would rush down, but at other times they'd just hang. Crazy.

Naturally I blamed Videotron. Nice people, but last time we had a problem they had to replace her router twice. As usual I got an agreeable support person. Everything tested out for him, but I couldn't run the Videotron speed test - it took ages to load. He wanted to test further, but I thanked him and told him I'd check things out internally.

You see, I'd lied to him about not having a router installed. Yeah, that's bad. I felt guilty because once he'd confirmed their network was ok I had a hunch where the problem was.

I turned my suspicions to the other machines on the WLAN, including my MacBook. Sure enough, when I shut the MacBook the modem lights slowed down and the Videotron speed test showed 1mbps downlink and 128K uplink - just what Mom pays for.

So what the heck was the MacBook doing? It's not an XP machine, so I wasn't worried about malware. I don't like installing low level apps that require uninstallers, but I needed to know what was going on. So I installed the $30 Little Snitch 2 utility in demo mode
...Little Snitch has a free, built-in demo mode that provides the same protection and functionality as the full version. The demo runs for three hours, and it can be restarted as often as you like...
It's geeky, but, in short, LittleSnitch worked. The culprit? MobileMe iDisk file sync. If you have a local cached version of your iDisk share OS X Sync is very demanding about synchronizing with the remote MobileMe iDisk. I wouldn't notice this at home, but at my mother's OS X Sync was saturating the 128 kpbs uplink trying to sync a 28 MB file. The only clue to what's going on is a spinning icon seen if you view a Finder window sidebar. Turning off MobileMe sync doesn't stop this. You can only stop it by clicking on the spinning icon or by turning off local disk caching altogether.

So I was wrong, I did have malware. Apple malware.
--
My Google Reader Shared items (feed)