ATA 188

I have a Cisco ATA 188 phone adapter. Problem i am having is that i cannot get to the HTTP configuration page(http://ipaddress/dev). I also cannot ping the device from my PC or switch.
I can however ping the ATA from the router console, which i find odd, because the ATA is connected to the switch, and the switch cannot ping it, yet the router can.
Anyway, i put an analog phone into port 1 and pressed the button to get to the config menu, i dont know the key command to get HTTP access. I can review the IP, Subnet, NTP settings, TFTP, ect...
Just cant seem to get to it. Can anyone help on this? Thanks in advance!

Sounds like the ATA might not have a default gateway.
To configure default gateway, choose option 2#. Separate dots with *.
Please reboot the ATA after you save the changes.
Regards,
Anup

Similar Messages

Cisco ISE and ATA 188 profiling.

I have tried to profile cisco ATA 188 adapter, based on cdp attribute;
Platform: Cisco ATA 188
and assigned to a create a same identity group. I am not able to see device profiled according to identity group assigned. Instead of it its always assigned to "cisco - device" group.
On cisco switch side, i am seeing device being in data domain instead of voice domain, but strange enough its getting ip address from voice dhcp pool. If dot1x configs are not applied on port device is getting ip address from voice vlan and working fine.
Any suggestion for this case?

Can you post a screenshot of the custom profiling policy that you configured?
Also, what version of code do you run on the switch and ISE

ATA 188 software installation

Hi, I bought few years ago Cisco ATA 188 , but never really used it, I installed it properly to Router, Computer, phone then I got dial tone but it does not work because I did not installed any software, I believe I need Call Management software, then I download
ata_03_02_04_sccp_090202_a.zip ,
ata_03_02_04_sccp_090202_a.zip
I don’t know is this correct software or not
Please help me out how to install properly with IP address and so on,
Also what beneficiary I could get if I use it in my business,
what is the advantage to have this devices at work,
Thanks
I really appreciated
Regards
[email protected]

Can be more specific claiming "it does not work" ?
Do you have a analog phone connected to ATA188 ? Is SIP account configured on ATA188 ? Is the ATA188 registered to SIP switch (PBX) ?
According software - you need to decide you wish to have SIP gateway or SCCP gateway.I assume you need to have SIP hateway, so SIP firmware needs to be loaded in ATA. SIP formware require no CallManager.
If you consider to use SCCP, then SCCP firmware needs to be installed. In such case you need to have CallManager as well. It's not free, you need to buy one.

Cisco ATA 188

I have the following problem :
We fax 5 page doc and then ATA 188 is not responding ? The green led on the back is on, the red light on the top bottom doesn't go on, it is visible on the network, and it responds to a ping.
This is what I got doing some read on Cisco's site :
"A hardware replacement is probably needed. Open a case with Cisco Technical Support."
We replace a ATA 188 almost every two weeks. We running CCM 3.3.4 with Service Release 1 and ES 49
Any suggestions ?

To resolve this problem, try to modify these parameters:
Change the fax speed to 9600 bps (the recommended speed for no issues).
Set the protcol to G3.
Disable the Error Correcting Mode (ECM).
If the other actions mentioned do not work, plug the fax machine into the Foreign Exchange Station (FXS) port in the router and configure the router for modem pass-through.
If none of these workarounds is successful, a different fax machine must be used.
This URL should help you:
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_qanda_item09186a00800946e1.shtml

ATA vs VG202 vs VIC3-2FXS-E/DID & Wireless

What is best solution moving forward?
Fax server probably two years out.
Background:
I have 34 locations
30 locations have 2 analog devices
4 Operations have 26, 14, 15, 10 analog devices
Currently we use ATA 188 and 186 and one VIC2-2FXS
We Have intermittent problems receiving faxes from Fax servers or other customers in general.

The VG20x are nice because you can use them as a full blown router (VPN, IGP, etc).
I think you'll have more cost per port using a VIC3 rather than VG204. Their capabilities will be equal, as opposed to when the ATAs were in use.
The ATAs are on their way out, and I think you'll find the VG20x to be an easier product to use and it will work better with faxes/modems. The ATAs don't have great fax/modem support where the VG20x will have T38 support and modem support.
For the locations with 15+ devices it may be worth looking into the VG224 as well, depending on usage.
-nick

Problem with Fax and ATA

Hi,
i do not have problem to send Fax to the PSTN, but when I try to receive a fax on the fax machine in port1 of the ATA, the machine never give fax signal.

Hi Leonardo,
Have a look at the following;
Cisco ATA 186 and Cisco ATA 188 Analog Telephone Adaptor Administrator's Guide (SCCP) (2.15.ms, Rev B0)
Configuring and Debugging Fax Services
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_administration_guide_chapter09186a00800c4d1e.html#1016012
Configuring and Troubleshooting the Cisco ATA 186 with Fax
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_configuration_example09186a00800d698e.shtml
Configure Fax Detection Method on the Cisco ATA 186
Use a web browser and go to http:///dev (for example, http://172.16.104.117/dev) in order to configure the Cisco ATA 186 using the web interface.
You must configure these parameters in order to configure the Cisco ATA 186.
Audio Mode
bit 2 (18)=0 Enable detection of FAX CED (answer) tone and switch to FAX mode for the rest of the call if the tone is detected.
Hope this helps!
Rob

ATA with Winfax.....not a good combo

I have an ata 188. Attached to this 188 is a Windows 2000 server with WInfax installed (A mass fax program).
Anyway, 90% of the faxes fail, time after time, i think its the ATA, because before with a normal phone line coming into the building, only a few faxes failed.
Any suggestions? Thanks in advance!

Certain PC fax/modems may fail when trying to communicate with Cisco gateways configured for T.37.

ATA LICENSE

i will know if a licence is need for use ATA 186 or ATA 188 device with non cisco ipabx or gateway ?

I think no license required for ATA 186 act as H323 device.

PSTN number portability within ISPs?

My ISP in Sweden is offering IP telephony and number portability from the PSTN operator to their network. Their message is simple: Keep your phone number, your old telephone, change your access network and save money.
For this purpose, they provide customers with an ATA-188 analogue telephone adaptor that is plugged in at the WAN connector installed at apartments in the area where I live. Then the regular analogue terminal is used to originate and terminate calls.
I will be living abroad for two years and would like to access the service my Swedish ISP provides. I want to receive and make calls being abroad as if I would be physically at my apartment in Sweden.
Therefore, I was thinking how the ATA-188 will be able to access my Swedish ISP network from abroad through another ISP network and act as it would be physically plugged in at my WAN connector in Sweden.
My ISP has all Cisco switches on its network. How about having two VPN routers that support VoIP? Having one router physically at the WAN access in Sweden, another router connected to the ATA-188 to the ISP abroad and a VPN tunnel between them. May this network topology serve my purpose?
Having this network configuration, I wonder how to have the VoIP traffic at the VPN tunnel bounced back from the router in Sweden for reaching the SIP server of my Swedish ISP that provides the VoIP service.
Is this solution for number portability within ISP feasible?
I will appreciate any suggestion or alternative solution and which home/office broadband Cisco routers are suitable for this application.
Enrique

Hello, I have a cisco 2651 with ccme 3.3 and I want to route my external calls PSTN through my SIP provider.
parameters form provider are:
sip.provider.com
login and password port 5060
I have configured this in the sip-ua but I have problems.
All of the IP phones I have behond the router try to authenticate.
I only want 1 authentication from the router
Then i need to tell the internal extensions when they have to go to the PSTN via the SIP provider.
Please can you help me? Is there any example?

Callmanager upgrades

whats the opinions on how upgrades re handled.
we have a pub & 2 subs on 4.1.2, and need to upgrade to support some devices that are not available on the current system. i.e. ATA 188, 2801 Router 7941/7961 handsets.
I realise the device packages can be added fairly easy, however as we're on 4.1.2 a few releases behind, I feel that an upgrade is probably due.
However whats putting me off is the time involved in the proceedure, i.e. from what I see I need to upgrade OS, & sql as well as the ccm software.
Our maintainer who I could ask to do this, wants about 1.5 days per server, which seems excessive to me and when its three servers thats taking a lot of time.
How does anyone else schedule upgrades, comments please.

i've done an 8 server cluster in 24 hours, so 3 servers should take no more than 9 hours. (if you don't have any show stopping errors/issues)
definately can be done in a business day plus a bit of overtime. (or after hours which is better for the users in most cases)
must be done one server at a time, especially during the synchronizing the CCM030x database process. (publisher first then one subscriber at a time)
be sure to follow disaster recovery steps such as performing a BARS backup before starting, pulling an HDD of a RAID/Mirror set, etc.
also, have all the disks, SRs, patches, data ready to go. all these are stated in the step-by-step upgrade instructions.

