Showing posts with label Kung-Fu. Show all posts
Showing posts with label Kung-Fu. Show all posts

Monday, December 28, 2009

Request for comments: 2010 Hackintosh Dream Setup



[caption id="" align="alignleft" width="288" caption="Lego Hackintosh!"]Parts Installed by rpster88.jpeg[/caption]

I'm putting together a spec for the world's greatest Hackintosh desktop system. This won't be a guide on how to install a Hackintosh, or a list of all available and supported components. That's covered in much greater detail elsewhere.

This guide will conver my own sick twisted fantasy Hackintosh dream system.

What is a Hackintosh??

A Hackintosh is an Intel based white-box PC that has had a modified version of Mac OS X 10.[4-6] installed on it. It's legally dubious, frankly, and Apple pretends to care, but I don't think they do... Much.

Why don't they care very much? Building a Hackintosh is a pain, and then you don't get the premium commercial support from Apple. So basically you won't be able to use your Hackintosh in a stable commercial environment. I'm sure there are people out there that use Hackintosh systems for commercial purposes, but I don't think this is a segment that is taking significant market-share away from Apple. Hell, from what I can see a lot of the people that build Hackintosh computers are already Apple fans and own Apple hardware/software.

tl;dr, a Hackintosh is an Apple computer without any of the benefits of Apple hardware. It's an expensive toy.

If you love Mac OS X, and you are a PC hardware gearhead with a penchant for modding, AND you're not using the system you're going to build to do anything you need to rely on, a Hackintosh could work for you.

The criteria for my Hackintosh dream system will be as follows;

  • Reasonable price (considering what I want)

  • Most optimal performance available.

  • 100% compatability with MacOS X 10.6.x


So, question time!

What components would you put in a high-end Hackintosh system?


What components would you like to see?


What case would you use??


Points of Interest

Adam Savage rides his electric unicycle thingee







Via Bikes and the City. This is a video of a motorized unicycle called an SBU, by Focus Designs, with Adam Savage behind, or on, the wheel. These are cool! I had never heard of them.
I can never personally justify electric bikes and light EV's. I can ride faster, all day, with my own power. So it stays at "neato" for me, not a must have.

Tuesday, October 27, 2009

Blogging with Ecto 3, and a quick tip.

I was a prolific user of Ecto when I first stumbled upon it back during the version 2.4 days. Ecto is now up to version 3 and it is as awesome a blogging tool as ever. It looks like http://ecto.kung-foo.tv no longer works, but that's ok, because the Ecto software and forums are now hosted at IllumineX.


If you are an Ecto 2 licensee, your license for Ecto 2 will get you access to Ecto 3 free of charge.


One snag I came across when I started using Ecto 3 was an error coming back from both the Amazon Helper and the Flickr Helper.


For the Amazon Helper, the error was;



"The request must contain the parameter Signature."



For the Flickr Helper, the error was;



"Failed to get data from Flickr!"



So a quick search rendered the following forum post at IllumineX, which led to the following page explaining how to install the new plugins.


So basically both Amazon and Flickr have updated their API, and therefore the plugins need to be updated.


Here are the quick links to both.



Follow the instructions here and you'll be rolling again within a minute.


Ok let's test the plugins;


Amazon











Flickr





Cannondale Bad Boy Ultra 2007





That's really nice!!

Monday, October 26, 2009

How we anonymize you

Cute video via Core77 that animates how Google Street View attempts to shield your privacy.



Of course, as anyone who has had their license plate displayed in plain view in Google Street View can tell you (ahem..), it's not a perfect system.

Sunday, October 25, 2009

Cool Tools: Rescue CD 3.11

Thanks to F-Secure for putting out this cool tool;



Now it is time to release the new Rescue CD for which we put out the beta some time ago. We decided to update the version number to 3.11 since we added a couple of useful utilities to the CD image. Otherwise this is the same version as is available on our Internet Security 2010 installation CD.



Take a look a the release announcement and download here.

Thursday, October 22, 2009

Quick impression of the new Macbook

design_unibody_20091020


As you are probably aware Apple recently released a new line of low-end Macbooks with updated specs and an updated body mold. I picked one up today to replace my amazingly loyal but aging Powerbook 12". Actually to be more accurate, this Macbook will take the place of three different systems that I use. My Powerbook, an ancient Ubuntu Thinkpad 600E, and a Windows/Ubuntu desktop.


