XPost: aus.computers   
   From: none@not.here   
      
   Computer Nerd Kev wrote:   
   > In aus.computers Paul  wrote:   
   >> On Wed, 12/24/2025 1:41 AM, Computer Nerd Kev wrote:   
   >>> In aus.computers Axel  wrote:   
   >>>> or in a nutshell.. the question now is why did it write to that drive   
   >>>> and not others? is the size of the drive or it's software/technology   
   >>>> relevant?   
   >>> Maybe that drive (or the NTFS driver) is just too slow for whatever   
   >>> signal issue you have with the rack to be triggered.   
   >>>   
   >>> I'm not sure if they still do it on new HDDs, but maybe there's a   
   >>> jumper setting on the other drives to limit the speed?   
   >>> https://en.wikipedia.org/wiki/SATA#SATA_1.5_Gbit/s_and_SATA_3_Gbit/s   
   >> No guarantees, but maybe an   
   >>   
   >>     lsusb   
   >>   
   >> and check the detection on the rack, would give   
   >> some idea of the controller being used.   
   > He said "swapped the cable to another motherboard (MB) SATA port"   
   > so that must mean the rack uses SATA connection/s to the   
   > motherboard, not USB. In that case "lsusb" won't show it. If the   
   > rack is poorly designed or an old model then maybe it introduces   
   > too much signal noise for operating at higer data speeds. Or maybe   
   > there's a bad connection, but he also said he replaced the rack.   
   >   
      
   the rack was in perfect condition. only reason I swapped it for a   
   (brand) new one is because I had one on hand, and of course to eliminate   
   the possibility that the original was defective in some way.   
      
   --   
   Linux Mint 22.2   
   {I shot Felix and buried him}   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)