[SUMMARY}: panic message at boot

Hi Managers,

I'm sorry for the late summary.

Thanks very much for help from Tony Walsh, Jan-Olaf Droese, Ric Anderson,
Thomas Lester.

They gave me a couple of suggestions:
1. Not enough patching on my server. I have checked this out and that wasn't
the problem.
2. Try to use (instead of rsync) the dd command. I do not know why but the
dd command didn't work on my server (I could not perform remote copy using
dd)
3. The root partition to big (over 2GB). The format command listed exact
2GB, so I resized the root partition to 1.98GB, reinstall system and tried.
This step didn't help
4. One of the managers pointed out that I should use Disk Suite instead of
rsyncing.. I will follow that idea.

After all these steps I used the ufsdump (and ufsrestore) command. The disk
started working. ???!!!

Also I was told that the 36 GB (Seagate drives) are not really qualified to
be installed in an SS20.

Thanks,
My best regards,
Piotr Wolak


Piotr Wolak wrote:

> Hello Sun Managers,
>
> I have a problem with my SparcStation 20 and I could not find any
> answers on the Internet or on SunSolve.com.
>
> System: SparcStation 20
> 4 processors Ross-RT625
> 480 MB memory
> Solaris 5.7
>
> This machine has two internal disk (the same partition layout). One is
> the system disk and the second one I use as a mirror copy. I do rsync
> from the system disk to the mirror disk. The mirror disk (the same as
> the system disk) is the Seagate Cheetah ST 336705LC (36GB). One week ago
> I restarted my server to test the mirror disk and I could not boot my
> system up because of a boot block problems. I sent the disk to vendor.
> It came back today, so I put it back into my server. I did the rsync,
> install the bootblk file and tried to test it. During the boot process I
> keep getting the following message:
>
> -------------------
> Nov  3 18:06:53 yankees unix: SunOS Release 5.7 Version Generic [UNIX(R)
> System V Release 4.0]
> Nov  3 18:06:53 yankees unix: Copyright (c) 1983-1998, Sun Microsystems,
> Inc.
> Nov  3 18:06:53 yankees unix: panic: affinity_set: setting f02690c8 but
> already bound to 8090001d
> Nov  3 18:06:53 yankees unix: BAD TRAP: type=1 rp=f0243424 addr=ea260000
> mmu_fsr=166 rw=3
> Nov  3 18:06:53 yankees unix: : Text fault
> Nov  3 18:06:53 yankees unix: kernel read fault at addr=0xea260000,
> pme=0x0
> Nov  3 18:06:53 yankees unix: MMU sfsr=166: Invalid Address on supv
> instr fetch at level 1
> Nov  3 18:06:53 yankees unix: pte addr = 0xf59833a8, level = 1
> Nov  3 18:06:53 yankees unix: pid=0, pc=0xea260000, sp=0xf0243470,
> psr=0x1e800bc0, context=0
> Nov  3 18:06:53 yankees unix: g1-g7: e, 1, f009a86c, 0, 13b968, 1,
> f0244020
> Nov  3 18:06:53 yankees unix: Begin traceback... sp = f0243470
> Nov  3 18:06:53 yankees unix: Called from f005f394, fp=f02434d0,
> args=81e80000 1 0 10 3 f024361d
> Nov  3 18:06:53 yankees unix: Called from f0041b60, fp=f0243580, args=0
> f02435dc 14 326 f026f7f0 f026bfc8
> Nov  3 18:06:53 yankees unix: Called from f009a93c, fp=f0243628, args=0
> f02436d8 0 3 3 f024361c
> Nov  3 18:06:53 yankees unix: Called from f00a2668, fp=f0243690,
> args=f0123c88 f02437a8 0 3 0 0
> Nov  3 18:06:53 yankees unix: Called from f00568b8, fp=f02436f8, args=0
> 0 f0284c00 f0287884 0 f0286000
> Nov  3 18:06:53 yankees unix: Called from f00564fc, fp=f0243760, args=0
> 1e400ce7 0 1e4000e7 0 0
> Nov  3 18:06:53 yankees unix: Called from f0056444, fp=f02437c0, args=1
> f0243868 0 1e000ce7 0 0
> Nov  3 18:06:53 yankees unix: Called from f006c060, fp=f0243820,
> args=f007c5ec f02690c8 8090001d f0244108
> f026912c ea260000
> Nov  3 18:06:53 yankees unix: Called from f006c43c, fp=f0243880,
> args=f02690c8 1 10 f590d3c0 f026412c ea260000
> Nov  3 18:06:53 yankees unix: Called from f006dda0, fp=f02438e0, args=0
> f0268788 f0269108 0 0 f59105c0
> Nov  3 18:06:53 yankees unix: Called from f006da3c, fp=f02439a0, args=6e
> f026ff20 1 18 f02690c8 ea260000
> Nov  3 18:06:53 yankees unix: Called from f006dbf0, fp=f0243a00, args=63
> 6e 64 f0243a66 f025f744 ff00
> Nov  3 18:06:53 yankees unix: Called from f005ce68, fp=f0243a68,
> args=f025f7c0 f025f7c4 63 63 6 c00
> Nov  3 18:06:53 yankees unix: Called from f00ba8d4, fp=f0243af8,
> args=f026fc00 10000 2000 f025e000 f0268c00 0
> Nov  3 18:06:53 yankees unix: Called from f00411c4, fp=f0243b88,
> args=1e400fe0 1e400fe0 2000 1e4000e0 81c52000
> f0127bc4
> Nov  3 18:06:53 yankees unix: Called from 100a08, fp=0, args=14802c 2034
> 140000 0 1135b8 0
> Nov  3 18:06:53 yankees unix: End traceback...
> Nov  3 18:06:53 yankees unix: panic: Text fault
> ---------------------------
>
> I tested this disk on another SparcStation and I got the same error. The
> system disk is working fine (the same model).
> If you could give me any clues or suggestion what is wrong I would
> appreciate it.
>
> I have had many problems with this kind of Seagate disks on my Sun
> servers (SparcStations 20). I do not know why. Does anyone of you use
> them ? Any reflections ?
>
> I will summarize.
>
> Thanks very much for your help !
> My best regards,
> Piotr
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers