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

Groups > alt.os.linux > #81253 > unrolled thread

Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE)

Started by"Carlos E.R." <robin_listas@es.invalid>
First post2025-04-03 22:01 +0200
Last post2025-04-05 22:03 +0200
Articles 6 on this page of 46 — 7 participants

Back to article view | Back to alt.os.linux

Contents

  Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-03 22:01 +0200
    Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-03 17:47 -0400
      Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 02:39 +0200
        Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-03 23:33 -0400
          Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 11:36 +0200
            Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:16 +0200
              Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 14:51 -0400
                Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 21:52 +0200
            Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-04 11:28 +0100
              Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:47 +0200
                Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-04 17:06 +0100
                  Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 19:09 +0200
                    Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "J.O. Aho" <user@example.net> - 2025-04-04 21:26 +0200
                      Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Mark Lloyd <not.email@all.invalid> - 2025-04-05 16:22 +0000
                        Re: Amazon (Was: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 21:01 +0200
      Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-06 14:44 +0200
    Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) vallor <vallor@cultnix.org> - 2025-04-04 06:30 +0000
      Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 03:53 -0400
        Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:53 +0200
          Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 13:44 +0200
          Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 23:40 +0200
            Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 13:33 +0200
              Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 18:23 +0200
                Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 21:04 +0200
      Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 12:15 +0200
        Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 16:30 -0400
          Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-04 22:52 +0200
            Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 18:46 -0400
            Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-05 00:20 +0100
              Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-04 23:05 -0400
              Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 12:47 +0200
                Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-05 14:14 +0100
                  Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 18:23 +0200
                    Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-06 00:13 -0400
                  Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Simon <SimonJ@eu.invalid> - 2025-04-07 09:42 +0000
                    Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-07 14:07 +0200
                      Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "J.O. Aho" <user@example.net> - 2025-04-07 16:37 +0200
                        Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-07 15:00 -0400
                          Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-08 02:34 +0200
                            Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-08 00:05 -0400
                            Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "J.O. Aho" <user@example.net> - 2025-04-08 08:09 +0200
                              Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Java Jive <java@evij.com.invalid> - 2025-04-08 11:16 +0100
                                Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) Paul <nospam@needed.invalid> - 2025-04-08 09:39 -0400
                              Re: Hard disk error (testing usb-storage instead of UAS) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-08 20:49 +0200
                                Re: Hard disk error (testing usb-storage instead of UAS) Paul <nospam@needed.invalid> - 2025-04-08 18:38 -0400
    Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 22:03 +0200

Page 3 of 3 — ← Prev page 1 2 [3]

#81307

From"J.O. Aho" <user@example.net>
Date2025-04-08 08:09 +0200
Message-ID<m5jsssFbl24U1@mid.individual.net>
In reply to#81304
On 08/04/2025 02.34, Carlos E.R. wrote:

> All the issues I have with this box appear to be caused by the firmware 
> of the box. None seem to be caused on the Linux side of things.

The workaround seems to be to degrade to the old USB behavior on the 
Linux side or flash a new firmware and hope it works.

Come back after you done one or other.

-- 
  //Aho

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

#81309

FromJava Jive <java@evij.com.invalid>
Date2025-04-08 11:16 +0100
Message-ID<vt2t1e$210id$1@dont-email.me>
In reply to#81307
On 2025-04-08 07:09, J.O. Aho wrote:
>
> On 08/04/2025 02.34, Carlos E.R. wrote:
>> 
>> All the issues I have with this box appear to be caused by the 
>> firmware of the box. None seem to be caused on the Linux side of things.
> 
> The workaround seems to be to degrade to the old USB behavior on the 
> Linux side or flash a new firmware and hope it works.

... which IIRC Paul thinks should be reversible if it doesn't, or return 
the unit as unfit for purpose and try a different make and model in the 
hope it has better firmware, &/or contact the manufacturer of either the 
box or the chip to explain the firmware problems and suggest that it 
would be in their interest to fix them, and suggest further that he, 
Carlos, would be willing to beta-test any fixed firmware they are 
willing to provide.

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

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

#81314

FromPaul <nospam@needed.invalid>
Date2025-04-08 09:39 -0400
Message-ID<vt38ub$2bi6o$1@dont-email.me>
In reply to#81309
On Tue, 4/8/2025 6:16 AM, Java Jive wrote:
> On 2025-04-08 07:09, J.O. Aho wrote:
>>
>> On 08/04/2025 02.34, Carlos E.R. wrote:
>>>
>>> All the issues I have with this box appear to be caused by the firmware of the box. None seem to be caused on the Linux side of things.
>>
>> The workaround seems to be to degrade to the old USB behavior on the Linux side or flash a new firmware and hope it works.
> 
> ... which IIRC Paul thinks should be reversible if it doesn't, or return the unit as unfit for purpose and try a different make and model in the hope it has better firmware, &/or contact the manufacturer of either the box or the chip to explain the firmware problems and suggest that it would be in their interest to fix them, and suggest further that he, Carlos, would be willing to beta-test any fixed firmware they are willing to provide.
> 

