Hi,
Following up on my previous e-mail, I wanted to mention that two usb interfaces are being recognized. Here is the relevant output of
% usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bb4 ProdID=0c02 Rev=02.22 S: Manufacturer=ARNOVA 10 S: Product=ARNOVA 10 S: SerialNumber=11223344 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I want to mount this as a USB storage device, so that i can access the filesystem.
Question: How do I mount the first interface?
Many thanks and best wishes, Ranjan
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Following up on my previous e-mail, I wanted to mention that two usb interfaces are being recognized. Here is the relevant output of
% usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bb4 ProdID=0c02 Rev=02.22 S: Manufacturer=ARNOVA 10 S: Product=ARNOVA 10 S: SerialNumber=11223344 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I want to mount this as a USB storage device, so that i can access the filesystem.
Question: How do I mount the first interface?
Sorry to add to my e-mail, the output of lsusb -v is as follows:
$ lsusb -v -s 001:024
Bus 001 Device 024: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1 / Magic / Tattoo (Debug) Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0bb4 High Tech Computer Corp. idProduct 0x0c02 Dream / ADP1 / G1 / Magic / Tattoo (Debug) bcdDevice 2.22 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 256mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
And the output of:
$ lsusb -D /dev/bus/usb/001/001 Device: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 3.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12
and
$ lsusb -D /dev/bus/usb/001/024 Device: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1 / Magic / Tattoo (Debug) Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0bb4 High Tech Computer Corp. idProduct 0x0c02 Dream / ADP1 / G1 / Magic / Tattoo (Debug) bcdDevice 2.22 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 256mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
All I want to do is to be able to mount the usb as a storage device and then edit files in it.
Many thanks again and best wishes, Ranjan
____________________________________________________________ GET FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at http://www.inbox.com/smileys Works with AIM?, MSN? Messenger, Yahoo!? Messenger, ICQ?, Google Talk? and most webmails
On 11/22/2012 02:38 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Following up on my previous e-mail, I wanted to mention that two usb interfaces are being recognized. Here is the relevant output of
% usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bb4 ProdID=0c02 Rev=02.22 S: Manufacturer=ARNOVA 10 S: Product=ARNOVA 10 S: SerialNumber=11223344 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I want to mount this as a USB storage device, so that i can access the filesystem.
Question: How do I mount the first interface?
Sorry to add to my e-mail, the output of lsusb -v is as follows:
$ lsusb -v -s 001:024
Bus 001 Device 024: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1 / Magic / Tattoo (Debug) Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0bb4 High Tech Computer Corp. idProduct 0x0c02 Dream / ADP1 / G1 / Magic / Tattoo (Debug) bcdDevice 2.22 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 256mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
And the output of:
$ lsusb -D /dev/bus/usb/001/001 Device: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 3.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12
and
$ lsusb -D /dev/bus/usb/001/024 Device: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1 / Magic / Tattoo (Debug) Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0bb4 High Tech Computer Corp. idProduct 0x0c02 Dream / ADP1 / G1 / Magic / Tattoo (Debug) bcdDevice 2.22 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 256mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
All I want to do is to be able to mount the usb as a storage device and then edit files in it.
Many thanks again and best wishes, Ranjan
I didn't catch your original email, so please excuse if I answer a question you didn't ask.
You want to mount a usb device that for some reason doesn't automount?
Try these commands in a console window:
[1] unplug the usb device
[2] > ls /dev
[3] plug in the device
[4] > ls /dev
Now identify the new device in /dev by comparing the output from [2] and [4].
There should be a new device (probably) named /dev/sd?n - where "?" is a letter ("a" - "z") and "n" is a number. There should be multiple devices, the device without a number, and 1 or more devices, one for each partition in the devices's filesystem. If the device has no partitions, the you only get /dev/sd?.
On my box, I always get devices "/dev/sdd" and "/dev/sdd1", but it depends on the storage devices in your system.
This information should also be in /var/log/messages.
If a new device doesn't appear in /dev, then someone smarter than me will be required.
[5] > mkdir <some-directory> - I usually do > mkdir X
[6] > sudo mount /dev/sd?n (or /dev/sd?) <some-directory>
If it fails to mount, then you should check the mount manpage for some options that might help ( -t ), but mount usually does the right thing.
You could also post the output of [6] to this list and someone will figure it out.
Regards,
John
Hi John,
Thanks for helping out!
On Thu, 22 Nov 2012 18:08:24 -0800 John Wendel jwendel10@comcast.net wrote:
On 11/22/2012 02:38 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Following up on my previous e-mail, I wanted to mention that two usb interfaces are being recognized. Here is the relevant output of
% usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bb4 ProdID=0c02 Rev=02.22 S: Manufacturer=ARNOVA 10 S: Product=ARNOVA 10 S: SerialNumber=11223344 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I want to mount this as a USB storage device, so that i can access the filesystem.
Question: How do I mount the first interface?
Sorry to add to my e-mail, the output of lsusb -v is as follows:
$ lsusb -v -s 001:024
Bus 001 Device 024: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1 / Magic / Tattoo (Debug) Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0bb4 High Tech Computer Corp. idProduct 0x0c02 Dream / ADP1 / G1 / Magic / Tattoo (Debug) bcdDevice 2.22 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 256mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
And the output of:
$ lsusb -D /dev/bus/usb/001/001 Device: ID 1d6b:0002 Linux Foundation 2.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 3.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12
and
$ lsusb -D /dev/bus/usb/001/024 Device: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1 / Magic / Tattoo (Debug) Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0bb4 High Tech Computer Corp. idProduct 0x0c02 Dream / ADP1 / G1 / Magic / Tattoo (Debug) bcdDevice 2.22 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 55 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 256mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk (Zip) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 66 bInterfaceProtocol 1 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
All I want to do is to be able to mount the usb as a storage device and then edit files in it.
Many thanks again and best wishes, Ranjan
I didn't catch your original email, so please excuse if I answer a question you didn't ask.
You want to mount a usb device that for some reason doesn't automount?
Try these commands in a console window:
[1] unplug the usb device
[2] > ls /dev
[3] plug in the device
[4] > ls /dev
Now identify the new device in /dev by comparing the output from [2] and [4].
The output differs by sdb and sdc
There should be a new device (probably) named /dev/sd?n - where "?" is a letter ("a" - "z") and "n" is a number. There should be multiple devices, the device without a number, and 1 or more devices, one for each partition in the devices's filesystem. If the device has no partitions, the you only get /dev/sd?.
On my box, I always get devices "/dev/sdd" and "/dev/sdd1", but it depends on the storage devices in your system.
This information should also be in /var/log/messages.
This matches the information above:
Nov 22 20:27:18 kharkai kernel: [25927.936207] sd 27:0:0:0: [sdb] Attached SCSI removable disk Nov 22 20:27:18 kharkai kernel: [25927.937450] sd 27:0:0:1: [sdc] Attached SCSI removable disk
If a new device doesn't appear in /dev, then someone smarter than me will be required.
[5] > mkdir <some-directory> - I usually do > mkdir X
mkdir /mnt/myusb
[6] > sudo mount /dev/sd?n (or /dev/sd?) <some-directory>
If it fails to mount, then you should check the mount manpage for some options that might help ( -t ), but mount usually does the right thing.
sudo mount /dev/sdb /mnt/myusb
yields the error:
mount: /dev/sdb: mount failed: Invalid argument
(same with /dev/sdc)
Not sure what to use with the -t argument. Here is the output of
sudo mount -l
$ sudo mount -l proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel) devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=1001772k,nr_inodes=250443,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel) tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755) /dev/sda2 on / type ext4 (rw,relatime,seclabel,data=ordered) [_Fedora-17-x86_6] securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,seclabel,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=26,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) configfs on /sys/kernel/config type configfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel) tmpfs on /media type tmpfs (rw,nosuid,nodev,noexec,relatime,seclabel,mode=755) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel) debugfs on /sys/kernel/debug type debugfs (rw,relatime) /dev/sda5 on /home type ext4 (rw,relatime,seclabel,data=ordered) [/usr/local1] /dev/sda6 on /usr/local type ext4 (rw,relatime,seclabel,data=ordered) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) gvfs-fuse-daemon on /run/user/maitra/gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
You could also post the output of [6] to this list and someone will figure it out.
Regards,
John
Many thanks again and best wishes! Ranjan
On 11/23/2012 10:41 AM, Ranjan Maitra wrote:
I didn't catch your original email, so please excuse if I answer a question you didn't ask.
You want to mount a usb device that for some reason doesn't automount?
Try these commands in a console window:
[1] unplug the usb device
[2] > ls /dev
[3] plug in the device
[4] > ls /dev
Now identify the new device in /dev by comparing the output from [2] and [4].
The output differs by sdb and sdc
Are you saying you don't have an sdb1 or sdc1?
If the device you have is a storage device which has partition table defined it you should get /dev/sdbX (where X is an integer). If you're not getting this, the device doesn't have a valid partition table.
On 11/22/2012 06:41 PM, Ranjan Maitra wrote:
sudo mount /dev/sdb /mnt/myusb
The "blkid" command will give you more info about the device
sudo blkid -p /dev/sdb
will show you the partition type ( like PTTYPE="dos" ), if there is one.
sudo blkid -p /dev/sdb1
will show you the filesystem type of partition 1
/dev/sdd1: LABEL="WD1000" UUID="694b6f8b-42e6-49e8-be51-5806e5e315e9" SEC_TYPE="ext2" VERSION="1.0" TYPE="ext3" USAGE="filesystem" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x83" PART_ENTRY_NUMBER="1"
try
sudo mount /dev/sdb1 /mnt/myusb
The -t argument takes a filesystem type - "vfat" is very commonly used on usb devices, so try
sudo mount -t vfat /dev/sdb1 /mnt/myusb
But mount should figure this out automagically.
Regards,
John
On Fri, 23 Nov 2012 11:17:47 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
On 11/23/2012 10:41 AM, Ranjan Maitra wrote:
I didn't catch your original email, so please excuse if I answer a question you didn't ask.
You want to mount a usb device that for some reason doesn't automount?
Try these commands in a console window:
[1] unplug the usb device
[2] > ls /dev
[3] plug in the device
[4] > ls /dev
Now identify the new device in /dev by comparing the output from [2] and [4].
The output differs by sdb and sdc
Are you saying you don't have an sdb1 or sdc1?
If the device you have is a storage device which has partition table defined it you should get /dev/sdbX (where X is an integer). If you're not getting this, the device doesn't have a valid partition table.
Yes, this is correct. Any suggestions then?
Thanks, Ranjan
____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!
On 11/22/2012 06:41:21 PM, Ranjan Maitra wrote:
On 11/22/2012 02:38 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Following up on my previous e-mail, I wanted to mention that two
usb
interfaces are being recognized. Here is the relevant output of
% usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480 MxCh=
0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bb4 ProdID=0c02 Rev=02.22 S: Manufacturer=ARNOVA 10 S: Product=ARNOVA 10 S: SerialNumber=11223344 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I want to mount this as a USB storage device, so that i can
access the
filesystem.
Question: How do I mount the first interface?
Sorry to add to my e-mail, the output of lsusb -v is as follows:
[snip]
Here's an alternate method.
Your disks should each have a unique UUID identifier, that can be used to create a fstab entry.
For example, when I plug in my USB MP3 player, /dev/disk/by-uuid gets a symlink 1839-015E, symbolic link to `../../sdb'. Not much use. However, I have an entry in /etc/fstab: UUID=1839-015E /Media/Sansa2 ..., which allows me to access its contents by mounting /Media/Sansa2.
This works on Fedora 17. On 16, the link was in a different directory, but the principle was the same.
Good luck.
On 11/23/2012 11:30 AM, Ranjan Maitra wrote:
On Fri, 23 Nov 2012 11:17:47 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
Are you saying you don't have an sdb1 or sdc1?
If the device you have is a storage device which has partition table defined it you should get /dev/sdbX (where X is an integer). If you're not getting this, the device doesn't have a valid partition table.
Yes, this is correct. Any suggestions then?
As root.....(example below for my USB thumb drive)
[root@meimei ~]# parted /dev/sdb GNU Parted 3.0 Using /dev/sdg Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print <----user input
Model: Ut165 (scsi) Disk /dev/sdg: 2022MB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags:
Number Start End Size File system Flags 1 0.00B 2022MB 2022MB fat32
(parted) quit <----user input
On Thu, 22 Nov 2012 19:39:20 -0800 Geoffrey Leach geoff@hughes.net wrote:
On 11/22/2012 06:41:21 PM, Ranjan Maitra wrote:
On 11/22/2012 02:38 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Following up on my previous e-mail, I wanted to mention that two
usb
interfaces are being recognized. Here is the relevant output of
% usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480 MxCh=
0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bb4 ProdID=0c02 Rev=02.22 S: Manufacturer=ARNOVA 10 S: Product=ARNOVA 10 S: SerialNumber=11223344 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I want to mount this as a USB storage device, so that i can
access the
filesystem.
Question: How do I mount the first interface?
Sorry to add to my e-mail, the output of lsusb -v is as follows:
[snip]
Here's an alternate method.
Your disks should each have a unique UUID identifier, that can be used to create a fstab entry.
For example, when I plug in my USB MP3 player, /dev/disk/by-uuid gets a symlink 1839-015E, symbolic link to `../../sdb'. Not much use. However, I have an entry in /etc/fstab: UUID=1839-015E /Media/Sansa2 ..., which allows me to access its contents by mounting /Media/Sansa2.
Thanks! Does this happen only upon mounting. Because I don't have such an entry corresponding to /dev/sdb or /dev/sdc
$ ll /dev/disk/by-uuid total 0 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 359f5eea-47cb-42c4-b96e-974b6f07ad19 -> ../../sda3
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 d0b7bacc-879a-4b34-9ddd-76f438a28c5d -> ../../sda6
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 e082b796-2fc7-449b-95d8-a39ef6a29891 -> ../../sda2
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 EEE4584BE4581863 -> ../../sda1
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 f2ed8f21-da63-4def-a674-afdc90e448c5 -> ../../sda5
(I am on F17.)
Many thanks, Ranjan
Thanks again, John! This does not work for me.
On Thu, 22 Nov 2012 19:23:27 -0800 John Wendel jwendel10@comcast.net wrote:
On 11/22/2012 06:41 PM, Ranjan Maitra wrote:
sudo mount /dev/sdb /mnt/myusb
The "blkid" command will give you more info about the device
sudo blkid -p /dev/sdb
will show you the partition type ( like PTTYPE="dos" ), if there is one.
sudo blkid -p /dev/sdb1
will show you the filesystem type of partition 1
/dev/sdd1: LABEL="WD1000" UUID="694b6f8b-42e6-49e8-be51-5806e5e315e9" SEC_TYPE="ext2" VERSION="1.0" TYPE="ext3" USAGE="filesystem" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x83" PART_ENTRY_NUMBER="1"
sudo blkid -p /dev/sdb error: /dev/sdb: No medium found
sudo blkid -p /dev/sdc error: /dev/sdc: No medium found
Btw, for context, here is the background to this device: it is a tablet (ARNOVA 10). From my e-mail of earlier this afternoon....
"I am using F17 (LXDE) but this is not really the issue here.
So, I had this old Arnova 10 tablet which I wanted to unroot, and install Android 2.2 (from 2.1) so I flashed the apprpriate image using the USB connection and all appeared well.
However, during the touchscreen calibration stage, the calibration did not get done correctly (or much at all from what I can tell). Looking around, this seems to be happen and the way to get around it is to go in and remove the necessary files. The trouble however is that I can no longer mount the USB so I can not enter the device. When I mount the USB onto my F17, I get the following:
Bus 001 Device 006: ID 0bb4:0c02 High Tech Computer Corp. Dream / ADP1 / G1 / Magic / Tattoo (Debug)
however, this does not get mounted. Actually, the screen of the tablet says "USB connected" but unfortunately also "USB debugging connected". (And the latter is the problem: the issue appears to be that the latter has to be disabled, which can only be done using the touchscreen, which is not recognized.) Btw, I can not attach a mouse or a keyboard to the tablet either because the USB mode has to be activated (done using a touchscreen again). Also, there is some paperclip press on some reset hole that should reset the device to factory settings, but absolutely nothing happens (my fingers become sore from pushing the clip interminably).
Question: is there a way to "force" linux (F17) to mount the USB as a storage device? I understand the naivette of this question, but is something else possible?"
Many thanks again and best wishes!
Ranjan
try
sudo mount /dev/sdb1 /mnt/myusb
The -t argument takes a filesystem type - "vfat" is very commonly used on usb devices, so try
sudo mount -t vfat /dev/sdb1 /mnt/myusb
But mount should figure this out automagically.
Regards,
John
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 11/22/2012 08:21:20 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 19:39:20 -0800 Geoffrey Leach geoff@hughes.net wrote:
On 11/22/2012 06:41:21 PM, Ranjan Maitra wrote:
On 11/22/2012 02:38 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Hi,
Following up on my previous e-mail, I wanted to mention that
two
usb
interfaces are being recognized. Here is the relevant output
of
% usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480
MxCh=
0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0bb4 ProdID=0c02 Rev=02.22 S: Manufacturer=ARNOVA 10 S: Product=ARNOVA 10 S: SerialNumber=11223344 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I want to mount this as a USB storage device, so that i can
access the
filesystem.
Question: How do I mount the first interface?
Sorry to add to my e-mail, the output of lsusb -v is as
follows:
[snip]
Here's an alternate method.
Your disks should each have a unique UUID identifier, that can be
used
to create a fstab entry.
For example, when I plug in my USB MP3 player, /dev/disk/by-uuid
gets a
symlink 1839-015E, symbolic link to `../../sdb'. Not much use.
However,
I have an entry in /etc/fstab: UUID=1839-015E /Media/Sansa2 ..., which allows me to access its contents by mounting /Media/Sansa2.
Thanks! Does this happen only upon mounting. Because I don't have such an entry corresponding to /dev/sdb or /dev/sdc
$ ll /dev/disk/by-uuid total 0 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 359f5eea-47cb-42c4-b96e-974b6f07ad19 -> ../../sda3
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 d0b7bacc-879a-4b34-9ddd-76f438a28c5d -> ../../sda6
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 e082b796-2fc7-449b-95d8-a39ef6a29891 -> ../../sda2
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 EEE4584BE4581863 -> ../../sda1
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 f2ed8f21-da63-4def-a674-afdc90e448c5 -> ../../sda5
(I am on F17.)
This is before mounting. Looks like your UUID is 359f5eea-47cb-42c4- b96e-974b6f07ad19. I'll bet that if you look in /etc/fstab, you'll find that there's an entry UUID=d0b7bacc-879a-4b34-9ddd-76f438a28c5d ... make a directory for your new disk and then make an entry for your new UUID that mimics the existing one, with appropriate changes. Then mount that directory.
On Fri, 23 Nov 2012 12:07:01 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
On 11/23/2012 11:30 AM, Ranjan Maitra wrote:
On Fri, 23 Nov 2012 11:17:47 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
Are you saying you don't have an sdb1 or sdc1?
If the device you have is a storage device which has partition table defined it you should get /dev/sdbX (where X is an integer). If you're not getting this, the device doesn't have a valid partition table.
Yes, this is correct. Any suggestions then?
As root.....(example below for my USB thumb drive)
[root@meimei ~]# parted /dev/sdb GNU Parted 3.0 Using /dev/sdg Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print <----user input
Model: Ut165 (scsi) Disk /dev/sdg: 2022MB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags:
Number Start End Size File system Flags 1 0.00B 2022MB 2022MB fat32
(parted) quit <----user input
Thanks again! Same story....
sudo parted /dev/sdb Error: Error opening /dev/sdb: No medium found Retry/Cancel?
Many thanks and best wishes! Ranjan
____________________________________________________________ Receive Notifications of Incoming Messages Easily monitor multiple email accounts & access them with a click. Visit http://www.inbox.com/notifier and check it out!
On 11/23/2012 12:27 PM, Ranjan Maitra wrote:
sudo blkid -p /dev/sdb error: /dev/sdb: No medium found
sudo blkid -p /dev/sdc error: /dev/sdc: No medium found
Btw, for context, here is the background to this device: it is a tablet (ARNOVA 10). From my e-mail of earlier this afternoon....
If I read this correctly..... You are plugging this tablet into at running F17 system via a USB connector? And, you're expecting to access the tablet's file system on the F17 system?
Thanks, Geoff! Sorry I do not understand (please see below):
On Thu, 22 Nov 2012 20:28:24 -0800 Geoffrey Leach geoff@hughes.net wrote:
On 11/22/2012 08:21:20 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 19:39:20 -0800 Geoffrey Leach geoff@hughes.net wrote:
On 11/22/2012 06:41:21 PM, Ranjan Maitra wrote:
On 11/22/2012 02:38 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
> Hi, > > Following up on my previous e-mail, I wanted to mention that
two
usb
> interfaces are being recognized. Here is the relevant output
of
> > % usb-devices > > T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480
MxCh=
0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=0bb4 ProdID=0c02 Rev=02.22 > S: Manufacturer=ARNOVA 10 > S: Product=ARNOVA 10 > S: SerialNumber=11223344 > C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 > Driver=usb-storage > I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 > Prot=01 Driver=(none) > > I want to mount this as a USB storage device, so that i can
access the
> filesystem. > > Question: How do I mount the first interface? Sorry to add to my e-mail, the output of lsusb -v is as
follows:
[snip]
Here's an alternate method.
Your disks should each have a unique UUID identifier, that can be
used
to create a fstab entry.
For example, when I plug in my USB MP3 player, /dev/disk/by-uuid
gets a
symlink 1839-015E, symbolic link to `../../sdb'. Not much use.
However,
I have an entry in /etc/fstab: UUID=1839-015E /Media/Sansa2 ..., which allows me to access its contents by mounting /Media/Sansa2.
Thanks! Does this happen only upon mounting. Because I don't have such an entry corresponding to /dev/sdb or /dev/sdc
$ ll /dev/disk/by-uuid total 0 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 359f5eea-47cb-42c4-b96e-974b6f07ad19 -> ../../sda3
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 d0b7bacc-879a-4b34-9ddd-76f438a28c5d -> ../../sda6
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 e082b796-2fc7-449b-95d8-a39ef6a29891 -> ../../sda2
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 EEE4584BE4581863 -> ../../sda1
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 f2ed8f21-da63-4def-a674-afdc90e448c5 -> ../../sda5
(I am on F17.)
This is before mounting. Looks like your UUID is 359f5eea-47cb-42c4- b96e-974b6f07ad19. I'll bet that if you look in /etc/fstab, you'll find that there's an entry UUID=d0b7bacc-879a-4b34-9ddd-76f438a28c5d ... make a directory for your new disk and then make an entry for your new UUID that mimics the existing one, with appropriate changes. Then mount that directory. --
The entry for UID=359f5eea-47cb-42c4-b96e-974b6f07ad19 is for swap.
Here is my /etc/fstab.
# # /etc/fstab # Created by anaconda on Tue May 29 12:02:11 2012 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=e082b796-2fc7-449b-95d8-a39ef6a29891 / ext4 defaul ts 1 1 UUID=f2ed8f21-da63-4def-a674-afdc90e448c5 /home ext4 defaults 1 2 UUID=d0b7bacc-879a-4b34-9ddd-76f438a28c5d /usr/local ext4 defaults 1 2 UUID=359f5eea-47cb-42c4-b96e-974b6f07ad19 swap swap defaults 0 0
What should I be doing?
Many thanks again!
Ranjan
On Fri, 23 Nov 2012 12:39:21 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
On 11/23/2012 12:27 PM, Ranjan Maitra wrote:
sudo blkid -p /dev/sdb error: /dev/sdb: No medium found
sudo blkid -p /dev/sdc error: /dev/sdc: No medium found
Btw, for context, here is the background to this device: it is a tablet (ARNOVA 10). From my e-mail of earlier this afternoon....
If I read this correctly..... You are plugging this tablet into at running F17 system via a USB connector? And, you're expecting to access the tablet's file system on the F17 system?
Yes, and as I mentioned earlier, it has been possible in the past (before this USB debugging mode got activated).
Many thanks, Ranjan
____________________________________________________________ FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop! Check it out at http://www.inbox.com/marineaquarium
On 11/23/2012 03:16 PM, Ranjan Maitra wrote:
On Fri, 23 Nov 2012 12:39:21 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
On 11/23/2012 12:27 PM, Ranjan Maitra wrote:
sudo blkid -p /dev/sdb error: /dev/sdb: No medium found
sudo blkid -p /dev/sdc error: /dev/sdc: No medium found
Btw, for context, here is the background to this device: it is a tablet (ARNOVA 10). From my e-mail of earlier this afternoon....
If I read this correctly..... You are plugging this tablet into at running F17 system via a USB connector? And, you're expecting to access the tablet's file system on the F17 system?
Yes, and as I mentioned earlier, it has been possible in the past (before this USB debugging mode got activated).
Right..... To summarize.... Everything was working fine. Then you "flashed" the tablet with an image to change its OS or configuration. When you powered it up you had problems with the touchscreen and you've got USB debugging enabled and other problems....like not being able to get to the the file system of the tablet like you used to....
Sounds to me like all your problems are on the tablet side and unless it acts correctly to service the USB connection there isn't much to be done on the F17 side. The "No medium found" error seems to bear it out.
Contact Arnova support?
Don't know anything about the Arnova products.... But all of the tablets I've seen use the (from off condition) hold volume down button and then hold power on button until the reset screen is displayed to do a hard reset.
On Fri, 23 Nov 2012 15:42:10 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
On 11/23/2012 03:16 PM, Ranjan Maitra wrote:
On Fri, 23 Nov 2012 12:39:21 +0800 Ed Greshko Ed.Greshko@greshko.com wrote:
On 11/23/2012 12:27 PM, Ranjan Maitra wrote:
sudo blkid -p /dev/sdb error: /dev/sdb: No medium found
sudo blkid -p /dev/sdc error: /dev/sdc: No medium found
Btw, for context, here is the background to this device: it is a tablet (ARNOVA 10). From my e-mail of earlier this afternoon....
If I read this correctly..... You are plugging this tablet into at running F17 system via a USB connector? And, you're expecting to access the tablet's file system on the F17 system?
Yes, and as I mentioned earlier, it has been possible in the past (before this USB debugging mode got activated).
Sounds to me like all your problems are on the tablet side and unless it acts correctly to service the USB connection there isn't much to be done on the F17 side. The "No medium found" error seems to bear it out.
Thanks! I was just wondering if this could still be mounted? The USB is "seen" as per usb-devices (as a storage and some other device) with two interfaces, so as suggested in the earlier e-mail, I was thinking that it may perhaps be possible.
Don't know anything about the Arnova products.... But all of the tablets I've seen use the (from off condition) hold volume down button and then hold power on button until the reset screen is displayed to do a hard reset.
Yes, but pressing a pin into the reset hole while holding the volume up button down does not seem to have any (much, if you count in my sore fingers) effect. Perhaps that button is bad.
Many thanks again for all the help and the discussion (nothing may come out of it, but I am learning new things here too).
Best wishes, Ranjan
On Thu, 22 Nov 2012 20:28:24 -0800 Geoffrey Leach geoff@hughes.net wrote:
On 11/22/2012 08:21:20 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 19:39:20 -0800 Geoffrey Leach geoff@hughes.net wrote:
On 11/22/2012 06:41:21 PM, Ranjan Maitra wrote:
On 11/22/2012 02:38 PM, Ranjan Maitra wrote:
On Thu, 22 Nov 2012 15:57:46 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
> Hi, > > Following up on my previous e-mail, I wanted to mention that
two
usb
> interfaces are being recognized. Here is the relevant output
of
> > % usb-devices > > T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 15 Spd=480
MxCh=
0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=0bb4 ProdID=0c02 Rev=02.22 > S: Manufacturer=ARNOVA 10 > S: Product=ARNOVA 10 > S: SerialNumber=11223344 > C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=256mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 > Driver=usb-storage > I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 > Prot=01 Driver=(none) > > I want to mount this as a USB storage device, so that i can
access the
> filesystem. > > Question: How do I mount the first interface? Sorry to add to my e-mail, the output of lsusb -v is as
follows:
[snip]
Here's an alternate method.
Your disks should each have a unique UUID identifier, that can be
used
to create a fstab entry.
For example, when I plug in my USB MP3 player, /dev/disk/by-uuid
gets a
symlink 1839-015E, symbolic link to `../../sdb'. Not much use.
However,
I have an entry in /etc/fstab: UUID=1839-015E /Media/Sansa2 ..., which allows me to access its contents by mounting /Media/Sansa2.
Thanks! Does this happen only upon mounting. Because I don't have such an entry corresponding to /dev/sdb or /dev/sdc
$ ll /dev/disk/by-uuid total 0 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 359f5eea-47cb-42c4-b96e-974b6f07ad19 -> ../../sda3
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 d0b7bacc-879a-4b34-9ddd-76f438a28c5d -> ../../sda6
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 e082b796-2fc7-449b-95d8-a39ef6a29891 -> ../../sda2
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 EEE4584BE4581863 -> ../../sda1
lrwxrwxrwx. 1 root root 10 Nov 22 12:06 f2ed8f21-da63-4def-a674-afdc90e448c5 -> ../../sda5
(I am on F17.)
This is before mounting. Looks like your UUID is 359f5eea-47cb-42c4- b96e-974b6f07ad19. I'll bet that if you look in /etc/fstab, you'll find that there's an entry UUID=d0b7bacc-879a-4b34-9ddd-76f438a28c5d ... make a directory for your new disk and then make an entry for your new UUID that mimics the existing one, with appropriate changes. Then mount that directory.
Hi,
Continuing on with this, I have the following entries in the directories in /dev/disk (sorry for the mangling):
$ ls -l */ by-id/: total 0 lrwxrwxrwx. 1 root root 9 Nov 23 18:04 ata-HITACHI_HTS541612J9SA00_SB3D41EWGSZ5RL -> ../../sda lrwxrwxrwx. 1 root root 10 Nov 23 18:04 ata-HITACHI_HTS541612J9SA00_SB3D41EWGSZ5RL-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 ata-HITACHI_HTS541612J9SA00_SB3D41EWGSZ5RL-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 ata-HITACHI_HTS541612J9SA00_SB3D41EWGSZ5RL-part3 -> ../../sda3 lrwxrwxrwx. 1 root root 10 Nov 23 18:04 ata-HITACHI_HTS541612J9SA00_SB3D41EWGSZ5RL-part4 -> ../../sda4 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 ata-HITACHI_HTS541612J9SA00_SB3D41EWGSZ5RL-part5 -> ../../sda5 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 ata-HITACHI_HTS541612J9SA00_SB3D41EWGSZ5RL-part6 -> ../../sda6 lrwxrwxrwx. 1 root root 9 Nov 22 12:06 ata-MATSHITADVD-RAM_UJ-852_HC43_043146 -> ../../sr0 lrwxrwxrwx. 1 root root 9 Nov 23 18:04 usb-ARNOVA_10_11223344-0:0 -> ../../sdb lrwxrwxrwx. 1 root root 9 Nov 23 18:04 usb-ARNOVA_10_11223344-0:1 -> ../../sdc lrwxrwxrwx. 1 root root 9 Nov 23 18:04 wwn-0x5000cca54dcae5d8 -> ../../sda lrwxrwxrwx. 1 root root 10 Nov 23 18:04 wwn-0x5000cca54dcae5d8-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 wwn-0x5000cca54dcae5d8-part2 -> ../../sda2 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 wwn-0x5000cca54dcae5d8-part3 -> ../../sda3 lrwxrwxrwx. 1 root root 10 Nov 23 18:04 wwn-0x5000cca54dcae5d8-part4 -> ../../sda4 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 wwn-0x5000cca54dcae5d8-part5 -> ../../sda5 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 wwn-0x5000cca54dcae5d8-part6 -> ../../sda6
by-label/: total 0 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 _Fedora-17-x86_6 -> ../../sda2 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 \x2fusr\x2flocal1 -> ../../sda5
by-path/: total 0 lrwxrwxrwx. 1 root root 9 Nov 23 18:04 pci-0000:00:1a.7-usb-0:3:1.0-scsi-0:0:0:0 -> ../../sdb lrwxrwxrwx. 1 root root 9 Nov 23 18:04 pci-0000:00:1a.7-usb-0:3:1.0-scsi-0:0:0:1 -> ../../sdc
by-uuid/: total 0 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 359f5eea-47cb-42c4-b96e-974b6f07ad19 -> ../../sda3 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 d0b7bacc-879a-4b34-9ddd-76f438a28c5d -> ../../sda6 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 e082b796-2fc7-449b-95d8-a39ef6a29891 -> ../../sda2 lrwxrwxrwx. 1 root root 10 Nov 23 18:04 EEE4584BE4581863 -> ../../sda1 lrwxrwxrwx. 1 root root 10 Nov 22 12:06 f2ed8f21-da63-4def-a674-afdc90e448c5 -> ../../sda5
The two interfaces of the USB are in the by-path. From your e-mail, I understood that I may have to create an entry in the by-uuid? What should I use there then? Something else? Sorry that I am unclear here.
So, I mimicked what was going on with another test case (USB) and tried the following:
cd /dev/disk/by-path
sudo touch ../../sdb1 (this command I think is not correct)
sudo ln -s ../../sdb1 pci-0000:00:1a.7-usb-0:3:1.0-scsi-0:0:0:0-part1
cd /dev/disk/by-id
sudo ln -s ../../sdb1 usb-ARNOVA_10_11223344-0:0-part1
cd by-uuid/
sudo ln -s ../../sdb1 ARNOVA\ 10
sudo mount /dev/sdb1 /mnt/myusb
mount: /dev/sdb1 is not a block device (maybe try `-o loop'?)
I suspect the problem is in the first stage (second command above) because the commands above don't know that ../../sdb1 is part of /dev/sdb.
$ ll /dev/sdb brw-rw----. 1 root disk 8, 16 Nov 23 18:31 /dev/sdb
sudo chown root.disk /dev/sdb1
ll /dev/sdb1 -rw-r--r--. 1 root disk 0 Nov 23 18:35 /dev/sdb1
How do I tell it that it is a partition, perhaps 8, 17 where the 0 is? (Sorry for the naivette? Will parted help here?)
Many thanks again and best wishes, Ranjan
____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth
-
Ed Greshko -
Geoffrey Leach -
John Wendel -
Ranjan Maitra -
Ranjan Maitra