Buffer I/o Error On Device Dm-1 Logical Block 0
Contents |
on megaraid rebuild, analysis and Issues related to hardware problems Post Reply Print view Search Advanced search 13 posts 1 2 Next jamesNJ buffer i o error on device sdb logical block 0 Posts: 18 Joined: 2015/02/25 21:49:44 CentOS server freeze/crash on megaraid rebuild, buffer i o error on device sdc logical block 0 analysis and Quote Postby jamesNJ » 2015/07/24 17:25:21 Hello all,I have a problem with a large CentOS 7 buffer i o error on device sr0 logical block 0 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. If it
Buffer I O Error On Device Sdc1 Logical Block
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 to result in all buffer i o error on device sda logical block 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 systemd-udevd process kicks in and the system eventu
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 10.10 box and created a LVM in it. kernel buffer i/o error on device dm-2 logical block Then copied some files to it and restarted the machine to see if
Buffer I/o Error On Device Dm-3
it would mount into the right mountpoint. It didn't. So I decided to see if it was there (vg in
Buffer I/o Error On Device Dm-0 Logical Block Redhat
question is export): raub strangepork:~$ sudo vgscan Reading all physical volumes. This may take a while... /dev/dm-0: read failed after 0 of 4096 at 429496664064: Input/output error /dev/dm-0: read failed after 0 of http://www.centos.org/forums/viewtopic.php?t=53481 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 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 https://www.redhat.com/archives/linux-lvm/2010-November/msg00011.html 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 block 104857598 [ 335.467647] Buffer I/O error on device dm-0, logical block 0 [ 335.467671] Buffer I/O error on device dm-0, logical block 0 [ 335.467703] Buffer I/O error on device dm-0, logical block 1 [ 335.467734] Buffer I/O error on device dm-0, logical block 104857599 [ 335.467762] Buffer I/O error on devic
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 http://unix.stackexchange.com/questions/98208/i-o-errors-on-linux-lvm about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered http://forums.fedoraforum.org/showthread.php?t=115702 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 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 error on 4 down vote favorite I have a CentOS 6 box with 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 error on device ls to the logical volumes and they show up in lvdisplay, but first I get a bunch 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,29032752 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 atte
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Other Versions > EOL (End Of Life) Versions FC5, Buffer I/O error on device dm-0, logical block 0 FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search EOL (End Of Life) Versions This is a Forum to discuss problems and workarounds for versions of Fedora that have passed End of Life. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 2nd July 2006, 11:50 AM oocc Offline Registered User Join Date: Feb 2005 Posts: 4 FC5, Buffer I/O error on device dm-0, logical block 0 Hi, I have a FC5+Windows 2000 dual system, recently, if I try to boot my FC5, I will get lots of "Buffer I/O error on device dm-0, logical block 0" and then the messages "EXT3-fs: Can't read superblock on 2nd try." "mount: error mounting /dev/root on /sysroot as ext3: Invalid argument" "setuproot: moving /dev/ failed: No such file or directions" "setuproot: error mounting /proc: No such file or directory" "setuproot: error mounting /sys: No such file or directory" "switchroot: mount failed: No such file or directory" "Kernel panic - not syncing: Attempted to kill init!" I am wondering you if you could help solve the problem, at least I need to access some data in the linux partition. Thanks. oocc View Public Profile Find all posts by oocc Tags block, buffer, device, dm0, error, fc5, i or o, logical « Previous Thread | Next Thread » Thread Tools Show Printable Version Display Modes Linear Mode Switch to Hybrid Mode Switch to Threaded Mode Search this Thread Advanced Search Posting Rules You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Forum Rules Forum Jump User Control Panel Private Messages Subscriptions Who's Online Search Forums Forums Home Fedora Resources Tips About The Forum Guides & Solutions (Not For Questions) News Fedora Project Elections Links Fedora 23/24 Installation, Upgrades and Live Media Using Fedora Hardware & Laptops Servers & Networking Security