Kernel Buffer I/o Error On Device Dm-1 Logical Block
Contents |
Bad disk? Date: Wed, 10 Nov 2010 09:39:00 -0500 Yesterday I added a hard drive (to put extra stuff on it) to my ubuntu kernel buffer i/o error on device dm-2 logical block 10.10 box and created a LVM in it. Then copied some buffer i/o error on device dm-4 logical block files to it and restarted the machine to see if it would mount into the right mountpoint. buffer i/o error on device dm-3 It didn't. So I decided to see if it was there (vg in question is export): raub strangepork:~$ sudo vgscan Reading all physical volumes. This may take a buffer i/o error on device dm-0 logical block redhat while... /dev/dm-0: read failed after 0 of 4096 at 429496664064: Input/output error /dev/dm-0: read failed after 0 of 4096 at 429496721408: Input/output error /dev/dm-0: read failed after 0 of 4096 at 0: Input/output error /dev/dm-0: read failed after 0 of 4096 at 4096: Input/output error /dev/dm-0: read failed after 0 of 4096 at 0: Input/output error Found
Lost Page Write Due To I/o Error On Dm-0
volume group "export" using metadata type lvm2 Found volume group "root" using metadata type lvm2 raub strangepork:~$ Those dm-0 messages do not make me happy. dmesg and vgchange make me think the problem is on the new drive: [ 268.024593] scsi 0:0:0:0: Direct-Access ATA ST3500320NS SN04 PQ: 0 ANSI: 5 [ 268.024900] sd 0:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/465 GiB) [ 268.024918] sd 0:0:0:0: Attached scsi generic sg2 type 0 [ 268.024996] sd 0:0:0:0: [sdc] Write Protect is off [ 268.025003] sd 0:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 268.025046] sd 0:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 268.025377] sdc: sdc1 [ 268.049853] sd 0:0:0:0: [sdc] Attached SCSI disk [ 335.467482] quiet_error: 3 callbacks suppressed [ 335.467492] Buffer I/O error on device dm-0, logical block 104857584 [ 335.467540] Buffer I/O error on device dm-0, logical block 104857584 [ 335.467589] Buffer I/O error on device dm-0, logical block 104857598 [ 335.467615] Buffer I/O error on device dm-0, logical bloc
on megaraid rebuild, analysis and Issues related to hardware problems Post Reply Print view Search Advanced search 13 posts 1 2
Buffer I/o Error On Device Dm-7 Logical Block
Next jamesNJ Posts: 18 Joined: 2015/02/25 21:49:44 CentOS server freeze/crash on megaraid buffer i/o error on device logical block rebuild, analysis and Quote Postby jamesNJ » 2015/07/24 17:25:21 Hello all,I have a problem with a large buffer i/o error on dev dm-0 logical block CentOS 7 server hosting an LSI MegaRAID controller with 16x 1tb SAS drives. The server goes dead at night requiring a forced reboot or power cycle to restore service. https://www.redhat.com/archives/linux-lvm/2010-November/msg00011.html If it matters, this server has 1 large RAID-6 volume with 1 global hot spare available.I believe I have narrowed this issue down to the MegaRAID controller being busy with a RAID rebuild, and some automated action occurring at night that confuses LVM into oblivion. The issue is difficult to narrow down because this “automated action” seems http://www.centos.org/forums/viewtopic.php?t=53481 to result in all file systems being marked read-only. Syslog seems to continue working, but obviously cannot write useful data out to disk. Hence I have only been able to collect data on those rare times that I can actually log in when this issue occurs. I was able to capture 2 points of data that seem to start out with the same error condition.This only seems to occur when a drive fails and the MegRAID rebuilds to the global hot spare, or if I force some action on the RAID which causes a drive fail and rebuild to an alternate disk (I had a few disks get SMART predictive failures and have been working to replace these with new). I initially thought this issue was related to smartd warning messages, however when I replaced the last drive with predictive failures, the rebuild triggered the same behavior.So what seems to be the pattern is that I kick off a rebuild (which takes many hours) and then sometime around midnight a s
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads http://unix.stackexchange.com/questions/98208/i-o-errors-on-linux-lvm with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign http://askubuntu.com/questions/520358/logical-block-number-in-the-buffer-i-o-error 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 I/O errors on Linux LVM up vote 4 down vote favorite I have a CentOS 6 box with i/o error LVM setup and one of the PVs is a USB disk (I know). One of them is getting the error: Oct 30 10:57:07 alpha01 kernel: lost page write due to I/O error on dm-3 Oct 30 10:57:07 alpha01 kernel: Buffer I/O error on device dm-3, logical block 4 Which is causing problems with all of the LVs on it. pvs shows the PV as unknown device. I can ls to the logical volumes and they show up in lvdisplay, but first I get a bunch i/o error on of IO errors. I made sure the cables are secure between the USB drive. What should I do to get this back up and running for the meanwhile? Should I unmount each LV and run an fsck.ext4 on each one like fsck.ext4 -y /dev/vg1/lv_logvolname ? linux lvm fsck share|improve this question asked Oct 30 '13 at 15:06 Gregg Leventhal 2,31032752 In addition to fsck, if the external drive is SMART capable, checking the drive status/health and running the drive self tests may be useful. Backing up all the data may also be important. –rickhg12hs Oct 30 '13 at 15:44 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted I usually don't go the route of running an fsck and assume the disk is failing or has bad sectors. I definitely wouldn't run the fsck using the -y, since this will give fsck to attempt to start moving blocks which may exacerbate the problem. Instead I'll run a tool such as Spinrite (Commercial) or HDAT2 (freeware) on the disk to do the analysis & potential repair. What else? See my other answers to these questions for additional methods: fsck -cc /dev/sdb1 gives this result. Is everything okay> Detect damaged audio CD The 2nd link provides details about another tool, safecopy for attempting to recover data from a failed/failing drive. It doesn't attempt to do any repairing of hte HDD. share|improve this answer edited Aug 4 '15 at 22:28 answered Oct 30 '13 at 16:19 slmb
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 and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered 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 ask a question Anybody can answer The best answers are voted up and rise to the top Logical Block number in the “Buffer I/O error” up vote 2 down vote favorite I was trying to determine a bad PV which was causing the LV to report Buffer I/O error and found this interesting behaviour in the "Buffer I/O error" message. On a Large LV that is mapped to different PVs, I tried to use the "logical block" reported in the error, to match with the dmsetup table to find out which target device it was on. However this method doesn't seem to be reliable. I used dmsetup to create a device mapper device, with one or a number of holes in it. And the error messages are very interesting and I can't make sense of the pattern. It seems the "Logical Block" number in the error message depends on the size of the hole and also it's position. Is there a definitive way to locate the actual bad block? Here are the tests that I did +++ TEST 1 error block at 8, buffer i/o error at LB 8 root@ubuntu:~# dmsetup create test x.tab root@ubuntu:~# dmsetup table test 0 8 linear 8:16 0 8 1 error 9 1000 linear 8:16 8 root@ubuntu:~# dd if=/dev/mapper/test of=/dev/null bs=512 count=1000 dd: error reading ‘/dev/mapper/test’: Input/output error 8+0 records in 8+0 records out 4096 bytes (4.1 kB) copied, 0.000977434 s, 4.2 MB/s root@ubuntu:~# Sep 5 17:21:07 ubuntu kernel: [ 1358.811671] bio: crea