Home > I O > I O Error Err_mask

I O Error Err_mask

Something with > interrupt routing/IPI, missing irq ack? We have this issue with both ext3 and ext4 filesystems. Try to tune host os page flusher behavior to avoid accumulating of significant amount of dirty pages in host file system buffers. Everything works fine, but if I provide the "nosmp" option to the kernel, I get some (S)ATA errors and the system does not boot.

Booting another !SMP kernel > works fine. If you'd like to contribute content, let us know. Switching to ext3 seemed to lessen the occurrences though. Host Ubuntu 11.10/64 guest ubuntu 10.04/64 virtual box 4.1.2 comment:4 in reply to: ↑ 3 Changed 5 years ago by frank Replying to [email protected]: I am seeing the exact same thing. https://ubuntuforums.org/showthread.php?t=2233818

On regular bootups, I get this message: ata1: SATA max UDMA/133 cmd 0xf8850100 ctl 0x00000000 bmdma 0x00000000 irq 218 ata2: SATA max UDMA/133 cmd 0xf8850180 ctl 0x00000000 bmdma 0x00000000 irq 218 while the nosmp one gets this (the screenshot cut the irq part): ata1: SATA max UDMA/133 abar m2048 [at] 0x9b30400 port 0x9b304100 irq 223 ata2: SATA max UDMA/133 abar m2048 [at] 0x9b30400 port 0x9b304100 irq 223 Don't know if the irq # change is significant or not. Drive Interface Issues These are problems with the cables and connections to the drive, both power and data, or the quality of the power supplied. yes lowmem_reserve[]: 0 3254 16132 16132 Node 0 DMA32 free:219600kB min:13620kB low:17024kB high:20428kB active_anon:57196kB inactive_anon:35036kB active_file:755084kB inactive_file:755128kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:3332896kB mlocked:0kB dirty:55196kB writeback:220kB mapped:8040kB shmem:0kB slab_reclaimable:43016kB slab_unreclaimable:9960kB kernel_stack:8kB pagetables:2396kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:208 all_unreclaimable? Last edited by sudodus; July 11th, 2014 at 07:55 AM.

Offline surface scan supported. The guest storage control is SATA AHCI with host I/O caching enabled. system_call_fastpath+0x16/0x1b Mem-Info: Node 0 DMA per-cpu: CPU 0: hi: 0, btch: 1 usd: 0 CPU 1: hi: 0, btch: 1 usd: 0 CPU 2: hi: 0, btch: 1 usd: 0 CPU 3: hi: 0, btch: 1 usd: 0 Node 0 DMA32 per-cpu: CPU 0: hi: 186, btch: 31 usd: 88 CPU 1: hi: 186, btch: 31 usd: 0 CPU 2: hi: 186, btch: 31 usd: 0 CPU 3: hi: 186, btch: 31 usd: 0 Node 0 Normal per-cpu: CPU 0: hi: 186, btch: 31 usd: 35 CPU 1: hi: 186, btch: 31 usd: 0 CPU 2: hi: 186, btch: 31 usd: 0 CPU 3: hi: 186, btch: 31 usd: 0 active_anon:55213 inactive_anon:13423 isolated_anon:0 active_file:591922 inactive_file:592035 isolated_file:0 unevictable:0 dirty:38310 writeback:280 unstable:0 free:227453 slab_reclaimable:39250 slab_unreclaimable:26638 mapped:83791 shmem:0 pagetables:6131 bounce:0 Node 0 DMA free:15924kB min:64kB low:80kB high:96kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15700kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata1.00: qc timeout (cmd 0xec) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata1: port is slow to respond, please be patient (Status 0x80) ata1: COMRESET failed (errno=-16) ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ...

This time, it's 14.04, although I'm still experiencing the same situation. Booting another !SMP kernel > > works fine. The two most important tools for initial analysis are the syslog and the SMART report. In other words the computer won't post in legacy IDE, I need native IDE to work.

I actually went back to the shop where I bought my unit. How to easily fix To Identify I O Error Err_mask error? There have been too many cases of drives thrown out or returned by an RMA process, when the problem was just a bad cable! no [2583901.669250] lowmem_reserve[]: 0 0 21210 21210 [2583901.669254] Node 0 Normal free:13752kB min:17440kB low:21800kB high:26160kB active_anon:458404kB inactive_anon:56672kB active_file:7959020kB inactive_file:7992044kB unevictable:0kB isolated(anon):32kB isolated(file):192kB present:21719040kB mlocked:0kB dirty:1675664kB writeback:108736kB mapped:3502240kB shmem:344kB slab_reclaimable:410208kB slab_unreclaimable:74592kB kernel_stack:2672kB pagetables:14684kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable?

