failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)

[   12.460014] ata1: SRST failed (errno=-16)
[   17.626677] ata1: link is slow to respond, please be patient (ready=0)
[   22.480011] ata1: SRST failed (errno=-16)
[   27.646681] ata1: link is slow to respond, please be patient (ready=0)
[   38.106817] ata1.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[   48.266676] ata1: link is slow to respond, please be patient (ready=0)
[   53.120011] ata1: SRST failed (errno=-16)
[   58.286674] ata1: link is slow to respond, please be patient (ready=0)
[   63.140012] ata1: SRST failed (errno=-16)
[   68.306678] ata1: link is slow to respond, please be patient (ready=0)
[   78.766814] ata1.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[   88.926670] ata1: link is slow to respond, please be patient (ready=0)
[   93.780006] ata1: SRST failed (errno=-16)
[   98.946675] ata1: link is slow to respond, please be patient (ready=0)
[  103.800007] ata1: SRST failed (errno=-16)
[  108.966670] ata1: link is slow to respond, please be patient (ready=0)
[  119.426806] ata1.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[  129.586668] ata1: link is slow to respond, please be patient (ready=0)
[  134.440001] ata1: SRST failed (errno=-16)
[  139.606666] ata1: link is slow to respond, please be patient (ready=0)
[  144.460004] ata1: SRST failed (errno=-16)
[  149.626664] ata1: link is slow to respond, please be patient (ready=0)
[  160.086806] ata1.00: FORCE: horkage modified (noncq)
[  160.087219] ata1.00: ATA-8: ST3500320AS, SD15, max UDMA/133
[  160.087224] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (not used)
[  160.100556] ata1.00: configured for UDMA/133
[  160.100746] scsi 0:0:0:0: Direct-Access     ATA      ST3500320AS      SD15 PQ: 0 ANSI: 5

 

I have a second WD hard drive that is not being detected by the BIOS and is throwing the error "ata1.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)"

Some people say it's a bad drive but this has happened before and numerous powering on/off attempts got it going.  Most posts about this issue ended up saying it was just a bad SATA port (or possibly controller), so I'll try swapping cables and ports and see if there is a difference.


Tags:

init_dev_params, err_mask, ata, srst, errno, horkage, modified, noncq, udma, sectors, multi, lba, ncq, configured, scsi, pq, ansi, wd, detected, bios, quot, numerous, powering, attempts, posts, sata, controller, ll, swapping, cables, ports,

Latest Articles

  • How To Force Flash an AMD Instinct GPU To Another Model Using Debian Ubuntu Mint Linux
  • How To compile ollama from source to use unsupported AMD GPU with rocm in Ubuntu Debian
  • QEMU KVM Virtio GPU Windows Cannot Select 1080P
  • Linux Gnome Desktop Ubuntu Mint Debian Gets Slower After Weeks
  • Firefox How to Save Full Page As Screenshot/PDF
  • Nvidia Datacenter Driver Tesla Slow nvidia-smi response and high utilization with 0 usage
  • ffmpeg how to normalize / increase the volume of your audio
  • kdenlive audio blips pops cracks artifacts solution fix
  • haproxy / nginx certbot SSL issues
  • nginx how to see the real IP when behind a CDN
  • Docker how to find real container child process ID
  • Alibaba Aliyun how to reset password solution 'Setup does not meet the requirements, please resetting'
  • RTL88X Series 80Mhz hostapd mode for Linux Debian Kali
  • How To Deploy Your Own Mastodon Server in Docker
  • ffmpeg burning subtitles in non-English errors [Parsed_subtitles_0 @ 0x561d3a0b3b80] Glyph 0x6709 not found, selecting one more font for (Sans, 700, 0)
  • rsyslog in container config
  • Interesting Whisper AI CPU vs GPU Test
  • How to install pytorch with cuda capability for AI acceleration with Nvidia Tesla etc.. GPUs
  • How to Spider the web archive.org to recover your old website/webpage
  • Debian 10 /etc/apt/sources.list