Since this is the low-end, I don't have a Firewire port, or an SD card reader, but to be frank I won't miss either of those features. If I was a professional photographer or videographer that might get in the way.


Screen shot 2009-10-22 at 10.22.30 PM


I opted for a 4GB RAM upgrade, since I do a lot of "multitasking" and I sometimes work with Parallels, simulating Linux and FreeBSD installs. The 4GB of RAM has paid off, I think. If you get a Macbook, opt for the RAM upgrade. People always say "Macs love RAM", and it's still just as true.


So far I'm very impressed with the horsepower this laptop packs. Even as Apple's lowest-end portable offering, it's taking everything I can throw at it. The fan is pretty quiet despite my running of flash videos and Second Life in the background. It's staying fairly cool overall although there are some hot spots.


This crazy crap is my average usage. No wonder I think I need 3 computers


I notice when the graphics card kicks in to high gear, the keys (WSAD in particular) start to heat up, but so far it hasn't been a big deal. I can't comment on how much it might cook my groin, because I've got a laptop lap-table thing that I swear by.


The physical build quality feels sturdy, considering it's not aluminum like a Macbook Pro. But it's still plastic, there's no doubt about it. As much as I loved my aluminum Powerbook, I couldn't justify the $800+ premium for another Aluminum bodied laptop, at least in this generation of Apple computers. Let's see what happens in a couple of years.


I've popped the back off of it to take a look inside (had to, I couldn't help it!) and you can get to pretty much all of the components with little fuss. This is a huge change from most Apple laptops I've dealt with in the last decade. I changed out the hard drives on both my Blueberry iBook and my Powerbook, and each time was a huge production requiring documentation of every step, and of which screws went where.


When the time comes, I'll be able to drop a 500GB SATA drive into this MacBook without giving myself any new wrinkles in the process.


Let's see how I feel in a month, but at the moment, I'm more than happy with this Macbook as a replacement for my Powerbook AND desktop systems.

Tuesday, October 13, 2009

Use Synergy to share a keyboard between an Ubuntu desktop and an Apple laptop

Oy vey. How do I explain this one without sounding like a total alien?


Ok, so I'm using a program called Synergy to share a keyboard between an Ubuntu desktop system and an Apple Powerbook. The program is made up of a "server" and a number of "clients". Since the Ubuntu desktop isn't going anywhere, I am using it as the server and the Powerbook is the client.


It works great. Much easier than having a zillion keyboards on my desk, or in this case reaching over to my laptop to answer an IM or e-mail. BUT, please note the SECURITY CONCERNS at the bottom of this article.


So here we go;


Step 1) Download Synergy2 for the Mac and install.


Download Synergy2 for the Mac and decompress synergy. The binaries come out as synergyc and synergys. synergyc is the binary we want to use on the Powerbook. I have mine in /opt/local/bin/.


Example; decompress the binary package via Apple's Terminal


scarr@awesome:~$ cd tmp && tar zxvf ~/Downloads/zxvf synergy-1.3.1-1.OSX.tar.gz
...etc... output of file...
scarr@awesome:~/tmp$ cd synergy-1.3.1/
scarr@awesome:~/tmp/synergy-1.3.1$ ls -al
total 2888
drwxr-xr-x 3 scarr scarr 4096 2006-04-02 16:17 .
drwxr-xr-x 4 scarr scarr 4096 2009-10-13 21:57 ..
-rw-r--r-- 1 scarr scarr 293309 2006-04-02 16:17 ChangeLog
drwxr-xr-x 2 scarr scarr 4096 2006-04-02 16:17 doc
-rw-r--r-- 1 scarr scarr 861 2006-04-02 16:17 README
-rwxr-xr-x 1 scarr scarr 1029440 2006-04-02 16:17 synergyc
-rw-r--r-- 1 scarr scarr 793 2006-04-02 16:17 synergy.conf
-rwxr-xr-x 1 scarr scarr 1593984 2006-04-02 16:17 synergys


Step 2) install the Synergy server on to our Ubuntu box.


From the command line, do the following;



scarr@awesome:~$ sudo aptitude search synergy
[sudo] password for scarr:
i quicksynergy - GUI for easy configuration of Synergy
i A synergy - Share mouse, keyboard and clipboard over the network