Could someone please tell me how to fix this if it is a bug? http://www.linuxquestions.org/questions/linux-kernel-70/kernel-2-6-24-3-12-ata2-00-failed-to-identify-io-error-err_mask%3D0x4-627603/ horde Linux - General 5 02-17-2008 04:23 AM kernel: vesafb: probe of vesafb0 failed with error -6 Toadman Mandriva 0 05-28-2005 09:13 PM online_update failed - ERROR(Media:connection failed)[Connect failed] rover SUSE / openSUSE 8 02-22-2005 07:57 AM kernel 2.6.8 compile error mkinitrd failed mcalizo Linux - Software 0 11-30-2004 01:58 AM All times are GMT -5. About Us Contact us Privacy Policy Terms of use How to fix To Identify I O Error Err_mask Error? 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.

Dec 15 08:02:29 vault kernel: [ 2338.011969] ata4: hard resetting link Dec 15 08:02:29 vault kernel: [ 2338.332268] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Dec 15 08:02:33 vault kernel: [ 2342.108804] ata4.00: configured for UDMA/133 Dec 15 08:02:33 vault kernel: [ 2342.108811] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108815] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108818] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108820] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108823] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108826] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108829] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108831] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108834] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108837] ata4.00: device reported invalid CHS sector 0 Dec 15 08:02:33 vault kernel: [ 2342.108840] ata4.00: device reported invalid CHS sector 0 At this point the guest needs to be shut down and the drive mounted and fsck, which complains about allot of IO handle stuff. However, if a better cable does not solve the issue, then it is probably a power problem (loose power cable or backplane connection, poor connectors, poor power splitter, overloaded power supply, too many drives on power rail, bad power supply, etc). There have been other complaints about Linux becoming unresponsive when lots of data is written, e.g.  https://bugzilla.kernel.org/show_bug.cgi?id=43094 - that one has been closed on formal grounds, but it's highly likely that the nvidia kernel module makes any difference. It is common after opening a computer case, to jostle the cables, and SATA cables are notorious for coming loose, if they aren't the locking type.

The host machine runs Ubuntu 10.04 with VirtualBox 4.1.8r75467. Booting another !SMP kernel > works fine. basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.) Recommended Solution Links: (1) Download (To Identify I O Error Err_mask 0x4) repair utility. There are two (2) ways to fix To Identify I O Error Err_mask 0x4 Error: Advanced Computer User Solution (manual update): 1) Start your computer and log on as an administrator. 2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore. 3) In the new window, select "Restore my computer to an earlier time" option and then click Next. 4) Select the most recent system restore point from the "On this list, click a restore point" list, and then click Next. 5) Click Next on the confirmation window. 6) Restarts the computer when the restoration is finished.

Thank you in advance. FAQ Forum Quick Links Unanswered Posts New Posts View Forum Leaders FAQ Contact an Admin Forum Community Forum Council FC Agenda Forum Governance Forum Staff Ubuntu Forums Code of Conduct Forum IRC Channel Ubuntu Community Ubuntu Get Ubuntu Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Do you want to help us debug the posting issues ? < is the place to report it, thanks !

comment:12 Changed 2 months ago by aeichner Status changed from new to closed Resolution set to obsolete Please reopen if still relevant with a recent VirtualBox release.

LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel Kernel 2.6.24.3-12 ata2.00 failed to identify (io error, err_mask=0x4) User Name Remember Me? The problem also exists in 2.6.24-rc2. The channel itself is usually something like ata3 or ata12, the actual attached drive will be something like ata2.00 and ata13.01. Getting the syslog Use UnMENU, go to the Syslog plugin and view and download the syslog from there Capturing your syslog Viewing the System Log As of version 4.5beta2 of unRAID: - May now read syslog directly via browser by referencing 'http://tower/log/syslog' (substitute 'tower' with your server name).

Note: The manual fix of To Identify I O Error Err_mask 0x1error is Only recommended for advanced computer users.Download the automatic repair toolinstead. 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. How does it work? Host Ubuntu 11.10/64 guest ubuntu 10.04/64 virtual box 4.1.2 Please try VirtualBox 4.1.8.

