Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #177757

Re: HELP! Re: How to fix I/O errors? (SOLVED)

From Marc Auslander <marcslists@gmail.com>
Newsgroups linux.debian.user
Subject Re: HELP! Re: How to fix I/O errors? (SOLVED)
Date 2017-02-12 21:50 +0100
Message-ID <ta9fQ-2ui-7@gated-at.bofh.it> (permalink)
References (15 earlier) <ta9fQ-2ui-39@gated-at.bofh.it> <ta9fQ-2ui-41@gated-at.bofh.it> <ta9fQ-2ui-43@gated-at.bofh.it> <ta9fQ-2ui-45@gated-at.bofh.it> <ta9fQ-2ui-47@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Marc Shapiro <marcnshap@gmail.com> writes:

> BTW, what is your third partition, and why would you not separate it
> now if starting from scratch?
My third partition is for backups which I make to protect against
software or operator error.  At one point it was on a separate disk
since disks were small and without LVM had to be a different
partition/file system.
>
>
> One other question.  If using raid, how do you know when a disk is
> starting to have trouble, as mine did?  Since the whole purpose of
...
> Marc

Ok - I'm pretty paranoid about that.  smart is checking.
mdadm will notice if a disk is bad and turn
it off, so to speak.  Again in the logs.
I run a cron job to check form smart errors based on:

    smartctl -l error -q errorsonly "device"
    smartctl -H -q errorsonly "device"

But I've always checked all my disks once a week.  A root cron job
reads the whole disk with dd into /dev/null.  Any error get logged, of
course.  Separately, a cron job scans syslog and syslog.1 grepping for
"IO Error" and informs me by email if any new errors are found.  This
catches error in the dd check but also actual errors in operation.

Back to linux.debian.user | Previous | Next | Find similar | Unroll thread


Thread

Re: HELP! Re: How to fix I/O errors? (SOLVED) Marc Auslander <marcslists@gmail.com> - 2017-02-12 21:50 +0100

csiph-web