Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E.R." 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 21:52:37 +0200 Lines: 51 Message-ID: <5tp5clx4c8.ln2@Telcontar.valinor> References: <7263clxr47.ln2@Telcontar.valinor> <4bm3clx6pp.ln2@Telcontar.valinor> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net UmhVxURjB64PFwAnkpoGsALgjmhgvBVG/rnRW+pywBMfCsWwzJ X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:dhwEg5I+9xpkk+kLE+Yb/bT2LEo= sha256:7qzISZsBWr6bZJ2IbOJfe2ggEqgQxphZmQeIro/wEmY= User-Agent: Mozilla Thunderbird Content-Language: es-ES, en-CA In-Reply-To: Xref: csiph.com alt.os.linux:81271 alt.comp.os.windows-11:18279 On 2025-04-04 20:51, Paul wrote: > On Fri, 4/4/2025 6:16 AM, Carlos E.R. wrote: ... >> 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. Yes, there is a tiny blue LED that blinks fast with activity. It is hard to see. I mentioned in another post how to make it blink to identify a disk. > 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. Yes, that's a different model of box, more expensive. I intentionally did not buy that one because I prefer software raid. > > 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. No, my box has no modes, it is just separate disks. I will do a software raid 6 on that. This means it will be slow. -- Cheers, Carlos.