similar to: CentOS-6.8 fsck report Maximal Count

We have a remote warm standby system running CentOS-6.8 as a KVM system with multiple guests. One of the guests began reporting an error when running aide. Caught SIGBUS/SEGV while mmapping. File was truncated while aide was running? Caught SIGBUS/SEGV. Exiting The /var/log/messages file contained this: Mar 9 09:14:13 inet12 kernel: end_request: I/O error, dev vda, sector 14539264 Mar 9

On Fri, March 10, 2017 9:52 am, Warren Young wrote: > On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >> >> On Thu, March 9, 2017 09:46, John Hodrien wrote: >>> >>> fsck's not good at finding disk errors, it finds filesystem errors. >> >> If not fsck then what? > > badblocks(8). And I definitely will

On Fri, March 10, 2017 11:57, m.roth at 5-cent.us wrote: > > Looks like only one sector's bad. Running badblocks should, > I think, mark that sector as bad, so the system doesn't try > to read or write there. I've got a user whose workstation has > had a bad sector running for over a year. However, if it > becomes two, or four, or 64 sectors, it's replacement

I get up around 0630, u can come anytime after that. I want to hit the range that morning but if I KNEW when you are arriving, I could plan around that... > On Mar 10, 2017, at 9:28 AM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: >> >> >> On Fri, March 10, 2017 9:52 am, Warren Young wrote: >>> On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at

On Tue, Mar 14, 2017, 7:41 AM James B. Byrne <byrnejb at harte-lyne.ca> wrote: > On Fri, March 10, 2017 11:57, m.roth at 5-cent.us wrote: > > > > > Looks like only one sector's bad. Running badblocks should, > > I think, mark that sector as bad, so the system doesn't try > > to read or write there. I've got a user whose workstation has > > had

On Mar 10, 2017, at 9:28 AM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > > On Fri, March 10, 2017 9:52 am, Warren Young wrote: >> On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >>> >>> On Thu, March 9, 2017 09:46, John Hodrien wrote: >>>> >>>> fsck's not good at finding disk

On Mar 10, 2017, at 6:32 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: > > On Thu, March 9, 2017 09:46, John Hodrien wrote: >> >> fsck's not good at finding disk errors, it finds filesystem errors. > > If not fsck then what? badblocks(8).

Hi All, I'm currently running an embedded linux system (arm) with a CF card mounted as EXT3. I'll copy some system details below... Anyway, I'm getting some drive errors and I'm wondering if they're due to bad/old drivers, something with EXT3 and CF latency, or something else entirely. These are the errors: hda: write_intr error1: nr_sectors=1, stat=0x51 hda:

All, Trying to figure out how to deal with, I assume, a dying disk that's unfortunately on / (ext3). Getting errors similar to: Dec 31 20:44:30 mybox kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } Dec 31 20:44:30 mybox kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=163423, high=0, low=163423, sector=163360 Dec 31 20:44:30 mybox kernel: end_request:

Hi, I'm having some serious problems diagnosing a hardware issue in my linux system. The following error occurs intermittently. I have replaced hard drives and it is still occurring. I'm trying to determine if it's a device conflict, a problem with the motherboard or something else. Can anyone help? hda: dma_intr: status=0x51 {DriveReady SeekComplete Error} hda: dma_intr: 0x40

Dear all, I'm trying to find a way to automate checkdisk every 1 month on a weekend. in other words i want checkdisk to run every saturday morning. i can of course change the default mount/count though that wont let me control WHEN it will happen. so i need your expert opinion with the following if possible: 1. reboot into single user mode 2. start checkdisk for all disks 3. once done,

Hello, I was wondering if anyone could point me in the right direction? I am receiving these in my log file and do not know what they mean or what to look for; Mar 8 04:03:56 bms kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 8 04:03:56 bms kernel: ata3.00: cmd 25/00:28:42:d3:37/00:00:13:00:00/e0 tag 0 cdb 0x0 data 20480 in Mar 8 04:03:56 bms kernel: res

I just tried this with CentOS 5.3 as well, and got exactly the same symptoms and dmesg output. (As a point of comparison, Ubunu 8.04 on my work laptop is able to access the drive.) Obviously "not detected" is a misapprehension, though I'm puzzled why "lsusb" doesn't show it. The device is there even though the partition table can't be read. ---------- Forwarded

Hi, Sorry for the need of the long winded email. Looking for some answers to the following. I am setting up a xen PV domU on top of a LVM partitioned DRBD device. Everything was going just fine until I tried to test the filesystems in the domU. Here is my setup; Dom0 OS: CentOS release 5 (Final) Kernel: 2.6.18-8.1.4.el5.centos.plusxen Xen: xen-3.0.3-25.0.3.el5 DRBD:

There are a number of flaws in the blktap userspace daemon when dealing with I/O errors. - The backends which use AIO check the io_events.res member to determine if an I/O error occurred. Which is good. But when calling the callback to signal completion of the I/O, they pass the io_events.res2 member Now this seems fine at first glance[1] "res is the usual result of an I/O

Hi All, I had to reboot a machine as I lost the ssh connectivity to it. I could ping to it though. On rebooting, the dmesg buffer showed the following messsage hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x40 { UncorrectableError }, CHS=7520/0/155, sector=1820440 end_request: I/O error, dev 16:02 (hdc), sector 1820440 hdc: dma_intr: status=0x51 { DriveReady

Hi, with being exposed to more and more failed hard disks reports, I've accumulated several questions of the logged messages in /var/log/messages file: like how to identifying failed disks(partitions), where is the exact failed sector(s) on the hard disk, and why badblocks reports OK to the reported disk failure. Let me explained the above with the following several example. scenario #1, a

Hi List, What this means? md: syncing RAID array md0 md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction. md: using 128k window, over a total of 2096384 blocks. md: md0: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:sda2 disk 1, wo:0, o:1, dev:sdb2 sd 0:0:0:0:

Hi, I run hundreds of Redhat 8.0 boxes and Fedora Core 1 boxes, both Operation systems boxes give me some trouble reporting disk errors like the following (collected from /var/log/messages of each linux boxes by my own script). And a "badblocks" command on some of the related hard drive reports that failed sectors found, while others reports no, false-positive. Any one can give me

what file system are you using?? ssd drives have different characteristics that need to be accomadated (including a relatively slow write process which is obvious as soon as the buffer is full), and never, never put a swap partition on it, the high activity will wear it out rather quickly.? might also check cables, often a problem particularly if they are older sata cables being run at a possibly