sqlite error: disk I/O error

Brandon S Allbery KF8NH allbery at kf8nh.com
Fri Jul 9 17:36:00 PDT 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 7/9/10 18:28 , Scott Haneda wrote:
> On Jul 9, 2010, at 7:11 AM, Daniel J. Luke wrote:
> 
>> On Jul 9, 2010, at 1:53 AM, Scott Haneda wrote:
>>> Going a bit off topic here, but S.M.A.R.T. is not all that smart, and there could be data that is secretly failing and becoming corrupt, yet passing all tests.
>>
>> I've had good luck with smartmontools (available from MacPorts ;-) ).
>>
>> Adding something like:
>>
>> DEVICESCAN -m my_email at my_domain -s (S/../.././02|L/../../6/03) -M exec /usr/bin/mail
>>
>> to smartd.conf
>>
>> So far, every failing disk has generated an error email some time before it became totally unreadable (which makes it less likely that I'll have to restore from backup, so usually saves me some time). Nothing is going to be able to give you 100% warning, though...
> 
> This appears to be a significantly complex set of tools.  I read over the man pages and the conf file. There is an initial test you run `sudo smartctl -t short /dev/disk0s2` which when run, from what I can gather, sets up the device in a way that prepares it for automated running in the future.
> 
> Instructions say to keep running `smartctl -t short /dev/disk0s2` until you get results, which I have been trying:
>   smartctl 5.39.1 2010-01-28 r3054 [x86_64-apple-darwin10.4.0] (local build)
>   Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
> 
>   === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
>   Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
>   Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
>   Testing has begun.
>   Please wait 2 minutes for test to complete.
>   Test will complete after Fri Jul  9 15:17:34 2010
> 
> Each time I run it, that time to completion moves forward, I don't think it will ever finish.  For example, here is a second run:

The point you are missing is that this command doesn't execute on OSX; it
runs *on the drive*.  Every time you reissue the command, the drive dumps
the running test and starts over.  You need to collect the result of the
selftest from the drive after waiting the specified amount of time (or more).

- -- 
brandon s. allbery     [linux,solaris,freebsd,perl]      allbery at kf8nh.com
system administrator  [openafs,heimdal,too many hats]  allbery at ece.cmu.edu
electrical and computer engineering, carnegie mellon university      KF8NH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkw3wHAACgkQIn7hlCsL25XV6ACgmwPQSwePOMjHcWFD4uOCk7fZ
Me0AniEZdUkcSB/Qdqx22NR4nuGKP8sR
=QYpb
-----END PGP SIGNATURE-----


More information about the macports-users mailing list