I plugged in a 250 GB Seagate 7200.10 hard drive into my Feisty box this evening, and to my surprise, /dev/sdd appeared along with a bunch of stuff in my dmesg output. This is on an NVIDIA Nforce 4 motherboard.

[189006.364000] ata3: exception Emask 0×10 SAct 0×0 SErr 0×150000 action 0×2 frozen
[189006.364000] ata3: hard resetting port
[189013.280000] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[189013.328000] ata3.00: ata_hpa_resize 1: sectors = 488397168, hpa_sectors = 488397168
[189013.328000] ata3.00: ATA-7: ST3250620AS, 3.AAJ, max UDMA/133
[189013.328000] ata3.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[189013.392000] ata3.00: ata_hpa_resize 1: sectors = 488397168, hpa_sectors = 488397168
[189013.392000] ata3.00: configured for UDMA/133
[189013.392000] ata3: EH pending after completion, repeating EH (cnt=4)
[189013.392000] ata3: EH complete
[189013.396000] scsi 2:0:0:0: Direct-Access     ATA      ST3250620AS      3.AA PQ: 0 ANSI: 5
[189013.396000] ata3: bounce limit 0xFFFFFFFFFFFFFFFF, segment boundary 0xFFFFFFFF, hw segs 61
[189013.400000] SCSI device sdd: 488397168 512-byte hdwr sectors (250059 MB)
[189013.404000] sdd: Write Protect is off
[189013.404000] sdd: Mode Sense: 00 3a 00 00
[189013.408000] SCSI device sdd: write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[189013.412000] SCSI device sdd: 488397168 512-byte hdwr sectors (250059 MB)
[189013.412000] sdd: Write Protect is off
[189013.412000] sdd: Mode Sense: 00 3a 00 00
[189013.416000] SCSI device sdd: write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
[189013.416000]  sdd: unknown partition table
[189013.432000] sd 2:0:0:0: Attached scsi disk sdd
[189013.432000] sd 2:0:0:0: Attached scsi generic sg4 type 0

Download all the Ubuntu i386 and AMD64 ISOs with one command.

wget ftp://mirrors.kernel.org/ubuntu-releases/7.04/ubuntu-7.04-{desktop,server,alternate}-{i386,amd64}.iso

Maybe I like it because it’s in my price range (unlike that 108″ LCD they keep showing off), but the new Antec Sonata III (pic) case looks like a stealth fighter compared to my aging Sonata I. I’ve grown tired of my current case, but it is quiet. This may get me to upgrade. Or I’ll go with the Antec Nine Hundred.

Sweet.

I recently upgrade my main workstation’s hard drive under Ubuntu 6.10 and noticed a couple things changed during the process. Here are my instructions for a fast and reliably hard drive swap. I’m using SATA drives without LVM using the default Ubuntu install and partition options for this howto.