Faxing - protocol selection

I am trying to understand the order of fax protocol selection. For example, lets take a PSTN gateway that is MGCP enabled. Fax passthrough, T38 relay and Cisco fax relay are enabled. Which protocol will be used to negotiate with the far end device first(ATA, vg248 etc) ? Is there a particular order in which negotiation takes place ?
On the mgcp gateway the follwing commands are present.
mgcp modem passthrough codec g711ulaw
mgcp modem passthrough voip mode nse
ccm-manager fax protocol cisco (default)
no mgcp t38 fax inhibit (default)

In my opinion the best fax protocol is T38 (standard) followed by CISCO Fax relay (similar to T38) and the last option is fax pass through.
ATA 188 doesn't support T38. You can find more info about ATA MGCP here:
http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_administration_guide_chapter09186a00805fe011.html
Info about VG248 here:
http://www.cisco.com/en/US/products/hw/gatecont/ps2250/products_configuration_example09186a008020160d.shtml
On your gateway you can configure T38 as first option. If T38 negotiation fail the second option will be CISCO or pass through:
fax protocol {t38 [nse [force]] [ls-redundancy value [hs-redundancy value]] [fallback {cisco |
none | pass-through {g711ulaw | g711alaw}}]}

ATA bus error

Hello,
I have some problems with hard drive on my laptop. Sometimes everything freezes for few seconds (usually during start-up, but sometimes after I login) and I get some errors. After that, everything seems to be working fine.
Part of dmesg with errors:
[ 10.019887] ata1.00: cmd 60/00:10:10:da:59/01:00:0f:00:00/40 tag 2 ncq 131072 in
res 41/84:00:f2:da:59/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.019968] ata1.00: status: { DRDY ERR }
[ 10.019992] ata1.00: error: { ICRC ABRT }
[ 10.020017] ata1: hard resetting link
[ 10.339913] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 10.443163] ata1.00: configured for UDMA/133
[ 10.443191] ata1: EH complete
[ 10.516832] ata1.00: exception Emask 0x0 SAct 0x7000 SErr 0x0 action 0x6
[ 10.516877] ata1.00: irq_stat 0x40000008
[ 10.516902] ata1.00: failed command: READ FPDMA QUEUED
[ 10.516935] ata1.00: cmd 60/e8:60:e8:16:3b/00:00:0f:00:00/40 tag 12 ncq 118784 in
res 41/84:e8:8c:17:3b/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.517017] ata1.00: status: { DRDY ERR }
[ 10.517041] ata1.00: error: { ICRC ABRT }
[ 10.517067] ata1: hard resetting link
[ 10.836973] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 10.964972] ata1.00: configured for UDMA/133
[ 10.965002] ata1: EH complete
[ 10.984003] ata1: limiting SATA link speed to 3.0 Gbps
[ 10.984015] ata1.00: exception Emask 0x0 SAct 0x60020000 SErr 0x0 action 0x6
[ 10.984106] ata1.00: irq_stat 0x40000008
[ 10.984157] ata1.00: failed command: READ FPDMA QUEUED
[ 10.984225] ata1.00: cmd 60/20:e8:40:6e:b0/00:00:13:00:00/40 tag 29 ncq 16384 in
res 41/84:20:46:6e:b0/00:00:13:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 10.984397] ata1.00: status: { DRDY ERR }
[ 10.984445] ata1.00: error: { ICRC ABRT }
[ 10.984497] ata1: hard resetting link
[ 11.304016] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 11.409308] ata1.00: configured for UDMA/133
[ 11.409343] ata1: EH complete
[ 11.441025] vboxpci: IOMMU not found (not registered)
[ 11.543239] bbswitch: version 0.8
[ 11.543246] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[ 11.543252] bbswitch: Found discrete VGA device 0000:03:00.0: \_SB_.PCI0.RP05.PEGP
[ 11.543262] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 11.543355] bbswitch: detected an Optimus _DSM function
[ 11.543372] pci 0000:03:00.0: enabling device (0006 -> 0007)
[ 11.543434] bbswitch: Succesfully loaded. Discrete card 0000:03:00.0 is on
[ 11.545169] bbswitch: disabling discrete graphics
[ 11.545181] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 13.327790] r8169 0000:01:00.0 enp1s0: link up
[ 20.651344] ata1.00: exception Emask 0x0 SAct 0x2000000 SErr 0x0 action 0x6
[ 20.651349] ata1.00: irq_stat 0x40000008
[ 20.651353] ata1.00: failed command: READ FPDMA QUEUED
[ 20.651359] ata1.00: cmd 60/08:c8:98:86:ae/00:00:10:00:00/40 tag 25 ncq 4096 in
res 41/84:08:98:86:ae/00:00:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 20.651361] ata1.00: status: { DRDY ERR }
[ 20.651363] ata1.00: error: { ICRC ABRT }
[ 20.651367] ata1: hard resetting link
[ 20.971293] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 21.080441] ata1.00: configured for UDMA/133
[ 21.080467] ata1: EH complete
[ 21.121498] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[ 21.121503] ata1.00: irq_stat 0x40000008
[ 21.121507] ata1.00: failed command: READ FPDMA QUEUED
[ 21.121513] ata1.00: cmd 60/00:e8:00:f4:69/01:00:0f:00:00/40 tag 29 ncq 131072 in
res 41/84:00:ee:f4:69/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 21.121515] ata1.00: status: { DRDY ERR }
[ 21.121517] ata1.00: error: { ICRC ABRT }
[ 21.121521] ata1: hard resetting link
[ 21.441483] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 21.546775] ata1.00: configured for UDMA/133
[ 21.546795] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 21.546798] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 21.546801] sd 0:0:0:0: [sda] ASC=0x47 ASCQ=0x0
[ 21.546802] sd 0:0:0:0: [sda] CDB:
[ 21.546804] cdb[0]=0x28: 28 00 0f 69 f4 00 00 01 00 00
[ 21.546812] blk_update_request: I/O error, dev sda, sector 258601984
[ 21.546829] ata1: EH complete
[ 21.606131] ata1.00: exception Emask 0x0 SAct 0x200 SErr 0x0 action 0x6
[ 21.606139] ata1.00: irq_stat 0x40000008
[ 21.606145] ata1.00: failed command: READ FPDMA QUEUED
[ 21.606155] ata1.00: cmd 60/88:48:00:d8:36/00:00:0f:00:00/40 tag 9 ncq 69632 in
res 41/84:88:04:d8:36/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 21.606160] ata1.00: status: { DRDY ERR }
[ 21.606163] ata1.00: error: { ICRC ABRT }
[ 21.606170] ata1: hard resetting link
[ 21.924963] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 22.035385] ata1.00: configured for UDMA/133
[ 22.035408] ata1: EH complete
[ 22.111984] ata1: limiting SATA link speed to 1.5 Gbps
[ 22.111991] ata1.00: exception Emask 0x0 SAct 0x1000000 SErr 0x0 action 0x6
[ 22.111994] ata1.00: irq_stat 0x40000008
[ 22.111997] ata1.00: failed command: READ FPDMA QUEUED
[ 22.112003] ata1.00: cmd 60/90:c0:48:39:32/00:00:0f:00:00/40 tag 24 ncq 73728 in
res 41/84:90:8a:39:32/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 22.112005] ata1.00: status: { DRDY ERR }
[ 22.112007] ata1.00: error: { ICRC ABRT }
[ 22.112011] ata1: hard resetting link
[ 22.431783] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 22.535011] ata1.00: configured for UDMA/133
[ 22.535038] ata1: EH complete
[ 22.618877] ata1.00: exception Emask 0x0 SAct 0x1e SErr 0x0 action 0x6
[ 22.618886] ata1.00: irq_stat 0x40000008
[ 22.618891] ata1.00: failed command: READ FPDMA QUEUED
[ 22.618901] ata1.00: cmd 60/00:08:08:2c:32/01:00:0f:00:00/40 tag 1 ncq 131072 in
res 41/84:00:70:2c:32/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 22.618906] ata1.00: status: { DRDY ERR }
[ 22.618909] ata1.00: error: { ICRC ABRT }
[ 22.618920] ata1: hard resetting link
[ 22.938608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 23.023643] ata1.00: configured for UDMA/133
[ 23.023682] ata1: EH complete
[ 53.428943] ata1.00: exception Emask 0x1 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[ 53.428953] ata1.00: irq_stat 0x40000008
[ 53.428960] ata1.00: failed command: READ FPDMA QUEUED
[ 53.428971] ata1.00: cmd 60/00:00:00:e8:31/01:00:10:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x5 (timeout)
[ 53.428976] ata1.00: status: { DRDY }
[ 53.428981] ata1.00: failed command: READ FPDMA QUEUED
[ 53.428990] ata1.00: cmd 60/08:08:20:fe:e9/00:00:0f:00:00/40 tag 1 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.428994] ata1.00: status: { DRDY }
[ 53.428998] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429006] ata1.00: cmd 60/08:10:28:fe:e9/00:00:0f:00:00/40 tag 2 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429010] ata1.00: status: { DRDY }
[ 53.429014] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429022] ata1.00: cmd 60/08:18:30:fe:e9/00:00:0f:00:00/40 tag 3 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429026] ata1.00: status: { DRDY }
[ 53.429029] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429037] ata1.00: cmd 60/08:20:38:fe:e9/00:00:0f:00:00/40 tag 4 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429042] ata1.00: status: { DRDY }
[ 53.429045] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429053] ata1.00: cmd 60/08:28:40:fe:e9/00:00:0f:00:00/40 tag 5 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429057] ata1.00: status: { DRDY }
[ 53.429061] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429069] ata1.00: cmd 60/08:30:48:fe:e9/00:00:0f:00:00/40 tag 6 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429073] ata1.00: status: { DRDY }
[ 53.429076] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429084] ata1.00: cmd 60/08:38:50:fe:e9/00:00:0f:00:00/40 tag 7 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429089] ata1.00: status: { DRDY }
[ 53.429092] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429100] ata1.00: cmd 60/08:40:58:fe:e9/00:00:0f:00:00/40 tag 8 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429104] ata1.00: status: { DRDY }
[ 53.429108] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429116] ata1.00: cmd 60/08:48:60:fe:e9/00:00:0f:00:00/40 tag 9 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429120] ata1.00: status: { DRDY }
[ 53.429124] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429132] ata1.00: cmd 60/08:50:68:fe:e9/00:00:0f:00:00/40 tag 10 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429136] ata1.00: status: { DRDY }
[ 53.429139] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429148] ata1.00: cmd 60/08:58:70:fe:e9/00:00:0f:00:00/40 tag 11 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429152] ata1.00: status: { DRDY }
[ 53.429155] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429163] ata1.00: cmd 60/08:60:78:fe:e9/00:00:0f:00:00/40 tag 12 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429168] ata1.00: status: { DRDY }
[ 53.429171] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429179] ata1.00: cmd 60/08:68:80:fe:e9/00:00:0f:00:00/40 tag 13 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429183] ata1.00: status: { DRDY }
[ 53.429187] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429195] ata1.00: cmd 60/08:70:18:e8:a9/00:00:16:00:00/40 tag 14 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429199] ata1.00: status: { DRDY }
[ 53.429203] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429211] ata1.00: cmd 60/08:78:90:fe:e9/00:00:0f:00:00/40 tag 15 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429215] ata1.00: status: { DRDY }
[ 53.429218] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429226] ata1.00: cmd 60/08:80:98:fe:e9/00:00:0f:00:00/40 tag 16 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429230] ata1.00: status: { DRDY }
[ 53.429234] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429242] ata1.00: cmd 60/08:88:a0:fe:e9/00:00:0f:00:00/40 tag 17 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429246] ata1.00: status: { DRDY }
[ 53.429250] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429258] ata1.00: cmd 60/08:90:a8:fe:e9/00:00:0f:00:00/40 tag 18 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429262] ata1.00: status: { DRDY }
[ 53.429265] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429273] ata1.00: cmd 60/08:98:b0:fe:e9/00:00:0f:00:00/40 tag 19 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429277] ata1.00: status: { DRDY }
[ 53.429281] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429289] ata1.00: cmd 60/08:a0:b8:fe:e9/00:00:0f:00:00/40 tag 20 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429293] ata1.00: status: { DRDY }
[ 53.429297] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429305] ata1.00: cmd 60/08:a8:c0:fe:e9/00:00:0f:00:00/40 tag 21 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429309] ata1.00: status: { DRDY }
[ 53.429312] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429320] ata1.00: cmd 60/08:b0:c8:fe:e9/00:00:0f:00:00/40 tag 22 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429325] ata1.00: status: { DRDY }
[ 53.429328] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429336] ata1.00: cmd 60/08:b8:d0:fe:e9/00:00:0f:00:00/40 tag 23 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429340] ata1.00: status: { DRDY }
[ 53.429344] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429352] ata1.00: cmd 60/08:c0:d8:fe:e9/00:00:0f:00:00/40 tag 24 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429356] ata1.00: status: { DRDY }
[ 53.429360] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429367] ata1.00: cmd 60/08:c8:e0:fe:e9/00:00:0f:00:00/40 tag 25 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429372] ata1.00: status: { DRDY }
[ 53.429375] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429383] ata1.00: cmd 60/08:d0:e8:fe:e9/00:00:0f:00:00/40 tag 26 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429387] ata1.00: status: { DRDY }
[ 53.429391] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429399] ata1.00: cmd 60/08:d8:f0:fe:e9/00:00:0f:00:00/40 tag 27 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429403] ata1.00: status: { DRDY }
[ 53.429407] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429414] ata1.00: cmd 60/08:e0:f8:fe:e9/00:00:0f:00:00/40 tag 28 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429419] ata1.00: status: { DRDY }
[ 53.429422] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429430] ata1.00: cmd 60/08:e8:00:ff:e9/00:00:0f:00:00/40 tag 29 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429435] ata1.00: status: { DRDY }
[ 53.429438] ata1.00: failed command: READ FPDMA QUEUED
[ 53.429446] ata1.00: cmd 60/08:f0:88:fe:e9/00:00:0f:00:00/40 tag 30 ncq 4096 in
res 40/00:f0:88:fe:e9/00:00:0f:00:00/40 Emask 0x1 (device error)
[ 53.429450] ata1.00: status: { DRDY }
[ 53.429458] ata1: hard resetting link
[ 53.749173] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 53.836070] ata1.00: configured for UDMA/133
[ 53.836079] ata1.00: device reported invalid CHS sector 0
[ 53.836116] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836119] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836121] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836123] sd 0:0:0:0: [sda] CDB:
[ 53.836125] cdb[0]=0x28: 28 00 0f e9 fe 20 00 00 08 00
[ 53.836133] blk_update_request: I/O error, dev sda, sector 266993184
[ 53.836148] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836151] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836153] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836154] sd 0:0:0:0: [sda] CDB:
[ 53.836155] cdb[0]=0x28: 28 00 0f e9 fe 28 00 00 08 00
[ 53.836162] blk_update_request: I/O error, dev sda, sector 266993192
[ 53.836167] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836169] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836171] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836173] sd 0:0:0:0: [sda] CDB:
[ 53.836174] cdb[0]=0x28: 28 00 0f e9 fe 30 00 00 08 00
[ 53.836180] blk_update_request: I/O error, dev sda, sector 266993200
[ 53.836185] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836187] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836189] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836190] sd 0:0:0:0: [sda] CDB:
[ 53.836191] cdb[0]=0x28: 28 00 0f e9 fe 38 00 00 08 00
[ 53.836198] blk_update_request: I/O error, dev sda, sector 266993208
[ 53.836202] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836204] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836206] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836208] sd 0:0:0:0: [sda] CDB:
[ 53.836209] cdb[0]=0x28: 28 00 0f e9 fe 40 00 00 08 00
[ 53.836215] blk_update_request: I/O error, dev sda, sector 266993216
[ 53.836220] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836222] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836224] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836225] sd 0:0:0:0: [sda] CDB:
[ 53.836226] cdb[0]=0x28: 28 00 0f e9 fe 48 00 00 08 00
[ 53.836232] blk_update_request: I/O error, dev sda, sector 266993224
[ 53.836237] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836239] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836241] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836242] sd 0:0:0:0: [sda] CDB:
[ 53.836243] cdb[0]=0x28: 28 00 0f e9 fe 50 00 00 08 00
[ 53.836249] blk_update_request: I/O error, dev sda, sector 266993232
[ 53.836253] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836255] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836257] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836259] sd 0:0:0:0: [sda] CDB:
[ 53.836260] cdb[0]=0x28: 28 00 0f e9 fe 58 00 00 08 00
[ 53.836266] blk_update_request: I/O error, dev sda, sector 266993240
[ 53.836270] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836272] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836274] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836276] sd 0:0:0:0: [sda] CDB:
[ 53.836277] cdb[0]=0x28: 28 00 0f e9 fe 60 00 00 08 00
[ 53.836283] blk_update_request: I/O error, dev sda, sector 266993248
[ 53.836287] sd 0:0:0:0: [sda] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08
[ 53.836289] sd 0:0:0:0: [sda] Sense Key : 0xb [current] [descriptor]
[ 53.836291] sd 0:0:0:0: [sda] ASC=0x0 ASCQ=0x0
[ 53.836293] sd 0:0:0:0: [sda] CDB:
[ 53.836294] cdb[0]=0x28: 28 00 0f e9 fe 68 00 00 08 00
[ 53.836300] blk_update_request: I/O error, dev sda, sector 266993256
[ 53.836354] ata1: EH complete
[ 53.922776] ata1.00: exception Emask 0x0 SAct 0x20 SErr 0x0 action 0x6
[ 53.922827] ata1.00: irq_stat 0x40000008
[ 53.922855] ata1.00: failed command: READ FPDMA QUEUED
[ 53.922891] ata1.00: cmd 60/00:28:38:3f:04/01:00:10:00:00/40 tag 5 ncq 131072 in
res 41/84:00:5a:3f:04/00:01:10:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 53.922981] ata1.00: status: { DRDY ERR }
[ 53.923007] ata1.00: error: { ICRC ABRT }
[ 53.923037] ata1: hard resetting link
[ 54.242882] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 54.357940] ata1.00: configured for UDMA/133
[ 54.357967] ata1: EH complete
[ 54.413337] ata1.00: limiting speed to UDMA/100:PIO4
[ 54.413343] ata1.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x6
[ 54.413387] ata1.00: irq_stat 0x40000008
[ 54.413412] ata1.00: failed command: READ FPDMA QUEUED
[ 54.413445] ata1.00: cmd 60/20:40:c0:04:b1/00:00:16:00:00/40 tag 8 ncq 16384 in
res 41/84:20:d4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 54.413527] ata1.00: status: { DRDY ERR }
[ 54.413551] ata1.00: error: { ICRC ABRT }
[ 54.413578] ata1: hard resetting link
[ 54.733264] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 54.835393] ata1.00: configured for UDMA/100
[ 54.835419] ata1: EH complete
[ 54.883575] ata1.00: exception Emask 0x0 SAct 0x8 SErr 0x0 action 0x6
[ 54.883618] ata1.00: irq_stat 0x40000008
[ 54.883643] ata1.00: failed command: READ FPDMA QUEUED
[ 54.883675] ata1.00: cmd 60/08:18:e0:04:b1/00:00:16:00:00/40 tag 3 ncq 4096 in
res 41/84:08:e4:04:b1/00:00:16:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 54.883756] ata1.00: status: { DRDY ERR }
[ 54.883779] ata1.00: error: { ICRC ABRT }
[ 54.883805] ata1: hard resetting link
[ 55.203636] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 55.301754] ata1.00: configured for UDMA/100
[ 55.301780] ata1: EH complete
[ 55.357428] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[ 55.357474] ata1.00: irq_stat 0x40000008
[ 55.357500] ata1.00: failed command: READ FPDMA QUEUED
[ 55.357532] ata1.00: cmd 60/f0:90:e0:34:a5/00:00:0e:00:00/40 tag 18 ncq 122880 in
res 41/84:f0:ea:34:a5/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 55.357613] ata1.00: status: { DRDY ERR }
[ 55.357636] ata1.00: error: { ICRC ABRT }
[ 55.357661] ata1: hard resetting link
[ 55.677344] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 55.779200] ata1.00: configured for UDMA/100
[ 55.779228] ata1: EH complete
[ 55.954538] ata1.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x6
[ 55.954585] ata1.00: irq_stat 0x40000008
[ 55.954610] ata1.00: failed command: READ FPDMA QUEUED
[ 55.954643] ata1.00: cmd 60/00:90:00:eb:a4/01:00:0e:00:00/40 tag 18 ncq 131072 in
res 41/84:00:10:eb:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 55.954725] ata1.00: status: { DRDY ERR }
[ 55.954748] ata1.00: error: { ICRC ABRT }
[ 55.954774] ata1: hard resetting link
[ 56.274496] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.367864] ata1.00: configured for UDMA/100
[ 56.367921] ata1: EH complete
[ 56.448401] ata1.00: limiting speed to UDMA/33:PIO4
[ 56.448412] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6
[ 56.448483] ata1.00: irq_stat 0x40000008
[ 56.448524] ata1.00: failed command: READ FPDMA QUEUED
[ 56.448578] ata1.00: cmd 60/00:10:58:ec:a4/01:00:0e:00:00/40 tag 2 ncq 131072 in
res 41/84:00:fe:ec:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 56.448715] ata1.00: status: { DRDY ERR }
[ 56.448753] ata1.00: error: { ICRC ABRT }
[ 56.448798] ata1: hard resetting link
[ 56.768215] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.856253] ata1.00: configured for UDMA/33
[ 56.856297] ata1: EH complete
[ 56.898690] ata1.00: exception Emask 0x0 SAct 0x60 SErr 0x0 action 0x6
[ 56.898770] ata1.00: irq_stat 0x40000008
[ 56.898816] ata1.00: failed command: READ FPDMA QUEUED
[ 56.898876] ata1.00: cmd 60/00:30:c8:ee:a4/01:00:0e:00:00/40 tag 6 ncq 131072 in
res 41/84:00:e8:ee:a4/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 56.899029] ata1.00: status: { DRDY ERR }
[ 56.899072] ata1.00: error: { ICRC ABRT }
[ 56.899121] ata1: hard resetting link
[ 57.218560] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 57.311513] ata1.00: configured for UDMA/33
[ 57.311542] ata1: EH complete
[ 57.355664] ata1.00: exception Emask 0x0 SAct 0x500 SErr 0x0 action 0x6
[ 57.355754] ata1.00: irq_stat 0x40000008
[ 57.355806] ata1.00: failed command: READ FPDMA QUEUED
[ 57.355873] ata1.00: cmd 60/58:50:00:ec:a4/00:00:0e:00:00/40 tag 10 ncq 45056 in
res 41/84:58:1a:ec:a4/00:00:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 57.356044] ata1.00: status: { DRDY ERR }
[ 57.356091] ata1.00: error: { ICRC ABRT }
[ 57.356145] ata1: hard resetting link
[ 57.675608] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 57.766781] ata1.00: configured for UDMA/33
[ 57.766816] ata1: EH complete
[ 57.806077] ata1.00: exception Emask 0x0 SAct 0x3000 SErr 0x0 action 0x6
[ 57.806134] ata1.00: irq_stat 0x40000008
[ 57.806164] ata1.00: failed command: READ FPDMA QUEUED
[ 57.806203] ata1.00: cmd 60/00:68:70:24:a5/01:00:0e:00:00/40 tag 13 ncq 131072 in
res 41/84:00:f2:24:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 57.806302] ata1.00: status: { DRDY ERR }
[ 57.806330] ata1.00: error: { ICRC ABRT }
[ 57.806362] ata1: hard resetting link
[ 58.125961] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 58.211103] ata1.00: configured for UDMA/33
[ 58.211156] ata1: EH complete
[ 58.249769] ata1.00: exception Emask 0x0 SAct 0x18000 SErr 0x0 action 0x6
[ 58.249854] ata1.00: irq_stat 0x40000008
[ 58.249901] ata1.00: failed command: READ FPDMA QUEUED
[ 58.249962] ata1.00: cmd 60/00:80:20:27:a5/01:00:0e:00:00/40 tag 16 ncq 131072 in
res 41/84:00:a2:27:a5/00:01:0e:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 58.255626] ata1.00: status: { DRDY ERR }
[ 58.258790] ata1.00: error: { ICRC ABRT }
[ 58.261924] ata1: hard resetting link
[ 58.579657] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 58.666164] ata1.00: configured for UDMA/33
[ 58.666199] ata1: EH complete
[ 58.716707] ata1.00: exception Emask 0x0 SAct 0x4000000 SErr 0x0 action 0x6
[ 58.718539] ata1.00: irq_stat 0x40000008
[ 58.720328] ata1.00: failed command: READ FPDMA QUEUED
[ 58.722121] ata1.00: cmd 60/00:d0:68:92:5c/01:00:0f:00:00/40 tag 26 ncq 131072 in
res 41/84:00:76:92:5c/00:01:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 58.725736] ata1.00: status: { DRDY ERR }
[ 58.727553] ata1.00: error: { ICRC ABRT }
[ 58.728965] ata1: hard resetting link
[ 59.046670] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 59.132488] ata1.00: configured for UDMA/33
[ 59.132515] ata1: EH complete
[ 59.180459] ata1.00: exception Emask 0x0 SAct 0x20000000 SErr 0x0 action 0x6
[ 59.181979] ata1.00: irq_stat 0x40000008
[ 59.182990] ata1.00: failed command: READ FPDMA QUEUED
[ 59.183943] ata1.00: cmd 60/f8:e8:68:93:5c/00:00:0f:00:00/40 tag 29 ncq 126976 in
res 41/84:f8:6a:93:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 59.185831] ata1.00: status: { DRDY ERR }
[ 59.186778] ata1.00: error: { ICRC ABRT }
[ 59.187715] ata1: hard resetting link
[ 59.507035] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 59.610051] ata1.00: configured for UDMA/33
[ 59.610080] ata1: EH complete
[ 59.661766] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[ 59.663154] ata1.00: irq_stat 0x40000008
[ 59.664089] ata1.00: failed command: READ FPDMA QUEUED
[ 59.665027] ata1.00: cmd 60/98:38:60:94:5c/00:00:0f:00:00/40 tag 7 ncq 77824 in
res 41/84:98:64:94:5c/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 59.666916] ata1.00: status: { DRDY ERR }
[ 59.669774] ata1.00: error: { ICRC ABRT }
[ 59.672954] ata1: hard resetting link
[ 59.990695] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 60.087554] ata1.00: configured for UDMA/33
[ 60.087600] ata1: EH complete
[ 60.217903] ata1.00: exception Emask 0x0 SAct 0x80 SErr 0x0 action 0x6
[ 60.219413] ata1.00: irq_stat 0x40000008
[ 60.220456] ata1.00: failed command: READ FPDMA QUEUED
[ 60.221440] ata1.00: cmd 60/20:38:00:1b:3e/00:00:0f:00:00/40 tag 7 ncq 16384 in
res 41/84:20:18:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 60.223332] ata1.00: status: { DRDY ERR }
[ 60.224269] ata1.00: error: { ICRC ABRT }
[ 60.225206] ata1: hard resetting link
[ 60.544531] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 60.653686] ata1.00: configured for UDMA/33
[ 60.653713] ata1: EH complete
[ 60.701540] ata1.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x6
[ 60.703016] ata1.00: irq_stat 0x40000008
[ 60.704106] ata1.00: failed command: READ FPDMA QUEUED
[ 60.705056] ata1.00: cmd 60/88:50:78:1b:3e/00:00:0f:00:00/40 tag 10 ncq 69632 in
res 41/84:88:78:1b:3e/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 60.706949] ata1.00: status: { DRDY ERR }
[ 60.707884] ata1.00: error: { ICRC ABRT }
[ 60.708824] ata1: hard resetting link
[ 61.028237] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 61.142293] ata1.00: configured for UDMA/33
[ 61.142319] ata1: EH complete
[ 61.195399] ata1.00: exception Emask 0x0 SAct 0x8000 SErr 0x0 action 0x6
[ 61.197750] ata1.00: irq_stat 0x40000008
[ 61.200089] ata1.00: failed command: READ FPDMA QUEUED
[ 61.201690] ata1.00: cmd 60/20:78:10:39:38/00:00:0f:00:00/40 tag 15 ncq 16384 in
res 41/84:20:14:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 61.204897] ata1.00: status: { DRDY ERR }
[ 61.206484] ata1.00: error: { ICRC ABRT }
[ 61.208071] ata1: hard resetting link
[ 61.525313] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 61.630818] ata1.00: configured for UDMA/33
[ 61.630845] ata1: EH complete
[ 61.675724] ata1.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x6
[ 61.677345] ata1.00: irq_stat 0x40000008
[ 61.678943] ata1.00: failed command: READ FPDMA QUEUED
[ 61.680539] ata1.00: cmd 60/50:90:30:39:38/00:00:0f:00:00/40 tag 18 ncq 40960 in
res 41/84:50:70:39:38/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 61.683756] ata1.00: status: { DRDY ERR }
[ 61.685369] ata1.00: error: { ICRC ABRT }
[ 61.686586] ata1: hard resetting link
[ 62.005676] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 62.108289] ata1.00: configured for UDMA/33
[ 62.108316] ata1: EH complete
[ 62.162783] ata1.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x6
[ 62.164411] ata1.00: irq_stat 0x40000008
[ 62.166015] ata1.00: failed command: READ FPDMA QUEUED
[ 62.167617] ata1.00: cmd 60/20:b0:d8:c3:3d/00:00:0f:00:00/40 tag 22 ncq 16384 in
res 41/84:20:d8:c3:3d/00:00:0f:00:00/00 Emask 0x410 (ATA bus error) <F>
[ 62.170837] ata1.00: status: { DRDY ERR }
[ 62.172433] ata1.00: error: { ICRC ABRT }
[ 62.173698] ata1: hard resetting link
[ 62.492749] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 62.607944] ata1.00: configured for UDMA/33
[ 62.607974] ata1: EH complete
Output of smartctl -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop SSHD
Device Model: ST1000LM014-SSHD-8GB
Serial Number: W3829AM6
LU WWN Device Id: 5 000c50 07be01372
Firmware Version: LVD3
User Capacity: 1,000,204,886,016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Sun May 10 11:12:02 2015 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 150) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 198) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1081) SCT Status supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 158141600
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 429
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 4319585187
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1864
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 437
184 End-to-End_Error 0x0032 089 089 099 Old_age Always FAILING_NOW 11
187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 069 052 045 Old_age Always - 31 (Min/Max 25/31)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 50
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6179
194 Temperature_Celsius 0x0022 031 048 000 Old_age Always - 31 (0 19 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 13 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 13 occurred at disk power-on lifetime: 1779 hours (74 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 10 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 b0 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 30 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 09:58:40.403 FLUSH CACHE EXT
61 00 08 ff ff ff 4f 00 09:58:40.403 WRITE FPDMA QUEUED
Error 12 occurred at disk power-on lifetime: 1722 hours (71 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 30 50 3a c5 4e 00 00:01:28.045 READ FPDMA QUEUED
Error 11 occurred at disk power-on lifetime: 1537 hours (64 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:00:35.199 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:00:35.198 READ FPDMA QUEUED
60 00 08 10 10 2b 4f 00 00:00:35.188 READ FPDMA QUEUED
60 00 e0 20 e0 78 4f 00 00:00:35.187 READ FPDMA QUEUED
60 00 90 68 e1 78 4f 00 00:00:35.185 READ FPDMA QUEUED
Error 10 occurred at disk power-on lifetime: 1525 hours (63 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 a0 ff ff ff 4f 00 00:00:15.374 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 80 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
60 00 68 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
Error 9 occurred at disk power-on lifetime: 1525 hours (63 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 08 e0 9e 31 4f 00 00:00:15.146 READ FPDMA QUEUED
60 00 a8 ff ff ff 4f 00 00:00:15.073 READ FPDMA QUEUED
60 00 18 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 98 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:00:15.068 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Is this software bug or hard drive failure? Thanks in advance.

Thanks for your answers.
2ion wrote:
Not necessarily, this is a Seagate hard drive. AFAIK Seek Error Rate and Raw Read Error Rate are 48bit values where the lower 24bit encode the total number of sectors read/saught (which overflows to zero) and the upper 24bit encode the acutal errors.
smartctl -v 1,hex48 -v 7,hex48 -a /dev/sda
should display OP's data in a usuable format.
In fact, I turned my recently purchased laptop in for a hard disk replacement of almost the same type as OP (ST500LM000-SSHD-8GB) twice, but all three drives of this type I had provided SMART values which were more of an oracle rather than data useful for monitoring purposes. Forums are full with people unsure about what to do with this kind of drives. If you google for the End-to-End errors with Seagate drives (here marked as FAILING!), you'll find people reporting that Seagate's own tools do not report any errors despite the attribute in question being reported by monitoring tools just as bad... Seagate is the horror. So, I'd say that it is rather uncertain whether the SMART values are connected to the actual drive failing or a faulty cable.
OP, did you see these errors from the beginning or after a certain time, or perhaps after a kernel upgrade? Did you check the drive's cable? What was the situation before these errors showed up (maybe under Windows?)
smartctl -v 1,hex48 -v 7,hex48 -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Laptop SSHD
Device Model: ST1000LM014-SSHD-8GB
Serial Number: W3829AM6
LU WWN Device Id: 5 000c50 07be01372
Firmware Version: LVD3
User Capacity: 1,000,204,886,016 bytes [1,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon May 11 12:09:29 2015 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 150) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 198) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1081) SCT Status supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 115 099 006 Pre-fail Always - 0x000005184840
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 433
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 0x0001017be679
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1880
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 441
184 End-to-End_Error 0x0032 089 089 099 Old_age Always FAILING_NOW 11
187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 052 045 Old_age Always - 39 (Min/Max 37/39)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 50
193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6282
194 Temperature_Celsius 0x0022 039 048 000 Old_age Always - 39 (0 19 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 13 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 13 occurred at disk power-on lifetime: 1779 hours (74 days + 3 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 10 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 b0 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
60 00 30 ff ff ff 4f 00 09:58:41.053 READ FPDMA QUEUED
ea 00 00 00 00 00 a0 00 09:58:40.403 FLUSH CACHE EXT
61 00 08 ff ff ff 4f 00 09:58:40.403 WRITE FPDMA QUEUED
Error 12 occurred at disk power-on lifetime: 1722 hours (71 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.048 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:01:28.047 READ FPDMA QUEUED
60 00 30 50 3a c5 4e 00 00:01:28.045 READ FPDMA QUEUED
Error 11 occurred at disk power-on lifetime: 1537 hours (64 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 00 ff ff ff 4f 00 00:00:35.199 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:00:35.198 READ FPDMA QUEUED
60 00 08 10 10 2b 4f 00 00:00:35.188 READ FPDMA QUEUED
60 00 e0 20 e0 78 4f 00 00:00:35.187 READ FPDMA QUEUED
60 00 90 68 e1 78 4f 00 00:00:35.185 READ FPDMA QUEUED
Error 10 occurred at disk power-on lifetime: 1525 hours (63 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 a0 ff ff ff 4f 00 00:00:15.374 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:00:15.373 READ FPDMA QUEUED
60 00 80 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
60 00 68 ff ff ff 4f 00 00:00:15.370 READ FPDMA QUEUED
Error 9 occurred at disk power-on lifetime: 1525 hours (63 days + 13 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 00 08 e0 9e 31 4f 00 00:00:15.146 READ FPDMA QUEUED
60 00 a8 ff ff ff 4f 00 00:00:15.073 READ FPDMA QUEUED
60 00 18 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 98 ff ff ff 4f 00 00:00:15.072 READ FPDMA QUEUED
60 00 00 ff ff ff 4f 00 00:00:15.068 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 1871 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
These errors just appeared, not after upgrade and I didn't get them in the beginning. The situation before errors - everything worked exactly the same, I see no difference in performance, except that few seconds long freeze that sometimes happen. Can't tell about Windows, I have it pre-installed but never used it so I can't compare. I didn't check the cable, and I'd rather not do that - I don't want to mess with hardware, if I do something wrong I lose the warranty. If something is wrong then I'd rather have it checked and fixed by someone who knows how to do that (and for free, because I still have the warranty).

ATA Dial-Up Modem

I would like to use my ATA 186/188 to operate with a dial-up modem. I understand that this configuration is not supported, but some users have gotten it to work using fax configuration's on their 186. I have the following configuration on my 186 and it does not connect:
AudioMode: 0x00150015
ConnectMode: 0x90000400
LBRCodec: 1
Does anyone have a known configuration that would work for this use? Maybe I need to add a command to my router? Thanks in advance.

This doc should help you. We followed this doc and we are able to use the ATA's as modems. Mind you that it certainly isn't the greatest of speeds.
http://cisco.com/en/US/products/hw/gatecont/ps514/products_administration_guide_chapter09186a00800c4d1e.html

Fax success on ATA?

I know the Cisco ATAs (186 & 188) support faxing through G.711, potentially also with passthrough configured on CME, but can anyone provide comments on their experience doing this?
Is it easy enough to attain 14.4kbps speeds on the fax?
We're looking at using ATAs to replace some POTS lines in a small office. The ATAs will be on the same LAN as CME and will be sending and receiving faxes via two BRI ports on the CME system (2801).
I'm looking more for comments on how well it works rather than pointers to documentation on how to do it. (which I already have)

Callmanager
Verify region setting is using G711 codec
Gateway
Config t
Voice service voip
modem passthrough nse codec g711ulaw
dial-peer voice XXXXXXX voip
modem passthrough nse codec g711ulaw
Reference
http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a008053b51f.html
If you add the above then change the ATA (http://X.Y.Z.A/dev)
Audio Parameters
LBRCodec to 0
AudioMode 0x00150015 (default is 0x00350035)
ConnectMode 0x90000400 (default is 0x90000400)

ATA for 33.6 kbps

Cisco ATA 186/188 supports speeds up to 14.4 kbps.
(http://www.cisco.com/en/US/products/hw/gatecont/ps514/products_qanda_item09186a00800946e1.shtml)
Any experience for third party ATA that is working fine with 33.6 kbps modem/fax?

What you are looking for is SuperG3 fax compatibility. A very simple (but expensive) way to do this is to use an IOS router (12.4T software) with an FXS card configured as an MGCP or H323 gateway. Sadly this is also a pain in the rear to configure in large numbers. If you centralise your fax lines or have a spare slot on the router, this is the best option.
If you are on Call Manager 5, you might want to try the mediatrix product (www.mediatrix.com) which is a SIP compatible SuperG3 TA. It also does H323 so may work ok with CM4. However, I have not used this device, and can't speak for its compatibility with other gateways.
A final, rather pathetic, way to do this is to nail up the ATA to G.711 only and let the SG3 machine try to fight its way through.
We hope and pray for the day that the ATA gets the SG3 upgrade!

ATA 188

Similar Messages

Maybe you are looking for