As I understand it, the flasher has a "record old BIOS function",
an "erase SPI chip", then power cycle the unit (a HDD must
be connected), and the "flash SPI chip" function can then
be used to flash the SPI.

If you did not like the result, you could flash in the backup
copy and return the unit to original condition.

The SPI chip is good for a large number of write attempts.
It's better quality than TLC for example. It should be NOR
flash, and not NAND flash. A handful of flash cycles won't
harm it. And while it has the "settings" storage for the
device (the NVRAM function), that's not going to receive
any changes (unless there existed a utility to do that).
The preferences are flashed in at the same time as the
flash main block. For example, one of your preferences
could be to turn off UAS, and to turn off aggressive
power saving (it will shut down the drive after ten seconds
of inactivity). There may be other ways in the passthru command
set, to spin down a drive.

But when your unit doesn't have a user manual, this must
all be my imagination :-)

   Paul

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

#81317 — Re: Hard disk error (testing usb-storage instead of UAS)

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-04-08 20:49 +0200
SubjectRe: Hard disk error (testing usb-storage instead of UAS)
Message-ID<0n7gclx6mh.ln2@Telcontar.valinor>
In reply to#81307
On 2025-04-08 08:09, J.O. Aho wrote:
> On 08/04/2025 02.34, Carlos E.R. wrote:
> 
>> All the issues I have with this box appear to be caused by the 
>> firmware of the box. None seem to be caused on the Linux side of things.
> 
> The workaround seems to be to degrade to the old USB behavior on the 
> Linux side or flash a new firmware and hope it works.
> 
> Come back after you done one or other.
> 

<0.5> 2025-04-08T19:57:43.732682+02:00 Isengard kernel - - - [    T0] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.4.0-150600.23.42-default root=UUID=0d457df1-... showopts splash=verbose resume=/dev/disk/by-label/Swap verbose mitigations=auto usbstorage.quirks=152d:0578:u

...

