Thanks in advance for reading my thread. I am not very familiar with Unix so please bear with me if I say anything stupid.
I have a SunFire V100 server with Solaris 8, which I made into a Boot/Install/Profile server. Recently, I re-install the V100 box with Solaris 10.
The Solaris 10 installation had no errors. Same with the boot server installation. I retained the jumpstart directory ,/etc/hosts, and /etc/ethers from before the new installation (when it was still using Solaris 8).
I tried to jumpstart another V100 server with a Solaris 8 image. There were no errors during the entire process. However, when the jumpstarted server tried to boot after the jumpstart, the file system seems to be missing! It asks me to check file system manually, but it shows this error.
"Can't stat /dev/rdsk/c0t2d0s0".
The configuration for my network interfaces were also errored out.
"ifconfig: plumb: dmfe0: Bad file number."
If anyone have ANY idea as to how to fix this problem. Please tell me.
Solaris 8 is fairly old, while a V100 is a fairly new server. It is possible your jumpstart server has a older version of Sol 8 which doesn't have hardware support for a V100. I've run into that situation in the past. The fact it can't find your hard drive at all and doesn't recognize the network interface address makes me think that might be your situation too.
Sun releases HW support updates for their operating systems. You'll see them listed like "Solaris 8 HW 02/02" for the Feb. 2002 release. Make sure you have the most recent one and see if that fixes your problem. The newest we have for Solaris 8 is 02/04, but I'm not sure if there is a newer one than that available.
I will try to get an image with a newer version of Solaris, but I am not sure if it's actually a hardware support problem since I could perform the jumpstart when my jumpstart server is using Sol 8.
But when I upgraded the jumpstart server to Sol 10, it fails. Even though everything else stays constant. I am still jumpstarting the same box, and using the same image as before.
Oh, I misunderstood your problem. Solaris 10 should definately have hardware support for a V100 in it so it isn't that.
One other idea I have - I see it isn't finding c0t2d0s0. Is it possible that device address is incorrect? Most solaris boxes I've adminned have c0t0d0s0 as the root partition. I know some of the newest sun servers have their internal controllers for fibre-channel disks laid out differently though. I think I've seen one machine where it was c1t0d0s0 instead. So maybe that is the error here - your jumpstart server is getting the device address different from what the server thinks it is.
That stuff should be in your jumpstart directory. The class (a.k.a. profile) and rules files are where you would look to see if any of that stuff is wrong now that you upgraded to Sol 10 instead of Sol 8.
The other possibility is the hard drive has failed. But that wouldn't explain not being able to find the network interface. That is why I think the devices under /dev being messed up on your newly jumpstarted server is more likely.
boot in single user mode from the network ( boot net -s )
when the system is booted, mount the root disk on /mnt.
cd /mnt/etc and have a look at what you have in /mnt/etc/vfstab and compare that with you disk layout.
also ifconfig -a and check if your /mnt/etc/host and /mnt/etc/hostname.* corresponds.
I have a laptop and need to build an Oracle Linux kickstart server and a Solaris Jumpstart server that can build sparc and x86 systems.
Is the best way to create a dual boot from grub for Oracle Linux and Solaris x86?
Can the Oracle Kickstart be used as a Jumpstart to build both Solaris 10... (2 Replies)
I am performing this installation on a Sun T5220. There is an aftermarket Adaptec StorageTek raid controller card installed. I have created the raid array, and it is referred to as c1t0d0. Here is the profile I have created:
install_type
initial_install
system_type server
cluster SUNWCXall... (4 Replies)
Hello everyone,
I tried to install solaris 10 using the command # boot net - install.
I take the image correctly but when you start installing the Operating system installation takes a long (4 hours I have left and not advancing but not send me any errors), it can be seen from the following:
... (7 Replies)
Hi All
I have a Solaris 10 jumpstart boot/config server set up on a subnet, and am trying to use it to build a client (the only other machine on the network). Things start out just fine, with the client booting into the Solaris Installation program, but then it just coredumps just as it's... (4 Replies)
I need a little help figuring out why my custom jumpstart network installation is dumping me to a manual install.
I am trying to install Solaris 10 (unattended) over the wire from my jumpstart server to an HP Proliant DL380 server but I'm having difficulties with the unattended part.
So, what... (2 Replies)
Hi all ,
I am trying to jumpstart ( webstart) solaris 9 on E2900 ( client) using the DVD of a V440 server ( jumstart server). I did the setup for the V440 as follows :
cleaning up preexisting install client "XXXXXXX"
removing XXXXXXXfrom bootparams
removing /etc/bootparams, since it is... (14 Replies)
I just built a jumpstart server on a Solaris 9 sun box and have had no problems jumpstarting other sol9 boxes using the custom rules. I've also copied a Solaris 10 image onto that same solaris 9 server and have had problems loading Solaris 10. These boxes will go directly to the manual OS install... (5 Replies)
Hello All,
I use flar to install servers. I am not sure why it does not restore my hostname.bge0, hostname.bge1, ... from the same server with quad NIC card. Right now, I use a shell script to copy my networking information. Am I doing anything wrong or is flar behaving the way it is suppose... (1 Reply)
Hi,
I build a jumpstart server with a running dhcp server. I already managed to install a x86 client via network. But my sparc clients aren't still working.
When booting via network I get the following message:
Timeout waiting for ARP/RARP packet
I ran "snoop" on the server:
client2 ->... (1 Reply)