lkml.org 
[lkml]   [1999]   [May]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: sym/ncr53c8xx phase error still present in 2.2.7

    This all sounds like the problem I had with 2.0.3x (x=2 or 3). I have
    read several reports of this error. The earliest error was apparently
    with 2.0.18.

    The 53c7,8xx Driver reports:

    scsi0 : WARNING : INTFLY with no completed commands.

    just before corrupting the disk. The BSD port always tells something
    like:

    ncr53c810-0-<target 0, lun 0>: phase change 2-3 6@00fff828 resid=2.
    ncr53c810-0-<target 0, lun 0>: phase change 2-7 10@00fff62c resid=4.

    These are the corrupted disk types I'm aware of:

    IBM DPES-31080
    IBM DCAS-34330 Rev: S65A
    IBM DORS
    1.2 Gbyte HP SCSI

    mostly but not exclusively IBM drives.

    One report states it happend often while copying data to the 4th
    partition of the harddisk using mtools. This indicates that it's not
    directly the filesystem codes fault.

    In the following example the DOS partition got overwritten:

    Disk /dev/sda: 134 heads, 62 sectors, 1019 cylinders
    Units = cylinders of 8308 * 512 bytes

    Device Boot Start End Blocks Id System
    /dev/sda1 1 370 1536949 6 DOS 16-bit >=32M
    /dev/sda2 371 402 132928 82 Linux swap
    /dev/sda3 * 403 1019 2563018 83 Linux native

    22:19:41 kernel: ncr53c875-0-<0,0>: phase change 2-3 6@00009845 resid=2.
    22:19:41 kernel: ncr53c875-0-<0,0>: phase change 2-7 10@00009e45 resid=4.
    22:19:41 kernel: ncr53c875-0-<0,0>: phase change 2-7 10@00009a45 resid=4.
    22:19:44 kernel: led
    22:19:44 kernel: attempt to access beyond end of device
    22:19:44 kernel: 08:01: rw=0, want=2075433, limit=1536949
    22:19:44 kernel: Directory sread (sector 0x3f5651) failed
    22:19:44 kernel: attempt to access beyond end of device
    22:19:44 kernel: 08:01: rw=0, want=2075433, limit=1536949
    22:19:44 kernel: Directory sread (sector 0x3f5651) failed

    The limit seems to be ok here.


    Another user was able to start fdisk after the corruption. He told me
    the extended partitions were set to zero while the primary partitions
    looked Ok. After reboot the extended partitions were back again and
    just the first partition was corrupted.


    HTH

    Peter
    --
    _ x ___
    / \_/_\_ /,--' p.steiner@t-online.de (Peter Steiner)
    \/>'~~~~//
    \_____/ signature V0.2 alpha

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:51    [W:0.019 / U:31.152 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site