fwbackups 1.44 progress

First of all I wanted to mention I've registered #fwbackups irc.freenode.net, so you you have an account feel free to come by and discuss and ideas, feedback or bugs.

I've also been learning C++ (slowly) so I'm going to rewrite fwbackups into C++ but keep the interface the same. In other words, you shouldn't notice a thing except it being much, much faster! A friend also recently joined the development team, so hoepfully 1.44 won't take too long and we're planning to release with support for archives, direct copy as well as incremental backups à-la-Time Machine, have a backend plug-in system and have it run naitively in OS X too!


Fedora 9

Fedora 9 is here! As usual, this new Fedora release is the best so far and includes many new features from PackageKit replacing Pup and Pirut to the new PolicyKit system that makes regular users perform tasks that require root privledges easily. Check it out at fedoraproject.org.


Don't forget the ice cubes

My cousin has a 4 year-old iBook G4 that died recently... When I took a look at it, it was pretty evident that it was a hard disk failure. My cousin didn't have a backup and the iBook wouldn't boot at all, so I held Command+S to boot in single user mode and see what was recoverable. Everything seemed fine.

The longer I used the iBook, the more "ls" and "cd" hung... That's never a good sign. I plugged in my USB disk and tried to dd the iBook's disk over, which did work but at 5KB/s. That comes to roughly 72 days to copy the entire 60GB disk! I've heard the stories about people freezing their hard drives to get some data off, so figured at this point there was nothing to lose and it was worth a try. I stuck the Mac in the fridge for an hour and went to buy a 6-to-6pin Firewire cable.

When I got back, the Mac was nice and cold. I connected the iBook to a working Mac with the Firewire cable, connected my USB disk to the working Mac and finally, booted the iBook while holding "T" (for target disk mode - it makes the iBook act as an external disk).

To my surprise, not only did the iBook turn on (screen working and all), but the working Mac I had connected the iBook to recognized the iBook's hard internal disk! I was able to start running dd and then thought "that's great and all, but who says it's not going at 5KB/s again?" Well, a quick kill -s SIGINFO $! revealed that it was copying at over 5MB/s... Not bad!

The verdict? The freezer myth is true. I kept a ziplock filled with ice cubes around the area where the disk drive is on the iBook, and it kept up the 6MB/s rate for over 8 hours now, save for a few spots where there were bad sectors or funnily enough, when the ice melted! If you'd like to try this procedure, here's the condensed version:

  1. Make sure you have a partition that supports large files (ie, FAT32 won't cut it - we're making a disk image the size of the hard disk you're recovering). In my case, I used a 100GB HFS+ volume.
  2. Place the dead Mac in the fridge for an hour.
  3. Connect the dead Mac to a working one with a Firewire cable, and boot the dead Mac while holding "T" on it's keyboard. You should see the Firewire logo appear on it's screen after a moment.
  4. On the functional Mac, open Disk Utility again and you'll see the "Macintosh HD" volume from the dead Mac on the left pane. Select it and do File > Get Info to determine the partition identifier. It should be diskXsY, where X and Y are typically numbers under 10.
  5. Open a Terminal (Applications > Utilities > Terminal) and enter:
    dd if=/dev/diskXsY of="/Volumes/VOLNAME/dd.img" bs=512 conv=noerror &
    pid=$!;while true;do kill -s SIGINFO $pid;sleep 15;done

Remember to replace diskXsY with the identifier we found for the dead Mac's Macintosh HD. Replace VOLNAME with the volume name of drive you'd like to save the image to. It could be a networked, internally, or externally attached volume. For example, I used a volume on my external USB disk which had the name BACKUPS. I used the following:

dd if=/dev/disk1s2 of="/Volumes/BACKUPS/dd.img" bs=512 conv=noerror &

These commands will clone the dead Mac's hard disk partition, effectively creating a .dmg disk image of the dead Mac's drive. Once dd has finished, you'll find the image saved as dd.img on the volume you selected. dd will skip any bad sectors it encounters, so some data may be lost but if you're lucky you'll be able to get a good chunk out (in this case I was able to recover ~90% of the data). Statistics about the transfer progress are printed every 15 seconds - Once the disk copy is done, you can hit <ctrl+c> and quit the terminal to stop printing them. I hope this is able to help someone who needs data off their Mac!

Realtek HD + Mic (aka Intel Integrated Audio on ICH8)

I bought a low-end Logitech headset recently and it works perfectly in Linux but for some reason in Windows the volume was terrible. To make matters worse, it seemed like the drivers don't support mic boost and only the main "capture" slider is changable… The others such as line-in are locked!

After a bit of Googleing I came to relatively simple fix to the problem. If you're looking for a way to bring up your mic's volume, follow these steps:

  1. Update to the lastest drivers available from the Realtek website.
  2. Browse to C:\Program Files\Realtek\Audio\InstallShield and run the program named MicCal.exe
  3. Follow the on-screen instructions and when promted with a slider, bring it down to zero, leave it there for a few seconds. Raise it to 100% and be sure to click Next right away. Continue with the on-screen instructions to finish the wizard.
  4. Open up Realtek HD Sound Effect Manager from the Sounds, Speech & Audio Devices control panel category. You'll notice under the Playback knob on the left, you have a litte wrench/tool icon; click it and make sure Rear Pink In is checked off.
  5. Now, (use the arrows as needed) click the small button labeled .. (the Advanced button) under Rear Pink In. There, hidden, are the options for Mic Boost!

Reference: johnnygoodface's post at techspot forums

Future of fwbackups: What features do you like?

I've been thinking about the future of fwbackups, and the engines are causing me a bit of trouble. TimeVault is pretty cool and I'd like to implement something similar, but to do that I have to scrap the tar and tar+gz engines. I could also forget the TimeVault-like features for now and implement incremental backups. So, what do you think? I've got a poll running so you can vote for your preferred option on the left.

On another note, 1.43.2rc1 will include a minimize to system tray function so that fwbackups can stay in the tray as an applet :)