Conecting to an Ubuntu server

[clskier]

I have set up an Ubuntu Server for use as a file and print server in my house. I now want to also use it as a charging/syncing station for all my various mp3 players and cameras around the house. I started with what I thought would be the easiest; A Sansa Fuze set to MSC mode. I expected to plug it into the USB port, mount it as a drive, and use Rsync to move files back and forth on a nightly basis. When I plug it in and sudo command "fdisk -l" I get the following:

Disk /dev/sdc: 4077 MB, 4077912064 bytes
126 heads, 62 sectors/track, 1019 cylinders
Units = cylinders of 7812 * 512 = 3999744 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6f20736b

This doesn't look like a partition table
Probably you selected the wrong device.

Device Boot Start End Blocks Id System
/dev/sdc1 ? 99608 245731 570754815+ 72 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(357, 116, 40) logical=(99607, 97, 11)
Partition 1 has different physical/logical endings:
phys=(357, 32, 45) logical=(245730, 44, 51)
Partition 1 does not end on cylinder boundary.
/dev/sdc2 ? 21594 269422 968014120 65 Novell Netware 386
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(288, 115, 43) logical=(21593, 80, 47)
Partition 2 has different physical/logical endings:
phys=(367, 114, 50) logical=(269421, 14, 42)
Partition 2 does not end on cylinder boundary.
/dev/sdc3 ? 239361 487188 968014096 79 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(366, 32, 33) logical=(239360, 18, 30)
Partition 3 has different physical/logical endings:
phys=(357, 32, 43) logical=(487187, 77, 39)
Partition 3 does not end on cylinder boundary.
/dev/sdc4 ? 369391 369398 27749+ d Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(372, 97, 50) logical=(369390, 104, 25)
Partition 4 has different physical/logical endings:
phys=(0, 10, 0) logical=(369397, 117, 33)
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

Do I need to reformat the disk or something?

Thanks

[CrowdAds]

[meetooman]

I don't know what going on here, but I imagine that the output of the dmesg command could also help.

[friartek]

It would appear that SanDisk is doing something really strange here. I have 3 Fuze and 1 e280 and all have the multiple partitions. One Fuze has the identical table as yours, the other 2(purchased recently) have the same block sizes but the start, stop, logical and physical numbers are different. The numbers don't add up anywhere near 4GB. When a Fuze is mounted it shows a 3.7GB partition(4GB less overhead - about what you would expect). My e280 is different, it has one W95 FAT32 partition with 7833300 blocks and one OS/2 hidden C: drive partition with 20480 blocks. The e280 partitions at least look reasonable. I'm not sure what kind of game SanDisk is playing here, especially with the Fuze. I am assuming that the firmware is aware of what is going on and how to present it properly through the USB connection.

This doesn't help me to get around my current problem with the older Fuze that currently won't boot. It reports needing 90GB of space for the database, then shuts down. When hooked to my Debian box I can't mount the Sansa Fuze, but the SD card mounts fine. Put the Fuze on a Mac and it mounts, but can't delete anything. It puts it in the trash and will not delete the trash. I guess I'll try a PC next to see if it works any better there. Strange!

Still looking, but so far have not been able to find a posting of what is really going on with the partition tables. It would appear that as strange as they look, it works -- most of the time.