(Fwd) SUMMARY: diskhangup - fsck errors and sense key error

From: Paul Harren (egk9@gdeb.com)
Date: Fri Apr 19 1996 - 06:50:25 CDT


--- Forwarded mail from sun-managers-relay@ra.mcs.anl.gov

From: heo@cslsun10.sogang.ac.kr (Heo Sung Gwan)
Reply-To: heo@cslsun10.sogang.ac.kr (Heo Sung Gwan)
Subject: SUMMARY: diskhangup - fsck errors and sense key error
To: sun-managers@ra.mcs.anl.gov
Date: Fri, 19 Apr 1996 14:52:16 +0900 (KST)

Hi,

Thanks to the following, who responded to my question:
 kdoss@cvimail.CV.COM(Kennedy Doss)
 sweh@mpn.com(Stephen Harris)
 staggsd@SEOUL-FKJ3.KOREA.ARMY.MIL(David Staggs)
 bbyoung@amoco.com(Brad Young)
 kwthomas@wizard.nssl.uoknor.edu(Kevin W. Thomas)

 Most of them suggested that I rescan for bad blocks, reformat,
recreate the filesystem, and restore the files. And they indicated that
I prepare to buy a new disk.
 But still I don't know exactly what the sense key error is and
why the sense key error occurs. Some said that the cause may be SCSI cable
and termination.

After recoverying the filesystem I ran sundiag during one day.
No error was detected. But I am anxious about my disk. If someday morning
I find the filesystem corrupted, I will have to reformat, recreate
the filesystem, etc ...

My original message was:

>I have serious problem on internal disks. I have 4 disks on a SPARKstation 20
running SunOS 4.1.3_U1 :
> sd0(internal)
> sd1(external)
> * sd2(internal) - h and g 2 partitions
> sd3(external)

>Yesterday I found the system down. The system was in PROM monitor mode(ok
prompt) with bootblock error message. So I boot the machine from cd-rom and
repair bootblock of sd0 with installboot command.
>
>But while rebooting, the system fell into single user mode with fsck errors on
sd2, including superblock error message on sd2g. First I ran 'fsck -b 32'(the
block 32 is an always alternate superblock - from manpage of fsck). It seemed
succeeded. Then I ran fsck on sd2g and sd2h. But I got a lot of errors on
blocks and inodes. After several fscks, still I get the following errors from
fsck :
>
>** /dev/rsd2g
>** Last Mounted on /user3
>** Phase 1 - Check Blocks and Sizes
>16781880 BAD I=200
>16832397 BAD I=24586
>16842495 BAD I=24604
>16842453 BAD I=24615
>16832677 BAD I=24726
>69611 DUP I=32771
>69615 DUP I=32776
>71040 DUP I=32801
>78320 DUP I=32824
>78285 DUP I=32863
>71168 DUP I=32872
>72136 DUP I=32894
>...
>
>EXCESSIVE DUP BLKS I=368767
>CONTINUE? y
>785904 DUP I=368777
>785800 DUP I=368804
>786288 DUP I=368805
>785780 DUP I=368806
>785700 DUP I=368827
>785726 DUP I=368857
>17564288 BAD I=369011
>...
>
>** Phase 2 - Check Pathnames
>DIRECTORY CORRUPTED I=24631 OWNER=w931102 MODE=40750
>SIZE=1024 MTIME=Apr 2 10:07 1996
>DIR=?
>
>SALVAGE? y
>
>Segmentation fault (core dumped)
>
>
>
>In /var/adm/message files there are the errors on sd0 and sd0g(/user3) :
>
>Apr 13 08:57:23 csltoy2 vmunix: sd0g: Error for command 'write'
>Apr 13 08:57:23 csltoy2 vmunix: sd0g: Error Level: Retryable
>Apr 13 08:57:23 csltoy2 vmunix: sd0g: Block 16, Absolute Block: 604816
>Apr 13 08:57:23 csltoy2 vmunix: sd0g: Sense Key: Aborted Command
>Apr 13 08:57:23 csltoy2 vmunix: sd0g: Vendor 'CONNER' error code: 0x47
>Apr 13 08:57:46 csltoy2 vmunix: r code: 0x47
>...(repeated)
>Apr 13 12:06:11 csltoy2 vmunix: esp0: SCSI bus DATA IN phase parity error
>Apr 13 12:06:11 csltoy2 vmunix: sd0a: Error for command 'read'
>Apr 13 12:06:11 csltoy2 vmunix: sd0a: Error Level: Retryable
>Apr 13 12:06:11 csltoy2 vmunix: sd0a: Block 16272, Absolute Block: 16272
>Apr 13 12:06:11 csltoy2 vmunix: sd0a: Sense Key: Aborted Command
>Apr 13 12:06:11 csltoy2 vmunix: sd0a: Vendor 'CONNER' error code: 0x48
>...(repeated)
>Apr 13 14:40:23 csltoy2 vmunix: bad block 16968783, <3>/user3: bad block
>Apr 13 14:40:23 csltoy2 vmunix: bad block 16968783, ino 90293
>Apr 13 14:40:26 csltoy2 vmunix: bad block 16877629, <3>/user3: bad block
>Apr 13 14:40:26 csltoy2 vmunix: bad block 16877629, ino 40989
>Apr 13 14:40:27 csltoy2 vmunix: bad block 16900959, <3>/user3: bad block
>Apr 13 14:40:27 csltoy2 vmunix: bad block 16900959, ino 57455
>Apr 13 14:43:19 csltoy2 vmunix: dev = 0x716, block = 2936, fs = /user3
>Apr 13 14:43:19 csltoy2 vmunix: panic on cpu 0: free: freeing free frag
>Apr 13 14:43:19 csltoy2 vmunix: syncing file systems... panic on cpu 0: zero
>Apr 13 14:43:19 csltoy2 vmunix: 01354 low-memory static kernel pages
>Apr 13 14:43:19 csltoy2 vmunix: 00748 additional static and sysmap kernel
pages
>Apr 13 14:43:19 csltoy2 vmunix: SuperSPARC/SuperCache: PAC ENABLED
>Apr 13 14:43:19 csltoy2 vmunix: SunOS Release 4.1.3_U1-KLE1.1.3_U1
(GENERIC_KOR)
> #1: Mon Feb 5 14:14:10 KST 1996
>Apr 13 14:43:19 csltoy2 vmunix: Copyright (c) 1983-1993, Sun Microsystems,
Inc.
>...(booting messeges)
>
>What is the error messages ?
>What is problem? Hardware problem?
>How can I recovery our disk ?
>
>Help me please.

Heo

---
//////////////////////////////////////////////////////////////////////////////
      /     /   _____/   ____  / Heo Sung-Gwan
     /     /   /        /     /  Dept. of Computer Science, Sogang University,
    ____  /   _____/   /     /   Seoul, Korea.
   /     /   /        /     /
__/   __/  _______/ _______/     E-mail: heo@cslsun10.sogang.ac.kr
///////////////////////////////////////////////////////////////////////////////

---End of forwarded mail from sun-managers-relay@ra.mcs.anl.gov

I received this email message today which is not addressed to me. I do not know why; however, since it is addressed to you, I am forwarding it in case you did not get a copy from the sender.

-- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% Paul A. Harren %% %% Electric Boat Corporation %% %% 75 Eastern Point Rd %% %% Groton, CT %% %% (860) 433-3465 %% %% pharren@gdeb.com %% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:58 CDT