Ata1.00 Failed To Identify I/o Error Err_mask=0x40
Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. ata failed to identify (i/o error err_mask=0x4) Bug244760 - ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) Summary: ata1.00: failed to emask 0x10 (ata bus error) IDENTIFY (I/O error, err_mask=0x4) Status: CLOSED NOTABUG Aliases: None Product: Fedora Classification: Fedora Component: kernel (Show other bugs) Sub Component: --- Version: 7 Hardware: All Linux Priority low Severity high TargetMilestone: --- TargetRelease: --- Assigned To: Kernel Maintainer List QA Contact: Brian Brock Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2007-06-18 20:53 EDT by srinivas varadaraj Modified: 2007-11-30 17:12 EST (History) CC List: 1 user (show) snecklifter See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2007-09-29 19:31:09 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description srinivas varadaraj 2007-06-18 20:53:56 EDT Description of problem: ATA driver ( pata_via 0000:00:0f.0: version 0.2.1 ). Version-Release number of selected component (if applicable): version 0.2.1 lspci -v output 00:0f.0 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP]) Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE Flags: bus master, medium devsel, latency 32, IRQ 17 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1] [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1] I/O ports at e100 [size=16] Capabilities: [c0] Power Management version 2 The primary controller is disabled on startup and the drives are not recognized. Write protecting the kernel read-only data: 800k libata version 2.20 loaded. pata_via 0000:00:0f.0: version 0.2.1 ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001e100 irq 14 ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001e108 irq 15 scsi0 : pata_via ata1.00: q
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 7799 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 repeating themselves over a short period of time. Should I be worried, if so how can https://bugzilla.redhat.com/show_bug.cgi?id=244760 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: 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 http://lime-technology.com/forum/index.php?topic=27491.0 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) (Drive related)May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (Errors)May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: revalidation failed (errno=-5) (Minor Issues)May 19 12:20:36 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:46 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)May 19 12:20:46 GOOGOLPLEX kernel:
Opened 5 years ago Last modified 7 weeks ago High I/O causing filesystem corruption Reported by: Indigo42 Owned by: Priority: major Component: virtual disk Version: VirtualBox 4.1.4 Keywords: Cc: Guest type: Linux Host type: Linux Description (last modified by klaus) (diff) https://www.virtualbox.org/ticket/10031 Hello, We are running an Ubuntu 10.04 32bit guest on a RHEL 64 http://www.hwupgrade.it/forum/archive/index.php/t-1821271.html bit host. The guest storage control is SATA AHCI with host I/O caching enabled. Host info: OS Type: Linux (2.6.18-194.el5) VirtualBox: 4.1.4 (74291) Processors: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz (2) HWVirtEx, PAE, Long Mode (64-bit) It seems during times of high I/O, like backups and etc, the guest filesystem resets to read-only. failed to We have this issue with both ext3 and ext4 filesystems. Switching to ext3 seemed to lessen the occurrences though. Here is a snip of syslog around the time of the corruption.. Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12 Dec 15 08:01:48 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12 Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon failed to identify MTA-v4: load average: 12 Dec 15 08:02:03 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12 Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MTA-v4: load average: 12 Dec 15 08:02:18 vault sm-mta[1437]: rejecting connections on daemon MSP-v4: load average: 12 Dec 15 08:02:29 vault kernel: [ 2338.011698] ata4.00: exception Emask 0x0 SAct 0xffff SErr 0x0 action 0x6 frozen Dec 15 08:02:29 vault kernel: [ 2338.011714] ata4.00: failed command: WRITE FPDMA QUEUED Dec 15 08:02:29 vault kernel: [ 2338.011721] ata4.00: cmd 61/00:00:b7:5c:9d/04:00:09:00:00/40 tag 0 ncq 524288 out Dec 15 08:02:29 vault kernel: [ 2338.011723] res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Dec 15 08:02:29 vault kernel: [ 2338.011726] ata4.00: status: { DRDY } Dec 15 08:02:29 vault kernel: [ 2338.011729] ata4.00: failed command: WRITE FPDMA QUEUED Dec 15 08:02:29 vault kernel: [ 2338.011736] ata4.00: cmd 61/00:08:77:31:9d/04:00:09:00:00/40 tag 1 ncq 524288 out Dec 15 08:02:29 vault kernel: [ 2338.011737] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 15 08:02:29 vault kernel: [ 2338.011740] ata4.00: status: { DRDY } Dec 15 08:02:29 vault kernel: [ 2338.011743] ata4.00: failed command: WRITE FPDMA QUEUED Dec 15 08:02:29 vault kernel: [ 2338.011749] ata4.00: cmd 61/00:10:77:35:9d/04:00:09:00:00/40 tag 2 ncq 524288 out Dec 15 08:02:29
domanda ma ho appena messo il naso in linux dopo aver fatto l'installazione di ubuntu 8.04 su disco primary slave, in ambiente ubuntu non si vede niente del disco master primario. in particolare il mio pc ha due dischi rigidi: il master primario (con 2 partizioni, nella prima xp) da 80 gb, e slave primario (con ubuntu) da 40 gb nella fase di installazione il master non lo vedeva e ha installato sullo slave. cambiando nel bios le sequenze di boot, riesco a usare sia xp (con hdd0) che ubuntu (con hdd1). se invece lascio come primo boot hdd0, mi chiede quale SO voglio usare ma mentre per xp non da problemi, per ubuntu si ferma con initramfs in ubuntu se faccio i comandi mount o fstab non vede comunque mai il disco da 80 gb, e l'altro lo chiama sda (non dovrebbe essere sdb?) vi prego di aiutarmi il disco master č NTFS ma non cambia niente anche con NTFS-3G (che perdipių non mi lascia mettere la spunta a dischi interni) Grazie medicina17-09-2008, 10:40Ma WinXP lo vedeva l'altro hard disk prima che lo utilizzassi per mettere Linux? I ponticelli situati sul retro dell'hard disk sono posizionati secondo il risultato desiderato? filifer17-09-2008, 11:32sė, prima (e anche adesso) xp lo vedeva. prima di linux era formattato ntfs se non mi ricordo male. poi dopo averlo formattato in fase di installazione in ext3 ho dovuto installare un software per farglielo vedere i ponticelli sono configurati per disco xp primary master e linux primary slave sono sempre stati cosė, non so bene quali siano le conseguenze medicina17-09-2008, 12:11Puoi allegare l'output del comando dmesg? Sono le informazioni che il kernel Linux invia al momento dell'avvio. filifer17-09-2008, 15:39ecco la schermata: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 2.6.24-21-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Mon Aug 25 17:32:09 UTC 2008 (Ubuntu 2.6.24-21.42-generic) [ 0.000000] BIOS-provided physical RAM map: [