scarr@awesome:~$ sudo aptitude install synergy


You can use the other app in that list, QuickSynergy, to quickly set up the server config. If you do, the config that QuickSynergy generates will be in ~/.quicksynergy/synergy.conf. The downside of QuickSynergy; it doesn't seem to allow much customization, which you may need.


Step 3) Configure the Synergy server.


Configuring Synergy can be a bit confusing but once you've got the layout visualized it makes a lot more sense.


Here's my example config on the server side for reference, which is on the Ubuntu desktop;



section: screens
awesome:
codebook:
meta = alt
alt = meta
end
section: links
awesome:
left = codebook
codebook:
right = awesome
end


awesome is the Ubuntu desktop. codebook is the Powerbook.


So in "section: screens" we define what systems will share awesome's keyboard and mouse. If you'll notice, under codebook's example I've defined a swap of the alt and meta keys.


I've got an Apple keyboard hooked up to awesome, but when I enter codebook's screen, awesome sends an alt in the place of the command key and vice versa for alt. To fix that, I just swapped 'em. Depending on the keyboard you're using, you can mix and match. It's very handy to be able to do that. A list of the keys is in the synergys man page, but here they are below for reference.



· Modifier keys:
shift = {shift|ctrl|alt|meta|super|none}
ctrl = {shift|ctrl|alt|meta|super|none}
alt = {shift|ctrl|alt|meta|super|none}
meta = {shift|ctrl|alt|meta|super|none}
super = {shift|ctrl|alt|meta|super|none}

In "section: links" we define how these systems are configured.

So awesome is to the right of codebook.


[caption id="attachment_4544" align="alignnone" width="300" caption="Pardon The Mess! Awesome is to the right of Codebook"]Pardon The Mess! Awesome is to the right of Codebook[/caption]


Step 4) Run the client and the server


- On awesome, the server, from the command line I run

synergys -c /home/scarr/.synergy/synergy.conf


This is pretty straight forward. I am running the daemon with the configuration we just wrote. It should slip into the background and you can close the terminal.


- On codebook, the client, from the command line I run

/opt/local/bin/synergyc -n codebook 10.10.10.10


In this instance, I am defining the name to send to the server as codebook. The IP address of awesome is 10.10.10.10, which is where codebook will connect.


If everything has gone according to plan you'll be able to slip between the two systems, taking the clipboard with you, which is astonishingly handy!


Step X) some automation


To get the server to start up when I log on to the Ubuntu box, I have asked Ubuntu to run it under System -> Preferences -> Startup Applications


To run the client on the Powerbook, I used Automator to make a shortcut to the terminal command.. This part is still somewhat messy, but it's easy and works.


SECURITY CONCERNS


Synergy is unencrypted and mostly passwordless (if you don't count obfuscating your computer name, which is already sketchy security since it is, once again, unencrypted). Do not use synergy on a network you do not trust implicitly. Because it is unencrypted, all communications between the synergy server and synergy client will be readable in plain text in TCP/IP packets.


There are ways around this, like tunneling synergy through SSH, but that's just one shelf above what I'm willing to explain. If you want to start down this road, you can look at http://www.securityfocus.com/infocus/1816 which is a good starting point.

Monday, July 6, 2009

Possible SSH 0-day vulnerability? And a couple of semi-helpful iptables tips.

Update 07/08/2009: This is starting to sound less and less like a 0-day and more like a single administrative error or lapse. Either way it's a warning; don't be lax with your SSH access. SSH is for the most part secure, but there's always the chance that it can be exploited.

Update 07/07/2009: SANS is also as vexed with the lack of info on this issue as everyone else I've contacted.  They're a great place to watch for more data as it becomes available.  If anything new happens I'll also update here, but I'll probably get it from SANS myself.

w9tedz

I'm sorta loathe to report this, since I don't have anything to substantiate it other than rumors flying on web hosting bulliten boards and Twitter, but there is word of a 0-day SSH vulnerability floating around.

Translated Rumor

Translated Rumor Source

I have no more information on this than that, other than hearing that several hosts are locking down SSH also.

So I've been running around tonight locking down my visible servers.

This is actually good practice for the most part.  SSH is a powerful service, so any vulnerability to it tends to get magnified in importance very quickly, and also as information on the vulnerability spreads attacks multiply quickly.

The fix is simple; block SSH access to untrusted IPs.  At this juncture even if it upsets your clients, you might want to until more information trickles out about the status of this vulnerability.

If you want an easy way to create and test some new iptables rules, you can do what I do (no warranties, etc).

  1. do an 'iptables-save > ~root/tmp_iptables'

  2. edit ~root/tmp_iptables and add the following lines before the line that says COMMIT.  Substituting the IPs and hostnames I have added for your own of course.
    -A INPUT -s 10.0.0.1 -p tcp -m tcp --dport 22 -j ACCEPT
    -A INPUT -s my.devlab.ca -p tcp -m tcp --dport 22 -j ACCEPT
    -A INPUT -p tcp -m tcp --dport 22 -j DROP

  3. do a 'cat ~root/tmp_iptables | iptables-restore' and cross your fingers


If things have gone horribly wrong, and I have led you down a terrible path, cutting off your SSH access, you can either console in and re-do that same process, but taking out the SSH rules, or you can have your service provider console in, or reboot the box.   The nifty thing about this method is that it's not a permanent change to your server.  It will only last until your next reboot, unless you have some process that automatically saves any iptables rules you put into place.

Saturday, June 27, 2009

Recompress gzipped files as bzip2

Just a quickie. No warranties of course ;)

