O Error On Device Sda3
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings
Buffer I/o Error On Device Logical Block
and policies of this site About Us Learn more about Stack Overflow the buffer i/o error on device sdb logical block 0 linux company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered
Buffer I O Error On Device Sda Logical Block 0 Linux
Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can buffer i/o error on device dm-0 ask a question Anybody can answer The best answers are voted up and rise to the top Is this drive failure or something else? up vote 10 down vote favorite 2 I have a year-old drive that's giving me trouble. Copying data to it fails after about 8-10GB of transfers. It spontaneously changes to 'read only'. It's properly formatted ext4, I'm the buffer i/o error on device logical block 0 owner. Searching online, it looks like this is a symptom of a failing drive. How do I confirm this, since the SMART tests indicate otherwise? I did the obvious like check the Disk Utility, and ran the extended SMART test. All results from Disk Utility come back perfect. Read error rate and reallocated sectors are showing zero. I'm guessing this disk is bad and SMART isn't detecting it, though I don't understand why. I'd like to confirm what the problem is. I'm having no problems with the other disks in the machine. fstab: proc /proc proc nodev,noexec,nosuid 0 0 UUID=62e11126-3f06-43f0-bd5a-29b411bb8160 / ext4 errors=remount-ro 0 1 UUID=5e2d6348-be6e-4d5d-8f7f-1a5c1cab7db2 /home ext4 defaults 0 2 UUID=97e594a3-c783-4c73-97c0-682afcdc88b6 none swap sw 0 0 /dev/disk/by-label/Media /media/Media ntfs-3g defaults,user,locale=en_GB.utf8 0 0 Output of dmesg | less: (There are hundreds more 'Buffer I/O error' lines above) [22734.511487] Buffer I/O error on device sda1, logical block 302203 [22734.511489] Buffer I/O error on device sda1, logical block 302204 [22734.511490] Buffer I/O error on device sda1, logical block 302205 [22734.511492] Buffer I/O error on device sda1, logical block 302206 [22734.511494] Buffer I/O error on device sda1, logical
Start here for a quick overview of the site Help Center Detailed answers to any questions you might
Buffer I O Error On Device Sdb Logical Block
have Meta Discuss the workings and policies of this site About redhat buffer i/o error on device Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting
Buffer I/o Error On Dev Async Page Read
ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; http://askubuntu.com/questions/141862/is-this-drive-failure-or-something-else it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Buffer I/O error on device (sata drive) up vote 2 down vote favorite 2 I keep getting these messages in one of my servers kernel logs http://serverfault.com/questions/613249/buffer-i-o-error-on-device-sata-drive (which is responsible for file operations). I wonder if anybody knows how serious are these issues. I cannot use smartmontools because the disks are handled by a 3ware card which has it's own (very limited tw_cli utility). [2522065.275739] sd 0:0:1:0: [sdg] CDB: [2522065.275741] Read(10): 28 00 2e 90 97 f8 00 00 08 00 [2522065.275750] end_request: I/O error, dev sdg, sector 781228024 [2522065.281091] Buffer I/O error on device sdg, logical block 97653503 [2522065.287157] sd 0:0:1:0: [sdg] Device not ready [2522065.287163] sd 0:0:1:0: [sdg] [2522065.287166] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [2522065.287168] sd 0:0:1:0: [sdg] [2522065.287170] Sense Key : Not Ready [current] [2522065.287174] sd 0:0:1:0: [sdg] [2522065.287176] Add. Sense: Logical unit not ready, cause not reportable [2522065.287179] sd 0:0:1:0: [sdg] CDB: [2522065.287181] Read(10): 28 00 00 00 00 00 00 00 20 00 [2522065.287190] end_request: I/O error, dev sdg, sector 0 [2522065.291147] Buffer I/O error on device sdg, logical block 0 [2522065.291147] Buffer I/O error on device sdg, logical block 1 [2522065.291147] Buffer I/O error on device sdg, l
1 #1 2013-05-11 15:08:31 marzecki Member Registered: 2011-08-28 Posts: 15 HDD errors after ArchLinux installation on partition used by Windows I'm after the installation of ArchLinux on the ASUS laptop.The partitions has been created as follows:/dev/sda3 46G https://bbs.archlinux.org/viewtopic.php?id=163128 / /dev/sda2 72M /boot /dev/sda4 230G /homeAll partitions are EXT4. The /dev/sda1 partition is another Windoze NTFS partition.Before this, there were two NTFS partitions (sda1 and sda2). sda2 has been removed and new http://www.ubuntu-es.org/node/183155 sda2, sda3, sda4 has been created.After running an ArchLinux install medium dmesg showed up with kernel errors. I ignored it and installed new system on the above partitions.Now, on every boot kernel shows following o error errors:ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata1.00: irq_stat 0x40000008 ata1.00: failed command: READ FPDMA QUEUED [145B blob data] ata1.00: status: { DRDY ERR } ata1.00: error: { UNC }end_request: I/O error, dev sda, sector 976773167 Buffer I/O error on device sda, logical block 122096645 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata1.00: irq_stat 0x40000008 ata1.00: failed command: READ o error on FPDMA QUEUED [145B blob data] ata1.00: status: { DRDY ERR } ata1.00: error: { UNC }and some logs below:ata1.00: configured for UDMA/133 sd 0:0:0:0: [sda] Unhandled sense code sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Descriptor sense data with sense descriptors (in hex): 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 3a 38 60 2f sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4 sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 3a 38 60 28 00 00 08 00Do you guys think this is caused by bad sectors???I searched the web and found some ideas.It can be an Kernel Bug on ATA ACPI. On Ubuntu 9.10 they solved this issue by creating a file containing "options libata noacpi=1" in /etc/modprobe.d/.http://ubuntuforums.org/archive/index.p … 34762.htmlBut Bugzilla says it can be an NCQ issue (if I understand correctly):https://bugzilla.redhat.com/show_bug.cgi?id=404851I managed to swich from AHCI to IDE and nothing changed... So I'm back on AHCI.This part of this HDD was previously used by windozes. I think there are bad sectors but I don't know if its even related to this issue.Whole (current) boot log pasted here:http://pastebin.com/Z32ZDc99 Offline #2 2013-05-11 15:22:26 WonderWoofy Member From: Los G
generalBuenas! Recurro nuevamente al foro para ver si alguien me puede ayudar con el mini-problema que tengo. Resulta que hace poco probe una tarjeta de video que tenia tirada y pues no me gusto y volvi a la que tenia antes ( nvidia gt520, no es integrada) supuse que no pasaría nada y pues pasaron 2 dias y no paso nada raro por el cambio tan rapido de hardware. (Escribo esta parte porque quizá hice algo que hecho a perder el disco aunque no tengo la menor idea.) Al tercer dia tenia el computador con mi sesion con windows (Particion SDA1) y se fue a negro y no respondio. Reinicie a la mala y la bios se demoro mas de lo normal en reconocer los componentes, y windows no iniciaba. Me las arregle para iniciar windows y pasar chkdsk y listo, windows volvio a funcionar. Pero cuando inicio ubuntu 12.04 (tengo dual boot) que tengo en una particion del mismo disco, me indica esto antes de llegar a lightdm: Buffer I/O error on device sda1, logical block 797027 Esto es solo una linea pero son varias. La forma que consegui ver el error desde el escritorio fue escribir en consola " dmesg -> ~/Descargas/loc " El documente loc es bastante largo y no quise copiarlo entero. Por si sirve agrego la informacion de fdisk -l Disco /dev/sda: 160.0 GB, 160041885696 bytes 255 cabezas, 63 sectores/pista, 19457 cilindros, 312581808 sectores en total Unidades = sectores de 1 * 512 = 512 bytes Tamaño de sector (lógico / físico): 512 bytes / 512 bytes Tamaño E/S (mínimo/óptimo): 512 bytes / 512 bytes Identificador del disco: 0x7cc67cc6 Dispositivo Inicio Comienzo Fin Bloques Id Sistema /dev/sda1 * 63 61432559 30716248+ 7 HPFS/NTFS/exFAT /dev/sda2 61432621 283121663 110844521+ f W95 Ext'd (LBA) /dev/sda3 283121664 312580095 14729216 83 Linux /dev/sda5 61432623 281119684 109843531 7 HPFS/NTFS/exFAT /dev/sda6 2811207