| View previous topic :: View next topic |
| Author |
Message |
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
 Posted: Sat Nov 07, 2020 10:01 am Post subject: |
 |
|
After recovering the EEPROM I still can not boot.
Are there any dependencies between the EEPROM image and the firmware? |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Sat Nov 07, 2020 12:47 pm Post subject: |
|
|
samo,
The new BOOTLOADER: permits booting from USB, with no SD Card required.
It checks the SD card first.
Is your SD card fitted properly?
With no storage devices attached to the Pi at all, it should give a repeating pattern of flashes on the green LED as it looks for something to load.
If that's OK, your firmware is good.
Power off the Pi.
Fit the SD card only. No USB storage.
Its should draw the 'rainbow' test pattern, then in 20 sec or so, the screen should clear and kernel messages appear. Its a long wait.
Before the 'rainbow' test pattern appears, you get a different pattern of flashes as /boot is being read.
I don't think fixup4* and start4* are required to track the firmware.
Mine are from June this year.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Sat Nov 07, 2020 10:04 pm Post subject: |
|
|
After recovering the EEPROM and downloading the latest firmware and kernel the rpi4 is booting correctly again.
| Code: | # rpi-eeprom-update
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Do 3. Sep 12:11:43 UTC 2020 (1599135103)
LATEST: Do 3. Sep 12:11:43 UTC 2020 (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1 |
But sadly the external SDD still causes problems. The connection is always interrupted, no matter if with or without UAS, if mounted or not, if the SSD is accessed or not.
Interestingly, the happens periodically after 181s - 182s.
| Code: | ...
[ 1284.121661] usb 2-1: USB disconnect, device number 9
[ 1284.123471] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1284.123674] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
[ 1284.446049] usb 2-1: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd
[ 1284.466972] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[ 1284.466987] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 1284.466999] usb 2-1: Product: Extreme SSD
[ 1284.467010] usb 2-1: Manufacturer: SanDisk
[ 1284.467021] usb 2-1: SerialNumber: 323033344339343031313038
[ 1284.471044] usb 2-1: UAS is blacklisted for this device, using usb-storage instead
[ 1284.471158] usb 2-1: UAS is blacklisted for this device, using usb-storage instead
[ 1284.471172] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 1284.471674] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 55a8: 800000
[ 1284.471827] scsi host1: usb-storage 2-1:1.0
[ 1286.257774] scsi 1:0:0:0: Direct-Access SanDisk Extreme SSD 0111 PQ: 0 ANSI: 6
[ 1286.911966] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 1286.913246] sd 1:0:0:0: [sdb] Write Protect is off
[ 1286.913263] sd 1:0:0:0: [sdb] Mode Sense: 4b 00 10 00
[ 1286.913960] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 1286.915198] scsi 1:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6
[ 1287.027352] sdb: sdb1
[ 1287.030499] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 1466.997659] usb 2-1: USB disconnect, device number 10
[ 1467.006374] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1467.006658] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
...
[ 1649.889656] usb 2-1: USB disconnect, device number 11
[ 1649.896516] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1649.896726] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
...
[ 1832.705655] usb 2-1: USB disconnect, device number 12
[ 1832.716065] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 1832.716264] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
...
[ 2015.549657] usb 2-1: USB disconnect, device number 13
[ 2015.551579] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 2015.551784] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
...
[ 2198.393655] usb 2-1: USB disconnect, device number 14
[ 2198.395493] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 2198.395705] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
... |
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Sun Nov 08, 2020 9:32 am Post subject: |
|
|
samo,
That sounds like sleep timer somewhere.
Does it do it USB 2 or on a PC?
Test both.
The idea is to try to determine if its the Pi, or the drive.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Sun Nov 08, 2020 10:45 am Post subject: |
|
|
NeedySeagoon,
On USB2 it works smoothly.
| Code: | [45013.353511] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd
[45013.487087] usb 1-1.3: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[45013.487103] usb 1-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[45013.487115] usb 1-1.3: Product: Extreme SSD
[45013.487126] usb 1-1.3: Manufacturer: SanDisk
[45013.487138] usb 1-1.3: SerialNumber: 323033344339343031313038
[45013.489426] usb 1-1.3: UAS is blacklisted for this device, using usb-storage instead
[45013.489608] usb 1-1.3: UAS is blacklisted for this device, using usb-storage instead
[45013.489631] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[45013.491545] usb-storage 1-1.3:1.0: Quirks match for vid 0781 pid 55a8: 800000
[45013.491716] scsi host1: usb-storage 1-1.3:1.0
[45015.248606] scsi 1:0:0:0: Direct-Access SanDisk Extreme SSD 0111 PQ: 0 ANSI: 6
[45015.891821] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[45015.892113] scsi 1:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6
[45015.892719] sd 1:0:0:0: [sdb] Write Protect is off
[45015.892734] sd 1:0:0:0: [sdb] Mode Sense: 4b 00 10 00
[45015.896100] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[45016.000686] sdb: sdb1
[45016.003768] sd 1:0:0:0: [sdb] Attached SCSI disk |
Comparing USB2 from my previous post with USB3 from above I see the following differences:
USB2: | Code: | [45013.353511] usb 1-1.3: new high-speed USB device number 3 using xhci_hcd
... |
USB3: | Code: | [ 1284.446049] usb 2-1: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd
...
[ 1286.915198] scsi 1:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6 |
And it works also smoothly at the PC (USB3)
| Code: | [ 2490.793093] usb 4-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 2490.805774] usb 4-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[ 2490.805777] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 2490.805779] usb 4-1: Product: Extreme SSD
[ 2490.805780] usb 4-1: Manufacturer: SanDisk
[ 2490.805782] usb 4-1: SerialNumber: 323033344339343031313038
[ 2490.808404] scsi host6: uas
[ 2492.205552] scsi 6:0:0:0: Direct-Access SanDisk Extreme SSD 0111 PQ: 0 ANSI: 6
[ 2492.206017] sd 6:0:0:0: Attached scsi generic sg3 type 0
[ 2492.206497] scsi 6:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6
[ 2492.206662] sd 6:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[ 2492.206740] sd 6:0:0:0: [sdc] Write Protect is off
[ 2492.206742] sd 6:0:0:0: [sdc] Mode Sense: 4b 00 10 00
[ 2492.206906] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 2492.206945] scsi 6:0:0:1: Attached scsi generic sg4 type 13
[ 2492.207171] sd 6:0:0:0: [sdc] Optimal transfer size 33553920 bytes
[ 2492.217032] sdc: sdc1
[ 2492.218203] sd 6:0:0:0: [sdc] Attached SCSI disk |
Do you know how to get more debug info for USB in dmesg?
BR |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Sun Nov 08, 2020 11:00 am Post subject: |
|
|
samo,
That points the finger very firmly at the Pi.
Which kernel are you using on the Pi?
There is a USB debug option in the kernel. Its a kernel rebuild.
That's very much a last resort as kernel DEBUG options are permitted to interfere with normal operation.
There is also a kernel verbosity setting for dmesg. The kernel build sets a default value for it but it can be changed after booting too.
The kernel help tells how. Its will be a /proc or /sys setting.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Sun Nov 08, 2020 5:17 pm Post subject: |
|
|
NeddySeagoon,
I'm using the kernel which I downloaded together with firmware from https://github.com/raspberrypi/firmware
| Code: | # uname -a
Linux rpi4 5.4.74-v8+ #1366 SMP PREEMPT Fri Nov 6 14:45:23 GMT 2020 aarch64 GNU/Linux |
I will take a look at the debugging/verbosity options and try them out.
BR |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Sun Nov 08, 2020 5:45 pm Post subject: |
|
|
samo,
That's the prebuilt binary kernel you would have got had you built your own starting with | Code: | | make bcm2711_defconfig |
It should be good.
I'm running | Code: | # uname -a
Linux Pi4_~arm64 5.4.45-v8+ #1 SMP PREEMPT Fri Jun 12 21:56:38 BST 2020 aarch64 GNU/Linux |
which has a few tweaks.
That works here. I can host the binary if you want to try it, or you can get an older kernel out of git.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Sun Nov 08, 2020 8:32 pm Post subject: |
|
|
NeddySeagoon,
The USB debug options provide a lot of information in dmesg. Maybe a bit too much. But I noticed nothing unusual.
Before I now try to change the kernel verbosity, I gratefully accept your offer and try it with your kernel.
BR |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Mon Nov 09, 2020 1:39 pm Post subject: |
|
|
samo,
My Pi4 kernel bits and pieces are at http://bloodnoc.org/~roy/Pi4/samo/
A few words of explanation are in order.
$ ls public_html/Pi4/samo/ -1
This is the kernel modules directory. Copy it recursively to /lib/modules/ beside the kernel modules you already have. You must not change its name, its used by the kernel to find its modules.
| Code: | | bcm2711-rpi-4-b.dtb_64 |
This is the device tree file. It goes in to /boot. Its not the default file name. You can either rename it or add a line to /boot/confiig.txt to use it. See Later.
It gets generated by compiling te the kernel.
| Code: | fixup4cd.dat
fixup4.dat
fixup4db.dat
fixup4x.dat |
These are the fixup4.* files used by the Pi4. You should not need them, they are included for completeness.
This is the kernel. It goes in to /boot. Its not the default file name. You can either rename it or add a line to /boot/confiig.txt to use it.
| Code: | start4cd.elf
start4db.elf
start4.elf
start4x.elf |
These are the start4.* files used by the Pi4. You should not need them, they are included for completeness.
To use my kernel and device tree names add the following to /boot/config.txt
| Code: | # as we don't use default kernel names, we must set 64 bit mode.
# arm_control=0x200 # is the old way
arm_64bit=1
# Pi 4
device_tree=bcm2711-rpi-4-b.dtb_64
# Pi 4 64 bit
kernel=kernel-5.4.45-v8+ |
That switches the Pi to 64 bit mode and loads the named device_tree and kernel.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Mon Nov 09, 2020 10:01 pm Post subject: |
|
|
NeddySeagoon,
I copied the modules, kernel, bcm2711-rpi-4-b.dtb_64 and modified the config.txt as described. The SSD is still periodically disconnected. I uploaded my dmesg output here
Can you upload your dmesg output for comparison?
BR |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Tue Nov 10, 2020 8:49 am Post subject: |
|
|
samo,
dmesg from my Pi 4.
/dev/sdb ?
Root is on /dev/mmcblk0p3
What is /dev/sda?
Please post youroutput. Be sure its lists both drives.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Tue Nov 10, 2020 12:53 pm Post subject: |
|
|
NeddySeagoon,
The diff is a bit confusing in the second half, because I use OpenRc and you systemd (see also Pastebin).
My SSD is first connected as sda and after the disconnect it is connected as sdb.
Are there any relevant hardware changes from Raspberry Pi 4 Model B Rev 1.2 to Rev 1.4?
BR
Last edited by samo on Tue Nov 10, 2020 10:38 pm; edited 2 times in total |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Tue Nov 10, 2020 4:59 pm Post subject: |
|
|
samo,
I use OpenRC everywhere.
Google wants me to log in to view your diff. That's not happening.
Please use a pastebin.
-- edit --
Wild guess. Do you have power management enabled in the drive, so that it goes to sleep after 3 minutes of inactivity.?
What do you get in the log when you do | Code: | | dd if=/dev/sda of=/dev/null |
That will copy the content of /dev/sda to /dev/null.
It should take a lot longer than 3 minutes too. Do you get errors while the drive is active?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Wed Nov 11, 2020 8:57 am Post subject: |
|
|
NeddySeagoon,
also while dd is running the SSD is disconnected.
BR |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Wed Nov 11, 2020 10:45 pm Post subject: |
|
|
| Even if I completely disable power management in the kernel (CONFIG_PM = n), the SSD is periodically disconnected. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Wed Nov 11, 2020 10:50 pm Post subject: |
|
|
samo,
We can rule out power management then.
Power management can be done by both the kernel and the drive, but not when the drive is busy, which was the point of the keep the drive busy test.
I've run out of ideas ant its time to sleep too. I'll post back if anything else occurs to me.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Thu Nov 12, 2020 8:45 am Post subject: |
|
|
| Also with the latest Raspberry Pi OS (32-bit, 2020-08-20) the SSD is periodically disconnected. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Thu Nov 12, 2020 9:16 am Post subject: |
|
|
samo,
About all that's left is the PSU,
The drive says that it needs 900mA (almost). If it went over 1200mA the PI PSU may have problems as that's all there is for all connected USB devices.
Do you ever get any undervolt alarms in dmesg, on the screen, or does the Red LED ever go out.
We are only looking for a very short undervolt spike so it may go undetected.
About the only test without an oscilloscope is to power the drive separately from the Pi.
That means a powered USB3 hub or some electronics skills.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Wed Nov 25, 2020 10:24 pm Post subject: |
|
|
Hi,
The SSD works (even with UAS) with an external power supply connected via y-cable
NeddySeagoon, thanks for supporting.
BR |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Wed Nov 25, 2020 11:36 pm Post subject: |
|
|
samo,
That's a real USB3 Y-cable?
Do you have a link?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Thu Nov 26, 2020 4:21 am Post subject: |
|
|
NeddySeagoon,
I ordered this one.
BR |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54208
Location: 56N 3W
|
| Posted: Thu Nov 26, 2020 2:01 pm Post subject: |
|
|
samo,
Thank you.
USB Y-cables have always been a horrible hack.
I thought they had gone away with USB3, so I've learned something there.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
samo
Guru
Joined: 13 Mar 2004
Posts: 489
|
| Posted: Thu Nov 26, 2020 7:39 pm Post subject: |
|
|
NeddySeagoon,
Maybe the problem with the Y-cables is that they connect 2 USB ports together? At least the init sequence looks confusing.
| Code: | [39755.021291] usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[39755.042354] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[39755.042372] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[39755.042384] usb 2-1: Product: Extreme SSD
[39755.042395] usb 2-1: Manufacturer: SanDisk
[39755.042406] usb 2-1: SerialNumber: 323033344339343031313038
[39755.054374] scsi host0: uas
[39756.656912] scsi 0:0:0:0: Direct-Access SanDisk Extreme SSD 0111 PQ: 0 ANSI: 6
[39756.659584] scsi 0:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6
[39756.659904] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[39756.660149] sd 0:0:0:0: [sda] Write Protect is off
[39756.660206] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[39756.661074] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[39756.661955] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
[39757.080839] usb 2-1: USB disconnect, device number 3
[39757.081482] usb 2-1: cmd cmplt err -108
[39757.081503] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[39757.081548] sd 0:0:0:0: tag#6 uas_zap_pending 0 uas-tag 1 inflight: CMD
[39757.081562] sd 0:0:0:0: tag#6 CDB: opcode=0x0 00 00 00 00 00 00
[39757.320936] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
[39757.320956] sd 0:0:0:0: [sda] Sense not available.
[39757.564943] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[39757.564962] sd 0:0:0:0: [sda] Sense not available.
[39757.660935] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[39757.868927] sda: detected capacity change from 1000204886016 to 0
[39758.196929] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
[39758.196948] sd 0:0:0:0: [sda] Sense not available.
[39758.436926] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[39758.436945] sd 0:0:0:0: [sda] Sense not available.
[39758.820925] sd 0:0:0:0: [sda] Attached SCSI disk
[39759.169286] usb 2-1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[39759.190264] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[39759.190284] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[39759.190296] usb 2-1: Product: Extreme SSD
[39759.190308] usb 2-1: Manufacturer: SanDisk
[39759.190318] usb 2-1: SerialNumber: 323033344339343031313038
[39759.201588] scsi host0: uas
[39760.801515] scsi 0:0:0:0: Direct-Access SanDisk Extreme SSD 0111 PQ: 0 ANSI: 6
[39760.804159] scsi 0:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6
[39760.804482] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[39760.805342] sd 0:0:0:0: [sda] Write Protect is off
[39760.805359] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[39760.806354] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[39760.807046] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
[39761.216853] usb 2-1: USB disconnect, device number 4
[39761.217503] usb 2-1: cmd cmplt err -108
[39761.217524] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[39761.217574] sd 0:0:0:0: tag#24 uas_zap_pending 0 uas-tag 1 inflight: CMD
[39761.217588] sd 0:0:0:0: tag#24 CDB: opcode=0x0 00 00 00 00 00 00
[39761.456937] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
[39761.456956] sd 0:0:0:0: [sda] Sense not available.
[39761.696912] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[39761.696931] sd 0:0:0:0: [sda] Sense not available.
[39761.796938] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[39762.088930] sda: detected capacity change from 1000204886016 to 0
[39762.408937] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=0x00
[39762.408956] sd 0:0:0:0: [sda] Sense not available.
[39762.648948] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[39762.648967] sd 0:0:0:0: [sda] Sense not available.
[39763.032944] sd 0:0:0:0: [sda] Attached SCSI disk
[39763.373262] usb 2-1: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[39763.398294] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[39763.398314] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[39763.398326] usb 2-1: Product: Extreme SSD
[39763.398337] usb 2-1: Manufacturer: SanDisk
[39763.398347] usb 2-1: SerialNumber: 323033344339343031313038
[39763.409821] scsi host0: uas
[39764.997188] scsi 0:0:0:0: Direct-Access SanDisk Extreme SSD 0111 PQ: 0 ANSI: 6
[39764.999311] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[39764.999496] sd 0:0:0:0: [sda] Write Protect is off
[39764.999513] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[39764.999821] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[39765.000481] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
[39765.002334] scsi 0:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6
[39765.022478] sda: sda1
[39765.026640] sd 0:0:0:0: [sda] Attached SCSI disk
[39765.464846] usb 2-1: USB disconnect, device number 5
[39765.467197] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[39765.708888] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
[39766.545338] usb 2-1: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
[39766.566294] usb 2-1: New USB device found, idVendor=0781, idProduct=55a8, bcdDevice= 1.11
[39766.566314] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[39766.566326] usb 2-1: Product: Extreme SSD
[39766.566337] usb 2-1: Manufacturer: SanDisk
[39766.566348] usb 2-1: SerialNumber: 323033344339343031313038
[39766.576843] scsi host0: uas
[39766.582077] scsi 0:0:0:0: Direct-Access SanDisk Extreme SSD 0111 PQ: 0 ANSI: 6
[39766.587783] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[39766.587960] sd 0:0:0:0: [sda] Write Protect is off
[39766.587965] scsi 0:0:0:1: Enclosure WD SES Device 0111 PQ: 0 ANSI: 6
[39766.587978] sd 0:0:0:0: [sda] Mode Sense: 4b 00 10 00
[39766.589855] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[39766.591282] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
[39766.613206] sda: sda1
[39766.617599] sd 0:0:0:0: [sda] Attached SCSI disk |
BR |
|
| Back to top |
|
|
|
Gentoo on Alternative Architectures