<0.6> 2025-04-08T19:59:29.396137+02:00 Isengard kernel - - - [    T9] usb 2-1: new SuperSpeed USB device number 8 using xhci_hcd
<0.6> 2025-04-08T19:59:29.416175+02:00 Isengard kernel - - - [    T9] usb 2-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= 3.01
<0.6> 2025-04-08T19:59:29.416230+02:00 Isengard kernel - - - [    T9] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<0.6> 2025-04-08T19:59:29.416234+02:00 Isengard kernel - - - [    T9] usb 2-1: Product: External HDD
<0.6> 2025-04-08T19:59:29.416237+02:00 Isengard kernel - - - [    T9] usb 2-1: Manufacturer: External USB3.0
<0.6> 2025-04-08T19:59:29.416239+02:00 Isengard kernel - - - [    T9] usb 2-1: SerialNumber: 0000007788FC
<0.6> 2025-04-08T19:59:29.420143+02:00 Isengard kernel - - - [    T9] usb-storage 2-1:1.0: USB Mass Storage device detected
<0.6> 2025-04-08T19:59:29.420175+02:00 Isengard kernel - - - [    T9] usb-storage 2-1:1.0: Quirks match for vid 152d pid 0578: 1800000
<0.6> 2025-04-08T19:59:29.420178+02:00 Isengard kernel - - - [    T9] scsi host6: usb-storage 2-1:1.0
<1.6> 2025-04-08T19:59:29.441025+02:00 Isengard mtp-probe - - -  checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
<1.6> 2025-04-08T19:59:29.441602+02:00 Isengard mtp-probe - - -  bus: 2, device: 8 was not an MTP device
<1.6> 2025-04-08T19:59:29.475720+02:00 Isengard mtp-probe - - -  checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
<1.6> 2025-04-08T19:59:29.475976+02:00 Isengard mtp-probe - - -  bus: 2, device: 8 was not an MTP device
<0.5> 2025-04-08T19:59:30.456232+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:0: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:30.456274+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:1: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:30.456278+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:2: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:30.456283+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:3: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:30.456285+02:00 Isengard kernel - - - [   T41] sd 6:0:0:0: Attached scsi generic sg7 type 0
<0.5> 2025-04-08T19:59:30.456287+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:30.456289+02:00 Isengard kernel - - - [   T41] sd 6:0:0:1: Attached scsi generic sg8 type 0
<0.5> 2025-04-08T19:59:30.456291+02:00 Isengard kernel - - - [   T41] sd 6:0:0:2: Attached scsi generic sg9 type 0
<0.5> 2025-04-08T19:59:30.456293+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:30.456295+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:30.456297+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:3: Attached scsi generic sg10 type 0
<0.5> 2025-04-08T19:59:30.456298+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Write Protect is off
<0.7> 2025-04-08T19:59:30.456300+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:30.463175+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Disabling FUA
<0.5> 2025-04-08T19:59:30.463216+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:30.463219+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:30.463221+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:30.463224+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:30.463226+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:30.463228+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:30.463230+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:30.463231+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:30.463233+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Write Protect is off
<0.7> 2025-04-08T19:59:30.463234+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:30.463236+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Disabling FUA
<0.5> 2025-04-08T19:59:30.463238+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:30.484172+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Write Protect is off
<0.7> 2025-04-08T19:59:30.484208+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:30.484212+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Disabling FUA
<0.5> 2025-04-08T19:59:30.484214+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:30.484216+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:30.484218+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:30.484220+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Write Protect is off
<0.7> 2025-04-08T19:59:30.484221+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:30.484223+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Disabling FUA
<0.5> 2025-04-08T19:59:30.484225+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:30.488218+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Attached SCSI disk
<0.5> 2025-04-08T19:59:30.528130+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Attached SCSI disk
<0.5> 2025-04-08T19:59:30.544181+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Attached SCSI disk
<0.5> 2025-04-08T19:59:30.548130+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Attached SCSI disk
<1.4> 2025-04-08T19:59:31.044839+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdh': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
<1.4> 2025-04-08T19:59:31.045188+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdf': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
<1.4> 2025-04-08T19:59:31.045344+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdi': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
<1.4> 2025-04-08T19:59:31.056710+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdg': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
<0.6> 2025-04-08T19:59:32.400127+02:00 Isengard kernel - - - [    T9] usb 2-3: new SuperSpeed USB device number 9 using xhci_hcd
<0.6> 2025-04-08T19:59:32.420138+02:00 Isengard kernel - - - [    T9] usb 2-3: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= 3.01
<0.6> 2025-04-08T19:59:32.420174+02:00 Isengard kernel - - - [    T9] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<0.6> 2025-04-08T19:59:32.420177+02:00 Isengard kernel - - - [    T9] usb 2-3: Product: External HDD
<0.6> 2025-04-08T19:59:32.420180+02:00 Isengard kernel - - - [    T9] usb 2-3: Manufacturer: External USB3.0
<0.6> 2025-04-08T19:59:32.420183+02:00 Isengard kernel - - - [    T9] usb 2-3: SerialNumber: 0000007788FC
<0.6> 2025-04-08T19:59:32.428144+02:00 Isengard kernel - - - [    T9] usb-storage 2-3:1.0: USB Mass Storage device detected
<0.6> 2025-04-08T19:59:32.428192+02:00 Isengard kernel - - - [    T9] usb-storage 2-3:1.0: Quirks match for vid 152d pid 0578: 1800000
<0.6> 2025-04-08T19:59:32.428195+02:00 Isengard kernel - - - [    T9] scsi host7: usb-storage 2-3:1.0
<1.6> 2025-04-08T19:59:32.441321+02:00 Isengard mtp-probe - - -  checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
<1.6> 2025-04-08T19:59:32.441561+02:00 Isengard mtp-probe - - -  bus: 2, device: 9 was not an MTP device
<1.6> 2025-04-08T19:59:32.474703+02:00 Isengard mtp-probe - - -  checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
<1.6> 2025-04-08T19:59:32.474934+02:00 Isengard mtp-probe - - -  bus: 2, device: 9 was not an MTP device
<0.5> 2025-04-08T19:59:33.460167+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:0: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:33.460215+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:1: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:33.460221+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:2: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:33.460224+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:3: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
<0.5> 2025-04-08T19:59:33.460226+02:00 Isengard kernel - - - [   T40] sd 7:0:0:0: Attached scsi generic sg11 type 0
<0.5> 2025-04-08T19:59:33.460228+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:33.460230+02:00 Isengard kernel - - - [   T40] sd 7:0:0:1: Attached scsi generic sg12 type 0
<0.5> 2025-04-08T19:59:33.460232+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:33.460234+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:33.460235+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Write Protect is off
<0.7> 2025-04-08T19:59:33.460237+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:33.460238+02:00 Isengard kernel - - - [   T40] sd 7:0:0:2: Attached scsi generic sg13 type 0
<0.5> 2025-04-08T19:59:33.460240+02:00 Isengard kernel - - - [   T40] sd 7:0:0:3: Attached scsi generic sg14 type 0
<0.5> 2025-04-08T19:59:33.464177+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:33.464218+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:33.464221+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:33.464223+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Write Protect is off
<0.7> 2025-04-08T19:59:33.464226+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:33.464227+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Disabling FUA
<0.5> 2025-04-08T19:59:33.464229+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:33.464231+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:33.472155+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Disabling FUA
<0.5> 2025-04-08T19:59:33.472196+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:33.484228+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Attached SCSI disk
<0.5> 2025-04-08T19:59:33.484260+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:33.484264+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:33.484267+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Write Protect is off
<0.7> 2025-04-08T19:59:33.484269+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:33.484271+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Disabling FUA
<0.5> 2025-04-08T19:59:33.484393+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:33.484421+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Very big device. Trying to use READ CAPACITY(16).
<0.5> 2025-04-08T19:59:33.484444+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
<0.5> 2025-04-08T19:59:33.484461+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] 4096-byte physical blocks
<0.5> 2025-04-08T19:59:33.488234+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Write Protect is off
<0.7> 2025-04-08T19:59:33.488382+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Mode Sense: 47 00 00 08
<0.5> 2025-04-08T19:59:33.488388+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Disabling FUA
<0.5> 2025-04-08T19:59:33.488390+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
<0.5> 2025-04-08T19:59:33.508190+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Attached SCSI disk
<0.5> 2025-04-08T19:59:33.536129+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Attached SCSI disk
<0.5> 2025-04-08T19:59:33.560145+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Attached SCSI disk
<1.4> 2025-04-08T19:59:34.186210+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdl': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
<1.4> 2025-04-08T19:59:34.192694+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdk': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
<1.4> 2025-04-08T19:59:34.216776+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdm': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
<1.4> 2025-04-08T19:59:34.227692+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdj': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)


