Re: need help with approx-gc
On 20150508_1446-0600, Bob Proulx wrote:
> Paul E Condon wrote:
> > I run approx on one of my local jessie machines. The approx installation
> > is strictly by using the approx deb, which includes a weekly run of
> > approx-gc , which should just clean out the local repository of debs that
> > are no longer useful. But approx-gc has started reporting I/O errors.
>
> It is reporting I/O errors as in the disk drive is failing types of
> errors? As in hardware errors outside of the software?
>
> What is reported? Are the errors in the /var/log/syslog or
> /var/log/kern.log files? What types of errors?
The following is just a few examples from kern.log:
May 8 11:32:49 cmn kernel: [4880283.861027] sd 2:0:0:0: [sda]
May 8 11:32:49 cmn kernel: [4880283.861032] Add. Sense: Unrecovered read error - auto reallocate failed
May 8 11:32:49 cmn kernel: [4880283.861036] sd 2:0:0:0: [sda] CDB:
May 8 11:32:49 cmn kernel: [4880283.861038] Read(10): 28 00 00 f6 38 00 00 00 08 00
May 8 11:32:49 cmn kernel: [4880283.861051] end_request: I/O error, dev sda, sector 16136192
May 8 11:32:10 cmn kernel: [4880244.912960] 00 f6 38 00
May 8 11:32:10 cmn kernel: [4880244.912967] sd 2:0:0:0: [sda]
May 8 11:32:10 cmn kernel: [4880244.912971] Add. Sense: Unrecovered read error - auto reallocate failed
May 8 11:32:10 cmn kernel: [4880244.912975] sd 2:0:0:0: [sda] CDB:
May 8 11:32:10 cmn kernel: [4880244.912977] Read(10): 28 00 00 f6 38 00 00 00 08 00
May 8 11:32:10 cmn kernel: [4880244.912990] end_request: I/O error, dev sda, sector 16136192
May 8 11:32:10 cmn kernel: [4880244.912990] end_request: I/O error, dev sda, sector 16136192
All of them have the same sector number. This is the sda drive, which is
formatted as ext4. Is there some way that the automatic reallocate could the
repaired by a forced manual fsck? and is the rescue function on the netinst CD
adequate for this?
>
> less /var/log/kern.log
>
> Are you running SMART? What do the SMART error logs say?
Not running SMART.
What Debian package provides smartctl ?
I don't think the following tests will make the reallocation problem
go away.
I was planning to do something else this weekend, Oh well.
Thanks ;-)
>
> smartctl -l error /dev/sda
> smartctl -l selftest /dev/sda
>
> Are you running selftests? If not try running a SMART selftest and
> seeing what is the result of it.
>
> smartctl -t short /dev/sda
> sleep 120 # or whatever is predicted above
> smartctl -l selftest /dev/sda
>
> If short is okay then try a 'long' test. If you are seeing I/O errors
> then I would be worried the disk is failing. In which case the SMART
> would confirm it. (SMART isn't a good predictor. But it can confirm
> a diagnosis.)
>
> Bob
--
Paul E Condon
pecondon@mesanetworks.net
Reply to: