SUMMARY: Nonrecoverable Medium Error when booting and CAM_ERROR p acket

From: Huang, Yihan <yihan.huang_at_ntu.ac.uk>
Date: Fri, 21 Jan 2000 14:28:29 +0000

Thanks to all who responded:

        Joe Fletcher [joe_at_meng.ucl.ac.uk]
        alan_at_nabeth.cxo.dec.com
        John J. Francini [francini_at_progress.com]
        Stan Horwitz [stan_at_astro.ocis.temple.edu]
        Ralph Wegner [wegner_at_hst.rwth-aachen.de]
        Nikola Milutinovic [Nikola.Milutinovic_at_ev.co.yu]

My question is present below as a attachment. Some suggested
        'CAM_ERROR usually means SCSI channel problem or the unit's
electronic is
        gone. Check your cable and especially your termination, if you have
one.'

I did check them. They all fine.

John Francini suggested:
         'to bring the system up single-user, mount the partition read-only
        (and ignore the needs-fsck status) using mount -r -d, and do your
        dump. It's possible that one or more directories may not be
        readable, but you should be able to dump most of the disk.
        Then replace the drive and restore from the dump you just made.'

I thought this might be a good idea. However, when I did mount -r -d to /mnt
and then tried to dump, the following error messages were displayed:

>dump: Bad file system specification or bad file system. The raw device must
be entered when >the file system's pathname has not been entered in the
fstab file. A bad file system is >reported when the the magic number is not
found in the super block.
>
>dump: The entire dump is aborted.

Therefore, the data is simply lost.

        ------------------------------------------
> I have a DEC AlphaStation 200 that is running Digital Unix 4.0B. Two
> installed RZ28D disk drives have the SCSI Nos. 0 and 1, respectively. A
> very serious problem happened when booting. The following ERROR messages
> appear during automatic booting:
>
> Checking local filesystem:
> .....
>
> Hard Error Detected
> DEC RZ28D (C) DEC RZ28D
> Active CCB at time of error
> CCB request completed with an error
> Error, exception, or abnormal condition
> MEDIUM ERROR - Nonrecoverable medium error
> /dev/rrz1g: CANNOT READ: BLK 3219168
> /dev/rrz1g: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>
> THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
>
> /dev/rrz1g (/usr/users)
>
> Automatic reboot failed. Run fsck manually.
> Repair filesystem(s), then reboot (/sbin/reboot)
>
> When I run fsck in single-user mode, the following messages displayed many
> times:
>
> Cam_logger: CAM_ERROR packet
> Cam_logger: bus 0 target 1 lun 0
> Cdisk_complete
> Retries Exhausted
> ......
> ......
>
> CANNOT READ: BLK 3219168
> CONTINUE ? [yn]
>
> When I enter 'y', it continued to display with
>
> The following DISK SECTORS can not be read
> ......
>
> Unfortunately all users data are stored in this partition. And this
> happened just I wanted to start to dump for backup.
>
> WHAT's the PROBLEM and how can I fix it? Do I lose all the data? I checked
> all the cables and connections, and when I do >>>show device, both drivers
> there.
>
>
>
Received on Fri Jan 21 2000 - 14:33:35 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:40 NZDT