[atlas] USB drive

Hi all,

I have a probe that's been down for several days now. I did contact RIPE
about it, but support has been superficial. I also didn't yet find the
level of technical detail I need in the information on the website and
in this list's archives.

The 8GB drive, when reformatted on a windows box with FAT32 as per
support instructions, surprisingly only comes out with a 1GB partition.
Inspecting the drive under linux, I find multiple partitions, with only
the first containing an a fat32 filesystem:

Platte /dev/sdc: 7927 MByte, 7927234560 Byte
244 Köpfe, 62 Sektoren/Spur, 1023 Zylinder, zusammen 15482880 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Festplattenidentifikation: 0xc3072e18

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sdc1            2048     2099199     1048576    b  W95 FAT32
/dev/sdc2         2099200     4196351     1048576   83  Linux
/dev/sdc3         4196352     6293503     1048576   83  Linux

On first glance, the others contain ext2 filesystems

# fsck -N /dev/sdc?
fsck von util-linux 2.20.1
[/sbin/fsck.vfat (1) -- /dev/sdc1] fsck.vfat /dev/sdc1 
[/sbin/fsck.ext2 (2) -- /dev/sdc2] fsck.ext2 /dev/sdc2 
[/sbin/fsck.ext2 (3) -- /dev/sdc3] fsck.ext2 /dev/sdc3 

but on further inspections do not contain a valid magic number in their superblocks, so they are effectively unformatted. I would therefore suspect that they are not being used by the probe.

Now the question:
What is the correct layout supposed to look like (primary/secondary, size, ID, FS-type)? I would like to get my probe back up and running.

Bonus question: 
What can I expect to find in point of files/data on the drive, that would tell me whether the probe was working correctly until I cut power and removed the drive?

Thanks,
Michael