The time now is 08:42 PM. 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 110 099 006 Pre-fail Always - 26679192 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 69 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1192938 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 105 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 69 183 Runtime_Bad_Block 0x0032 020 020 000 Old_age Always - 80 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 096 000 Old_age Always - 468158644334 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 063 061 045 Old_age Always - 37 (Min/Max 37/37) 194 Temperature_Celsius 0x0022 037 040 000 Old_age Always - 37 (0 25 0 0 0) 195 Hardware_ECC_Recovered 0x001a 049 037 000 Old_age Always - 26679192 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 194 000 Old_age Always - 9105 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 259480449187943 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1072978654 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2265266160 SMART Error Log Version: 1 No Errors Logged 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. Click here follow the steps to fix To Identify I O Error Err_mask 0x1 and related errors. It runs 5 virtual machines, both Arch Linux and Ubuntu 10.04.

g_abExecMemory+0x3e3f/0x180000 [vboxdrv] [] ? g_abExecMemory+0x86ad/0x180000 [vboxdrv] [] ? No kernel level trickery involved at all. The To Identify I O Error Err_mask error is the Hexadecimal format of the error caused.

Therefore if write operation in the host takes too long (what can happen if host flushes too much dirty pages to disk) then guest kernel may consider it as SATA timeout and trigger error handling procedure. When this happens most guests output lines with "failed command: WRITE FPDMA QUEUED". no lowmem_reserve[]: 0 0 0 0 Node 0 DMA: 1*4kB 0*8kB 1*16kB 1*32kB 2*64kB 1*128kB 1*256kB 0*512kB 1*1024kB 1*2048kB 3*4096kB = 15924kB Node 0 DMA32: 3024*4kB 2090*8kB 1462*16kB 875*32kB 528*64kB 249*128kB 96*256kB 48*512kB 22*1024kB 1*2048kB 0*4096kB = 219600kB Node 0 Normal: 4490*4kB 5913*8kB 4506*16kB 3159*32kB 1876*64kB 965*128kB 313*256kB 107*512kB 54*1024kB 1*2048kB 0*4096kB = 674288kB 1184083 total pagecache pages 130 pages in swap cache Swap cache stats: add 9947, delete 9817, find 594/648 Free swap = 13349756kB Total swap = 13386492kB 4194288 pages RAM 2629507 pages reserved 893107 pages shared 433355 pages non-shared and in the guest, they log things like this: Buffer I/O error on device sda2, logical block 4099963 sd 0:0:0:0: [sda] Unhandled error code sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06 sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 69 65 3e 00 00 08 00 end_request: I/O error, dev sda, sector 6907198 Buffer I/O error on device sda2, logical block 835286 EXT4-fs warning (device sda2): ext4_end_bio:242: I/O error writing to inode 2341288 (offset 0 size 4096 starting block 863400) JBD2: Detected IO errors while flushing file data on sda2-8 ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: failed command: WRITE DMA ata1.00: cmd ca/00:08:d6:a0:1b/00:00:00:00:00/e0 tag 0 dma 4096 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata1.00: status: { DRDY } ata1: hard resetting link ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata1.00: configured for UDMA/133 ata1.00: device reported invalid CHS sector 0 ata1: EH complete ata1.00: qc timeout (cmd 0xec) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1: hard resetting link ata1.00: status: { DRDY } ata1.00: failed command: WRITE FPDMA QUEUED ata1.00: cmd 61/08:30:a6:a1:44/00:00:04:00:00/40 tag 6 ncq 4096 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata1.00: device reported invalid CHS sector 0 Please fix this problem, we are still waiting for a long time for this fix. The same is even more important for backplanes, make sure that drives are firmly and well seated in their trays, and cannot be vibrated loose.

This article contains information that shows you how to fix To Identify I O Error Err_mask 0x4 both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to To Identify I O Error Err_mask 0x4 error code that you may receive. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. I don't know whether it is a bug in my hardware, Linux/Ubuntu or VirtualBox, but it is quite a severe problem for me. Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 12 Thread: Error ID I/O error, dev sda, sector Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode July 11th, 2014 #1 teodyseguin View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Mar 2013 Beans 7 Error ID I/O error, dev sda, sector I am experiencing the same problem as this person posted over here http://ubuntuforums.org/showthread.php?t=2048100 I had my machine bought just 1 week now, and I expect everything will just go smooth.

What causes To Identify I O Error Err_mask 0x1 error? Any settings changes won't be saved either, until the flash drive is accessible again. So this may be problem for any type 2 virtualizer running on top of host file system cache. rtR0MemAllocEx+0xbe/0x116 [vboxdrv] [] ?