Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Jumpstart problem

Status
Not open for further replies.

ponetguy2

MIS
Aug 28, 2002
442
US
Hello Everyone,

I am new to Jumpstart and I'm trying to build a box w/ Solaris 8. I do not manage the Jumpstart server, someone else does. I was instructed to run a script on the boot/jumpstart server and enter the appropriate entries. So I did. The client was able to boot and all seems well until the system started rebooting over and over again. Any advise will be appreciated.

Here is the prompt on the screen during the reboot process:

(I Xed out the hostname, MAC, and Serial for security purposes)

screen not found.
keyboard not found.
Keyboard not present. Using ttya for input and output.


Sun Fire 280R (2 X UltraSPARC-III+) , No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.5, 4096 MB memory installed, Serial #xxxxxxx.
Ethernet address x:x:xx:x:xx:xx, Host ID: xxxxxx.



Rebooting with command: boot
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w21000004cf725f79,0:a File and args:
SunOS Release 5.8 Version Generic_117350-41 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
configuring IPv4 interfaces: eri0.
Hostname: hostname
metainit: hostname: there are no existing databases

The / file system (/dev/rdsk/c1t0d0s0) is being checked.
/dev/rdsk/c1t0d0s0: INCORRECT DISK BLOCK COUNT I=17266 (12 should be 0) (CORRECTED)
/dev/rdsk/c1t0d0s0: UNREF FILE I=17266 OWNER=root MODE=100444
/dev/rdsk/c1t0d0s0: SIZE=0 MTIME=Jan 23 05:51 2007 (CLEARED)

/dev/rdsk/c1t0d0s0: CORRECT GLOBAL SUMMARY/dev/rdsk/c1t0d0s0: 45385 files, 1111363 used, 3017927 free (2903 frags, 376878 blocks, 0.1% fragmentation)

***** FILE SYSTEM WAS MODIFIED *****
Configuring /dev and /devices

panic[cpu1]/thread=2a1000f7d20: BAD TRAP: type=31 rp=2a1000f7400 addr=e800000018 mmu_fsr=0

sched: trap type = 0x31
addr=0xe800000018
pid=0, pc=0x781ccd5c, sp=0x2a1000f6ca1, tstate=0x480001607, context=0x0
g1-g7: 726ff1, 30000118010, 0, 0, 2a1000f72fc, 0, 2a1000f7d20

