Monday, November 5, 2012

Hike: Rattlesnake Mountain

Hike: Rattlesnake Mountain
Distance: 20.5 mi
Location: Snoqualmie area I-90

My goal for this hike was to see how my body fared on a long hike. I have decided to seriously look into through hiking the PCT in 2014. While that sounds like a long ways away I have a lot of unanswered questions and preparations to make before I can undertake the adventure feeling prepared.

For those that don't know the Pacific Crest Trail (PCT) is a National Scenic trail that starts at the US/Mexico border and continues north through California, Oregon, and Washington on its way to Canada. It is 2,600 miles give or take and it travels through some of the most highly regarded scenery in the US. Because of the threat of snow in the High Sierra mountains most people start the trek around the end of April and finish 4-6 months later.

One of the things that concerns me most is the rigorous pace that is required to finish the PCT before the weather makes traveling in the upper Cascade elevations very difficult. For me I would only really be able to attempt the trek if most of my time on the trail was covered by vacation time that I have from work. With that in mind I've been tentatively budgeting 16-18 weeks for the whole PCT. Operating under those assumptions I will need to be averaging 25-30 miles of hiking per day.

That is a lot of hiking, and I am just not sure my body is up to the task. I've had some issues with my feet in the past that could make the trip impossible for me right from the get go. In order to find out I wanted to try a nice long hike that somewhat simulates what I could expect on the trail.

I chose the Rattlesnake Mountain hike because it had a good amount of mileage and was pretty close to home. The higher hikes around Seattle are starting to get a bit dicey when it comes to snow and the threat of snow. Rattlesnake Mountain is a fairly low elevation so it should stay clear of significant snow for quite a while.

I decided that for this trip I would try out the suggestions of trail running shoes rather then proper hiking boots. I've tried several boot styles, weights, brands etc (as my girlfriend can attest a trip to REI usually means at least 40 minutes of me looking at shoes). I chose a pair of Salomon XA Pro 3D Ultra 2 trail running shoes 1 size larger then my typical shoe size. I hadn't tried them on even the morning I set out, which when you are talking about boots is a death sentence. They performed very well and I only got a tiny blister on my heel after the whole 8 hour ordeal.

I also loaded up a backpack I have with about 15 lbs of various stuff in order to get an idea what it might be like on the PCT.

Something I have never considered before is the use of an umbrella while hiking. I've been reading that quite a few people hike the PCT with umbrellas because the afford good protection from the sun and the rain. I was surprised how nice it was to pop open the umbrella when the rain started coming down, rather then getting my rain jacket out.

20+ miles is a long way to hike, by just about anyone's estimations. 20 is pushing and probably beyond the range of my longest walking adventures. I have to say however that I was very impressed with how I felt after the 8 hours of hiking. I was definitely tired, and had some serious muscle soreness the following day, but I feel like I could have maybe done another few miles if I had rested for a little bit.

This is a good sign for my PCT hike. 20 miles would be a low mileage day for me on the PCT but considering that I haven't hiked seriously in over a year, I haven't been working out for the passed 2-3 months, I've always had issues with shoes and hiking, I think I did pretty darn well.

The hike itself was quite nice. The day was mostly drizzly and overcast. The trail moved through overgrown logging roads, clear cuts, under some power lines, through dense forests thick with fog, across some streams, and stopped at a lake. I had lunch and hiked the trail in reverse. The first 2/3 of the hike to the lake I was practically alone, except for a few runners. Then I started running into those hiking from the Rattlesnake Ledge trail head.

Overall I'd say the trip was a success here are some takeaways:
  • I need to drop a few pounds. Each pound I don't have to carry from the start the finish will make the whole trip that much easier.
  • I need to start up a cardio program again. I wasn't panting TOO bad on the trail, but it wasn't a walk in the park for me either.
  • I should maybe get my ankle and knee checked out by a professional. They weren't too bad on the trail, but within a few hours of being off the trail they were definitely sore. Perhaps hiking poles would help, but I'd rather see if I could address the real problem.
  • I will never wear hiking boots again. Ok maybe never, but never for hiking when there isn't feet of snow.
  • Hiking with an umbrella is awesome!
  • I do really like hiking. Something about being in the woods, with no one around is really calming for me.

A change of direction around here

Whoa! That was sudden! Unless you don't come to this blog that often you may have noticed that it looks entirely different then it used to.

What's going on eh?

I've decided to re-kindle and re-purpose my use of this blog. I want to move away from just dumping to any potential readers the things I find amusing on the internet and towards a place people can come to find out what is happening in my life. I hadn't posted anything to plecebo.org in over a year for several reasons, but largely because I felt like there was no one listening. What is the point in broadcasting information if you aren't broadcasting to everyone. So my intent here has changed. Hopefully I can use this space to chronicle the things in my life I love and you can come here to read about it.

