My system is Arch . I have a problem with:

Root@archiso ~ # [ 1324.8567321 ata5: softreset falled (deuice not ready) I 1331.876573) atas: softreset falled (device not ready) 1 1445.3900501 atas: Illegal qe active transItion (00000000-200000001) [ 1451.1733021 ata5: Illegal qc/active transition (00000000-300000001) [ 1523.0066961 ata5: 11legal qc_actlue transItion (00000000->00000001) [ 1561 .5133411 ataS: softreset failed (device not ready) ( 1591.9133513 ata5: Illegal qc_active transition (00000000->00000001) [ 1601.9366601 ata5: softreset failed (device not ready) [ 1619.750020] ataS: softreset falled (device not ready? [ 1901.9165911 ata5: softreset falled (device not ready) [ 1911.9632591 ata5: softreset falled (device not ready) [1916.9999571 ata5: softreset failed (device not ready) [ 1952.1732931 ata5: softreset failed (device not ready) [ 1952.1733501 atas: reset failed, gluing up [ 1962.1932521 ataS: softreset falled (device not ready) [ 1972.2132911 ata5: softreset falled (device not ready) [ 2007.2232361 ata5: softreset failed (device not ready) [ 2012.4265781 ateS: softreset falled (device not ready) I 2012.4266381 ata5: reset failed, giving up

My computer components : Custom Built Gaming PC with RGB

/Ryzen 5 1600/ 1TB

SSD/16GB DDR4 Ram/

AMD RX570

Does anyone know how to solve this problem?

Thank you in advance for your help.

  • theodoremangini@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    The most likely cause? Failed hard drive.

    Other possible causes? GRUB misconfigurations, kernel misconfigurations, bad M2 controller, etc…

    First, determine if hard drive needs replaced. If not, Google the error and work through the many possible solutions. Or reformat and reinstall.

    • frugallyliving@alien.topOPB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Good morning, and thank you for responding. I appreciate you taking the time to respond to my question. Do you recommend that I replace the hard drive and then run computer diagnostics?

      In addition, I will most likely perform S.M.A.R.T. • Perform an S.M.A.R.T. test on my SSD to rule out any potential hardware concerns. To accomplish this, I can use the smartctl command:

      smartctl /dev/sda -a

      If it doesn’t work, I’ll try Kernel Modules:•It’s possible that the problem is caused by a kernel module connected to my storage devices. I can try reloading these modules with the command:

      -r modprobe [module_name] [module_name] modprobe

      However, I’m not sure how to discover the module name; could you point me in the appropriate direction?

      I hope to hear from you soon. thank you!