Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#29 version 1.3 :: query failed

closed-wont-fix
1
2004-08-31
2004-08-08
Anonymous
No

using version 1.3 from 2004 Aug 01 disk image on a PowerBook G4
1.33Mhz, the following errors are in the log.

2004-08-08 14:28:02.059 efssmartd[416] ExtFS: SMART status
query failed with: 0xe00002ed!
2004-08-08 14:28:02.905 efssmartd[416] efssmartd: Warning
Status for disk FUJITSU MHT2080AT Media: 'The status query failed
due to an OS error.'.
2004-08-08 14:38:03.097 efssmartd[416] ExtFS: SMART status
query failed with: 0xe00002ed!
2004-08-08 14:38:03.098 efssmartd[416] efssmartd: Warning
Status for disk FUJITSU MHT2080AT Media: 'The status query failed
due to an OS error.'.
2004-08-08 14:43:03.105 efssmartd[416] ExtFS: SMART status
query failed with: 0xe00002ed!
2004-08-08 14:43:03.106 efssmartd[416] efssmartd: Warning
Status for disk FUJITSU MHT2080AT Media: 'The status query failed
due to an OS error.'.
2004-08-08 14:48:03.114 efssmartd[416] ExtFS: SMART status
query failed with: 0xe00002ed!
2004-08-08 14:48:03.115 efssmartd[416] efssmartd: Warning
Status for disk FUJITSU MHT2080AT Media: 'The status query failed
due to an OS error.'.

Discussion

  • Logged In: NO

    I forgot to include a vital piece of info. I'm using 10.3.4 w/all apple
    updates.

     
    • priority: 5 --> 1
    • status: open --> open-wont-fix
     
  • Logged In: YES
    user_id=595265

    This is expected behavior. This are just warnings to inform you that the
    S.M.A.R.T. status of a drive could not be obtained at that particular
    moment. These query failures seem common right after wakeup from
    sleep. The "0xe00002ed" errors are "device not responding". So it's likely
    your drive is still in the process of waking up.

    You can just ignore these warnings. If any actual S.M.A.R.T. errors are
    detected, a dialog will inform you of the error.

    HTH.

     
    • status: open-wont-fix --> closed-wont-fix