Additionally I'd like to use this blog to document my preperation for a Pacific Crest Trail through hike in 2014. It is a HUGE undertaking, and larger then anything else I've ever attempted. Stay tuned as I lay out my reasons for wanting to do the hike, and the things I'm doing and thinking about related to the hike.

Yea but where is all that great blog content that I used to come to your site for?

I knew that was your real question. For now you can find that content here: http://old.plecebo.org But over time I plan to migrate that information (by hand painstakingly) from the old platform (Drupal) to the new platform (Blogger). I just don't want to be responsible for keeping up with security updates on Drupal anymore.

Friday, November 18, 2011

Split Lossless Audio and tag it.

Nearly all this information was found on the blog:http://aidanjm.wordpress.com/2007/02/15/split-lossless-audio-ape-flac-wv...

The steps below are the steps that I follow to split my own audio that I find still in a single lossless file (usually .wav).

sudo apt-get install cuetools shntool flac
cuebreakpoints sample.cue | shnsplit -o flac sample.wav
cuetag sample.cue split-track*.flac

Thursday, November 17, 2011

All I want to do is give you my money!

I HATE to write paper checks. The reasons are many but to avoid making this post more about my hate of checks and less about the bogus extra fee the City forces on those who choose to pay in a more convenient way here is a short list of my issues with checks:



  • My handwriting sucks

  • I can never find my checkbook

  • Checks seem like a throwback from the past

Sunday, November 13, 2011

Backup Server

Backup is a server meant to work in conjunction with Zeus to perform offsite nightly backups of each other. Backup sits at one site and Zeus sits at another. Backup is a backup aggregration point for its site. Collecting all the backup files in one place so they can be pushed to Zeus nightly.

Hardware

Backup consists of the following hardware:
  • Supermicro MBD-X7SPA-H-O motherboard (Atom Based) 
  • CHENBRO ES34069-BK-120 Black SECC Pedestal Server Chassis 120W 
  • 16GB Mushkin USB drive used as the system drive 
  • 2x 2GB GSK F2-5300CL5D-4GBSA R RAM 
  • 4x 1TB WD SATA2 WD10EVDS green hard drives 

Installation

Ubuntu Server 10.04 64bit is installed on the Mushkin usb drive. The installation was pretty standard, I didn't change anything during installation and only selected to install the OpenSSH server role.

Post installation I updated & dist-upgraded, rebooted then installed a few packages: htop vim-nox mdadm xfsprogs xfsdump openssh-server

MDADM installs postfix by default and I chose to accept the default settings.

MDADM

mdadm is the linux raid interface that allows you to manage, create, and destroy your raid array. The man page is very detailed and helpful.

Partition

For each of the 4x1TB hard drives I had to create a new partition and set its type to the Linux RAID type.
For each of the disks do this:

sudo fdisk /dev/sda

chose to create a new primary partition (command n) use the default values to create a partition that takes the whole disk
change the partitions system ID (command t ) to Linux raid auto (code fd)
write the table to the disk and exit (command w)

Repeat those steps for each drive

Create the /dev/md0 array

I created the Raidarray using this command

sudo mdadm --create --verbose /dev/md0 --level=5 --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1

The array started syncing. An interesting note that gave me pause at first is that the array builds in a degraded state (with 3 of the 4 drives active) and the 4th device marked as a spare. After the initial sync it will add the spare back into the array.

cat /proc/mdstat looks like this:

Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]

md0 : active raid5 sdd1[3] sda1[0] sdb1[1] sdc1[2]

2930279808 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]



unused devices:

Create an mdadm.conf

This is the file that tells mdadm how to assemble your array when it first starts up. Without this you will need to do an mdadm --assemble on each reboot.

and my /etc/mdadm/mdadm.conf looks like this:

DEVICE partitions

HOMEHOST

MAILADDR me@myrealaddress.com

ARRAY /dev/md0 level=raid5 num-devices=4 metadata=00.90 UUID=3577b84b:f6e2fa73:e508a82b:f6f9bec0


this was created using these commands as root (sudo will not work for them):

echo "DEVICE partitions" > /etc/mdadm/mdadm.conf

echo "HOMEHOST " >> /etc/mdadm/mdadm.conf

echo "MAILADDR me@myrealaddress.com" >> /etc/mdadm/mdadm.conf

mdadm --detail --scan >> /etc/mdadm/mdadm.conf

Just for completeness, here is the output of mdadm --examine /dev/sda1

mdadm: metadata format 00.90 unknown, ignored.

/dev/sda1:

Magic : a92b4efc

Version : 00.90.00

UUID : 3577b84b:f6e2fa73:e508a82b:f6f9bec0 (local to host ASBackup)

Creation Time : Wed Sep 8 02:51:51 2010

Raid Level : raid5

Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)

Array Size : 2930279808 (2794.53 GiB 3000.61 GB)

Raid Devices : 4

Total Devices : 4

Preferred Minor : 0



Update Time : Wed Sep 8 11:47:49 2010

State : clean

Active Devices : 4

Working Devices : 4

Failed Devices : 0

Spare Devices : 0

