Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > nl.comp.os.linux.techniek > #9641 > unrolled thread

Data redden

Started byPaul van der Vlis <paul@vandervlis.nl>
First post2024-06-29 17:11 +0200
Last post2024-07-15 00:00 +0000
Articles 9 — 4 participants

Back to article view | Back to nl.comp.os.linux.techniek

Contents

  Data redden Paul van der Vlis <paul@vandervlis.nl> - 2024-06-29 17:11 +0200
    Re: Data redden "De ongekruisigde (ds.)" <ongekruisigde@gekruisigden.invalid> - 2024-06-29 17:08 +0000
      Re: Data redden a3@a3.nl.invalid (Adri Verhoef) - 2024-07-02 00:33 +0000
        Re: Data redden Ozymandias <ozymandias@ozymandias.invalid> - 2024-07-02 08:20 +0000
        Re: Data redden Paul van der Vlis <paul@vandervlis.nl> - 2024-07-03 13:01 +0200
          Re: Data redden Paul van der Vlis <paul@vandervlis.nl> - 2024-07-03 13:41 +0200
            Re: Data redden Ozymandias <ozymandias@ozymandias.invalid> - 2024-07-03 12:29 +0000
        Re: Data redden Paul van der Vlis <paul@vandervlis.nl> - 2024-07-03 13:58 +0200
          Re: Data redden a3@a3.nl.invalid (Adri Verhoef) - 2024-07-15 00:00 +0000

#9641 — Data redden

FromPaul van der Vlis <paul@vandervlis.nl>
Date2024-06-29 17:11 +0200
SubjectData redden
Message-ID<v5p872$3vlkv$1@dont-email.me>
Hoi,

Ik probeer de data te redden van een USB-disk. De vorige twee keer ging 
dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens 
het starten, maar is al vrij snel weer verdwenen.

Ik heb twee verschillende computers en kabels geprobeerd.
Zie onder output van dmesg.

Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten 
voortbestaan, zodat ik de data eraf kan halen?

Groet,
Paul