1. Prepare
1. Shutdown your machine and install your new hard drive. Don’t mess with your current hard drive (yet)
2. Find a LiveCD, I used the Ubuntu 6.10 LiveCD, it matched my OS, but it doesn’t have to. Knoppix should work fine.
3. Boot using your LiveCD
4. After booting, open a terminal and “sudo su” to become root
2. Setup your new drive
1. Use cfdisk /dev/sda to look at your partitions on your current drive. I have sda1 of type linux as most of my current drive, and a 6 GB sda5 as linux swap at the end
2. Duplicate this on your new drive using cfdisk /dev/sdb, adjusting for space as necessary. I created a new primary partition using cfdisk using all but 6 GB of space, then a new logical partition using the rest of the space. You must create the partitions in this order to get the right numbering
3. make the primary partition to bootable
4. set the swap partition as type 82 (linux swap)
5. save and quit
6. create filesystems on the new partitions using mkfs.ext3 /dev/sdb1 and mkswap /dev/sdb5
3. Copy data
1. Make directories to mount your old and new partitions, in this case, /mnt/sda1 and /mnt/sdb1
2. Mount your drives to these partitions using mount /dev/sda1 /mnt/sda1 and mount /dev/sdb1 /mnt/sdb1
3. Copy all your data from your old drive to your new drive using cp -a /mnt/sda1/* /mnt/sdb1/ . The -a will preserve owners, permissions, date, etc.
4. Get up and do something else. It took 70 minutes for my machine to copy about 150 GB of data from one drive to the other
4. Fix the boot options
1. This is where Ubuntu 6.10 differs from previous versions. Fstab and menu.lst both use UUID numbers to find partitions. To get the UUID number of your new partitions, run vol_id /dev/sdb1 and vol_id /dev/sdb5 . Copy these numbers into their appropriate places in your /mnt/sdb1/etc/fstab and /mnt/sdb1/boot/grub/menu.lst files. You may need to dig around the menu.lst to find all the entries.
2. Now install grub onto the MBR of the new drive to make it bootable. To do this I first chroot into my new system using chroot /mnt/sdb1 /bin/bash . Now that you’re in the new system, run grub. Inside grub, run setup (hd1,0) then root (hd1) . This will differ if you have a different drive setup. Quit grub (quit).
5. Finish up
1. Logout of your chroot (logout), unmount your mounted drives umount /dev/sda1 and umount /dev/sdb1, and shutdown your computer. Disconnect your old drive, plug your new drive into the old drive’s cable, and start your computer back up. If everything went well, it will boot back up as if nothing happened.

My poor iPod Mini’s hard drive died a couple days ago, which left me without a means to play MP3s while walking around. Since I haven’t yet purchased a headphone adapter for my phone, I started googling and discovered I would be able to replace the dead hard drive with a standard compactflash card. I couldn’t wait for the card to arrive before taking it apart.

Update:

My 4 GB compactflash card arrived, I installed it in my iPod mini, crossed my fingers that I plugged it in correctly (top of the cf card faces away from the circuit board), and reassembled the thing. That was it, I plugged it into my computer and it after running the “restore” from iTunes it works! I now have a flash memory iPod mini

My server decided that an executable file didn’t really exist on the file system, or so I thought. Lack of sleep was the main problem, but here are some things I did to check my file system for errors. I setup this file system on a Ubuntu 6.06 AMD64 install with LVM, so everything is in LVM instead of standard partitions.

# sudo e2fsck -n /dev/mapper/Ubuntu-root

This was showing errors, but I ran it while the system was mounted and running, so there were open files, so this was normal. The -n kept e2fsck from attempting to fix anything, which was good because later I ran the command after booting from an Ubuntu LiveCD and found no errors.

Before booting from the LiveCD I tried to get the system to fix itself by running fsck on boot. Two methods I used to do this on Ubuntu were running these from the live system before rebooting, they both accomplish the same thing, so only one was really needed.

# sudo touch /forcefsck

# sudo tune2fs -C 40 /dev/mapper/Ubuntu-root

These appeared to have no affect, probably because the filesystem was fine, but I took down the system and ran fsck from a LiveCD instead. Of course, this wasn’t as simple as it should have been, the LiveCD did not detect my LVM volumes, so /dev/mapper/Ubuntu-root was missing. The fix was to install LVM2 and start it up.

# sudo apt-get install lvm2
# sudo /etc/init.d/lvm start

The /dev/mapper/ entries then appeared and I could run all the fscks I wanted. At this point my fsck checks were coming out clean, so file system corruption was not to blame.

I had my first Ubuntu bug report confirmed and fixed by the Ubuntu team. The bug I encountered kept Lighty from coming back up when being restarted. Since the default logrotate scripts had Lighty restarting every night, this bug hit my Rails apps quite often. Extending the logrotate script’s rotate frequency helped, and I was about to install Monnit, but now it looks like I can skip that knowing the restart bug has been fixed. Hooray for well managed open source projects.

I just discovered that one of my websites made the printed version of Make Magazine. In issue 6, on page 124, there is a link to frozentech.com/content/livecd.php. This marks the first time I’ve been in print!

Other big firsts include being on the radio, mentioned by Leo Laporte (!) (first hour, at 20:30), being included in a presentation at LinuxWorld, and being on Slashdot, Digg, IBM Developerworks, and SecurityFocus.

I believe my quest for the perfect GUI file manager in Linux has been fulfilled after I stumbled across a file manager named Thunar while playing with XFCE on my Ubuntu laptop. My most missed feature from browsing Windows file systems has been the “List” view. It’s is, very simply, columns of file names, with nothing else. The main file browsers of Gnome and KDE, Nautlius and Konqueror, suprisingly cannot do this, and while they come close with a lot of customization, they do not mimic Windows Explorer perfectly. Nautilus like to wrap really long file name, or only do one file per line, and Konqueror likes to add “…” to the end of long filenames, which makes it less than useful.

Thunar does both these things, and does this very quickly. Here’s a pic of what I’m so excited about (right click and hit “view image” to see the full sized pic):