Ever since OSX ran on X86 hardware, it has been my primary OS – exclusively on MacBook Pro’s – and whilst learning it’s idiosyncrasies didn’t take long, as a heavy user of keyboard shortcuts I’d always been frustrated by dialog box choices.
The Tab key wouldn’t switch between the buttons, holding Alt or Cmd doesn’t hint at any shortcut letters available, but what does work is pressing the first letter of each buttons text whilst holding Cmd.
So in the example dialog box above, Cmd-C would cancel the choice, Cmd-K would keep the file and lastly Cmd-M would move the file to the trash. Simple, but not as obvious as you might think!
Infuriating wireless behaviour from my Apple MacBookPro5,3.
Every time it wakes from sleep, the wireless disconnects within about a minute and fails to re-join.
19/10/2010 18:48:47 kernel hibernate image path: /var/vm/sleepimage
19/10/2010 18:48:48 kernel AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
19/10/2010 18:48:49 kernel System SafeSleep
19/10/2010 20:17:34 kernel Wake reason = EC LID0
19/10/2010 20:17:34 kernel System Wake
19/10/2010 20:17:34 kernel Previous Sleep Cause: 5
19/10/2010 20:17:34 kernel en1: 802.11d country code set to 'X3'.
19/10/2010 20:17:34 kernel en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
19/10/2010 20:17:36 kernel Auth result for: 00:22:6b:7a:79:d7 MAC AUTH succeeded
19/10/2010 20:17:36 kernel AirPort: Link Up on en1
19/10/2010 20:17:36 kernel AirPort: RSN handshake complete on en1
19/10/2010 20:18:40 kernel en1: 802.11d country code set to 'DE'.
19/10/2010 20:18:40 kernel en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
19/10/2010 20:19:01 kernel AirPort: Link Down on en1. Reason 4 (Disassociated due to inactivity).
It’s been doing this for months now and I can’t figure out why, my Darwin debugging skills are too weak.
These are details from the WD10TPVT, a 2.5” 1TB (12.5mm) SATA drive from Western Digital.
It’s the Advanced Format (4096-byte physical sectors) version of their WD10TEVT disk, though with it’s current firmware you might not know it except for the small warning label on the top sticker of the drive itself.
This label suggests every OS other than Windows XP will work with this drive without any special adjustments, but I’d like to know if this is really true, or if there is a tangible performance impact of using this drive with a default partition layout on other operating systems, notably Linux.
Tejun Heo (of LKML fame) posted a very informative wiki article about the 4kb sector issue here : https://ata.wiki.kernel.org/index.php/ATA_4_KiB_sector_issues
SMART details :
Device Model: WDC WD10TPVT-00HT5T0 Serial Number: W -DXW151CU0xxxx Firmware Version: 01.01A01 User Capacity: 1,000,204,886,016 bytes
Linux detection :
scsi 6:0:0:0: Direct-Access WDC WD10TPVT-00HT5T0 01.0 PQ: 0 ANSI: 3 sd 6:0:0:0: [sdd] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) sd 6:0:0:0: [sdd] Write Protect is off sd 6:0:0:0: [sdd] Mode Sense: 23 00 10 00 sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
Oddly, WD seem to have purposefully made the drive advertise itself as having only 512-byte sectors, surely this is going to cause confusion with software trying to correctly identify and partition these 4096-byte sectored Advanced Format disks?
A well reported problem with the Apples MagSafe connectors, shorting within the cable due to repeated flexing at an acute angle near the connector and resulting breakdown of the insulating layer.
In my case, the insulation on the core conductor had broken down and begun to short to the outer ground shielding within 5mm of the MagSafe connector.
The connector itself is easy to take apart if you heat it first (heat gun or just a hairdryer will do).
I discarded the five centimetres of cable closest to the MagSafe connector, stripped the shielding back and re-soldered the two ground and single positive points. Adding two lengths of heat shrink tubing (a longer 3mm diameter piece with a shorter overlapping 5mm piece) to reduce future strain around the connector.
This MagSafe connector has been in regular use since late 2006, so it’s understandable that it might have been showing signs of wear and tear, but this is a common issue and one to keep a close eye on, I’m just glad I was at home when I saw this or I can well imagine it could have caught fire.
My changelog in no particular order, for my reference.
Installed Little Snitch
Installed Server Admin Tools
Installed globalSAN iSCSI Version 3.3.0
Edit /etc/sshd_config to have :
$ nvram boot-args="-v arch=x86_64"
$ defaults write /Library/Preferences/SystemConfiguration/com.apple.Boot 'Kernel Flags' '-v arch=x86_64'
$ defaults write com.apple.desktopservices DSDontWriteNetworkStores true
# launchctl load -w /System/Library/LaunchDaemons/com.apple.locate.plist
$ defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1
Bang the following into “net.inkhorn.noatime.plist” in /Library/LaunchDaemons
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.nullvision.noatime</string> <key>ProgramArguments</key> <array> <string>mount</string> <string>-vuwo</string> <string>noatime</string> <string>/</string> </array> <key>RunAtLoad</key> <true/> </dict> </plist>
Useful commands :
leela:~ tom$ hdiutil pmap -endoffsets /dev/disk0 MEDIA: ""; Size 238 GB (500118192 x 512); Max Transfer Blocks 2048 SCHEME: 1 GPT, "GPT Partition Scheme"  SECTION: 1 Type:'MAP'; Size 238 GB; Offset: 34 - 500118159, (500118125 x 512) ID Type Offset Size End Name (2) -- -------------------- ------------ ------------ ------------ -------------------- -------- 1 EFI 40 409600 409639 EFI System Partition 2 Apple_HFS 409640 499446368 499856007 256GB SSD Free 499856008 262151 500118158
Just a few thoughts …
- We know there was ZFS read and write support planned for Apples’ forthcoming Snow Leopard Server OS release.
- We know there are 64-bit MacBookPro’s out there with Expresscard34 slots.
- We know there are Expresscard34 SolidStateDisks available.
- We know there are large 500GB SATA rotating disk drives available.
So why couldn’t we have had ZFS on the (cheap and large) internal spinning disk and the ability to put an SSD ExpressCard in the slot for use as L2ARC ?
Except, in reality, we got an ExpressCard slot backed off a USB2 controller rather than a PCI-Express lane, ZFS support seems to have dropped off the radar and the new MBP’s dropped ExpressCard support anyway. Pity.
Having now several Parallels Virtual Machine images I’d quickly reached the limits of the 5400rpm 120GB SATA hard disk my MacBook Pro was CTO’d with.
To replace it I chose the the Seagate Momentus 7200.2 200GB model with 16MB cache.
Replacing the drive is time-consuming but straight forward, I could have used CarbonCopyCloner, but plumped for SuperDuper instead to copy the contents of the old drive to the new one which I had placed temporarily in a SATA Firewire enclosure.
The new disk isn’t really much faster, but the extra space made the operation worthwhile.