mount mass storage

Tue Feb 5 18:47:58 UTC 2013

On 02/05/2013 01:27 AM, Thufir Hawat wrote:
> On Tue, 05 Feb 2013 00:48:58 -0700, JD wrote:
>
> Here's the console results:
>
> root at dur:~#
> root at dur:~# lsusb
> Bus 002 Device 002: ID 0e8d:0002 MediaTek Inc.
> Bus 004 Device 002: ID 062a:0000 Creative Labs Optical mouse
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> root at dur:~#
> 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:~#
> root at dur:~#
> root at dur:~# fsck -y /dev/sdb1
> fsck from util-linux 2.20.1
> e2fsck 1.42.5 (29-Jul-2012)
> /dev/sdb1 is mounted.
> e2fsck: Cannot continue, aborting.
>
>
> root at dur:~#
> root at dur:~# mount
> /dev/mapper/dur-root on / type ext4 (rw,errors=remount-ro)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> none on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> udev on /dev type devtmpfs (rw,mode=0755)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
> none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
> none on /run/shm type tmpfs (rw,nosuid,nodev)
> none on /run/user type tmpfs
> (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
> /dev/sdb1 on /boot type ext2 (rw)
> gvfsd-fuse on /run/user/thufir/gvfs type fuse.gvfsd-fuse
> (rw,nosuid,nodev,user=thufir)
> /dev/sda1 on /media/thufir/105b0cdc-04f1-4bed-9e22-fb55cb80224b type ext4
> (rw,nosuid,nodev,uhelper=udisks2)
> root at dur:~#
> root at dur:~#
> root at dur:~# fsck -y /dev/sdb3
> fsck from util-linux 2.20.1
> e2fsck 1.42.5 (29-Jul-2012)
> fsck.ext2: No such file or directory while trying to open /dev/sdb3
> Possibly non-existent device?
> root at dur:~#
> root at dur:~# mount /dev/sdb1  /mnt/my-phone-p1
> mount: mount point /mnt/my-phone-p1 does not exist
> root at dur:~#
> root at dur:~# ll /mnt/
> total 8
> drwxr-xr-x  2 root root 4096 Oct  9 07:59 ./
> drwxr-xr-x 22 root root 4096 Feb  1 16:27 ../
> root at dur:~#
> root at dur:~# mkdir /mnt/my-phone-p1
> root at dur:~#
> root at dur:~# mount /dev/sdb1  /mnt/my-phone-p1
> root at dur:~#
> root at dur:~# ll /mnt/my-phone-p1/
> total 71622
> drwxr-xr-x 4 root root     1024 Feb  1 16:28 ./
> drwxr-xr-x 3 root root     4096 Feb  5 00:20 ../
> -rw-r--r-- 1 root root   856464 Dec 11 11:26 abi-3.5.0-21-generic
> -rw-r--r-- 1 root root   856743 Jan  8 14:11 abi-3.5.0-22-generic
> -rw-r--r-- 1 root root   856743 Jan 24 05:34 abi-3.5.0-23-generic
> -rw-r--r-- 1 root root   154427 Dec 11 11:26 config-3.5.0-21-generic
> -rw-r--r-- 1 root root   154427 Jan  8 14:11 config-3.5.0-22-generic
> -rw-r--r-- 1 root root   154427 Jan 24 05:34 config-3.5.0-23-generic
> drwxr-xr-x 5 root root     1024 Feb  1 16:28 grub/
> -rw-r--r-- 1 root root 15708915 Dec 30 03:51 initrd.img-3.5.0-21-generic
> -rw-r--r-- 1 root root 15709349 Jan 17 22:48 initrd.img-3.5.0-22-generic
> -rw-r--r-- 1 root root 15707704 Feb  1 16:28 initrd.img-3.5.0-23-generic
> drwxr-xr-x 2 root root    12288 Dec 29 22:05 lost+found/
> -rw-r--r-- 1 root root   176764 Jan  3 14:47 memtest86+.bin
> -rw-r--r-- 1 root root   178944 Jan  3 14:47 memtest86+_multiboot.bin
> -rw------- 1 root root  2322150 Dec 11 11:26 System.map-3.5.0-21-generic
> -rw------- 1 root root  2323082 Jan  8 14:11 System.map-3.5.0-22-generic
> -rw------- 1 root root  2322953 Jan 24 05:34 System.map-3.5.0-23-generic
> -rw------- 1 root root  5176464 Dec 11 11:26 vmlinuz-3.5.0-21-generic
> -rw------- 1 root root  5176592 Jan  8 14:11 vmlinuz-3.5.0-22-generic
> -rw------- 1 root root  5176144 Jan 24 05:34 vmlinuz-3.5.0-23-generic
> root at dur:~#
> root at dur:~# mkdir /mnt/my-phone-p3
> root at dur:~#
> root at dur:~# mount /dev/sdb3  /mnt/my-phone-p3
> mount: special device /dev/sdb3 does not exist
> root at dur:~#
>
>
>
>> OK, so I assume your pone has a 32GB flash, right?
>> It is being assigned linux "name" of /dev/sdb.
> No.
>
> Ok, maybe I should've mentioned that there are two hard drives, on 30GB,
> one 80GB.  The 30GB hard drive is being used, the 80GB has some data
> which will eventually get pulled off and that drive will get reformatted.
> I think this is opening a bit of a pandora's box, and, to mix metaphors,
> it's a red herring ;)
>
> The phone has a 4GB flash drive which has previously mounted on an old
> install fine.
>
> -Thufir
>
>
Sorry, on my screen and my bad eyes, sdb5 looked like sdb3.
So, replace sdb3 in your commands with sdb5.
Be sure the mount point directories exist before you issue
the mount command.
If sdb5 is also healthy, (per fsck), then unmount
sdb1 and sdb5, unplug your phone, and plug it back in.
If you do  not get a banner (usually asking your permission to open
the media or the data files on the phone), then something is wrong with
your desktop setup or missing desktop utils.