Netra Bad Magic number in disk label
Hi
The company i'm working for has a Netra which it acquired a while back. I was given the task of installing Solaris 10 on this box. When i brought the box online and connected through the LOM port, i tried to "boot disk" to which i got the error "Bad magic number in disk label" and "Can't open disk label package","Can't open boot device".
I'm assuming that if i could get to the "#" prompt, i could do a format - label but problem is, i can't get to that prompt from typing "console" at the LOM prompt.
Any ideas how i could go about this?
Thanks,
Charles
# 1
If the internal disk doesn't boot, then you're going to have to boot from other media, such as a CD/DVD, or the network after setting up a boot server.The '#' prompt is indicative of a running OS. -- Darren
# 2
The problem is though that there's no CD-ROM on that Netra and i don't think i can do a boot - net because there are no entries in the ethers and hosts files and that's the only way at the moment that i could do "net connectivity".Thanks,Charles
# 3
> The problem is though that there's no CD-ROM on that
> Netra and i don't think i can do a boot - net because
> there are no entries in the ethers and hosts files
> and that's the only way at the moment that i could do
> "net connectivity".
You'd have to create the entries.
If you already have a boot server, then you go to the installed image and cd into Tools. In there run
'./setup-install-client -e <etheraddress> hostname sun4u'
That'll set up the basics on the server to netboot the netra (assuming the image you have on the server supports the hardware).
From there, do a 'boot net -s' and it shold boot to a single-user prompt from the network. Either that or 'boot net' and actuallly re-install.
# 4
the setup_install_server command doesn't support the "-e" parameter but the add_install_client does. However, when i'd do ./add_install_client -e ethernet_address hostname sun4u, i'd get unknown client on hostname which was the client's hostname. That hostname is specified in my ethers file so not sure what's going on there right now.
Thanks,
Charles
# 5
> the setup_install_server command doesn't support the
> "-e" parameter but the add_install_client does.
Yup. brain cramp. add_install_client is correct.
> However, when i'd do ./add_install_client -e
> ethernet_address hostname sun4u, i'd get unknown
> client on hostname which was the client's hostname.
Does the jumpstart server resolve that name? Add it to /etc/hosts if it doesn't.
--
Darren
# 6
The thing is, that box doesn't have an IP address as far as i know. I should be able to use Jumpstart with only the ethernet address right? I just don't know how to get the Jumstartt server to resolve only an ethernet address.Thanks,Charles
# 7
No. You have to assign it an IP.
When it starts up, the jumpstart server hands it an IP address so it can come up on the network and transfer the files.
So if there's no IP for the host that the jumpstart server can resolve, it doesn't know what to tell it to use.
(This isn't quite true if you're doing a DHCP boot, but that's a little more work to get into place).
Can you get an IP for the client? You only need it during the jumpstart and can change it later.
--
Darren
# 8
That's too bad that i need an IP. I don't think that machine has an IP assigned and if it does, i don't know it. Furthermore, because of that "Bad magic number" message, i can't boot from disk and get to the console or do LOM>console (doesn't seem to work) so as this point, i'm really not sure what to do.
I'm wondering if i took out the card where the ethernet address and other info is saved if i'd get any farther, anything to enable me to get to the console and at least label the disk to get one error out of the way.
Thanks for the ideas,
Charles
# 9
> That's too bad that i need an IP. I don't think that
> machine has an IP assigned and if it does, i don't
> know it.
You don't need to give it the same one it had before (if any). It just needs any valid IP while it's booted from the network so it can talk to the jumpstart server.It should be on the same subnet as the jumpstart server to make things easy.
> Furthermore, because of that "Bad magic
> number" message, i can't boot from disk and get to
> the console or do LOM>console (doesn't seem to work)
> so as this point, i'm really not sure what to do.
Your options remain the same: Install a bootable disk, attach a CD/DVD drive and boot from media, create a jumpstart server and boot from network.
Getting a temporary IP for a netboot seems a minor hurdle.
> I'm wondering if i took out the card where the
> ethernet address and other info is saved if i'd get
> any farther, anything to enable me to get to the
> console and at least label the disk to get one error
> out of the way.
If you can see the 'OK' prompt and type 'boot disk' (where it errors), then you're *on* the console.
As said before, you must boot to an OS before you can label and/or install onto a disk.
--
Darren
# 10
Bad magic number normally caused by bad CDs. I had this problem before.. When burning CDs, make sure do not use drag and drop. Create the ISO CDs by using one of the burning software. In my case, I right-click on the ISO file and click at 'Record to CD', the window takes the default burning software (Easy Creator 5, in my case) and CDs work fine when install. Hope this help.
Ben
BenLe at 2007-7-6 22:12:41 >
# 11
> Bad magic number normally caused by bad CDs.The OP doesn't have a CD. He's getting that from the hard drive boot.-- Darren
