Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Paul <nospam@needed.invalid>
Newsgroups: alt.os.linux,alt.comp.os.windows-11
Subject: Re: Hard disk error (Error probing device: Error sending ATA command IDENTIFY DEVICE)
Date: Fri, 4 Apr 2025 16:30:59 -0400
Organization: A noiseless patient Spider
Lines: 63
Message-ID: <vspfi8$ctlr$1@dont-email.me>
References: <7263clxr47.ln2@Telcontar.valinor> <m59ck7Fk3odU1@mid.individual.net> <v3o4clxl55.ln2@Telcontar.valinor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 04 Apr 2025 22:31:07 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="15c7dd755516e28e960ed4de4858fc1f"; logging-data="423611"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+zdAPUghGrT1RMzhom5AjwqIkxgbHGjuo="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
Cancel-Lock: sha1:jtxsiEJUsKR0Qh2S3krIH9Rdtqk=
Content-Language: en-US
In-Reply-To: <v3o4clxl55.ln2@Telcontar.valinor>
Xref: csiph.com alt.os.linux:81272 alt.comp.os.windows-11:18281

On Fri, 4/4/2025 6:15 AM, Carlos E.R. wrote:
> On 2025-04-04 08:30, vallor wrote:
>> On Thu, 3 Apr 2025 22:01:43 +0200, "Carlos E.R." <robin_listas@es.invalid>
>> wrote in <7263clxr47.ln2@Telcontar.valinor>:
> 
> ...
> 
>>> What do you think about the error?
>>>
>>> <1.4> 2025-04-03T20:16:01.859892+02:00 Telcontar udisksd 2769 - -  Error
>>> probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sde':
>>> 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)
>>>
>>>
>>> Bug report?
>>>
>>> (openSUSE Leap 15.6)
>>
>> Well, Linux seems to see the partitions...
>>
>> Maybe the drives will work anyway?  Have you tested them?
> 
> I don't have yet the blank hard disks to construct the software raid I intended, I expect them early next week.
> 
> I have two disks with data that I connected. I launched a file copy from both disks simultaneously (a /usr directory) and they are running at speeds of 4.5M/S. No errors on log.
> 
> I can try big file write, simultaneously, with dd.
> 
> Telcontar:~/tmp/disk1 # dd if=/dev/zero of=test bs=5M count=1000 status=progress oflag=direct
> 5117050880 bytes (5.1 GB, 4.8 GiB) copied, 29 s, 176 MB/s
> 1000+0 records in
> 1000+0 records out
> 5242880000 bytes (5.2 GB, 4.9 GiB) copied, 29.5996 s, 177 MB/s
> Telcontar:~/tmp/disk1 #
> 
> Telcontar:~/tmp/disk2 # dd if=/dev/zero of=test bs=5M count=1000 status=progress oflag=direct
> 5153751040 bytes (5.2 GB, 4.8 GiB) copied, 30 s, 172 MB/s
> 1000+0 records in
> 1000+0 records out
> 5242880000 bytes (5.2 GB, 4.9 GiB) copied, 30.4898 s, 172 MB/s
> Telcontar:~/tmp/disk2 #
> 
> 
> So at least plain normal usage works.

When you get your practice disks *do a capacity test*.

1) Create the array.
2) Fill the array with 1GB test files until it is full.
3) Did the array corrupt at 2.2TB worth of files ?

I could find evidence that the thing was using 28-bit LBA
instead of 48-bit LBA. I don't think the SATA specs even allow
that. All of SATA, should be in 48-bit addressing mode.

You should be *very suspicious* about this product,
and use test procedures appropriate for "mystery meat".

   Paul