174264.957546] usb 1-1.5: new high-speed USB device number 23 using ehci-pci
[174265.107849] usb 1-1.5: New USB device found, idVendor=1058, 
idProduct=2620, bcdDevice=10.23
[174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
[174265.107855] usb 1-1.5: Product: Elements 2620
[174265.107856] usb 1-1.5: Manufacturer: Western Digital
[174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
[174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
[174265.108658] scsi host7: usb-storage 1-1.5:1.0
[174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620 
  1023 PQ: 0 ANSI: 6
[174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
[174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
[174267.141475] 
.........................................................ready
[174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ 
CAPACITY(16).
[174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks: 
(5.00 TB/4.55 TiB)
[174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
[174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
[174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
[174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
[174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
[174355.583306] usb 1-1.5: reset high-speed USB device number 23 using 
ehci-pci
[174360.691216] usb 1-1.5: device descriptor read/64, error -110
[174376.306788] usb 1-1.5: device descriptor read/64, error -110
[174376.494792] usb 1-1.5: reset high-speed USB device number 23 using 
ehci-pci
[174381.682674] usb 1-1.5: device descriptor read/64, error -110
[174397.306284] usb 1-1.5: device descriptor read/64, error -110
[174397.494297] usb 1-1.5: reset high-speed USB device number 23 using 
ehci-pci
[174408.178067] usb 1-1.5: device not accepting address 23, error -110
[174408.258059] usb 1-1.5: reset high-speed USB device number 23 using 
ehci-pci
[174418.929801] usb 1-1.5: device not accepting address 23, error -110
[174418.930555] usb 1-1.5: USB disconnect, device number 23
[174418.945792] print_req_error: 2 callbacks suppressed
[174418.945795] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945809] buffer_io_error: 2 callbacks suppressed
[174418.945811] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945880] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945886] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945910] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945913] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945933] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945934] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945938] ldm_validate_partition_table(): Disk read failed.
[174418.945943] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945945] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945952] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945953] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945961] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945962] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945969] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945971] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945974] Dev sdd: unable to read RDB block 0
[174418.945980] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945981] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.945988] blk_update_request: I/O error, dev sdd, sector 0 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[174418.945990] Buffer I/O error on dev sdd, logical block 0, async page 
read
[174418.946009]  sdd: unable to read partition table
[174418.973864] sd 7:0:0:0: [sdd] Read Capacity(16) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[174418.973867] sd 7:0:0:0: [sdd] Sense not available.
[174418.973878] sd 7:0:0:0: [sdd] Read Capacity(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[174418.973880] sd 7:0:0:0: [sdd] Sense not available.
[174418.973884] sd 7:0:0:0: [sdd] 0 512-byte logical blocks: (0 B/0 B)
[174418.973886] sd 7:0:0:0: [sdd] 4096-byte physical blocks
[174418.973897] sd 7:0:0:0: [sdd] Attached SCSI disk
[174419.109763] usb 1-1.5: new high-speed USB device number 24 using 
ehci-pci
[174424.433678] usb 1-1.5: device descriptor read/64, error -110
[174440.049263] usb 1-1.5: device descriptor read/64, error -110
[174440.241280] usb 1-1.5: new high-speed USB device number 25 using 
ehci-pci
[174445.425155] usb 1-1.5: device descriptor read/64, error -110
[174461.040753] usb 1-1.5: device descriptor read/64, error -110
[174461.148871] usb 1-1-port5: attempt power cycle
[174461.752759] usb 1-1.5: new high-speed USB device number 26 using 
ehci-pci
[174472.432497] usb 1-1.5: device not accepting address 26, error -110
[174472.512546] usb 1-1.5: new high-speed USB device number 27 using 
ehci-pci
[174483.184225] usb 1-1.5: device not accepting address 27, error -110
[174483.184471] usb 1-1-port5: unable to enumerate USB device



-- 
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl


[165276.915341]

[toc] | [next] | [standalone]

#9642

From"De ongekruisigde (ds.)" <ongekruisigde@gekruisigden.invalid>
Date2024-06-29 17:08 +0000
Message-ID<v5pf1q$uld$1@dont-email.me>
In reply to#9641
On 2024-06-29, Paul van der Vlis <paul@vandervlis.nl> wrote:
> Hoi,
>
> Ik probeer de data te redden van een USB-disk. De vorige twee keer ging 
> dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens 
> het starten, maar is al vrij snel weer verdwenen.
>
> Ik heb twee verschillende computers en kabels geprobeerd.
> Zie onder output van dmesg.
>
> Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten 
> voortbestaan, zodat ik de data eraf kan halen?

Als ik die log lees dan lijkt het ding gewoon kapot (elektronisch
of zo). Waarschijnlijk helaas voor de data erop.


> Groet,
> Paul
>
>
> 174264.957546] usb 1-1.5: new high-speed USB device number 23 using ehci-pci
> [174265.107849] usb 1-1.5: New USB device found, idVendor=1058, 
> idProduct=2620, bcdDevice=10.23
> [174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3, 
> SerialNumber=1
> [174265.107855] usb 1-1.5: Product: Elements 2620
> [174265.107856] usb 1-1.5: Manufacturer: Western Digital
> [174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
> [174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
> [174265.108658] scsi host7: usb-storage 1-1.5:1.0
> [174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620 
>   1023 PQ: 0 ANSI: 6
> [174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
> [174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
> [174267.141475] 
> .........................................................ready
> [174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ 
> CAPACITY(16).
> [174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks: 
> (5.00 TB/4.55 TiB)
> [174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
> [174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
> [174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
> [174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
> [174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
> [174355.583306] usb 1-1.5: reset high-speed USB device number 23 using 
> ehci-pci
> [174360.691216] usb 1-1.5: device descriptor read/64, error -110
> [174376.306788] usb 1-1.5: device descriptor read/64, error -110
> [174376.494792] usb 1-1.5: reset high-speed USB device number 23 using 
> ehci-pci
> [174381.682674] usb 1-1.5: device descriptor read/64, error -110
> [174397.306284] usb 1-1.5: device descriptor read/64, error -110
> [174397.494297] usb 1-1.5: reset high-speed USB device number 23 using 
> ehci-pci
> [174408.178067] usb 1-1.5: device not accepting address 23, error -110
> [174408.258059] usb 1-1.5: reset high-speed USB device number 23 using 
> ehci-pci
> [174418.929801] usb 1-1.5: device not accepting address 23, error -110
> [174418.930555] usb 1-1.5: USB disconnect, device number 23
> [174418.945792] print_req_error: 2 callbacks suppressed
> [174418.945795] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945809] buffer_io_error: 2 callbacks suppressed
> [174418.945811] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945880] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945886] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945910] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945913] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945933] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945934] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945938] ldm_validate_partition_table(): Disk read failed.
> [174418.945943] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945945] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945952] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945953] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945961] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945962] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945969] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945971] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945974] Dev sdd: unable to read RDB block 0
> [174418.945980] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945981] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.945988] blk_update_request: I/O error, dev sdd, sector 0 op 
> 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
> [174418.945990] Buffer I/O error on dev sdd, logical block 0, async page 
> read
> [174418.946009]  sdd: unable to read partition table
> [174418.973864] sd 7:0:0:0: [sdd] Read Capacity(16) failed: Result: 
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [174418.973867] sd 7:0:0:0: [sdd] Sense not available.
> [174418.973878] sd 7:0:0:0: [sdd] Read Capacity(10) failed: Result: 
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [174418.973880] sd 7:0:0:0: [sdd] Sense not available.
> [174418.973884] sd 7:0:0:0: [sdd] 0 512-byte logical blocks: (0 B/0 B)
> [174418.973886] sd 7:0:0:0: [sdd] 4096-byte physical blocks
> [174418.973897] sd 7:0:0:0: [sdd] Attached SCSI disk
> [174419.109763] usb 1-1.5: new high-speed USB device number 24 using 
> ehci-pci
> [174424.433678] usb 1-1.5: device descriptor read/64, error -110
> [174440.049263] usb 1-1.5: device descriptor read/64, error -110
> [174440.241280] usb 1-1.5: new high-speed USB device number 25 using 
> ehci-pci
> [174445.425155] usb 1-1.5: device descriptor read/64, error -110
> [174461.040753] usb 1-1.5: device descriptor read/64, error -110
> [174461.148871] usb 1-1-port5: attempt power cycle
> [174461.752759] usb 1-1.5: new high-speed USB device number 26 using 
> ehci-pci
> [174472.432497] usb 1-1.5: device not accepting address 26, error -110
> [174472.512546] usb 1-1.5: new high-speed USB device number 27 using 
> ehci-pci
> [174483.184225] usb 1-1.5: device not accepting address 27, error -110
> [174483.184471] usb 1-1-port5: unable to enumerate USB device
>
>
>