Checksum : 84d0cdaa - correct

Events : 38



Layout : left-symmetric

Chunk Size : 64K



Number Major Minor RaidDevice State

this 0 8 1 0 active sync /dev/sda1

0 0 8 1 0 active sync /dev/sda1

1 1 8 17 1 active sync /dev/sdb1

2 2 8 33 2 active sync /dev/sdc1

3 3 8 49 3 active sync /dev/sdd1

Format the array as XFS

Once the array was created I used

mkfs.xfs /dev/md0

to format the drive as xfs

Mount the array

I create a mount point for the array at /mnt/raid

sudo mkdir /mnt/raid

I then found the UUID of my raid array using blkid which for me gave this output:

/dev/sda1: UUID="3577b84b-f6e2-fa73-e508-a82bf6f9bec0" TYPE="linux_raid_member"

/dev/sdc1: UUID="3577b84b-f6e2-fa73-e508-a82bf6f9bec0" TYPE="linux_raid_member"

/dev/sdd1: UUID="3577b84b-f6e2-fa73-e508-a82bf6f9bec0" TYPE="linux_raid_member"

/dev/sdb1: UUID="3577b84b-f6e2-fa73-e508-a82bf6f9bec0" TYPE="linux_raid_member"

/dev/sde1: UUID="e77eb088-01de-41ab-bc0e-79d155f75642" TYPE="ext2"

/dev/sde5: UUID="Nf7hnj-ejy2-2jcm-h38l-urRP-rwng-oGecSz" TYPE="LVM2_member"

/dev/mapper/ASBackup-root: UUID="f862f5de-832c-4fb5-ab88-ae5eb848456a" TYPE="ext4"

/dev/mapper/ASBackup-swap_1: UUID="69b9bdaa-7b39-4175-a083-91287d1d0fbc" TYPE="swap"

/dev/md0: UUID="e366c151-d9ee-467e-967a-ed228d79c51d" TYPE="xfs"

The last one was important to me, since I wanted to auto mount the raid array on boot I would need to add an entry into my fstab

Add the array to the fstab


/etc/fstab will make sure that your drive is mounted each time the device is mounted. So this went into my fstab:

#/dev/md0 raid device

UUID=e366c151-d9ee-467e-967a-ed228d79c51d /mnt/raid xfs rw,user,auto 0 0

I then typed:

mount /mnt/raid

and the raid array was ready for business.

Testing drive failure

Since this server will be running in a remote location it is even more important that I be able to detect issues that may be arising on the server so I can either login remotely to troubleshoot or order new parts ASAP to keep the server running.

I am especially concerned about the raid array having issues and I want to be notified via email if there are problems with it. In order to simulate a drive failure I issue the following commands:

sudo mdadm --manage /dev/md0 --fail /dev/sda1

mdadm: metadata format 00.90 unknown, ignored.

mdadm: set /dev/sda1 faulty in /dev/md0

at this point I received an email in my inbox nearly instantly with the following information (it actually went to my spam folder, so look for it there):

This is an automatically generated mail message from mdadm

running on Backup



A Fail event had been detected on md device /dev/md0.



It could be related to component device /dev/sda1.



Faithfully yours, etc.



P.S. The /proc/mdstat file currently contains the following:



Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]

md0 : active raid5 sdd1[3] sda1[4](F) sdb1[1] sdc1[2]

2930279808 blocks level 5, 64k chunk, algorithm 2 [4/3] [_UUU]



unused devices:

Cool!

To put the drive back in the array use the following commands:

sudo mdadm --manage /dev/md0 --remove /dev/sda1

mdadm: metadata format 00.90 unknown, ignored.

mdadm: hot removed /dev/sda1



sudo mdadm --manage /dev/md0 --add /dev/sda1

mdadm: metadata format 00.90 unknown, ignored.

mdadm: re-added /dev/sda1

And the array starts to rebuild:

cat /proc/mdstat

Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]

md0 : active raid5 sda1[4] sdd1[3] sdb1[1] sdc1[2]

2930279808 blocks level 5, 64k chunk, algorithm 2 [4/3] [_UUU]

[>....................] recovery = 3.2% (31718400/976759936) finish=299.9min speed=52512K/sec



unused devices:

WIN!

Saturday, November 12, 2011

LVM Resources


From: http://www.howtoforge.com/linux_lvm

pvcreate /dev/md0
vgcreate imagestore /dev/md0
lvcreate --name ASZenData --size 500G imagestore
lvcreate --name ASZenSystem --size 10G imagestore
lvcreate --name VirtualBoxMachines --size 20G imagestore
mkfs.ext4 -m 1 /dev/imagestore/VirtualBoxMachines

KVM Virtualization

For Digium Cards:
"If you want to use KVM you'll need VT-d.

Xen supports paravirtual PCI passthrough which doesn't require VT-d. I
don't know about Vmware, etc.

Best Regards
Kenni Lund"
If your server doesn't support VT-D you will need to use XEN or move away from using the Digium cards