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

Groups > alt.comp.os.windows-11 > #18276

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

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 2025-04-04 14:51 -0400
Organization A noiseless patient Spider
Message-ID <vsp9na$6off$1@dont-email.me> (permalink)
References (1 earlier) <vsmvmc$1n9gc$1@dont-email.me> <4bm3clx6pp.ln2@Telcontar.valinor> <vsnjul$2fgla$1@dont-email.me> <nql4clxn8s.ln2@Telcontar.valinor> <g5o4clxl55.ln2@Telcontar.valinor>

Cross-posted to 2 groups.

Show all headers | View raw

On Fri, 4/4/2025 6:16 AM, Carlos E.R. wrote:
> On 2025-04-04 11:36, Carlos E.R. wrote:
>> On 2025-04-04 05:33, Paul wrote:
>>> On Thu, 4/3/2025 8:39 PM, Carlos E.R. wrote:
>>>> On 2025-04-03 23:47, Paul wrote:
>>>>> On Thu, 4/3/2025 4:01 PM, Carlos E.R. wrote:
>>
>> ...
>>
>>>> Sigh.
>>>>
>>>>
>>>> So you think this is a firmware issue, and nothing can be done on the Linux side?
>>>>
>>>
>>> It would seem "the underground" is distributing various firmwares for
>>> this thing. Maybe the SPI bus really does have a firmware capability
>>> to "fix" the stupid thing ? The architecture document isn't exactly honest
>>> about this.
>>>
>>> jms578fwupdater.tgz   2,089,194 bytes
>>>
>>>       JMS578FwUpdate   4,130,828 bytes
>>>
>>> I guess that means some of the devices, have a 4MB SPI flash chip.
>>> and that's where the firmware is stored or something. THis could be
>>> a small 8 pin DIP near the JMB578 on the circuit board.
>>>
>>> I don't like to quote "sources" for things like this, unless
>>> there is some sort of traceability for them.
>>>
>>> The firmware may have been written by JMicron, but JMicron are
>>> not likely to be serving the file like a RealTek might.
>>>
>>> And since it's a flasher-firmware thing, the OS firmware support
>>> is not of the same delivery type (some devices accept dynamic
>>> firmware which is stored in device RAM). This would be a firmware
>>> that is stored in  an outboard chip from the JMS578. It fixes issue
>>> such as TRIM, UASP diaablement, proper support of power saving,
>>> and so on.
>>>
>>> The work you are doing, is similar to the work an enclosure
>>> engineer might do, before shipping this project. Each user
>>> apparently expected to "sweep the web", "look for bootleg firmware",
>>> "install" and "hope for the best". A science project.
>>
>> That's out of my league :-(
> 
> I also asked on the openSUSE mail list, and a chap named Bengt said:
> 
> +++·····················
> I have no experience with this device but it seems like others are having problems as well with idVendor=152d, idProduct=0578 (JMicron Technology JMS578 SATA 6Gb/s)
> 
> https://linux-hardware.org/?id=usb:152d-0578
> ·····················++-   

It is not the "device" you have to worry about, it is
the firmware load that makes a difference.

As long as JMicron do not list the firmware(s) they
have as part of their production (RAID, non-RAID,
frame-based switching, enclosure-handling), it is hard to know precisely
how many firmware types there are to choose from, and
whether a different one would work better.

You would expect some enclosure management support. Some
units have a LED per drive, and maybe the controller chip
can communicate with the mux and light the lights it wants
to light.

Another form of input the controllers had in the past,
was mode switches, you could select JBOD, RAID0, RAID1, RAID10
with a couple DIP switches on the enclosure. And the firmware
would read those and operate the disks (with metadata written on them)
accordingly. Like if one drive is the odd drive, the other the even
drive, your clusters or inodes end up in the correct order,
each time the enclosure boots.

You can do a JBOD, and run a softRAID on top of them, which I gather
was your plan, until the drives did not behave themselves.

   Paul

Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

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) "Carlos E.R." <robin_listas@es.invalid> - 2025-04-05 22:03 +0200

csiph-web