-- 
De Kerk van Roodkapje (KvR) belijdt de enige ware religie! De
Rode Macht van Roodkapje is wetenschappelijk onderzocht en
bevestigd (google roodverschuiving).

[toc] | [prev] | [next] | [standalone]

#9648

Froma3@a3.nl.invalid (Adri Verhoef)
Date2024-07-02 00:33 +0000
Message-ID<sFz07E.uv44@a3.nl.invalid>
In reply to#9642
Op moederschip aarde schreef iemand die zich identificeerde als
De ongekruisigde (ds.) <deongekruisigde@invalid.invalid>:
>On 2024-06-29, Paul van der Vlis <paul@vandervlis.nl> wrote:
>> Hoi,
>>
>> Ik probeer de data te redden van een USB-disk. De vorige twee keer ging 
>> dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens 
>> het starten, maar is al vrij snel weer verdwenen.
>>
>> Ik heb twee verschillende computers en kabels geprobeerd.
>> Zie onder output van dmesg.
>>
>> Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten 
>> voortbestaan, zodat ik de data eraf kan halen?
>
>Als ik die log lees dan lijkt het ding gewoon kapot (elektronisch
>of zo). Waarschijnlijk helaas voor de data erop.
>
>
>> Groet,
>> Paul
>>
>>
>> 174264.957546] usb 1-1.5: new high-speed USB device number 23 using ehci-pci
>> [174265.107849] usb 1-1.5: New USB device found, idVendor=1058, 
>> idProduct=2620, bcdDevice=10.23
>> [174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3, 
>> SerialNumber=1
>> [174265.107855] usb 1-1.5: Product: Elements 2620
>> [174265.107856] usb 1-1.5: Manufacturer: Western Digital
>> [174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
>> [174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
>> [174265.108658] scsi host7: usb-storage 1-1.5:1.0
>> [174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620 
>>   1023 PQ: 0 ANSI: 6
>> [174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
>> [174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
>> [174267.141475] 
>> .........................................................ready
>> [174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ 
>> CAPACITY(16).
>> [174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks: 
>> (5.00 TB/4.55 TiB)
>> [174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
>> [174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
>> [174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
>> [174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
>> [174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
>> [174355.583306] usb 1-1.5: reset high-speed USB device number 23 using 
>> ehci-pci
>> [174360.691216] usb 1-1.5: device descriptor read/64, error -110
>> [174376.306788] usb 1-1.5: device descriptor read/64, error -110
>> [174376.494792] usb 1-1.5: reset high-speed USB device number 23 using 
>> ehci-pci
>> [174381.682674] usb 1-1.5: device descriptor read/64, error -110
>> [174397.306284] usb 1-1.5: device descriptor read/64, error -110
>> [174397.494297] usb 1-1.5: reset high-speed USB device number 23 using 
>> ehci-pci

https://askubuntu.com/questions/644010/ubuntu-cant-read-my-usb-device-descriptor-read-64-error-110
"The device descriptor read/64, error -110 means that USB port power supply was
exceeded."
https://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110
"USB error -110 means "Timeout expired before the transfer completed", which
could be caused by anything. Most commonly, it's because power was exceeded;
the host could not provide enough electric power for the pendrive to operate.
Because it has not enough power also the USB stick cannot provide the device
descriptor to the host, as a result it cannot be identified and so on. Maybe
your motherboard it's overloaded with devices that consume all the available
power."
"I had the same error, but with no USB device plugged in. I have a Suse 13.2
and 42.2 installed on an internal ssd drive in a HP ProBook 430. When I booted
into 42.2, I got that error and booting simply stopped there. Weird enough with
13.2 on the same hard disk I could boot with no problems. Following Johnsters
advice to unplug any power supply including battery removal finally did it, so
loads of thanks go there. And to all running into this post without any obvious
interaction of USB devices in their problems: Try making your system voltage
free, it still might do the trick."
"Main voltage is not high enough in my home. It's below 180V (normally
220-240). Sometimes I get the same error. Sometimes my PC restarts itself."

Ik realiseer me dat dit niet per se de oplossing voor jouw probleem is, Paul,
het zijn slechts suggesties; misschien brengen ze je op ideeën om het probleem
aan te pakken.

[toc] | [prev] | [next] | [standalone]

#9650

FromOzymandias <ozymandias@ozymandias.invalid>
Date2024-07-02 08:20 +0000
Message-ID<v60d7l$1iifd$1@dont-email.me>
In reply to#9648
On 2024-07-02, Adri Verhoef <a3@a3.nl.invalid> wrote:
> Op moederschip aarde schreef iemand die zich identificeerde als
> De ongekruisigde (ds.) <deongekruisigde@invalid.invalid>:
>>On 2024-06-29, Paul van der Vlis <paul@vandervlis.nl> wrote:
>>> Hoi,
>>>
>>> Ik probeer de data te redden van een USB-disk. De vorige twee keer ging 
>>> dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens 
>>> het starten, maar is al vrij snel weer verdwenen.
>>>
>>> Ik heb twee verschillende computers en kabels geprobeerd.
>>> Zie onder output van dmesg.
>>>
>>> Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten 
>>> voortbestaan, zodat ik de data eraf kan halen?
>>
>>Als ik die log lees dan lijkt het ding gewoon kapot (elektronisch
>>of zo). Waarschijnlijk helaas voor de data erop.
>>
>>
>>> Groet,
>>> Paul
>>>
>>>
>>> 174264.957546] usb 1-1.5: new high-speed USB device number 23 using ehci-pci
>>> [174265.107849] usb 1-1.5: New USB device found, idVendor=1058, 
>>> idProduct=2620, bcdDevice=10.23
>>> [174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3, 
>>> SerialNumber=1
>>> [174265.107855] usb 1-1.5: Product: Elements 2620
>>> [174265.107856] usb 1-1.5: Manufacturer: Western Digital
>>> [174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
>>> [174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
>>> [174265.108658] scsi host7: usb-storage 1-1.5:1.0
>>> [174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620 
>>>   1023 PQ: 0 ANSI: 6
>>> [174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
>>> [174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
>>> [174267.141475] 
>>> .........................................................ready
>>> [174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ 
>>> CAPACITY(16).
>>> [174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks: 
>>> (5.00 TB/4.55 TiB)
>>> [174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
>>> [174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
>>> [174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
>>> [174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
>>> [174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
>>> [174355.583306] usb 1-1.5: reset high-speed USB device number 23 using 
>>> ehci-pci
>>> [174360.691216] usb 1-1.5: device descriptor read/64, error -110
>>> [174376.306788] usb 1-1.5: device descriptor read/64, error -110
>>> [174376.494792] usb 1-1.5: reset high-speed USB device number 23 using 
>>> ehci-pci
>>> [174381.682674] usb 1-1.5: device descriptor read/64, error -110
>>> [174397.306284] usb 1-1.5: device descriptor read/64, error -110
>>> [174397.494297] usb 1-1.5: reset high-speed USB device number 23 using 
>>> ehci-pci
>
> https://askubuntu.com/questions/644010/ubuntu-cant-read-my-usb-device-descriptor-read-64-error-110
> "The device descriptor read/64, error -110 means that USB port power supply was
> exceeded."
> https://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110
> "USB error -110 means "Timeout expired before the transfer completed", which
> could be caused by anything. Most commonly, it's because power was exceeded;
> the host could not provide enough electric power for the pendrive to operate.
> Because it has not enough power also the USB stick cannot provide the device
> descriptor to the host, as a result it cannot be identified and so on. Maybe
> your motherboard it's overloaded with devices that consume all the available
> power."
> "I had the same error, but with no USB device plugged in. I have a Suse 13.2
> and 42.2 installed on an internal ssd drive in a HP ProBook 430. When I booted
> into 42.2, I got that error and booting simply stopped there. Weird enough with
> 13.2 on the same hard disk I could boot with no problems. Following Johnsters
> advice to unplug any power supply including battery removal finally did it, so
> loads of thanks go there. And to all running into this post without any obvious
> interaction of USB devices in their problems: Try making your system voltage
> free, it still might do the trick."
> "Main voltage is not high enough in my home. It's below 180V (normally
> 220-240). Sometimes I get the same error. Sometimes my PC restarts itself."

Als dit het probleem zou zijn dan valt er wellicht nog wat te redden.


> Ik realiseer me dat dit niet per se de oplossing voor jouw probleem is, Paul,
> het zijn slechts suggesties; misschien brengen ze je op ideeën om het probleem
> aan te pakken.

Probeer bv. eens een andere USB-poort of een andere computer om
te zien of dat verschil maakt.

-- 
"My name is Ozymandias, King of Kings:
Look on my works, ye Mighty, and despair!"

[toc] | [prev] | [next] | [standalone]

#9653

FromPaul van der Vlis <paul@vandervlis.nl>
Date2024-07-03 13:01 +0200
Message-ID<v63b25$25bgu$1@dont-email.me>
In reply to#9648
Op 02-07-2024 om 02:33 schreef Adri Verhoef:
> Op moederschip aarde schreef iemand die zich identificeerde als
> De ongekruisigde (ds.) <deongekruisigde@invalid.invalid>:
>> On 2024-06-29, Paul van der Vlis <paul@vandervlis.nl> wrote:
>>> Hoi,
>>>
>>> Ik probeer de data te redden van een USB-disk. De vorige twee keer ging
>>> dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens
>>> het starten, maar is al vrij snel weer verdwenen.
>>>
>>> Ik heb twee verschillende computers en kabels geprobeerd.
>>> Zie onder output van dmesg.
>>>
>>> Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten
>>> voortbestaan, zodat ik de data eraf kan halen?
>>
>> Als ik die log lees dan lijkt het ding gewoon kapot (elektronisch
>> of zo). Waarschijnlijk helaas voor de data erop.
>>
>>
>>> Groet,
>>> Paul
>>>
>>>
>>> 174264.957546] usb 1-1.5: new high-speed USB device number 23 using ehci-pci
>>> [174265.107849] usb 1-1.5: New USB device found, idVendor=1058,
>>> idProduct=2620, bcdDevice=10.23
>>> [174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3,
>>> SerialNumber=1
>>> [174265.107855] usb 1-1.5: Product: Elements 2620
>>> [174265.107856] usb 1-1.5: Manufacturer: Western Digital
>>> [174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
>>> [174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
>>> [174265.108658] scsi host7: usb-storage 1-1.5:1.0
>>> [174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620
>>>    1023 PQ: 0 ANSI: 6
>>> [174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
>>> [174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
>>> [174267.141475]
>>> .........................................................ready
>>> [174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ
>>> CAPACITY(16).
>>> [174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks:
>>> (5.00 TB/4.55 TiB)
>>> [174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
>>> [174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
>>> [174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
>>> [174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
>>> [174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
>>> [174355.583306] usb 1-1.5: reset high-speed USB device number 23 using
>>> ehci-pci
>>> [174360.691216] usb 1-1.5: device descriptor read/64, error -110
>>> [174376.306788] usb 1-1.5: device descriptor read/64, error -110
>>> [174376.494792] usb 1-1.5: reset high-speed USB device number 23 using
>>> ehci-pci
>>> [174381.682674] usb 1-1.5: device descriptor read/64, error -110
>>> [174397.306284] usb 1-1.5: device descriptor read/64, error -110
>>> [174397.494297] usb 1-1.5: reset high-speed USB device number 23 using
>>> ehci-pci
> 
> https://askubuntu.com/questions/644010/ubuntu-cant-read-my-usb-device-descriptor-read-64-error-110
> "The device descriptor read/64, error -110 means that USB port power supply was
> exceeded."
> https://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110
> "USB error -110 means "Timeout expired before the transfer completed", which
> could be caused by anything. Most commonly, it's because power was exceeded;
> the host could not provide enough electric power for the pendrive to operate.
> Because it has not enough power also the USB stick cannot provide the device
> descriptor to the host, as a result it cannot be identified and so on. Maybe
> your motherboard it's overloaded with devices that consume all the available
> power."
> "I had the same error, but with no USB device plugged in. I have a Suse 13.2
> and 42.2 installed on an internal ssd drive in a HP ProBook 430. When I booted
> into 42.2, I got that error and booting simply stopped there. Weird enough with
> 13.2 on the same hard disk I could boot with no problems. Following Johnsters
> advice to unplug any power supply including battery removal finally did it, so
> loads of thanks go there. And to all running into this post without any obvious
> interaction of USB devices in their problems: Try making your system voltage
> free, it still might do the trick."
> "Main voltage is not high enough in my home. It's below 180V (normally
> 220-240). Sometimes I get the same error. Sometimes my PC restarts itself."
> 
> Ik realiseer me dat dit niet per se de oplossing voor jouw probleem is, Paul,
> het zijn slechts suggesties; misschien brengen ze je op ideeën om het probleem
> aan te pakken.

Bedankt, ik ga hiernaar kijken...

Groet,
Paul


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl

[toc] | [prev] | [next] | [standalone]

#9654

FromPaul van der Vlis <paul@vandervlis.nl>
Date2024-07-03 13:41 +0200
Message-ID<v63ddl$25s1i$1@dont-email.me>
In reply to#9653
Op 03-07-2024 om 13:01 schreef Paul van der Vlis:
> Op 02-07-2024 om 02:33 schreef Adri Verhoef:
>> Op moederschip aarde schreef iemand die zich identificeerde als
>> De ongekruisigde (ds.) <deongekruisigde@invalid.invalid>:
>>> On 2024-06-29, Paul van der Vlis <paul@vandervlis.nl> wrote:
>>>> Hoi,
>>>>
>>>> Ik probeer de data te redden van een USB-disk. De vorige twee keer ging
>>>> dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens
>>>> het starten, maar is al vrij snel weer verdwenen.
>>>>
>>>> Ik heb twee verschillende computers en kabels geprobeerd.
>>>> Zie onder output van dmesg.
>>>>
>>>> Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten
>>>> voortbestaan, zodat ik de data eraf kan halen?
>>>
>>> Als ik die log lees dan lijkt het ding gewoon kapot (elektronisch
>>> of zo). Waarschijnlijk helaas voor de data erop.
>>>
>>>
>>>> Groet,
>>>> Paul
>>>>
>>>>
>>>> 174264.957546] usb 1-1.5: new high-speed USB device number 23 using 
>>>> ehci-pci
>>>> [174265.107849] usb 1-1.5: New USB device found, idVendor=1058,
>>>> idProduct=2620, bcdDevice=10.23
>>>> [174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3,
>>>> SerialNumber=1
>>>> [174265.107855] usb 1-1.5: Product: Elements 2620
>>>> [174265.107856] usb 1-1.5: Manufacturer: Western Digital
>>>> [174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
>>>> [174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
>>>> [174265.108658] scsi host7: usb-storage 1-1.5:1.0
>>>> [174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620
>>>>    1023 PQ: 0 ANSI: 6
>>>> [174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
>>>> [174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
>>>> [174267.141475]
>>>> .........................................................ready
>>>> [174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ
>>>> CAPACITY(16).
>>>> [174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks:
>>>> (5.00 TB/4.55 TiB)
>>>> [174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
>>>> [174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
>>>> [174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
>>>> [174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
>>>> [174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
>>>> [174355.583306] usb 1-1.5: reset high-speed USB device number 23 using
>>>> ehci-pci
>>>> [174360.691216] usb 1-1.5: device descriptor read/64, error -110
>>>> [174376.306788] usb 1-1.5: device descriptor read/64, error -110
>>>> [174376.494792] usb 1-1.5: reset high-speed USB device number 23 using
>>>> ehci-pci
>>>> [174381.682674] usb 1-1.5: device descriptor read/64, error -110
>>>> [174397.306284] usb 1-1.5: device descriptor read/64, error -110
>>>> [174397.494297] usb 1-1.5: reset high-speed USB device number 23 using
>>>> ehci-pci
>>
>> https://askubuntu.com/questions/644010/ubuntu-cant-read-my-usb-device-descriptor-read-64-error-110
>> "The device descriptor read/64, error -110 means that USB port power 
>> supply was
>> exceeded."
>> https://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110
>> "USB error -110 means "Timeout expired before the transfer completed", 
>> which
>> could be caused by anything. Most commonly, it's because power was 
>> exceeded;
>> the host could not provide enough electric power for the pendrive to 
>> operate.
>> Because it has not enough power also the USB stick cannot provide the 
>> device
>> descriptor to the host, as a result it cannot be identified and so on. 
>> Maybe
>> your motherboard it's overloaded with devices that consume all the 
>> available
>> power."
>> "I had the same error, but with no USB device plugged in. I have a 
>> Suse 13.2
>> and 42.2 installed on an internal ssd drive in a HP ProBook 430. When 
>> I booted
>> into 42.2, I got that error and booting simply stopped there. Weird 
>> enough with
>> 13.2 on the same hard disk I could boot with no problems. Following 
>> Johnsters
>> advice to unplug any power supply including battery removal finally 
>> did it, so
>> loads of thanks go there. And to all running into this post without 
>> any obvious
>> interaction of USB devices in their problems: Try making your system 
>> voltage
>> free, it still might do the trick."
>> "Main voltage is not high enough in my home. It's below 180V (normally
>> 220-240). Sometimes I get the same error. Sometimes my PC restarts 
>> itself."
>>
>> Ik realiseer me dat dit niet per se de oplossing voor jouw probleem 
>> is, Paul,
>> het zijn slechts suggesties; misschien brengen ze je op ideeën om het 
>> probleem
>> aan te pakken.
> 
> Bedankt, ik ga hiernaar kijken...

Ik heb hem nu aan een vrij nieuwe laptop gehangen met een forse USB-C 
voeding en natuurlijk een accu. Op zich gebeurd zo ongeveer hetzelfde, 
alleen krijg ik nu error -62.

paul@laptopp:~$ grep '62' /usr/include/asm-generic/errno.h
#define	ETIME		62	/* Timer expired */
paul@laptopp:~$

Dus ook een timeout...

Fout 110 is officieel "Connextion timeout".

Groet,
Paul

-- 
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl

[toc] | [prev] | [next] | [standalone]

#9658

FromOzymandias <ozymandias@ozymandias.invalid>
Date2024-07-03 12:29 +0000
Message-ID<v63g6g$26b7t$2@dont-email.me>
In reply to#9654
On 2024-07-03, Paul van der Vlis <paul@vandervlis.nl> wrote:
> Op 03-07-2024 om 13:01 schreef Paul van der Vlis:
>> Op 02-07-2024 om 02:33 schreef Adri Verhoef:
>>> Op moederschip aarde schreef iemand die zich identificeerde als
>>> De ongekruisigde (ds.) <deongekruisigde@invalid.invalid>:
>>>> On 2024-06-29, Paul van der Vlis <paul@vandervlis.nl> wrote:
>>>>> Hoi,
>>>>>
>>>>> Ik probeer de data te redden van een USB-disk. De vorige twee keer ging
>>>>> dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens
>>>>> het starten, maar is al vrij snel weer verdwenen.
>>>>>
>>>>> Ik heb twee verschillende computers en kabels geprobeerd.
>>>>> Zie onder output van dmesg.
>>>>>
>>>>> Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten
>>>>> voortbestaan, zodat ik de data eraf kan halen?
>>>>
>>>> Als ik die log lees dan lijkt het ding gewoon kapot (elektronisch
>>>> of zo). Waarschijnlijk helaas voor de data erop.
>>>>
>>>>
>>>>> Groet,
>>>>> Paul
>>>>>
>>>>>
>>>>> 174264.957546] usb 1-1.5: new high-speed USB device number 23 using 
>>>>> ehci-pci
>>>>> [174265.107849] usb 1-1.5: New USB device found, idVendor=1058,
>>>>> idProduct=2620, bcdDevice=10.23
>>>>> [174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3,
>>>>> SerialNumber=1
>>>>> [174265.107855] usb 1-1.5: Product: Elements 2620
>>>>> [174265.107856] usb 1-1.5: Manufacturer: Western Digital
>>>>> [174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
>>>>> [174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
>>>>> [174265.108658] scsi host7: usb-storage 1-1.5:1.0
>>>>> [174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620
>>>>>    1023 PQ: 0 ANSI: 6
>>>>> [174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
>>>>> [174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
>>>>> [174267.141475]
>>>>> .........................................................ready
>>>>> [174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ
>>>>> CAPACITY(16).
>>>>> [174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks:
>>>>> (5.00 TB/4.55 TiB)
>>>>> [174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
>>>>> [174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
>>>>> [174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
>>>>> [174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
>>>>> [174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
>>>>> [174355.583306] usb 1-1.5: reset high-speed USB device number 23 using
>>>>> ehci-pci
>>>>> [174360.691216] usb 1-1.5: device descriptor read/64, error -110
>>>>> [174376.306788] usb 1-1.5: device descriptor read/64, error -110
>>>>> [174376.494792] usb 1-1.5: reset high-speed USB device number 23 using
>>>>> ehci-pci
>>>>> [174381.682674] usb 1-1.5: device descriptor read/64, error -110
>>>>> [174397.306284] usb 1-1.5: device descriptor read/64, error -110
>>>>> [174397.494297] usb 1-1.5: reset high-speed USB device number 23 using
>>>>> ehci-pci
>>>
>>> https://askubuntu.com/questions/644010/ubuntu-cant-read-my-usb-device-descriptor-read-64-error-110
>>> "The device descriptor read/64, error -110 means that USB port power 
>>> supply was
>>> exceeded."
>>> https://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110
>>> "USB error -110 means "Timeout expired before the transfer completed", 
>>> which
>>> could be caused by anything. Most commonly, it's because power was 
>>> exceeded;
>>> the host could not provide enough electric power for the pendrive to 
>>> operate.
>>> Because it has not enough power also the USB stick cannot provide the 
>>> device
>>> descriptor to the host, as a result it cannot be identified and so on. 
>>> Maybe
>>> your motherboard it's overloaded with devices that consume all the 
>>> available
>>> power."
>>> "I had the same error, but with no USB device plugged in. I have a 
>>> Suse 13.2
>>> and 42.2 installed on an internal ssd drive in a HP ProBook 430. When 
>>> I booted
>>> into 42.2, I got that error and booting simply stopped there. Weird 
>>> enough with
>>> 13.2 on the same hard disk I could boot with no problems. Following 
>>> Johnsters
>>> advice to unplug any power supply including battery removal finally 
>>> did it, so
>>> loads of thanks go there. And to all running into this post without 
>>> any obvious
>>> interaction of USB devices in their problems: Try making your system 
>>> voltage
>>> free, it still might do the trick."
>>> "Main voltage is not high enough in my home. It's below 180V (normally
>>> 220-240). Sometimes I get the same error. Sometimes my PC restarts 
>>> itself."
>>>
>>> Ik realiseer me dat dit niet per se de oplossing voor jouw probleem 
>>> is, Paul,
>>> het zijn slechts suggesties; misschien brengen ze je op ideeën om het 
>>> probleem
>>> aan te pakken.
>> 
>> Bedankt, ik ga hiernaar kijken...
>
> Ik heb hem nu aan een vrij nieuwe laptop gehangen met een forse USB-C 
> voeding en natuurlijk een accu. Op zich gebeurd zo ongeveer hetzelfde, 
> alleen krijg ik nu error -62.
>
> paul@laptopp:~$ grep '62' /usr/include/asm-generic/errno.h
> #define	ETIME		62	/* Timer expired */
> paul@laptopp:~$
>
> Dus ook een timeout...
>
> Fout 110 is officieel "Connextion timeout".

Dit lijkt einde oefening. Als de data echt belangrijk zijn dan
zou je nog zo'n gespecialeerd bedrijf kunnen overwegen.


-- 
"My name is Ozymandias, King of Kings:
Look on my works, ye Mighty, and despair!"

[toc] | [prev] | [next] | [standalone]

#9656

FromPaul van der Vlis <paul@vandervlis.nl>
Date2024-07-03 13:58 +0200
Message-ID<v63edt$25s1i$3@dont-email.me>
In reply to#9648
Op 02-07-2024 om 02:33 schreef Adri Verhoef:
> Op moederschip aarde schreef iemand die zich identificeerde als
> De ongekruisigde (ds.) <deongekruisigde@invalid.invalid>:
>> On 2024-06-29, Paul van der Vlis <paul@vandervlis.nl> wrote:
>>> Hoi,
>>>
>>> Ik probeer de data te redden van een USB-disk. De vorige twee keer ging
>>> dat goed. Maar hier verschijnt /dev/sdd alleen tijdelijk even tijdens
>>> het starten, maar is al vrij snel weer verdwenen.
>>>
>>> Ik heb twee verschillende computers en kabels geprobeerd.
>>> Zie onder output van dmesg.
>>>
>>> Heeft iemand nog ideeën wat ik zou kunnen doen om /dev/sdd te laten
>>> voortbestaan, zodat ik de data eraf kan halen?
>>
>> Als ik die log lees dan lijkt het ding gewoon kapot (elektronisch
>> of zo). Waarschijnlijk helaas voor de data erop.
>>
>>
>>> Groet,
>>> Paul
>>>
>>>
>>> 174264.957546] usb 1-1.5: new high-speed USB device number 23 using ehci-pci
>>> [174265.107849] usb 1-1.5: New USB device found, idVendor=1058,
>>> idProduct=2620, bcdDevice=10.23
>>> [174265.107853] usb 1-1.5: New USB device strings: Mfr=2, Product=3,
>>> SerialNumber=1
>>> [174265.107855] usb 1-1.5: Product: Elements 2620
>>> [174265.107856] usb 1-1.5: Manufacturer: Western Digital
>>> [174265.107858] usb 1-1.5: SerialNumber: 57583732443631304B365431
>>> [174265.108279] usb-storage 1-1.5:1.0: USB Mass Storage device detected
>>> [174265.108658] scsi host7: usb-storage 1-1.5:1.0
>>> [174266.118725] scsi 7:0:0:0: Direct-Access     WD       Elements 2620
>>>    1023 PQ: 0 ANSI: 6
>>> [174266.119767] sd 7:0:0:0: Attached scsi generic sg4 type 0
>>> [174266.123256] sd 7:0:0:0: [sdd] Spinning up disk...
>>> [174267.141475]
>>> .........................................................ready
>>> [174324.485251] sd 7:0:0:0: [sdd] Very big device. Trying to use READ
>>> CAPACITY(16).
>>> [174324.485882] sd 7:0:0:0: [sdd] 9767475200 512-byte logical blocks:
>>> (5.00 TB/4.55 TiB)
>>> [174324.485885] sd 7:0:0:0: [sdd] 4096-byte physical blocks
>>> [174324.487263] sd 7:0:0:0: [sdd] Write Protect is off
>>> [174324.487268] sd 7:0:0:0: [sdd] Mode Sense: 47 00 10 08
>>> [174324.488713] sd 7:0:0:0: [sdd] No Caching mode page found
>>> [174324.488721] sd 7:0:0:0: [sdd] Assuming drive cache: write through
>>> [174355.583306] usb 1-1.5: reset high-speed USB device number 23 using
>>> ehci-pci
>>> [174360.691216] usb 1-1.5: device descriptor read/64, error -110
>>> [174376.306788] usb 1-1.5: device descriptor read/64, error -110
>>> [174376.494792] usb 1-1.5: reset high-speed USB device number 23 using
>>> ehci-pci
>>> [174381.682674] usb 1-1.5: device descriptor read/64, error -110
>>> [174397.306284] usb 1-1.5: device descriptor read/64, error -110
>>> [174397.494297] usb 1-1.5: reset high-speed USB device number 23 using
>>> ehci-pci
> 
> https://askubuntu.com/questions/644010/ubuntu-cant-read-my-usb-device-descriptor-read-64-error-110
> "The device descriptor read/64, error -110 means that USB port power supply was
> exceeded."
> https://stackoverflow.com/questions/13653692/device-descriptor-read-64-error-110
> "USB error -110 means "Timeout expired before the transfer completed", which
> could be caused by anything. Most commonly, it's because power was exceeded;
> the host could not provide enough electric power for the pendrive to operate.
> Because it has not enough power also the USB stick cannot provide the device
> descriptor to the host, as a result it cannot be identified and so on. Maybe
> your motherboard it's overloaded with devices that consume all the available
> power."
> "I had the same error, but with no USB device plugged in. I have a Suse 13.2
> and 42.2 installed on an internal ssd drive in a HP ProBook 430. When I booted
> into 42.2, I got that error and booting simply stopped there. Weird enough with
> 13.2 on the same hard disk I could boot with no problems. Following Johnsters
> advice to unplug any power supply including battery removal finally did it, so
> loads of thanks go there. And to all running into this post without any obvious
> interaction of USB devices in their problems: Try making your system voltage
> free, it still might do the trick."
> "Main voltage is not high enough in my home. It's below 180V (normally
> 220-240). Sometimes I get the same error. Sometimes my PC restarts itself."
> 
> Ik realiseer me dat dit niet per se de oplossing voor jouw probleem is, Paul,
> het zijn slechts suggesties; misschien brengen ze je op ideeën om het probleem
> aan te pakken.

Ik heb hem nu aan een vrij nieuwe laptop gehangen met een forse USB-C 
voeding en natuurlijk een accu. Op zich gebeurd zo ongeveer hetzelfde, 
alleen krijg ik nu error -62.

paul@laptopp:~$ grep '62' /usr/include/asm-generic/errno.h
#define	ETIME		62	/* Timer expired */
paul@laptopp:~$

Dus ook een timeout...

Fout 110 is officieel "Connextion timeout".

Groet,
Paul

-- 
Paul van der Vlis Linux systeembeheer Groningen
https://vandervlis.nl

[toc] | [prev] | [next] | [standalone]

#9695

Froma3@a3.nl.invalid (Adri Verhoef)
Date2024-07-15 00:00 +0000
Message-ID<sGn1CK.16uso@a3.nl.invalid>
In reply to#9656
Op moederschip aarde schreef iemand die zich identificeerde als
Paul van der Vlis  <paul@vandervlis.nl>:
>
>Ik heb hem nu aan een vrij nieuwe laptop gehangen met een forse USB-C 
>voeding en natuurlijk een accu. Op zich gebeurd zo ongeveer hetzelfde, 
>alleen krijg ik nu error -62.
>
>paul@laptopp:~$ grep '62' /usr/include/asm-generic/errno.h
>#define	ETIME		62	/* Timer expired */
>paul@laptopp:~$
>
>Dus ook een timeout...
>
>Fout 110 is officieel "Connextion timeout".

Tsja, of je nog iets aan mijn volgende zoekresultaat hebt, dat kan ik niet
beoordelen, Paul, maar je zou het volgende kunnen proberen: via
https://www.linuxquestions.org/questions/linux-hardware-18/i-get-a-device-descriptor-read-64-error-62-message-when-plugging-my-usb-key-4175733997/
"It's a hardware problem. Here is a little trick that has worked for several
people. Mind you, it's a very old thread." vond ik:
https://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error
(tja, zoals benoemd, het is een oud artikel, uit 2010):
"most probably it’s a result of hardware failure rather than a driver or kernel
bug. USB has an over-current protection, which gets triggered when power
consumption from the port is too high.
Unplug all USB devices from PC, turn power off, and wait a minute or two. Plug
everything back and boot into Linux.
I spent the whole morning, until found out why. I hope that this message will
save someone a few hours, and nerves.
PS: Actual errors may vary. You may see different port and/or error code. Ex.:
usb 3-1: device descriptor read/64, error -62"

Ik zou zeggen, blaat het niet, dan schaapt het niet.

Adri

[toc] | [prev] | [standalone]

Back to top | Article view | nl.comp.os.linux.techniek

csiph-web