Recompress gzipped items as bzip2

Handy if you need to conserve space in an archive.

for i in `ls *.gz`; do gunzip $i && bzip2 `echo $i | sed s/\.gz//` && echo "finished $i" ; done;

Friday, May 22, 2009

Yves Behar's supercharged motorcycle design

Very cool. I'm not the biggest fan of consumer electric cars, but personal transportation devices like electric bikes get a pass (for efficiency!)


But this? This is awesome.

Thursday, May 7, 2009

The bike helmet debate gets (more) personal

I've been on a bicycle since I was about 5 years old, so I've survived about 29 years of urban bicycling in Toronto's Metro area without "needing" a helmet.  Great statistic right?  

But it only takes one crash!  So here's what happened; 

On Friday the 1st I was biking home on Queen street west, which has street-car tracks.  I passed a cyclist, crossing over the tracks.  On my way back over to the right side my front wheel slipped on the track itself and I dumped my bike at full speed.  

As a result I slid far enough to shave about 25% of the skin off my lower right leg which sucked, but if I wasn't wearing the helmet I would have sustained the following head injuries; 

  • Slamming my right temple off of the asphalt repeatedly

  • Sliding the distance on my face so that it would match my leg

  • Finally cracking the top of my bare skull on the underside of the parked minivan that stopped my slide... hard


[caption id="attachment_4405" align="alignnone" width="225" caption="Helmet Burn"]Helmet Burn[/caption]

I hit the van and the ground so hard that my head still sustained injuries, bruising, and a sort of helmet burn from the impact.  

If I didn't have that helmet on, I would probably have landed in the hospital, or the basement of a hospital awaiting identification.

The implications hit home extra hard.  Before this accident I have been on the fence in the helmet debate.  In the past I've donned it to calm my wife's worries about my bicycle commuting, occasionally leaving it behind if I was just going around the block.  I feel like an idiot, in retrospect.  

If you're anti-helmet because you think a helmet looks embarrassing or geeky, just think how dumb you might feel convulsing and peeing yourself in front of a crowd for 8 minutes while they wait for the ambulance to take you away. 

I had no control over this accident as it was in progress.  Any thoughts of "falling right" were proven foolhardy.  This accident was caused by a slippery surface and speed.  The tracks didn't help, and neither did my full-tilt peddling, but asking for the "perfect ride" all the time is just as fanciful as thinking I was also, somehow, a Ninja.  

This accident could have been avoided; if I just didn't bike at all.  Not acceptable!  I'll bike, I'll get ready to take my lumps, but I won't take the chance of riding without a helmet.  It's too simple a protection, for too important a piece of equipment.

tl;dr Helmets are cheap and the payoff is excellent when you need it.  Wear one if you're smart.

