USB can not read all drive

manolakis · 12-02-2007, 05:13 AM

Hi there

I have a 128MB usb, and my laptop reads only 48MB. Does anybody know how can I fix it?

Thanks

tredegar · 12-02-2007, 06:12 AM

Quote:

Does anybody know how can I fix it?

Not without you telling us how it is partitioned, how it is mounted and what filesystem(s) it is formatted with

manolakis · 12-02-2007, 05:20 PM

Hi

Could you please tell me how can I find that out?

I am quite newbie to linux as you can realize.

Thanks

tredegar · 12-02-2007, 05:50 PM

Quote:

Could you please tell me how can I find that out?

Of course... Plug in your USB thingy, wait a moment, (choose "Open" if in doubt) then, in a terminal, konsole or whatever try these commands

Code:

fdisk -l

which will tell you about the partitions linux recognises, and how they they are formatted. Then,

Code:

mount

will tell you about how they are, or aren't, mounted

Note: you may have to be root for these commands to work (depends on your distro, and its security settings).
Just work out how to make these commands work (experiment a little), and post their output here.

The [Search] button on this page is quite useful, as may be the "related threads" list at the bottom of this page,

manolakis · 12-04-2007, 07:22 PM

These are the outputs

Quote:

debian:/home/manolakis# fdisk -l

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 9543 76654116 83 Linux
/dev/hda2 9544 9729 1494045 5 Extended
/dev/hda5 9544 9729 1494013+ 82 Linux swap / Solaris

Disk /dev/sda: 128 MB, 128450560 bytes
4 heads, 62 sectors/track, 1011 cylinders
Units = cylinders of 248 * 512 = 126976 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 395 48949 b W95 FAT32
/dev/sda2 396 512 14508 83 Linux
/dev/sda3 513 1011 61876 83 Linux

Disk /dev/sdb: 1 MB, 1474560 bytes
1 heads, 3 sectors/track, 960 cylinders
Units = cylinders of 3 * 512 = 1536 bytes

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

Device Boot Start End Blocks Id System
/dev/sdb1 ? 623257122 679486963 84344761 69 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(68, 13, 10) logical=(623257121, 0, 3)
Partition 1 has different physical/logical endings:
phys=(288, 115, 43) logical=(679486962, 0, 1)
Partition 1 does not end on cylinder boundary.
/dev/sdb2 ? 567173161 1190466982 934940732+ 73 Unknown
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(371, 114, 37) logical=(567173160, 0, 2)
Partition 2 has different physical/logical endings:
phys=(366, 32, 33) logical=(1190466981, 0, 3)
Partition 2 does not end on cylinder boundary.
/dev/sdb3 ? 858 858 0 74 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(371, 114, 37) logical=(857, 0, 3)
Partition 3 has different physical/logical endings:
phys=(372, 97, 50) logical=(857, 0, 2)
Partition 3 does not end on cylinder boundary.
/dev/sdb4 1 1145037824 1717556736 0 Empty
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 0) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
phys=(0, 0, 0) logical=(1145037823, 0, 3)
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

Quote:

# mount
/dev/hda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sdb on /media/usbdisk type vfat (rw,noexec,nosuid,nodev,quiet,shortname=mixed,uid=1000,gid=1000,umask=077,iocharset=utf8)
/dev/sda1 on /media/usbdisk-1 type vfat (rw,noexec,nosuid,nodev,quiet,shortname=mixed,uid=1000,gid=1000,umask=077,iocharset=utf8)

Thanks

tredegar · 12-05-2007, 05:02 AM

There is something wrong with the partition table on sdb.
I do not think this is fixable other than by re-partioning it, and then reformatting it.