verify disk integrity

From: Dermot Paikkos (dermot_at_sciencephoto.com)
Date: 07/20/04

  • Next message: E.W.Jones: "Summary: Telnet and ftp errors"
    Date: Tue, 20 Jul 2004 10:06:18 +0100
    To: tru64-unix-managers@ornl.gov
    
    

    Hi managers,

    SYS: DS10, tur64 5.1, 36GB UWSCSI SSB, advfs FS.

    I think I may have a corrupt disk and would like to verify. Our
    database is reporting problems with the data file which it can not
    repair with a re-index.

    I have tried to use scu to check the disk. `verify` did not report
    any problems. The output from `read` is below.

    Does anyone know if there are other tools I can use or if there is
    some way of establishing whether a disk is failing?

    Much appreciated.
    Dp.

    scu: Error number 1 occurred on Tue Jul 20 10:00:56 2004
    scu: Data compare error at byte 0 in record number 1
    scu: Logical block number where error occured is 0
    scu: Data expected = 0x39, data found = 0x00, byte count = 512
    scu: The incorrect data starts at address 0x140048000 (marked by
    asterisk '*')
    scu: Dumping Data Buffer (base = 0x140048000, offset = 0, limit = 512
    bytes):

    0x140048000 *00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00
    0x14004801c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00
    0x140048038 00 00 00 00 00 00 00 00 57 45 56 82 04 00 00 00 42 44 30
    33 36 36 33 34 39 43 00 00
    0x140048054 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 02 00 00 fe 00 00 00
    0x140048070 14 00 00 00 b2 36 00 00 d8 13 00 00 60 63 3d 04 00 00 00
    ....etc

    ~~
    Dermot Paikkos * dermot@sciencephoto.com
    Network Administrator @ Science Photo Library
    Phone: 0207 432 1100 * Fax: 0207 286 8668


  • Next message: E.W.Jones: "Summary: Telnet and ftp errors"

    Relevant Pages

    • Re: grinding on HDD
      ... do you have media sniffers or indexing enabled in an office suite on in disk ... Backup your data without overwriting any previous backup ... Verify HD cables are the correct type & securely fitted ... If Optical drives dissappear from the BIOS bootup... ...
      (alt.comp.hardware.pc-homebuilt)
    • Re: has K3B been abandoned?
      ... I gave up on asking k3b to verify anything. ... Then it waits for the disk to be recognized by the ... but a simple lack of a time delay bug is too ... I had the identical problem with Nautilus so K3B is not the problem ...
      (Fedora)
    • Re: has K3B been abandoned?
      ... the presence of a bug (arguably here in kernel-space) does ... I gave up on asking k3b to verify anything. ... Then it waits for the disk to be recognized by the drive NOT! ... but a simple lack of a time delay bug is too much trouble to fix I ...
      (Fedora)
    • Re: Usual method of safely writing a file?
      ... verify the backup, write the new file, verify that, and then ... only in cache and not on disk after you've verified them both. ... Verifying would just read data out of the cache, ... SCSI disks do NOT enable write caching. ...
      (comp.programming)
    • Re: k3b fails to verify
      ... I am running growisofs 5.21, ... The disk seems fine - i have even written subsequent sessions to it ... I would like it to verify but it ... discs have worked just fine so far. ...
      (alt.os.linux.suse)