A commenter, Mike, on this post at Treehugger, also summed it up nicely; 
Anyone who's casual about whether or not you should wear a bike helmet hasn't had the unique sensation of your head hitting the pavement after going over your handlebars, that's for sure. I literally cracked a piece of my helmet out that time. My head was the only part of me that didn't hurt. If I wasn't wearing a helmet, the impact may not have killed me, but it would likely have knocked me out, and left me at risk for getting run over in the middle of the road.

Since I now have to replace my bike helmet, I'm thinking about hitting MEC and picking up one of these on Monday when I can finally start riding again (below).  It's not a conventional MTB style helmet but my bike isn't conventional either. 

Bern Watts

Update: I'm not getting a Bern, Jean advised that I would look (more) like a lightbulb.  I agree.  AND, and I found out that on thursday food critic Toby Young got into a bike accident as well.
There’s a simple moral to this story: If you’re going to cycle in Central London, wear a helmet. If I’d been wearing one I probably could have got back on my bike and cycled home. It wasn’t my fault -- I mean, it really, really wasn’t my fault -- but I still feel like an arse. I called the number given to me by the guy who knocked me off and, needless to say, it’s false.

And now would be a good time to mention that some prick also performed a hit-and-run on Jonny5 from ZeroPerGallon.

It's been a bad week for cyclists.

Year of the helmet, people!

Thursday, April 30, 2009

Hey @treehugger help me out of the mobile iPhone landing page ghetto!

Now, I'm not singling out the awesome treehugger.com here, a lot of blogs are starting to do this; 

When I am reading my favorite blogs via Google Reader, or any app for that matter, and I want to follow a story back to that blog from the RSS feed, I will sometimes get re-directed to a "mobile" version of the page.  

This is not bad, in theory, but when the execution is wonky it's very frustrating.  The latest is one of my favorite blogs, Treehugger!  

Example:

 

[caption id="attachment_4388" align="alignnone" width="320" caption="Treehugger in Google Reader on an iPod Touch"]Treehugger in Google Reader on an iPod Touch[/caption]

And I click through...

 

[caption id="attachment_4389" align="alignnone" width="320" caption="The landing site on Treehugger in Safari on the iPod Touch"]The landing site on Treehugger in Safari on the iPod Touch[/caption]

So I hit the mobile page, which would be cool but I don't hit the story.  In fact I don't even see the story I wanted to expand on in this list.  Auugh!  Denied!  

There are a couple of other reasons why this is frustrating.

  1. I'm coming in from an iPod Touch, so the layout won't be mangled even if I hit the regular full-browser site.  Landing on the full site would still be plesant.  (I also have a BlackBerry 8700r, but there isn't a site on earth that it can render properly).

  2. There's no option to just default to the regular site without being bounced to the mobile site.  I believe Gawker has this option; it seems to set a cookie in your mobile browser saying "don't redirect this guy to the mobile site, he no like".  


Of all the trivial things I can worry about, I'm worrying about this :)  Mainly because I see it creeping in to every blog I read.  Every site seems to want to bump you into a mobile version, but by and large the mobile version doesn't have the same polish that the regular site has.

From an end user perspective I'd rather suffer with a potentially mangled full site than a broken mobile site.  I could probably find the story I was looking for at the Treehugger mobile landing page, but by the time I get to that page and realize I'm not looking at the story, then start calculating my options to get to that story I've forgotten what I want to read (yes, I'm a goldfish).

Please, Treehugger, fix it before I am fooled into buying a Hummer H2!  I need my daily econews fix or bad things happen.

Friday, April 24, 2009

A History of the Cannondale Bad Boy in PDF form

urban_badboy
I am a big fan of Cannondale's Bad Boy line, and I have been since they hit back in 199X(?).  Sure, they're a bit on the over-priced side, and there's a lot of style over substance (arguably) but they're great to ride and they look awesome.  
I finally managed to purchase a brand spanking new 2007 Cannondale Bad Boy Ultra that I will likely never shut up about and will nurse until at least 2016.  It has not been a letdown.  
The Bad Boy line is interesting for a couple of reasons; The marketing is geared towards urban hipsters who aren't into Dutch Bikes (so, like, me).  And this leads to all sorts of interesting variations on the Bad Boy theme.
So I'm trying to document these variations from Cannondale's site.  Here are the models listed from 2001 to 2009 from Cannondale's accessible archives (omitting I think 2004-2006, I can't get to those) from the North American market and some from Europe.  