Disks are sdf to sdm.

Isengard:~ # hdparm -i /dev/sdf

/dev/sdf:
  HDIO_GET_IDENTITY failed: Invalid argument
Isengard:~ #

Same as before.

Isengard:~ # l /dev/disk/by-id/ | grep sd[fghijklm]
lrwxrwxrwx 1 root root    9 Apr  8 19:59 ata-ST10000NT001-3LY101_WP022E9S -> ../../sdl
lrwxrwxrwx 1 root root    9 Apr  8 19:59 ata-ST10000NT001-3LY101_WP022JMK -> ../../sdh
lrwxrwxrwx 1 root root    9 Apr  8 19:59 scsi-SExternal_USB3.0_0000007788FC -> ../../sdf
lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:0 -> ../../sdf
lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:1 -> ../../sdg
lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:2 -> ../../sdh
lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:3 -> ../../sdi
lrwxrwxrwx 1 root root    9 Apr  8 19:59 wwn-0x5000c500faa885cf -> ../../sdh
lrwxrwxrwx 1 root root    9 Apr  8 19:59 wwn-0x5000c500faa9884b -> ../../sdl
Isengard:~ #

As you can see, not every disk is identified, and those that are do not have all the methods.


Isengard:~ # l /dev/disk/by-path/ | grep sd[fghijklm]
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-scsi-0:0:0:1 -> ../../sdg
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-scsi-0:0:0:2 -> ../../sdh
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-scsi-0:0:0:3 -> ../../sdi
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdf
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:1 -> ../../sdg
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:2 -> ../../sdh
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:3 -> ../../sdi
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0 -> ../../sdj
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:1 -> ../../sdk
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:2 -> ../../sdl
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:3 -> ../../sdm
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:0 -> ../../sdf
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:1 -> ../../sdg
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:2 -> ../../sdh
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:3 -> ../../sdi
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:0 -> ../../sdj
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:1 -> ../../sdk
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:2 -> ../../sdl
lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:3 -> ../../sdm
Isengard:~ #

There should be 8 entries for each identification method, one of them is incomplete.

So, there is no advantage for using usb-storage instead of UAS, as I thought.



The good news is that the names like pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:1 hold across boots referring to the same serial name. They do not hold if a disk is removed, the list is then recreated. It appears that the names hold as long as the disks are untouched. This is not affected by the quircks change.


I obtain the serial number with this script:

+++·····················
Isengard:~ # cat /root/bin/YottamasterSerialNumber
#!/bin/bash

