Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: jjreina on August 02, 2010, 03:30:25 AM
-
Hi all, How can i mount by command-line a device storage usb? Have i to install any extesion??
Thanks
-
1) find out what device it is (dmesg | tail), let's assume sda1
2) mount /dev/sda1
-
When i tip:
tc@box:~$ sudo mount /dev/sda1 /mnt/usb
mount: /dev/sda1 is not a valid block device
and
tc@box:~$ sudo fdisk -l
Disk /dev/hda: 255 MB, 255328256 bytes
8 heads, 61 sectors/track, 1021 cylinders
Units = cylinders of 488 * 512 = 249856 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 5 1189+ b Win95 FAT32
/dev/hda2 6 10 1220 83 Linux
/dev/hda3
but not find the usb device.
and ->
tc@box:~$ dmesg | tail
tsc2003 0-0048: registered (driver version 0.9)
tsc2003 0-0048: zdown=9, zup=7
hc2-tsc2007: init() baseio=0x0378, irq=10, rx=500
hc2-tsc2007: touching = true
e100 0000:00:02.0: firmware: requesting e100/d102e_ucode.bin
e100: eth0 NIC Link is Up 100 Mbps Full Duplex
ext3: No journal on filesystem on loop3
e100: eth0 NIC Link is Down
Clocksource tsc unstable (delta = -233312665 ns)
e100: eth0 NIC Link is Up 10 Mbps Full Duplex
any suggestion?
Thanks
-
try to see which other block devices are connected by looking at /sys/block - you shoud find the hda directory for you harddrive, and another one for the usb device.
you can also try running blkid and post here the output.
-
Try following commands in a terminal window and post output:
fdisk -l /dev/sda
fdisk -l /dev/sdb
This would help to identify issues caused by wrong partitioning and/or file system types.
-
Hi all, thanks for answering
Whit /sys/block->
tc@box:/sys/block$ ls
hda loop15 loop22 loop3 loop37 loop44 loop51 loop59 loop66 loop73 loop9 ram7
loop0 loop16 loop23 loop30 loop38 loop45 loop52 loop6 loop67 loop74 ram0
loop1 loop17 loop24 loop31 loop39 loop46 loop53 loop60 loop68 loop75 ram1
loop10 loop18 loop25 loop32 loop4 loop47 loop54 loop61 loop69 loop76 ram2
loop11 loop19 loop26 loop33 loop40 loop48 loop55 loop62 loop7 loop77 ram3
loop12 loop2 loop27 loop34 loop41 loop49 loop56 loop63 loop70 loop78 ram4
loop13 loop20 loop28 loop35 loop42 loop5 loop57 loop64 loop71 loop79 ram5
loop14 loop21 loop29 loop36 loop43 loop50 loop58 loop65 loop72 loop8 ram6
tc@box:/sys/dev/block$ blkid
/dev/hda1: SEC_TYPE="msdos" LABEL="APPS" UUID="822D-ACB8" TYPE="vfat"
/dev/hda3: UUID="3a4d7122-277a-4a50-8d38-93f21c7f75a1" SEC_TYPE="ext2" TYPE="ext3"
tc@box:~$ fdisk -l /dev/sda
fdisk: can't open '/dev/sda': No such device or address
tc@box:~$ fdisk -l /dev/sdb
fdisk: can't open '/dev/sdb': No such device or address
thanks for your help
-
Could you be more specific what your "device storage usb" exactly is?
Are you sure same PC has a 255MB hdd and has also a USB port?
What/where is loop3 ?
losetup /dev/loop3
-
Could you be more specific what your "device storage usb" exactly is?
is a 2 GB USB memory
What/where is loop3 ?
tc@box:~$ losetup /dev/loop3
/dev/loop3: [0303]:5986 (/mnt/hda3/tce/libusb.tcz)
-
As you happen to have libusb installed, do you also happen to have usb-utils installed?
If so, you could:
sudo lsusb
On a sidenote: the output of fdisk for your /dev/hda looks a bit strange to me...
-
Sorry but i am very noob whit linux and tc me only worked with Ubuntu :'(
tc@box:$ sudo lsusb
lsusb: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
-
Hmm, missing lib is in libusb, which losetup shows to be present...
try
dmesg |grep -i usb
-
tc@box:~$ dmesg |grep -i usb
Kernel command line: quiet nodhcp noswap vga=789 logo.nologo nousb local=hda3 tce=hda3 console=null
usbcore: USB support disabled
Initializing USB Mass Storage driver...
-
*cough*
It doesn't make sense to use a bootparam "nousb" and then expecting usb to work... :o
-
Sorry, but I got the boot file with parameters set and did not tell me anything.
Try to change it.
Thank you very much and sorry for the inconvenience.
Ok, edit boot file and i could mount usb not problem.
Thanks