Get the details from him,
http://www.satelliteguys.us/988817-post118.html, so you can attempt to create the proper partitions and see what it does.
From the sounds of it though, you may not even know that it re-partitions or formats the drive and if you got it right or not.
If it repartitions or recreates the file system, it will generate a new UUID (universally unique identifier) for each partition/filesystem it creates.
If I :
tune2fs -l /dev/node
after I format it as linux native on my linux PC (I don't have windows any more) and then run that again after it's been plugged into the 622, then I could see if the UUID has changed.
Typical tune2fs output...
tune2fs -l /dev/sdc2
tune2fs 1.35 (28-Feb-2004)
Filesystem volume name: root
Last mounted on: <not available>
Filesystem UUID: 7d99ac7d-9fc5-42ea-8f47-f2fb92b6b8de
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode filetype needs_recovery sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 2076704
Block count: 4152802
Reserved block count: 207640
Free blocks: 4068278
Free inodes: 2076693
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16352
Inode blocks per group: 511
Filesystem created: Fri Mar 4 13:13:51 2005
Last mount time: Fri Mar 4 13:15:17 2005
Last write time: Fri Mar 4 13:15:17 2005
Mount count: 1
Maximum mount count: 32
Last checked: Fri Mar 4 13:13:51 2005
Check interval: 15552000 (6 months)
Next check after: Wed Aug 31 14:13:51 2005
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: db72f256-ab6d-44ff-9fc5-f6256a64bcde
Journal backup: inode blocks
OK, you've now crossed over into the realm of super nerds, whereby even regular nerds steal your lunch money and throw rocks at you.