Playstation 3, USB backup, and error 80010006…

After a long time I decided to backup my Playstation 3. All I would need to connect a FAT32-formatted USB drive, and go to “System settings”/”Backup” in the PS3 menu. Easy? Right..

However, trying with two different USB drives, I got error 80010006 shortly after the backup had started. I could manually copy videos and game settings to the same drive so I did not understand what could have been wrong. After a little Googling, I found out that PS3 might be somewhat picky on how the USB drive is formatted. I used Mac OS X (10.6) to partition and format the drive to “MS-DOS” format (i.e. FAT32). It seems that PS3 does not like FAT32 drives formatted with a Mac. So, I booted up my Ubuntu PC and formatted one of the USB drives there (used system type 0x0c (W95 FAT32 (LBA)) instead of 0x0b (W95 FAT32)). And then it just worked…

So, it goes approximately like this (of course you may have a different device name and fdisk menus, but you get the idea):

# fdisk /dev/sdb

Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-12161, default 1): 
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-12161, default 12161): 
Using default value 12161

Command (m for help): p

Disk /dev/sdb: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       12161    97683201   83  Linux

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))

Command (m for help): p

Disk /dev/sdb: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       12161    97683201    c  W95 FAT32 (LBA)

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.

# mkfs.vfat -v /dev/sdb1
mkfs.vfat 3.0.7 (24 Dec 2009)
Auto-selecting FAT32 for large filesystem
/dev/sdb1 has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 195366402 sectors;
file system has 2 32-bit FATs and 32 sectors per cluster.
FAT size is 47674 sectors, and provides 6102219 clusters.
Volume ID is 3d0a6e1a, no volume label.
Facebooktwitterredditpinterestlinkedinmail

24 hours of geocaching

A rough plan to find geocaches in Tampere area.

I (tr1976), together with Petri (Peetu & family), Heikki (jasso76) and Jimmy (kji), succesfully completed a 24h geocaching marathon last Saturday, 7th of August, 2010. The idea for the event was probably a few months old. Planning started in June by voting for suitable dates. A few weeks before the actual date the planning started to get into speed. We had picked Tampere area, as it had probably the best density of caches and none of us had been extensively caching there. In 50 km radius we found almost 700 traditional caches with D/T = 3/3 or less none of us had found yet. We split the area into four, and each of us looked through the caches in his area, bookmarking ones that could be found somewhat quickly. Then we had a rough idea where we should start and approximately how we should proceed through the whole greater Tampere area.

Planning on paper is worth 100 gps devices.

Our original goal was to find 100 caches. After some Googling we found out bigger records. In USA a group of cachers had found 413 caches in 24 hours. We mentally raised the ultimate goal to 200. We realistically hoped for 150 finds. We eventually found 130. Considering the routes we took and the terrain we travelled on foot and a thunderstorm we can not be disappointed. No group would have been able to travel and find that exact set of caches much faster than that. Finding more caches would have required to drop most of the caches which required walking more than a hundred meters from the parking area. We did walk a lot. We walked in woods and climbed several hills with rough terrain. There were some drive-bys but not so many.

Started the journey - backup what ever you can.

We started our journey by meeting at Peetu’s house with a barbecue, and planning where to start – which would be the first cache to be found. Peetu needed to drop a TB to Janakkala, so we did a warm-up there, finding two caches.

Pre-GC24 T=3.0 caching in Janakkala by Heikki.

The first GC24 cache was to be near the Ikea of Tampere. We were in the area at about 23:30 on Friday. We planned the approach carefully and parked our car as close to the cache as possible. Eventually we were able to run to and back from the cache and drive to the second one in just five minutes. No much time for anything else than thinking on how to go fast forward. We were able to run through nine caches during the first hour. And it was dark all the time.

Then we just kept on going. Find a cache, run to car, write down the find and the time to a notepad. Enter the next one into two car navigators: Garmin and TomTom, and into Garmin Oregon, Garmin Colorado, an iPhone and a Nokia. Then driving. Then parking quickly, opening and closing doors and running into darkness. Another find… Then came the daylight and we could drop the flashlights. Then it was time to sweat even more.

Feeling a bit handicapped finding a cache in a handicapped sign on Saturday at 6 a.m.

First we cached south of the city of Tampere. Then we moved towards Kangasala. Then back to the city centre. Then a lunch break. Then to Pispala and Ylöjärvi. Then came a massive thunderstorm. That cost us probably 6-10 finds. We were waiting in the car for the storm to stop. It didn’t stop quickly. Then we decided to move a bit farther away, to Pirkkala area, hoping the storm would not be there. There we could have a few finds.

Find #100 - Heikki having the honor of finding.
Logging number 100 in 18 hours!

We found the cache number 100 at around 18:00. We could see a lot of debris on the roads and fallen trees, one in the middle of a roof of a house. We then moved back north, to Vuorentausta area. We kept on going, finding about 6-7 caches per hour. We moved north to Ylöjärvi, then towards Lielahti and north from there. We found the last cache, number 130, about 15 seconds before the midnight.

Altogether we drove about 270 km and walked probably 30-35 km in various terrains ranging from climbing rocky hills in the middle of the night to walking in the middle of Tampere in the middle of the day. I could not be more thankful to my fellow geocachers Petri, Heikki and Jimmy for sharing this great experience. A special thank you for Petri for driving us tirelessly around with his car and safely back home.

Facebooktwitterredditpinterestlinkedinmail

Garmin Colorado firmware bugs

Despite my previous blog post, the real problem was in the Colorado’s firmware. Not realizing, but I had had the problem already for a while. I went from firmware 3.30 to 3.40, then back to 3.20 and to 3.00 before I got it working as it should. Now it seems to start up when I change the GPX files in the device. This is probably the first time ever when I had to go back to an old software version because the new one has bugs. With open source computer software somebody (if not yourself) writes a patch, now the only solution is to stay at 3.00 until Garmin fixes the problem in a future firmware version…

Facebooktwitterredditpinterestlinkedinmail