Note: Europe seems to get some cool cool variations. 


2001-bad-boy-jekyll.pdf


2001-bad-boy


2001-bad-boy-ultra



2002-bad-boy


2002-bad-boy-scalpel


2002-bad-boy-ultra



2003-bad-boy-headshok


2003-bad-boy-jekyll


2003-bad-boy



2007-bad-boy-disc


2007-bad-boy


2007-bad-boy-ultra



2007-europe-bad-boy-650


2007-europe-bad-boy-700


2007-europe-bad-boy-8


2007-europe-bad-boy-8-ultra


2007-europe-bad-boy-carbon


2007-europe-bad-boy-nexus-ltd-2


2007-europe-bad-boy-rohloff-ltd-1


2007-europe-bad-boy-rohloff



2008-cannondale-bad-boy-disc


2008-cannondale-bad-boy


2008-cannondale-bad-boy-ultra



2008-europe-cannondale-bad-boy-650


2008-europe-cannondale-bad-boy-700


2008-europe-cannondale-bad-boy-8


2008-europe-cannondale-bad-boy-8-ultra


2008-europe-cannondale-bad-boy


2008-europe-cannondale-bad-boy-rohloff


2008-europe-cannondale-bad-boy-singlespeed


2008-europe-cannondale-bad-boy-ultra


2008-europe-g-star-raw-cannondale-present-raw-cannondale



2009-europe-cannondale-bad-boy-700


2009-europe-cannondale-bad-boy-8


2009-europe-cannondale-bad-boy-8-ultra


2009-europe-cannondale-bad-boy-disc


2009-europe-cannondale-bad-boy


2009-europe-cannondale-bad-boy-rohloff


2009-europe-cannondale-bad-boy-singlespeed


2009-europe-cannondale-bad-boy-ultra


2009-europe-cannondale-bad-boy-whiteedition-solo


2009-europe-cannondale-bad-boy-whiteedition-solo-ultra

Tuesday, April 7, 2009

Invalid node structure under Mac OS X 10.5 Leopard

So my Finder froze up today during a Time Machine backup operation.  After trying several standard tricks to get my Finder back, I finally rebooted.  Upon rebooting, Timebook, my Time Machine drive, wasn't mounting.

Bah!

This wouldn't have made me so nervous, but my iMac had a drive freak out about two months ago, and I had to recover fully from a Time Machine backup.  So there was a better chance than not that both could die on me if I didn't get this fixed soon enough.

Upon running Disk Utility, I received the always hair-raising Invalid Node structure.

