On Tue, Jul 02, 2013 at 06:36:48PM +0100, Peter Chant wrote: > On 07/02/2013 08:29 AM, Hugo Mills wrote: > >This is usually an indication that you have bad hardware -- I'd > >suggest testing RAM, PSU, CPU in that order. I'm not sure what, if > >anything, can be done to fix the error on the disk right now. > > Thanks, appreciated. > > Hmm. I've got one stick of ram out of the machine due to testing as > I had some freezes last week. So the damage probably happened then, if that stick is bad. Filesystems have this irritating habit of remembering things done to them across reboots. :) Hugo. > If it were one of the RAM, PSU and CPU then I'm unsure why this IO > issue only surfaces on the HDD and not the SSD. I ordered a new HDD > last night, before reading your post. If its not the disk I'll go > raid1. If it is the disk then I'll probally find out. > > >>Not that I've done anything other than a cursory check but it looks > >>like the read only data is fine. > > Might be a good idea to use that to refresh your backups, just in > >case my prediction about the fixability is correct. > > Well, first option is to drop in the new disk, freshly format it and > copy the data across (not add it as a second disk). If that fails > last backup was wednesday. I've not done much of note since then > apart from try to fix the disk issues. > > -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- The glass is neither half-full nor half-empty; it is twice as --- large as it needs to be.
Attachment:
signature.asc
Description: Digital signature
