Ata 8 .00 Failed To Identify I/o Error Err_mask=0x4
Contents |
gajo Member Registered: 2008-04-01 Posts: 93 Website long boot due to ata recognition problems [SOLVED] As the message says my boot is taking about 10 minutes, of which 95% of the time is ata failed to identify (i/o error err_mask=0x4) spent trying to recognize ata4 device.I'm using the x86_64 version of arch, which
Failed To Identify (i/o Error, Err_mask=0x100)
works just fine on my laptop, and on my desktop - when it boots that is.Another thing that puzzles me
Emask 0x10 (ata Bus Error)
is how am I getting those errors, considering I don't really have 4 ata drives, yet only two - hard disk and dvd rom.Anyway, this is my dmesg output :Linux version 2.6.24-ARCH (root@artin) (gcc version 4.3.0 (GCC) ) #1 SMP PREEMPT Sun Mar 30 10:50:22 CEST 2008 Command line: root=/dev/sda1 ro vga=791 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f000 (usable) BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000007fee0000 (usable) BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS) BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data) BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved) BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) Entering add_active_range(0, 0, 159) 0 entries of 256 used Entering add_active_range(0, 256, 524000) 1 entries of 256 used end_pfn_map = 1048576 DMI 2.4 present. ACPI: RSDP 000F9210, 0014 (r0 IntelR) ACPI: RSDT 7FEE3040, 003C (r1 IntelR AWRDACPI 42302E31 AWRD 0) ACPI: FACP 7FEE30C0, 0074 (r1 IntelR AWRDACPI 42302E31 AWRD 0) ACPI: DSDT 7FEE3180, 4BB6 (r1 INTELR AWRDACPI 1000 MSFT 100000E) ACPI: FACS 7FEE0000, 0040 ACPI: HPET 7FEE7E80, 0038 (r1 IntelR AWRDACPI 42302E31 AWRD 98) ACPI: MCFG 7FEE7F00, 003C (r1 IntelR AWRDACPI 42302E31 AWRD 0) ACPI: APIC 7FEE7D80, 0084 (r1 IntelR AWRDACPI 42302E31 AWRD 0) ACPI: SSDT 7FEE7F80, 015C (r1 PmRef Cpu0Ist 3000 INTL 20060912) ACPI: SSDT 7FEE8410, 02F1 (r1 PmRef CpuPm 3000 INTL 20040311) Entering add_active_range(0, 0, 159) 0 entries of 256 used Entering add_active_range(0, 256, 524000) 1 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 DMA32 4096 -> 1048576 Normal 1048576 -> 1048576 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0 -> 159 0: 256 -> 524000 On node 0 totalpages: 523903 DMA zone: 56 pages used for memmap DMA zone: 1354 pages reserved DMA zone: 2589 pages, LIFO batch:0 DMA32 zone: 7108 pages
Technology - unRAID Server Community » Legacy Support (unRAID 5 and Older) » General Support (V5 and Older) » Is error log showing HDD Problems? [SOLVED] « previous next » Send this topic Print Pages: [1] Go Down Author Topic: Is error log showing HDD Problems? [SOLVED] (Read 7794 times) Kandinsky Member Posts: 28 Is error log showing HDD Problems? [SOLVED] « on: May 19, 2013, 05:29:16 AM » Dear Experts,I am getting the errors below which seem to be https://bbs.archlinux.org/viewtopic.php?id=47039 repeating themselves over a short period of time. Should I be worried, if so how can I identify which drive is looking dodgy please? I am using the latest 12a release.Now with full syslog attached. Not sure which drive I need to give any smart report on since I don't know which one it is.May 19 12:20:10 GOOGOLPLEX kernel: http://lime-technology.com/forum/index.php?topic=27491.0 ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x800 action 0x6 frozen (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1: SError: { HostInt } (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: failed command: IDENTIFY DEVICE (Minor Issues)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in (Drive related)May 19 12:20:10 GOOGOLPLEX kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related)May 19 12:20:10 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:20 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)May 19 12:20:20 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:30 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)May 19 12:20:30 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:31 GOOGOLPLEX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)May 19 12:20:31 GOOGOLPLEX kernel: ata1.00: link online but device misclassified (Drive related)May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: qc timeout (cmd 0xec) (
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware ata3.00: failed to IDENTIFY User Name Remember Me? Password Linux - Hardware This forum is for Hardware issues. http://www.linuxquestions.org/questions/linux-hardware-18/ata3-00-failed-to-identify-940208/ Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our https://www.virtualbox.org/ticket/7736 community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note failed to that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction failed to identify to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 04-17-2012, 05:25 AM #1 adrianmariano Member Registered: Dec 2004 Distribution: Ubuntu Trusty Posts: 163 Rep: ata3.00: failed to IDENTIFY Running Ubuntu 11.10 I'm getting a constant stream of messages in syslod shown below. Does anybody know what these mean? Code: Apr 17 06:23:08 alpaca kernel: [156391.589757] ata3: hard resetting link Apr 17 06:23:08 alpaca kernel: [156391.909682] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 17 06:23:08 alpaca kernel: [156391.912347] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x100) Apr 17 06:23:13 alpaca kernel: [156396.908565] ata3: hard resetting link Apr 17 06:23:13 alpa
6 years ago Last modified 21 months ago SATA disks not found after reboot into linux (ICH9 only) Reported by: mmusterd Owned by: Priority: major Component: other Version: VirtualBox 3.2.10 Keywords: Cc: Guest type: Linux Host type: Windows Description (last modified by michaln) (diff) Situation: I have a IDE hdd with a linux installation on it, as well as grub. I have a IDE cdrom with an image of windows XP on it. I have a SATA hdd with windows XP on it, or nothing I want to boot the linux OS, which will determine if the windows XP partition is available and has booted correctly. If this is the case, a grub-reboot is issued to boot into windows XP once, otherwise the image is restored onto the HDD. If I reboot from windows XP, the linux OS should do the above again. On an actual machine, the procedure works without a hitch. However after a reboot from windows XP to linux (Start | Shut Down... | Restart) the linux suddenly can't find the SATA disks. dmesg has the following lines: [ 6.166426] ata1.00: qc timeout (cmd 0xec) [ 6.166426] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 6.516437] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 16.517619] ata1.00: qc timeout (cmd 0xec) [ 16.517619] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.517619] ata1: limiting SATA link speed to 1.5 Gbps [ 16.866406] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 46.866424] ata1.00: qc timeout (cmd 0xec) [ 46.866424] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 47.216399] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 47.566424] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 52.566425] ata2.00: qc timeout (cmd 0xec) [ 52.566425] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 52.916425] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 62.916398] ata2.00: qc timeout (cmd 0xec) [ 62.916398] ata2.00: failed to IDENTIFY (I/O error,