[SOLVED] Buffer I/O error on /dev/sdb1 (...) async page read
Linux - HardwareThis forum is for Hardware issues.
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 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 that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Buffer I/O error on /dev/sdb1 (...) async page read
Since some months ago I have been seeing the following error message every time I reboot:
Code:
Buffer I/O error on dev sdb1, logical block 11, async page read
I'm about to do a disk check from Windows, since this is a data partition in NTFS, but in any case, I would like to know if this is serious (HDD damaged/failing) or something that can be solved with chkdsk or a similar utility.
BTW, I am backing up the data contained in this partition from Debian with rsync and the system is lagging a lot. I don't remember this behavior while using rsync previously but I usually let it do its job while I do other things away from the computer.
It looks like you have a single block of 8 bad sectors at LBA 2136. The good news is that this should be easy to fix. I first need to confirm my assumptions that:
This is an ext3 or ext4 filesystem in a partition that begins at sector 2048,
These sectors are being used by inode 7 (EXT2_RESIZE_INO).
If that is true, then simply writing zeros to those sectors and running fsck will get that block reassigned to spare sectors and all will be well.
First, look at the output from "fdisk -l /dev/sdb" and confirm that partition 1 starts at sector 2048. If true, that means that LBA 2136 is at sector offset 88 in that partition. For a filesystem with the usual 4K blocksize, that would be filesystem block 11.
Verify that block 11 is assigned to inode 7. Run the following (as root) to confirm (the part you type is in blue):
If that is as shown, then you can zero that block safely:
Code:
dd if=/dev/zero of=/dev/sdb1 count=8 seek=88
Now, you need to reboot and force an fsck. I don't know how to force an interactive fsck at boot time in Debian. You'll have to look it up, or perhaps an Debian expert can chime in here.
rknichols, this is the output of fdisk -l /dev/sdb:
Code:
Disco /dev/sdb: 298,1 GiB, 320072933376 bytes, 625142448 sectores
Unidades: sectores de 1 * 512 = 512 bytes
Tamaño de sector (lógico/físico): 512 bytes / 512 bytes
Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes
Tipo de etiqueta de disco: dos
Identificador del disco: 0x80a400ea
Disposit. Inicio Comienzo Final Sectores Tamaño Id Tipo
/dev/sdb1 * 2048 501364735 501362688 239,1G 7 HPFS/NTFS/exFAT
/dev/sdb2 501366782 625142447 123775666 59G 5 Extendida
/dev/sdb5 501366784 541157375 39790592 19G 83 Linux
/dev/sdb6 541159424 586080255 44920832 21,4G 83 Linux
/dev/sdb7 586080319 625142447 39062129 18,6G 83 Linux
The partition begins at sector 2048, but it's an NTFS partition. Is there some way to fix it, maybe from Windows, or does it necessarily need to be formatted in ext3-4 to be able to invalidate that block?
The partition begins at sector 2048, but it's an NTFS partition.
Does Windows still run OK without complaint? Have you tried running "chkdsk" on that drive? Note that the "chkdsk" that runs when you've told Windows to "automatically repair" errors is much more thorough and actually verifies that all files can be read.
I'm not an expert on NTFS. I did try zeroing those 8 sectors in an NTFS filesystem, and Windows chkdsk did find and repair some errors. Of course my filesystem isn't your filesystem, and I really have no way to know whether any files were permanently lost or corrupted (I did it in a snapshot of a VM). You don't have a lot to lose (those sectors can't be read), so without any advice from someone more knowledgeable, that's all I can suggest doing.
Windows doesn't complain about that partition, but this is a data partition I use to share my files between Windows and Linux in my dual-boot setup (Windows is installed in another partition on /dev/sda).
Yesterday I ran chkdsk /F on the troubled partition from Windows and it found no errors at all. It's Linux which complains about /dev/sdb1 when booting the system, but other than that I have no problems whatsoever with this partition (all my data can be read/saved without issues from Linux and Windows).
Since this is a NTFS partition, I will do some research to see what other tools are available on Windows to diagnose and repair NTFS problems. Thanks a lot for your help!
Last edited by Hungry ghost; 02-28-2017 at 07:01 PM.
If you do not need to save the data currently in the partition, what I would do is zero the entire partition (dd if=/dev/zero of=/dev/sdb1 bs=1M oflag=direct), then run "smartctl -t long /dev/sdb" and examine the results of "smartctl -a /dev/sdb" to see if the drive seems healthy, then make a new NTFS filesystem there (from Windows, probably).
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,881
Rep:
I would still consider replacing the disk in question, if possible. As I have a Western Digital Caviar SE (Device Model: WDC WD2000JS-00PDB0), which has never reported any SMART errors (I have had it for about 10 or so years now, transplanted form my first PC), so the fact yours is reporting bad sectors, is not a good sign of things that may come. I can't guarantee that it will fail, but having said that, once again suggest you look at replacing it, if you can.
There are many transient events, both mechanical and electrical, that can cause a few sequential sectors to appear bad. Many of those are not an indication of future problems. Right now, a single block of 8 sectors is being reported as bad, and the drive has not seen any bad sectors elsewhere. Of course this drive is pretty small (320GB) by today's standards, and might be due for an upgrade. But, at this point I haven't seen anything else that would warrant replacing it. Do keep in mind that every new drive comes with the non-zero chance of infant mortality. At 22748 hours, the one is in the middle of its life.
I will try the suggestion to zero out the entire partition in a few days, when I have some time to do the backups and restore my data. In any case, I do regular backups of my data, so if something goes wrong, I will still be able to recover my data.
I'll keep you posted on how this goes after I zero out and reformat the partition.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.