if [ $# -eq 0 ]; then
     echo "Gets the serial number of a device from SMART data. Ask only one disk at a time (Yotta bug)"
     exit
fi

THEDISK=$1

# Ask twice, the first one is a cached answer that has to be disregarded.
smartctl -d sat -a $THEDISK | grep "Serial Number" 1>/dev/null
smartctl -d sat -a $THEDISK | grep "Serial Number"



Isengard:~ #
·····················++-

-- 
Cheers, Carlos.

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

#81319 — Re: Hard disk error (testing usb-storage instead of UAS)

FromPaul <nospam@needed.invalid>
Date2025-04-08 18:38 -0400
SubjectRe: Hard disk error (testing usb-storage instead of UAS)
Message-ID<vt48hs$37980$1@dont-email.me>
In reply to#81317
On Tue, 4/8/2025 2:49 PM, Carlos E.R. wrote:
> On 2025-04-08 08:09, J.O. Aho wrote:
>> On 08/04/2025 02.34, Carlos E.R. wrote:
>>
>>> All the issues I have with this box appear to be caused by the firmware of the box. None seem to be caused on the Linux side of things.
>>
>> The workaround seems to be to degrade to the old USB behavior on the Linux side or flash a new firmware and hope it works.
>>
>> Come back after you done one or other.
>>
> 
> <0.5> 2025-04-08T19:57:43.732682+02:00 Isengard kernel - - - [    T0] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.4.0-150600.23.42-default root=UUID=0d457df1-... showopts splash=verbose resume=/dev/disk/by-label/Swap verbose mitigations=auto usbstorage.quirks=152d:0578:u
> 
> ...
> 
> <0.6> 2025-04-08T19:59:29.396137+02:00 Isengard kernel - - - [    T9] usb 2-1: new SuperSpeed USB device number 8 using xhci_hcd
> <0.6> 2025-04-08T19:59:29.416175+02:00 Isengard kernel - - - [    T9] usb 2-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= 3.01
> <0.6> 2025-04-08T19:59:29.416230+02:00 Isengard kernel - - - [    T9] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> <0.6> 2025-04-08T19:59:29.416234+02:00 Isengard kernel - - - [    T9] usb 2-1: Product: External HDD
> <0.6> 2025-04-08T19:59:29.416237+02:00 Isengard kernel - - - [    T9] usb 2-1: Manufacturer: External USB3.0
> <0.6> 2025-04-08T19:59:29.416239+02:00 Isengard kernel - - - [    T9] usb 2-1: SerialNumber: 0000007788FC
> <0.6> 2025-04-08T19:59:29.420143+02:00 Isengard kernel - - - [    T9] usb-storage 2-1:1.0: USB Mass Storage device detected
> <0.6> 2025-04-08T19:59:29.420175+02:00 Isengard kernel - - - [    T9] usb-storage 2-1:1.0: Quirks match for vid 152d pid 0578: 1800000
> <0.6> 2025-04-08T19:59:29.420178+02:00 Isengard kernel - - - [    T9] scsi host6: usb-storage 2-1:1.0
> <1.6> 2025-04-08T19:59:29.441025+02:00 Isengard mtp-probe - - -  checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> <1.6> 2025-04-08T19:59:29.441602+02:00 Isengard mtp-probe - - -  bus: 2, device: 8 was not an MTP device
> <1.6> 2025-04-08T19:59:29.475720+02:00 Isengard mtp-probe - - -  checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> <1.6> 2025-04-08T19:59:29.475976+02:00 Isengard mtp-probe - - -  bus: 2, device: 8 was not an MTP device
> <0.5> 2025-04-08T19:59:30.456232+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:0: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:30.456274+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:1: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:30.456278+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:2: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:30.456283+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:3: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:30.456285+02:00 Isengard kernel - - - [   T41] sd 6:0:0:0: Attached scsi generic sg7 type 0
> <0.5> 2025-04-08T19:59:30.456287+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:30.456289+02:00 Isengard kernel - - - [   T41] sd 6:0:0:1: Attached scsi generic sg8 type 0
> <0.5> 2025-04-08T19:59:30.456291+02:00 Isengard kernel - - - [   T41] sd 6:0:0:2: Attached scsi generic sg9 type 0
> <0.5> 2025-04-08T19:59:30.456293+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:30.456295+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:30.456297+02:00 Isengard kernel - - - [   T41] scsi 6:0:0:3: Attached scsi generic sg10 type 0
> <0.5> 2025-04-08T19:59:30.456298+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Write Protect is off
> <0.7> 2025-04-08T19:59:30.456300+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:30.463175+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Disabling FUA
> <0.5> 2025-04-08T19:59:30.463216+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:30.463219+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:30.463221+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:30.463224+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:30.463226+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:30.463228+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:30.463230+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:30.463231+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:30.463233+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Write Protect is off
> <0.7> 2025-04-08T19:59:30.463234+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:30.463236+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Disabling FUA
> <0.5> 2025-04-08T19:59:30.463238+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:30.484172+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Write Protect is off
> <0.7> 2025-04-08T19:59:30.484208+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:30.484212+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Disabling FUA
> <0.5> 2025-04-08T19:59:30.484214+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:30.484216+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:30.484218+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:30.484220+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Write Protect is off
> <0.7> 2025-04-08T19:59:30.484221+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:30.484223+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Disabling FUA
> <0.5> 2025-04-08T19:59:30.484225+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:30.488218+02:00 Isengard kernel - - - [  T412] sd 6:0:0:0: [sdf] Attached SCSI disk
> <0.5> 2025-04-08T19:59:30.528130+02:00 Isengard kernel - - - [   T39] sd 6:0:0:2: [sdh] Attached SCSI disk
> <0.5> 2025-04-08T19:59:30.544181+02:00 Isengard kernel - - - [   T10] sd 6:0:0:1: [sdg] Attached SCSI disk
> <0.5> 2025-04-08T19:59:30.548130+02:00 Isengard kernel - - - [   T40] sd 6:0:0:3: [sdi] Attached SCSI disk
> <1.4> 2025-04-08T19:59:31.044839+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdh': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> <1.4> 2025-04-08T19:59:31.045188+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdf': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> <1.4> 2025-04-08T19:59:31.045344+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdi': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> <1.4> 2025-04-08T19:59:31.056710+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdg': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> <0.6> 2025-04-08T19:59:32.400127+02:00 Isengard kernel - - - [    T9] usb 2-3: new SuperSpeed USB device number 9 using xhci_hcd
> <0.6> 2025-04-08T19:59:32.420138+02:00 Isengard kernel - - - [    T9] usb 2-3: New USB device found, idVendor=152d, idProduct=0578, bcdDevice= 3.01
> <0.6> 2025-04-08T19:59:32.420174+02:00 Isengard kernel - - - [    T9] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> <0.6> 2025-04-08T19:59:32.420177+02:00 Isengard kernel - - - [    T9] usb 2-3: Product: External HDD
> <0.6> 2025-04-08T19:59:32.420180+02:00 Isengard kernel - - - [    T9] usb 2-3: Manufacturer: External USB3.0
> <0.6> 2025-04-08T19:59:32.420183+02:00 Isengard kernel - - - [    T9] usb 2-3: SerialNumber: 0000007788FC
> <0.6> 2025-04-08T19:59:32.428144+02:00 Isengard kernel - - - [    T9] usb-storage 2-3:1.0: USB Mass Storage device detected
> <0.6> 2025-04-08T19:59:32.428192+02:00 Isengard kernel - - - [    T9] usb-storage 2-3:1.0: Quirks match for vid 152d pid 0578: 1800000
> <0.6> 2025-04-08T19:59:32.428195+02:00 Isengard kernel - - - [    T9] scsi host7: usb-storage 2-3:1.0
> <1.6> 2025-04-08T19:59:32.441321+02:00 Isengard mtp-probe - - -  checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
> <1.6> 2025-04-08T19:59:32.441561+02:00 Isengard mtp-probe - - -  bus: 2, device: 9 was not an MTP device
> <1.6> 2025-04-08T19:59:32.474703+02:00 Isengard mtp-probe - - -  checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-3"
> <1.6> 2025-04-08T19:59:32.474934+02:00 Isengard mtp-probe - - -  bus: 2, device: 9 was not an MTP device
> <0.5> 2025-04-08T19:59:33.460167+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:0: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:33.460215+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:1: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:33.460221+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:2: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:33.460224+02:00 Isengard kernel - - - [   T40] scsi 7:0:0:3: Direct-Access     External  USB3.0          0301 PQ: 0 ANSI: 6
> <0.5> 2025-04-08T19:59:33.460226+02:00 Isengard kernel - - - [   T40] sd 7:0:0:0: Attached scsi generic sg11 type 0
> <0.5> 2025-04-08T19:59:33.460228+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:33.460230+02:00 Isengard kernel - - - [   T40] sd 7:0:0:1: Attached scsi generic sg12 type 0
> <0.5> 2025-04-08T19:59:33.460232+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:33.460234+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:33.460235+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Write Protect is off
> <0.7> 2025-04-08T19:59:33.460237+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:33.460238+02:00 Isengard kernel - - - [   T40] sd 7:0:0:2: Attached scsi generic sg13 type 0
> <0.5> 2025-04-08T19:59:33.460240+02:00 Isengard kernel - - - [   T40] sd 7:0:0:3: Attached scsi generic sg14 type 0
> <0.5> 2025-04-08T19:59:33.464177+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:33.464218+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:33.464221+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:33.464223+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Write Protect is off
> <0.7> 2025-04-08T19:59:33.464226+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:33.464227+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Disabling FUA
> <0.5> 2025-04-08T19:59:33.464229+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:33.464231+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:33.472155+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Disabling FUA
> <0.5> 2025-04-08T19:59:33.472196+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:33.484228+02:00 Isengard kernel - - - [   T39] sd 7:0:0:0: [sdj] Attached SCSI disk
> <0.5> 2025-04-08T19:59:33.484260+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:33.484264+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:33.484267+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Write Protect is off
> <0.7> 2025-04-08T19:59:33.484269+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:33.484271+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Disabling FUA
> <0.5> 2025-04-08T19:59:33.484393+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:33.484421+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Very big device. Trying to use READ CAPACITY(16).
> <0.5> 2025-04-08T19:59:33.484444+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] 19532873728 512-byte logical blocks: (10.0 TB/9.10 TiB)
> <0.5> 2025-04-08T19:59:33.484461+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] 4096-byte physical blocks
> <0.5> 2025-04-08T19:59:33.488234+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Write Protect is off
> <0.7> 2025-04-08T19:59:33.488382+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Mode Sense: 47 00 00 08
> <0.5> 2025-04-08T19:59:33.488388+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Disabling FUA
> <0.5> 2025-04-08T19:59:33.488390+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> <0.5> 2025-04-08T19:59:33.508190+02:00 Isengard kernel - - - [ T4797] sd 7:0:0:2: [sdl] Attached SCSI disk
> <0.5> 2025-04-08T19:59:33.536129+02:00 Isengard kernel - - - [  T412] sd 7:0:0:3: [sdm] Attached SCSI disk
> <0.5> 2025-04-08T19:59:33.560145+02:00 Isengard kernel - - - [   T10] sd 7:0:0:1: [sdk] Attached SCSI disk
> <1.4> 2025-04-08T19:59:34.186210+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdl': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> <1.4> 2025-04-08T19:59:34.192694+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdk': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> <1.4> 2025-04-08T19:59:34.216776+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdm': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> <1.4> 2025-04-08T19:59:34.227692+02:00 Isengard udisksd 2856 - -  Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdj': Unexpected sense data returned:#0120000: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#0120010: 00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00    ................#012 (g-io-error-quark, 0)
> 
> 
> Disks are sdf to sdm.
> 
> Isengard:~ # hdparm -i /dev/sdf
> 
> /dev/sdf:
>  HDIO_GET_IDENTITY failed: Invalid argument
> Isengard:~ #
> 
> Same as before.
> 
> Isengard:~ # l /dev/disk/by-id/ | grep sd[fghijklm]
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 ata-ST10000NT001-3LY101_WP022E9S -> ../../sdl
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 ata-ST10000NT001-3LY101_WP022JMK -> ../../sdh
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 scsi-SExternal_USB3.0_0000007788FC -> ../../sdf
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:0 -> ../../sdf
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:1 -> ../../sdg
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:2 -> ../../sdh
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 usb-External_USB3.0_0000007788FC-0:3 -> ../../sdi
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 wwn-0x5000c500faa885cf -> ../../sdh
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 wwn-0x5000c500faa9884b -> ../../sdl
> Isengard:~ #
> 
> As you can see, not every disk is identified, and those that are do not have all the methods.
> 
> 
> Isengard:~ # l /dev/disk/by-path/ | grep sd[fghijklm]
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-scsi-0:0:0:1 -> ../../sdg
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-scsi-0:0:0:2 -> ../../sdh
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-scsi-0:0:0:3 -> ../../sdi
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdf
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:1 -> ../../sdg
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:2 -> ../../sdh
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:3 -> ../../sdi
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:0 -> ../../sdj
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:1 -> ../../sdk
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:2 -> ../../sdl
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usb-0:3:1.0-scsi-0:0:0:3 -> ../../sdm
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:0 -> ../../sdf
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:1 -> ../../sdg
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:2 -> ../../sdh
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:1:1.0-scsi-0:0:0:3 -> ../../sdi
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:0 -> ../../sdj
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:1 -> ../../sdk
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:2 -> ../../sdl
> lrwxrwxrwx 1 root root    9 Apr  8 19:59 pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:3 -> ../../sdm
> Isengard:~ #
> 
> There should be 8 entries for each identification method, one of them is incomplete.
> 
> So, there is no advantage for using usb-storage instead of UAS, as I thought.
> 
> 
> 
> The good news is that the names like pci-0000:00:14.0-usbv3-0:3:1.0-scsi-0:0:0:1 hold across boots referring to the same serial name. They do not hold if a disk is removed, the list is then recreated. It appears that the names hold as long as the disks are untouched. This is not affected by the quircks change.
> 
> 
> I obtain the serial number with this script:
> 
> +++·····················
> Isengard:~ # cat /root/bin/YottamasterSerialNumber
> #!/bin/bash
> 
> if [ $# -eq 0 ]; then
>     echo "Gets the serial number of a device from SMART data. Ask only one disk at a time (Yotta bug)"
>     exit
> fi
> 
> THEDISK=$1
> 
> # Ask twice, the first one is a cached answer that has to be disregarded.
> smartctl -d sat -a $THEDISK | grep "Serial Number" 1>/dev/null
> smartctl -d sat -a $THEDISK | grep "Serial Number"
> 
> 
> 
> Isengard:~ #
> ·····················++-
> 

The log makes it sound like it is using a smaller CDB definition for some
commands, and then switches to the 16 byte CDB when it finds a "very big device".

I found this in a Google:

   "48 bits are for toys. SCSI's 16-byte CDBs use 64-bit logical block addresses. This has been the case
    since the 1990s, and implementing the read(16) and write(16) commands has been mandatory for
    DASD targets since the turn of the century. As I wrote a decade ago this puts the maximum size supported
    by the SCSI protocol in the ZiBs. - JdeBP Apr 15, 2015 at 16:11"

I'd expect both BOT and UAS to use CDBs and the SCSI stack,
because as far as I know, that's what is used for "foreign devices".
Anything which was not a ribbon cable (in the old days), or is not
SATA in the current era, will likely see CDBs used. They're also
used (Mode Sense) for optical drives.

If it supports 16 byte CDB, it should be using it always.

The advantage of BOT over UAS, was BOT was supposed to work, and
UAS was not supposed to work. For some definition of the correct
firmware version.

   Paul

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

#81289

From"Carlos E.R." <robin_listas@es.invalid>
Date2025-04-05 22:03 +0200
Message-ID<fte8clxvj8.ln2@Telcontar.valinor>
In reply to#81253
On 2025-04-03 22:01, Carlos E.R. wrote:
> 
> Hi,
> 
> I just bought a hard disk enclosure, a Yottamaster 5Bay USB3.0 Model F55 
> (non raid). My plan is to build a software raid 6 later.
> 
> Bought here <https://www.amazon.es/dp/B083Q8Z2KM>
> 
> I think it is this one:
> 
> <https://yottamaster.com/products/yottamaster-aluminum-5-bay-usb3-1- 
> type-c-external-hard-drive-enclosure-for-3-5-2-5-inch-sata-hdd-ssd- 
> support-5-x-16tb-mac-style-direct-attached-storage-das-ps500c3>

I just realized a big bug.

Telcontar:~/tmp/disk1 # smartctl -l selftest /dev/sdg | grep "# 1"
# 1  Extended offline    Completed without error       00%      3992         -
Telcontar:~/tmp/disk1 # smartctl -l selftest /dev/sdh | grep "# 1"
# 1  Extended offline    Completed without error       00%      3992         -
Telcontar:~/tmp/disk1 #

That output is wrong, the results for each disk have to be different.


Telcontar:~/tmp/disk1 # smartctl -a /dev/sdg | grep "User Capacity"
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/sdh | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 #

That output is correct.

Telcontar:~/tmp/disk1 # smartctl -a /dev/sdh | grep "# 1"
# 1  Extended offline    Completed without error       00%      3992         -
Telcontar:~/tmp/disk1 # smartctl -a /dev/sdg | grep "# 1"
# 1  Extended offline    Completed without error       00%       618         -
Telcontar:~/tmp/disk1 #

This output is also correct.


Thus, some smartctl commands report the wrong data, all from the same disk.


I also noticed that the denominations /dev/sdX change when hot removing and inserting the same disk, so better use UUID to refer to partitions in the raid.


  /dev/disk/by-id/ | grep sd[gh]

ata-ST1000DM003-1CH162_S1D6LGPP -> ../../sdg
scsi-SExternal_USB3.0_0000007788FC -> ../../sdg
usb-External_USB3.0_0000007788FC-0:0 -> ../../sdg
wwn-0x5000c5005b57c31a -> ../../sdg

usb-External_USB3.0_0000007788FC-0:1 -> ../../sdh


Some of the denominations are missing, the only one that is usable is "usb-..."


  /dev/disk/by-path/ | grep sd[gh]

  pci-0000:03:00.0-scsi-0:0:0:0 -> ../../sdg
  pci-0000:03:00.0-scsi-0:0:0:1 -> ../../sdh
  pci-0000:03:00.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdg
  pci-0000:03:00.0-usb-0:1:1.0-scsi-0:0:0:1 -> ../../sdh
  pci-0000:03:00.0-usbv3-0:1:1.0-scsi-0:0:0:0 -> ../../sdg
  pci-0000:03:00.0-usbv3-0:1:1.0-scsi-0:0:0:1 -> ../../sdh

These are usable. Now I remove a disk. Wait... Connect it back.

  /dev/disk/by-path/ | grep sd[gh]

  pci-0000:03:00.0-scsi-0:0:0:0 -> ../../sdg
  pci-0000:03:00.0-scsi-0:0:0:1 -> ../../sdh
  pci-0000:03:00.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdg
  pci-0000:03:00.0-usb-0:1:1.0-scsi-0:0:0:1 -> ../../sdh
  pci-0000:03:00.0-usbv3-0:1:1.0-scsi-0:0:0:0 -> ../../sdg
  pci-0000:03:00.0-usbv3-0:1:1.0-scsi-0:0:0:1 -> ../../sdh


Ok, they hold.

  /dev/disk/by-id/ | grep sd[gh]

  ata-ST1000DM003-1CH162_S1D6LGPP -> ../../sdg
  scsi-SExternal_USB3.0_0000007788FC -> ../../sdg
  usb-External_USB3.0_0000007788FC-0:0 -> ../../sdg
  usb-External_USB3.0_0000007788FC-0:1 -> ../../sdh
  wwn-0x5000c5005b57c31a -> ../../sdg

They also hold, but not all are present, only the "usb...".


Oh, well.


Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:0 | grep "User Capacity"
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:1 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]

Remove and insert one disk here.

Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:0 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:0 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:1 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:1 | grep "User Capacity"
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:1 | grep "User Capacity"
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:0 | grep "User Capacity"
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:0 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 #


Notice that the first time I run the command changing disk it confuses them:

Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:0 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:0 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:1 | grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Telcontar:~/tmp/disk1 # smartctl -a /dev/disk/by-id/usb-External_USB3.0_0000007788FC-0:1 | grep "User Capacity"
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Telcontar:~/tmp/disk1 #



I believe all this is a consequence of overriding the disk serial number. Fortunately, I will use partition uuid or labels to mount them or create the raid...



-- 
Cheers, Carlos.

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | alt.os.linux

csiph-web