000002a1000f7010 unix:die+a4 (31, 2a1000f7400, e800000018, 0, 2a1000f7400, c4022018)
%l0-3: 0000000000000004 000000001022ec94 0000000000000000 000000007fffffff
%l4-7: 00000000000000d5 000002a1000f729c 0000000000000000 0000000000000000
000002a1000f70f0 unix:trap+900 (e800000000, 1, 5, 0, 2a1000f7400, 0)
%l0-3: 0000000000000001 000000001022ec94 00000000104245b0 0000000000000000
%l4-7: 0000000000000031 0000000000000000 0000000000010200 0000000000000001
000002a1000f7230 unix:sfmmu_tsb_miss+66c (104293b0, 0, 30000147f88, 0, 30000147f88, 19)
%l0-3: 000000e800000000 0000000000000004 0000000000000000 00000310001bf100
%l4-7: 000000e800000000 000002a1000f762c 0000000000000000 000000e800000003
000002a1000f7350 unix:prom_rtt+0 (e800000000, cf726ff100000000, ffffffffffffffff, 8, 300025c4140, 1)
%l0-3: 0000000000000000 0000000000001400 0000000480001607 000000001001a8e0
%l4-7: 0000000000000000 0000000000000002 0000000000000000 000002a1000f7400
000002a1000f74a0 fcip:fcip_rt_update+184 (30000144008, 781ccba0, 300001e7028, 300001e7000, 0, 30000144100)
%l0-3: 00000300025c4148 00000300001e7000 ffffffffffffffff 0000000000000002
%l4-7: 00000300000902a8 0000030000144008 0000000000000000 00000300025c4140
000002a1000f7570 fcip:fcip_handle_topology+9c (300001e7000, 23b8, 30000144008, 300000902a8, 300000902a8, 3000231b800)
%l0-3: 000000001043a678 0000000000000018 000003000231bb80 0000000000000008
%l4-7: ffffffffffffffff 0000000000000002 0000000000000000 0000000000000000
000002a1000f7630 fcip:fcip_init_port+1d8 (78125800, 30000144040, 30000144008, 1e0, 300000902a8, ffffffffffffffff)
%l0-3: 0000000078125d18 00000000101180f4 0000000000000000 0000000000000000
%l4-7: 0000000000000000 00000000104245b0 0000030001cd95c0 0000030002691330
000002a1000f7700 fcip:fcip_port_attach_handler+84 (78125800, 78125d60, 30000144008, 300000902a8, 2, 2a1004b1d20)
%l0-3: 0000000010044c80 00000000781ce90c 0000000000004000 0000000000000000
%l4-7: 0000000000000000 00000000104245b0 0000030001cd99c0 0000000000000000
000002a1000f77b0 fcip:fcip_port_attach+504 (30000144260, 30000144040, 30000144008, 1, 0, 78125ae0)
%l0-3: 000002a1000f7938 0000000000000000 00000300000902a8 000003000106de18
%l4-7: 0000030000f65f28 000002a1002299a0 0000030002371a70 0000000000000000
000002a1000f7880 fctl:fctl_attach_ulps+1b4 (300003721f8, 300003721e8, 300003721e8, 3000258b020, 3000108d000, 0)
%l0-3: 00000000781cc2cc 0000000000000001 0000000000000001 000002a1000f1d20
%l4-7: 0000000000000000 0000000000000000 0000000000000000 000000007fffffff
000002a1000f7990 fp:fp_ulp_port_attach+14 (300025871c8, 1, 20, 1, 0, 0)
%l0-3: 0000030000027780 0000000010046d94 0000000000000000 0000000000000000
%l4-7: 0000000000000000 00000000104245b0 0000030000f61748 0000000000000002
000002a1000f7a40 genunix:taskq_thread+18c (30000f5fc28, 0, 104245b0, 10000, 30000f5fc5a, 30000f5fc80)
%l0-3: 000000001024f610 0000030000f5fc58 0000030000f5fc50 0000030000f5fc28
%l4-7: 0000030000f5fc48 00000300010a3308 000000000000001a 0000000000000001

syncing file systems... done
dumping to /dev/dsk/c1t0d0s1, offset 429588480
100% done: 26457 pages dumped, compression ratio 9.09, dump succeeded
rebooting...
Resetting ...


"Not all OSs suck, it's just that some OSs suck worse than others"


 
I noticed you have Disksuite was this a flash image or does that get installed separately. It also looks like a CPU paniced or something. I would try a boot net -s and fsck the hard drive then see if it boots again. The other possiblility is maybe the installation did not complete successfully.
 
Thank you for the reply coffeysm. I will try your suggestion tonight.

The message which caught my eye is this:

metainit: hostname: there are no existing databases

Maybe it is the flash image that caused the problem. Please forgive me, but as I said, I don't know Jumpstart that well. I don't even know where to troubleshoot the flash image. :(

"Not all OSs suck, it's just that some OSs suck worse than others"


 
I did a boot net -s and I am unable to fsck -y. From single user mode, I also tried to do a init 3. The result of init 3, took me to an installation prompt.



"Not all OSs suck, it's just that some OSs suck worse than others"


 
Well the metainit command just means that there are not metadb databases. If it is indeed a flash image from a system that had SDS configured it probably still has entries for the metadevices or something. You also need to specify the drive partition when you are in single user mode.

Code:
boot net -s
fsck -y /dev/rdsk/cWtXdYsZ
mount /dev/dsk/cWtXdYsZ /mnt

The files to check for meta device info are:
/etc/system - Put an * in front of these lines.
forceload: misc/md_trans
forceload: misc/md_raid
forceload: misc/md_hotspares
forceload: misc/md_sp
forceload: misc/md_stripe
forceload: misc/md_mirror
rootdev: some data here
set md:mddb_bootlist=some data here

/etc/lvm/md.cf - Delete it or rename it
/etc/lvm/md.tab - Delete it or rename it
/etc/lvm/mddb.cf - Delete it or rename it

/etc/vfstab - Check for any /dev/md/dsk or /dev/md/rdsk entries
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top