From the logs;
Apr  7 10:39:19 magneto Disk Utility[456]: Invalid node structure^[
Apr 7 10:39:19 magneto Disk Utility[456]: Volume check failed.
Apr 7 10:39:19 magneto Disk Utility[456]: Error: Filesystem verify or repair failed.
Apr 7 10:39:19 magneto Disk Utility[456]:
Apr 7 10:39:19 magneto Disk Utility[456]: Disk Utility stopped verifying “Timebook” because the following error was encountered:\n\nFilesystem verify or repair failed.
Apr 7 10:39:19 magneto Disk Utility[456]:
Apr 7 10:39:24 magneto Disk Utility[456]: Verify and Repair volume “Timebook”
Apr 7 10:39:24 magneto Disk Utility[456]: Starting repair tool:
Apr 7 10:39:24 magneto Disk Utility[456]: Checking Journaled HFS Plus volume.
Apr 7 10:39:24 magneto Disk Utility[456]: Checking Extents Overflow file.
Apr 7 10:39:24 magneto Disk Utility[456]: Checking Catalog file.
Apr 7 10:41:02 magneto Disk Utility[456]: Invalid node structure^[
Apr 7 10:41:02 magneto Disk Utility[456]: Volume check failed.
Apr 7 10:41:02 magneto Disk Utility[456]: Error: Filesystem verify or repair failed.
Apr 7 10:41:02 magneto Disk Utility[456]:
Apr 7 10:41:02 magneto Disk Utility[456]: Disk Utility stopped repairing “Timebook” because the following error was encountered:\n\nFilesystem verify or repair failed.

When you do a Google search, some sites suggest using the command line utility fsck_hfs with the -y option (assume Yes to every question.. if you run an fsck on a damaged filesystem you'll usually see why this is a good idea).  That didn't work for me, it would just crap out again the same way Disk Utility had.  What DID work was the following.. (after a sudo su -)

# fsck_hfs -rf /dev/disk1s3

Now, a lot of people suggest Diskwarrior to fix this problem.  I agree this is probably a good idea for Mac disk maintenance tasks.  The problem; Disk Warrior is $99 USD, and I'm cheap.  Hell, the Timebook was on or about $99 USD.  Disk Warrior will have to wait, but I will likely invest in it in the future.

After I ran the fsck command with the -f flag (to force fsck to check `clean' filesystems when preening.. don't ask me how or why this works over a -ry) the drive was mountable from Disk Utility. The first Time Machine run had this error in the console though, but I think it's harmless.
Apr  7 19:13:02 magneto /System/Library/CoreServices/backupd[1000]: Starting standard backup
Apr 7 19:13:03 magneto /System/Library/CoreServices/backupd[1000]: Backing up to: /Volumes/Timebook/Backups.backupdb
Apr 7 19:13:07 magneto /System/Library/CoreServices/backupd[1000]: Event store UUIDs don't match for volume: Macintosh HD
Apr 7 19:13:07 magneto /System/Library/CoreServices/backupd[1000]: Node requires deep traversal:/

Here's the full text of the command output below, for reference;
magneto:~ root# fsck_hfs -rf /dev/disk1s3
** /dev/rdisk1s3
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Rebuilding Catalog B-tree.
Invalid node structure
(4, 75586)
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
Incorrect number of thread records
(4, 32659)
** Checking multi-linked files.
Incorrect number of file hard links
** Checking Catalog hierarchy.
Invalid directory item count
(It should be 1178851 instead of 1178880)
** Checking Extended Attributes file.
Incorrect number of Extended Attributes
(It should be 1690486 instead of 1690462)
Incorrect number of Access Control Lists
(It should be 1690472 instead of 1690448)
Invalid leaf record count
(It should be 3699221 instead of 3699235)
** Checking multi-linked directories.
Incorrect number of directory hard links
** Checking volume bitmap.
Volume Bit Map needs minor repair
** Checking volume information.
Invalid volume free block count
(It should be 36497060 instead of 29689387)
Volume Header needs minor repair
(2, 0)
** Repairing volume.
Orphaned file hard link (id = 8785918)
Orphaned file hard link (id = 8785919)
Orphaned file hard link (id = 8785920)
Orphaned file hard link (id = 8785921)
[[ message repeated etc ...]]
Orphaned file hard link (id = 11098150)
Invalid first link in hard link chain (id = 11995430)
(It should be 12024532 instead of 12023278)
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
Invalid map node
(8, 61440)
** Checking multi-linked directories.
** Checking volume bitmap.
** Checking volume information.
** Repairing volume.
** Rechecking volume.
** Checking Journaled HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking multi-linked files.
** Checking Catalog hierarchy.
** Checking Extended Attributes file.
** Checking multi-linked directories.
** Checking volume bitmap.
** Checking volume information.
** The volume Timebook was repaired successfully.

Update: Jan 4, 2010 - While doing some digging, I found this article at Jthon's Place that describes how to fix a corrupted Time Machine backup.  NICE!

Thursday, March 26, 2009

Twitter Updates for 2009-03-27


Powered by Twitter Tools.

Wednesday, March 25, 2009

Twitter Updates for 2009-03-26


Powered by Twitter Tools.

Tuesday, March 24, 2009

Twitter Updates for 2009-03-25


  • RT @motionblur: Fox News idiots apologize for stupid comments about the Canadian military: http://bit.ly/PnHD3 #

  • RT @LtGenPanda: London cops reach new heights of anti-terror poster stupidity http://bit.ly/vuuVI #

  • RT @davenavarro6767: NIN/JA Wednesday tomorrow on Dark Matter 10p-12a PST on Indie Online/studio#877-900-1031 http://bit.ly/3RYHu #

  • At Saul Williams #

  • And Les Claypool #

  • Twittering at a concert (I'm "that guy") #

  • A couple of feet away from Saul Williams, but I have nothing interesting to say. #


Powered by Twitter Tools.

Monday, March 23, 2009

Twitter Updates for 2009-03-24


Powered by Twitter Tools.