mount mass storage

[JD]

On 02/05/2013 12:24 AM, Thufir Hawat wrote:
> Perhaps it's formatted wrong?
>
> root at dur:~#
> root at dur:~# fdisk -l
>
> Disk /dev/sda: 80.0 GB, 80026361856 bytes
> 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000d2c34
>
>     Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *        2048   152176639    76087296   83  Linux
> /dev/sda2       152178686   156301311     2061313    5  Extended
> /dev/sda5       152178688   156301311     2061312   82  Linux swap /
> Solaris
>
> Disk /dev/sdb: 30.8 GB, 30750031872 bytes
> 255 heads, 63 sectors/track, 3738 cylinders, total 60058656 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0004460a
>
>     Device Boot      Start         End      Blocks   Id  System
> /dev/sdb1            2048      499711      248832   83  Linux
> /dev/sdb2          501758    60057599    29777921    5  Extended
> /dev/sdb5          501760    60057599    29777920   8e  Linux LVM
>
> Disk /dev/mapper/dur-root: 28.4 GB, 28374466560 bytes
> 255 heads, 63 sectors/track, 3449 cylinders, total 55418880 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/mapper/dur-root doesn't contain a valid partition table
>
> Disk /dev/mapper/dur-swap_1: 2113 MB, 2113929216 bytes
> 255 heads, 63 sectors/track, 257 cylinders, total 4128768 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/mapper/dur-swap_1 doesn't contain a valid partition table
> root at dur:~#
>
>
>
> I'm looking at "doesn't contain a valid partition table" message...
>
>
>
> thanks,
>
> Thufir
>
>
OK, so I assume your pone has a 32GB flash, right?
It is being assigned linux "name" of /dev/sdb.

For starters, run
fsck -y /dev/sdb1    (which your message shows to be a Linux partition, 
but I am not sure what type of FS you have created on it.)
You have also set up partition 2 as an extended partition. WHY??? Wwere 
you planning on having many partitions???
You have set up partition 3 as a Linux Logical Volume. Why  did you do 
that? What did you want to "accomplish" by that?

Assuming you have a valid FS on partition 3, run

fsck -y /dev/sdb3

Once fsck finishes successfully,
try to manually mount partion 1 and 3:

Assuming fsck was successful:
mount /dev/sdb1  /mnt/my-phone-p1
mount /dev/sdb3  /mnt/my-phone-p3
Assuming of course the mount points exist. If not, create as necessary.
If the partitions mount and you can see your files, then you are in good 
shape.

Good luck.

If mount fails, then