After reformatting an external USB NTFS drive under Windows, Ubuntu identified and mounted automatically my external disk.
Now I’ve switched to openSUSE because of Google Go support, but Linux doesn’t regonize this drive anymore. I’ve checked the disk for errors and reformatted the drive again under Windows 7, but it didn’t help.
The disk just doesn’t show up anywhere in openSUSE (Dolphin, fdisk, /dev/disk).
Can somebody help me get this disk identified and mounted in openSUSE?
Help would be greatly appreciated.
With the device attached do
lsusb
and see if the device is recocnised.
Thanks Henk!
This might indicate the controller of the external USB 2.0 disk box, but I’m not sure:
Bus 005 Device 068: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
That seems to be a something from USB to ATA. But you can of course check if there is a difference by making two lsusb lists, one with the device attached and one without. And thus see if the system detects something ot not.
And please: post computer ouput between CODE tags: http://forums.opensuse.org/english/information-new-users/advanced-how-faq-read-only/451526-posting-code-tags-guide.html
I’ve pulled the USB plug from the PC, and the entry re “Bus 005 Device 068” disappeared when I entered lsusb again. So this seems to be the external USB NTFS disk.
I am not an expert here, but only trying to let you posts as much info as posible. That may help others to help you.
To see what type of device it is (and much more), please post the ouput of
lsusb -v -s 005:068
with the device entered in the same slot (else you have to find out first what the Bus and Device numbers are).
The thing is that we found out that your system detects the device is there and it reads the USB information from it. But it seems that it does not see it is a mass storage device and thus does not trigger udev to create the device special files in* /dev *for it (well, that is what you say, you did not prove it, thus we have to believe you).
The result: Nothing.
When I entered only lsusb, I got all USB devices, but lsub with the options brings zero.
By the way, the icons on top of my reply box don’t show a CODE tag icon as shown in the YouTube video…
I hope you checked the Bus and Device numbers thouroughly as I suggested. When it is shown in the short list, there must be output in the long list.
An alternative is
lsusb -v -d 04b4:
Did you realy go to the Advanced Editor (using the Go advanced button)? In other words, did you realy do the second step in the three step list?
On 2012-01-13 17:56, petgo wrote:
>
> I’ve pulled the USB plug from the PC, and the entry re “Bus 005 Device
> 068” disappeared when I entered lsusb again. So this seems to be the
> external USB NTFS disk.
You can plug in the device and then run “dmesg” on a terminal. The last few
lines will read what the kernel sees and what errors it finds. It would be
interesting to see that here - inside code tags.
You can run dmesg twice, one without the device, one after you plug it in,
so that you can detect the first line of interest.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
No, but now I did.I’ve seen that the USB disk got a new Device
Bus 005 Device 109: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
after plugging it into the PC again. However,
lsusb -v -s 005:109
did not bring any results either.
lsusb -v -d 04b4:
brought the following, again with a different Device number:
Bus 005 Device 081: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPIlibusb couldn't open USB device /dev/bus/usb/005/081: Permission denied.libusb requires write access to USB device nodes.Couldn't open device, some information will be missingDevice Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x04b4 Cypress Semiconductor Corp. idProduct 0x6830 CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI bcdDevice 0.01 iManufacturer 56 iProduct 78 iSerial 100 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 0mA 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 0x02 EP 2 OUT 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 0x88 EP 8 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0
Then I tried
lsusb -v -s 005:081
with no result too.@Carlos:“demsg” delivers results much greater than the limit of 15000 characters in a post.Any suggestion how to post them?
with no result too.@Carlos:“demsg” delivers results much greater than the limit of 15000 characters in a post.Any suggestion how to post them?
Plug in your device and issue
dmesg|tail
You can monitor the kernel uevents (udev messages) similarly
/sbin/udevadm monitor
On 2012-01-13 23:36, petgo wrote:
> @Carlos:“demsg” delivers results much greater than
> the limit of 15000 characters in a post.Any suggestion how to post them?
I told you that I want the lines at the end that change between before and
after. A dozen lines.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Also the computer output you posted as the answer to* lsusb -v -d … *is not by copy/paste of the text from the terminal window to in between the CODE tags. All new-lines have gone! Also you apparently now can use CODE tags, thus it seems that you did not read the instructions carfully the first time.
Please do read, reread and may even reread again what people here ask you to to. Thus when Carlos ask you to check what are the new lines added to dmesg during your plugin action, then do not complain about the whole of the dmesg output not fitting in a post. It is not only very frustrating for people who try to halep you when you do different then what they ask you, it also lets them doubt about all the information you gave them until now.
On 2012-01-14 11:16, hcvv wrote:
> Please do read, reread and may even reread again what people here ask
> you to to. Thus when Carlos ask you to check what are the new lines
> added to -dmesg- during your plugin action, then do not complain about
> the whole of the -dmesg- output not fitting in a post. It is not only
> very frustrating for people who try to halep you when you do different
> then what they ask you, it also lets them doubt about all the
> information you gave them until now.
Indeed.
I would love to have a command that did that automatically. Before sending
my post I tried and spent several minutes reading dmesg manual, because I
seem to remember seeing that thing somewhere. But I did not find it.
I also thought about looking at syslog, but I can’t be certain that kernel
output will be there. There I do have an automatic command to get the new
lines, but not safe.
So, dmesg.
It is frustrating to spend that time trying to help, and get that response.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Yes, but it is part of what you have to undergo when trying to help a community of people who differ very much in backgground. Many of them are not used to IT and thus not used to reading carefully and expressing themselves carefully and precise. It is part of the steep learning curve in using Linux (or any other OS when you want to manage it in earnest). One has to understand technical and logical thinking even before understanding the techniques themselves.
On 2012-01-14 14:06, hcvv wrote:
>
> robin_listas;2430199 Wrote:
>>
>>
>> It is frustrating to spend that time trying to help, and get that
>> response.
>>
>>
> Yes, but it is part of what you have to undergo when trying to help a
> community of people who differ very much in backgground. Many of them
> are not used to IT and thus not used to reading carefully and expressing
> themselves carefully and precise. It is part of the steep learning curve
> in using Linux (or any other OS when you want to manage it in earnest).
> One has to understand technical and logical thinking even before
> understanding the techniques themselves.
I know…
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
@Henk, Carlos and Deano: I apologize for not reading your instructions carefully enough.
Thank you, dank u wel, ¡muchasgracias!, gratie for spending your time and effort in trying to help me! I appreciate this very much.
Here are the commands that I ran:
lusb (with and without the USB 2.0 NTFS disk, here is the additional line with disk plugged in)
Bus 005 Device 075: ID04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0to ATA/ATAPI
This might indicate that the USB disk has a Cypress controller.
lsusb -v -s 005:075
This command brought no results.
Note: with the following command, the device number of the disk seems to have changed from 075 to 088.
lsusb -v -d 04b4:
Bus 005 Device 088: ID 04b4:6830 Cypress Semiconductor Corp. CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
libusb couldn't open USB device /dev/bus/usb/005/088: Permission denied.
libusb requires write access to USB device nodes.
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 0x04b4 Cypress Semiconductor Corp.
idProduct 0x6830 CY7C68300A EZ-USB AT2 USB 2.0 to ATA/ATAPI
bcdDevice 0.01
iManufacturer 56
iProduct 78
iSerial 100
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
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 0x02 EP 2 OUT
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 0x88 EP 8 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
With disk plugged in:
dmesg|tail
[13197.181777] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
[13197.382643] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
[13197.583612] usb 5-2: device not accepting address 99, error -22
[13197.685709] usb 5-2: reset high speed USB device number 99 using xhci_hcd
[13197.685765] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
[13197.886663] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
[13198.087603] usb 5-2: device not accepting address 99, error -22
[13198.189693] usb 5-2: reset high speed USB device number 99 using xhci_hcd
[13198.189747] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
[13198.390641] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
dmesg without disk, last lines starting with a reference to Cypress/usb 5-2 (wonder why Cypress shows up although the disk is not plugged in):
[14218.061375] usb 5-2: device not accepting address 4, error -22
[14218.163468] usb 5-2: reset high speed USB device number 4 using xhci_hcd
[14218.163521] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
[14218.364423] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x11.
[14218.565361] usb 5-2: device not accepting address 4, error -22
[14218.565395] usb 5-2: USB disconnect, device number 4
[14218.565414] sd 135:0:0:0: Device offlined - not ready after error recovery
[14218.565994] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880173b9c6c0
[14218.565998] xhci_hcd 0000:04:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880173b9c700
[14218.566020] xhci_hcd 0000:04:00.0: ERROR: unexpected command completion code 0x13.
[14218.667377] usb 5-2: new high speed USB device number 5 using xhci_hcd
[14218.679966] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14218.680319] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14218.680694] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14218.681068] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14218.681200] usb 5-2: New USB device found, idVendor=04b4, idProduct=6830
[14218.681202] usb 5-2: New USB device strings: Mfr=56, Product=78, SerialNumber=100
[14218.681203] usb 5-2: Product: USB2.0 Storage Device
[14218.681205] usb 5-2: Manufacturer: Cypress Semiconductor
[14218.681206] usb 5-2: SerialNumber: DEF107E9B3BD
[14218.681680] scsi136 : usb-storage 5-2:1.0
[14219.681518] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14219.681820] scsi 136:0:0:0: Direct-Access ST320082 2A PQ: 0 ANSI: 0
[14219.681989] sd 136:0:0:0: Attached scsi generic sg4 type 0
[14219.682604] sd 136:0:0:0: [sdd] 390721968 512-byte logical blocks: (200 GB/186 GiB)
[14219.683141] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14219.683560] sd 136:0:0:0: [sdd] Write Protect is off
[14219.683564] sd 136:0:0:0: [sdd] Mode Sense: 33 00 00 00
[14219.684130] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14219.684363] sd 136:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[14219.685110] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14219.685775] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14219.734126] sdd: sdd1
[14219.734939] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14219.735528] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14219.735731] sd 136:0:0:0: [sdd] Attached SCSI disk
[14245.499774] xhci_hcd 0000:04:00.0: WARN: transfer error on endpoint
[14245.550914] usb 5-2: USB disconnect, device number 5
dmesg with disk plugged in, last lines starting with a reference to Cypress/usb 5-2:
[14245.550914] usb 5-2: USB disconnect, device number 5
[14584.561963] usb 5-2: new high speed USB device number 6 using xhci_hcd
[14584.574522] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14584.574875] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14584.575250] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14584.575625] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
[14584.575756] usb 5-2: New USB device found, idVendor=04b4, idProduct=6830
[14584.575758] usb 5-2: New USB device strings: Mfr=56, Product=78, SerialNumber=100
[14584.575760] usb 5-2: Product: USB2.0 Storage Device
[14584.575761] usb 5-2: Manufacturer: Cypress Semiconductor
[14584.575762] usb 5-2: SerialNumber: DEF107E9B3BD
[14584.576364] scsi137 : usb-storage 5-2:1.0
[14585.576095] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14585.576400] scsi 137:0:0:0: Direct-Access ST320082 2A PQ: 0 ANSI: 0
[14585.576597] sd 137:0:0:0: Attached scsi generic sg4 type 0
[14585.577559] sd 137:0:0:0: [sdd] 390721968 512-byte logical blocks: (200 GB/186 GiB)
[14585.577975] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14585.578199] sd 137:0:0:0: [sdd] Write Protect is off
[14585.578201] sd 137:0:0:0: [sdd] Mode Sense: 33 00 00 00
[14585.578616] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14585.578790] sd 137:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[14585.579508] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14585.580090] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14585.638787] sdd: sdd1
[14585.639649] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14585.640423] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
[14585.640662] sd 137:0:0:0: [sdd] Attached SCSI disk
Because of length of post, I will post the results from /sb[size=2]in/udevadm monitor separately
[/size]Again many thanks for your help.
Peter
Deano, adding to my previous post including dmesg|tail, here are the initial udev messages from
[LEFT]/sbin/udevadm monitor
UDEV [15978.752517] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/scsi_device/177:0:0:0 (scsi_device)
UDEV [15978.752559] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/scsi_generic/sg4 (scsi_generic)
UDEV [15978.752807] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/scsi_disk/177:0:0:0 (scsi_disk)
UDEV [15978.752889] remove /devices/virtual/bdi/8:48 (bdi)
UDEV [15978.752949] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/bsg/177:0:0:0 (bsg)
UDEV [15978.752960] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/scsi_host/host177 (scsi_host)
UDEV [15978.762309] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/block/sdd (block) UDEV [15978.872180] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/block/sdd/sdd1 (block) UDEV [15978.872493] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/block/sdd/sdd1 (block) UDEV [15978.872691] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0/block/sdd (block) UDEV [15978.872812] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0/177:0:0:0 (scsi) UDEV [15978.872910] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177/target177:0:0 (scsi)
UDEV [15978.872994] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host177 (scsi)
UDEV [15978.873148] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0 (usb)
UDEV [15978.873693] remove /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2 (usb)
UDEV [15978.967500] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2 (usb)
UDEV [15978.968017] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0 (usb)
UDEV [15978.968304] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178 (scsi)
UDEV [15978.968555] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178/scsi_host/host178 (scsi_host) UDEV [15979.869652] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178/target178:0:0 (scsi)
UDEV [15979.869664] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178/target178:0:0/178:0:0:0 (scsi)
UDEV [15979.869672] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178/target178:0:0/178:0:0:0/scsi_disk/178:0:0:0 (scsi_disk)
UDEV [15979.869688] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178/target178:0:0/178:0:0:0/scsi_device/178:0:0:0 (scsi_device)
UDEV [15979.870352] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178/target178:0:0/178:0:0:0/scsi_generic/sg4 (scsi_generic)
UDEV [15979.870472] add /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/host178/target178:0:0/178:0:0:0/bsg/178:0:0:0 (bsg)
UDEV [15979.870544] add /devices/virtual/bdi/8:48 (bdi)[/LEFT]
[LEFT]Hope this is useful.
Peter[/LEFT]
On 2012-01-16 13:26, petgo wrote:
>
> @Henk, Carlos and Deano: I apologize for not reading your instructions
> carefully enough.
No problem.
> dmesg with disk plugged in, last lines starting with a reference to
> Cypress/usb 5-2:
This is the interesting part.
> Code:
> --------------------
> [14245.550914] usb 5-2: USB disconnect, device number 5
> [14584.561963] usb 5-2: new high speed USB device number 6 using xhci_hcd
> [14584.574522] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
> [14584.574875] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
> [14584.575250] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
> [14584.575625] xhci_hcd 0000:04:00.0: WARN: short transfer on control ep
> [14584.575756] usb 5-2: New USB device found, idVendor=04b4, idProduct=6830
> [14584.575758] usb 5-2: New USB device strings: Mfr=56, Product=78, SerialNumber=100
> [14584.575760] usb 5-2: Product: USB2.0 Storage Device
> [14584.575761] usb 5-2: Manufacturer: Cypress Semiconductor
> [14584.575762] usb 5-2: SerialNumber: DEF107E9B3BD
> [14584.576364] scsi137 : usb-storage 5-2:1.0
> [14585.576095] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
> [14585.576400] scsi 137:0:0:0: Direct-Access ST320082 2A PQ: 0 ANSI: 0
> [14585.576597] sd 137:0:0:0: Attached scsi generic sg4 type 0
> [14585.577559] sd 137:0:0:0: [sdd] 390721968 512-byte logical blocks: (200 GB/186 GiB)
> [14585.577975] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
> [14585.578199] sd 137:0:0:0: [sdd] Write Protect is off
> [14585.578201] sd 137:0:0:0: [sdd] Mode Sense: 33 00 00 00
> [14585.578616] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
> [14585.578790] sd 137:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
> [14585.579508] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
> [14585.580090] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
> [14585.638787] sdd: sdd1
> [14585.639649] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
> [14585.640423] xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
> [14585.640662] sd 137:0:0:0: [sdd] Attached SCSI disk
>
> --------------------
The device is connected as /dev/sdd, but has lots of errors. That is
probably the problem. If you can show equivalent output for ubuntu showing
that there is no problem, you can fill up a bugzilla against the kernel
with that info.
In fact, if you google for “xhci_hcd 0000:04:00.0: WARN: Stalled endpoint”
you find many entries.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I am not quite sure that I interprete this correct, but adding to Carlos observations, it seems that the device is disconnected due to the errors. Because it is still physicaly there, reconnection is tried and that is responsible for the renumbering of the Device on the Bus. Do a few lsusb commands every say 5 secs and you will see the Device number go up. (Yes, a computer is able do do the same error a million times a second 
).