USB serial number not shown with lsusb -v command
up vote
3
down vote
favorite
I have a USB-Stick from which I would like to read the serial number.
If I invoke the command
lsusb -v the output in the line iSerial is as follows:
iSerial 3
If i go to /proc/scsi/usb-storage and look into the file i get the following output:
Host scsi10: usb-storage
Vendor: USB
Product: Disk 2.0
Serial Number: 92071573E1272519149
Protocol: Transparent SCSI
Transport: Bulk
Quirks:
Why is there no serial output with the lsusb command on the one hand, but on the other hand I get a serial number from /proc/scsi/usb-storage. Where is the difference between the two methods to gather the serial?
linux usb proc lsusb
edited Jul 24 '17 at 18:53
Community♦
1
asked Apr 25 '17 at 8:46
Chris
162
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
up vote
3
down vote
favorite
I have a USB-Stick from which I would like to read the serial number.
If I invoke the command
lsusb -v the output in the line iSerial is as follows:
iSerial 3
If i go to /proc/scsi/usb-storage and look into the file i get the following output:
Host scsi10: usb-storage
Vendor: USB
Product: Disk 2.0
Serial Number: 92071573E1272519149
Protocol: Transparent SCSI
Transport: Bulk
Quirks:
Why is there no serial output with the lsusb command on the one hand, but on the other hand I get a serial number from /proc/scsi/usb-storage. Where is the difference between the two methods to gather the serial?
linux usb proc lsusb
edited Jul 24 '17 at 18:53
Community♦
1
asked Apr 25 '17 at 8:46
Chris
162
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have a USB-Stick from which I would like to read the serial number.
If I invoke the command
lsusb -v the output in the line iSerial is as follows:
iSerial 3
If i go to /proc/scsi/usb-storage and look into the file i get the following output:
Host scsi10: usb-storage
Vendor: USB
Product: Disk 2.0
Serial Number: 92071573E1272519149
Protocol: Transparent SCSI
Transport: Bulk
Quirks:
Why is there no serial output with the lsusb command on the one hand, but on the other hand I get a serial number from /proc/scsi/usb-storage. Where is the difference between the two methods to gather the serial?
linux usb proc lsusb
edited Jul 24 '17 at 18:53
Community♦
1
asked Apr 25 '17 at 8:46
Chris
162
I have a USB-Stick from which I would like to read the serial number.
If I invoke the command
lsusb -v the output in the line iSerial is as follows:
iSerial 3
If i go to /proc/scsi/usb-storage and look into the file i get the following output:
Host scsi10: usb-storage
Vendor: USB
Product: Disk 2.0
Serial Number: 92071573E1272519149
Protocol: Transparent SCSI
Transport: Bulk
Quirks:
Why is there no serial output with the lsusb command on the one hand, but on the other hand I get a serial number from /proc/scsi/usb-storage. Where is the difference between the two methods to gather the serial?
linux usb proc lsusb
linux usb proc lsusb
edited Jul 24 '17 at 18:53
Community♦
1
asked Apr 25 '17 at 8:46
Chris
162
edited Jul 24 '17 at 18:53
Community♦
1
asked Apr 25 '17 at 8:46
Chris
162
edited Jul 24 '17 at 18:53
Community♦
1
edited Jul 24 '17 at 18:53
Community♦
1
edited Jul 24 '17 at 18:53
Community♦
1
1
asked Apr 25 '17 at 8:46
Chris
162
asked Apr 25 '17 at 8:46
Chris
162
asked Apr 25 '17 at 8:46
Chris
162
162
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 2 days ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
lsusb may try to open the USB device as O_RDWR (read/write mode) and your user might not have the rights to do this (some error message "Couldn't open device, some information will be missing" should be inbetween the output, if so). Started as root lsusb should also be able to output the whole iSerial value.
answered Jul 24 '17 at 20:40
Jaleks
1,168422
add a comment |
up vote
0
down vote
There are lots of different USB devices in general (keyboard, mice, webcams, ...). lsusb deals with the connected devices on the USB protocol level.
Some USB device are storage devices (USB sticks, USB harddisks, ...). They understand a different protocol (more or less SCSI) on top of the USB protocol. Within this protocol, an USB storage device has a serial number (as does an ATA device). This is what you see in /proc/scsi/usb-storage.
The iSerial number you see in lsusb has nothing to do with it.
So that's why you see the serial number you are interested in with one method, but not with the other method. And that's why you can't use lsusb to get the kind of serial number you are interested in
answered Sep 7 at 6:16
dirkt
16.4k21335
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
lsusb may try to open the USB device as O_RDWR (read/write mode) and your user might not have the rights to do this (some error message "Couldn't open device, some information will be missing" should be inbetween the output, if so). Started as root lsusb should also be able to output the whole iSerial value.
answered Jul 24 '17 at 20:40
Jaleks
1,168422
add a comment |
up vote
0
down vote
lsusb may try to open the USB device as O_RDWR (read/write mode) and your user might not have the rights to do this (some error message "Couldn't open device, some information will be missing" should be inbetween the output, if so). Started as root lsusb should also be able to output the whole iSerial value.
answered Jul 24 '17 at 20:40
Jaleks
1,168422
add a comment |
up vote
0
down vote
up vote
0
down vote
lsusb may try to open the USB device as O_RDWR (read/write mode) and your user might not have the rights to do this (some error message "Couldn't open device, some information will be missing" should be inbetween the output, if so). Started as root lsusb should also be able to output the whole iSerial value.
answered Jul 24 '17 at 20:40
Jaleks
1,168422
lsusb may try to open the USB device as O_RDWR (read/write mode) and your user might not have the rights to do this (some error message "Couldn't open device, some information will be missing" should be inbetween the output, if so). Started as root lsusb should also be able to output the whole iSerial value.
answered Jul 24 '17 at 20:40
Jaleks
1,168422
answered Jul 24 '17 at 20:40
Jaleks
1,168422
answered Jul 24 '17 at 20:40
Jaleks
1,168422
answered Jul 24 '17 at 20:40
Jaleks
1,168422
1,168422
add a comment |
add a comment |
up vote
0
down vote
There are lots of different USB devices in general (keyboard, mice, webcams, ...). lsusb deals with the connected devices on the USB protocol level.
Some USB device are storage devices (USB sticks, USB harddisks, ...). They understand a different protocol (more or less SCSI) on top of the USB protocol. Within this protocol, an USB storage device has a serial number (as does an ATA device). This is what you see in /proc/scsi/usb-storage.
The iSerial number you see in lsusb has nothing to do with it.
So that's why you see the serial number you are interested in with one method, but not with the other method. And that's why you can't use lsusb to get the kind of serial number you are interested in
answered Sep 7 at 6:16
dirkt
16.4k21335
add a comment |
up vote
0
down vote
There are lots of different USB devices in general (keyboard, mice, webcams, ...). lsusb deals with the connected devices on the USB protocol level.
Some USB device are storage devices (USB sticks, USB harddisks, ...). They understand a different protocol (more or less SCSI) on top of the USB protocol. Within this protocol, an USB storage device has a serial number (as does an ATA device). This is what you see in /proc/scsi/usb-storage.
The iSerial number you see in lsusb has nothing to do with it.
So that's why you see the serial number you are interested in with one method, but not with the other method. And that's why you can't use lsusb to get the kind of serial number you are interested in
answered Sep 7 at 6:16
dirkt
16.4k21335
add a comment |
up vote
0
down vote
up vote
0
down vote
There are lots of different USB devices in general (keyboard, mice, webcams, ...). lsusb deals with the connected devices on the USB protocol level.
Some USB device are storage devices (USB sticks, USB harddisks, ...). They understand a different protocol (more or less SCSI) on top of the USB protocol. Within this protocol, an USB storage device has a serial number (as does an ATA device). This is what you see in /proc/scsi/usb-storage.
The iSerial number you see in lsusb has nothing to do with it.
So that's why you see the serial number you are interested in with one method, but not with the other method. And that's why you can't use lsusb to get the kind of serial number you are interested in
answered Sep 7 at 6:16
dirkt
16.4k21335
There are lots of different USB devices in general (keyboard, mice, webcams, ...). lsusb deals with the connected devices on the USB protocol level.
Some USB device are storage devices (USB sticks, USB harddisks, ...). They understand a different protocol (more or less SCSI) on top of the USB protocol. Within this protocol, an USB storage device has a serial number (as does an ATA device). This is what you see in /proc/scsi/usb-storage.
The iSerial number you see in lsusb has nothing to do with it.
So that's why you see the serial number you are interested in with one method, but not with the other method. And that's why you can't use lsusb to get the kind of serial number you are interested in
answered Sep 7 at 6:16
dirkt
16.4k21335
answered Sep 7 at 6:16
dirkt
16.4k21335
answered Sep 7 at 6:16
dirkt
16.4k21335
answered Sep 7 at 6:16
dirkt
16.4k21335
16.4k21335
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f361135%2fusb-serial-number-not-shown-with-lsusb-v-command%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
