Jumpstart problem

[dandan123]

I'm having a problem jumpstarting a server.

I get this on the server being jumpstarted -

Timeout waiting for ARP/RARP packet


And on the jumpstart server using snoop -

OLD-BROADCAST -> (broadcast) RARP C Who is 0:3:ba:3f:6d:ff ?

I've jumpstarted several servers using the same network connection.


Where do you think the problem could be ?

 

[dandan123]

It was an error in the /etc/hosts file.

 

[dandan123]

Still not out of the woods, I now get this error -

ERROR: Field 2 - Disk is not valid on this system (c0t0d0s0)

I'm using a 36GB disk on a V240

Any ideas ?

 

[maximusGeek]

Is c0t0d0s0 a valid disk? I dont have any v240s but I know that some systems will start with c1t1d0s0 or something else.

Ctrl C out of the installer and do a format

 

[christos]

check your profile and rules
looks like it may be tring to find c1t..... and c0t...... in steed of c0t1..... c0t2...... for mirroring
this happens when you use rule/profile from say an older E420R on a V240 etc where there is 1 scsi bus with muli targets not 2 (say) targets on 2 busses

 

[coffeysm]

It is probably an error in your rules file like someone stated. Change your profiles to read something like this:

rootdisk.sX (Where X = Slice Number.)

 

[cndcadams]

as coffesm point out rootdisk.sX (Where X = Slice Number.)

this is an example of one of my profiles


# more any_machine
install_type initial_install
system_type standalone
partitioning explicit
cluster SUNWCXall
filesys rootdisk.s0 6000 /
filesys rootdisk.s1 3024 swap
filesys rootdisk.s5 6000 /usr
filesys rootdisk.s6 free /export/home

thanks

ca

 

[dandan123]

The profile file was set up for c0t0 while on the system it was c1t0, funny thing though I've used this profile on other V240's so I guess some are c0t0 and some c1t0 ? Could it be due to this system have a CD drive while the others didn't ?

I'll have to look into that.

Thanks for all your help.

 

[cndcadams]

dandan123;

that is exactly what the issue is. The cdrom takes over contoller 0 and the internal disk drives end up on controller 1. I have delt with this issue myself.

Thanks

CA