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

  • Cisco Switches How To Get Of Port Line Status Console Messages
  • Cisco DHCP Snooping Relay Setup Information
  • Cisco Switch Setup Guide Command List
  • Cisco 2960 Switch Reset To Factory Defaults
  • How To Boot Cisco CUCM UCSInstall 8.6, 10, 11 and 12 on KVM/Proxmox
  • VBOX VirtualBox How To Import Raw .img Disk File
  • Windows Server 2012, 2016, 2019 How To Install and Missing Disabled Telnet Client
  • proxmox vm networking breaks when you restart your network on the hostnode
  • Linux ln symlink how to update existing symbolic link
  • Ubuntu 18.04 / Linux Mint 19.1 Cannot Type or Login - solution
  • LUKS Hard Drive Encryption on Linux Mint Ubuntu Debian etc how to mount encrypted hard drive
  • How to use nmap locate other machines/computers/servers on your network using nmap
  • Linux Mint 18.2 Create Config File To Start Application Upon Login
  • Dell Wyse Thin Client BIOS Access Key
  • sudoers file in /etc warning about comments/includes!
  • Centos 7 Reallocate logical volume space to another
  • lvm how to reduce volume size
  • letsencrypt certbot error "Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80."
  • SSH error cannot Forward or Listen "bind: Cannot assign requested address"
  • X11 SSH Linux Forwarding Error