Prev: Cannot boot x4200 via dhcp (from another x4200)
Next: Solaris 10 tape drive permission issues...
From: simoninusa2001 on 24 Feb 2007 08:09
I've just bought a Netra T1 105 and as it has no CD-ROM, I want to
Jumpstart it.

I've tried setting up a Jumpstart server using Linux (Fedora5) and
also from a Solaris 10 11/06 x86 VMWare instance, and both time the
"boot net - install" fails at the same point, with a "38e00 |" prompt,
here's the LOM output (serial/mac/hostid removed):

lom>
LOM event: power on
..
Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard
OpenBoot 3.10.27 ME, 1024 MB memory installed, Serial xxxxxx.
Ethernet address xxxxxx, Host ID: xxxxxx.

Drive not ready
Boot device: sec-disk File and args:
Drive not ready
Evaluating: boot

Can't open boot device

ok boot net - install
Boot device: /pci(a)1f,0/pci@1,1/network@1,1 File and args: - install
38e00 |

Swapping out the drives from a D130 makes no difference, other than
the "drive not ready" bit from LOM gets replaced with:

"Boot device: pri-disk File and args:
:217: The file just loaded does not appear to be executable."

add_install_client seems to have worked properly (on Solaris/VMWare)
and creates pretty much the same bootparams/dfstab/ethers/hosts/
tftpboot entries as the Linux tutorials. It couldn't find adb, but the
IP addresses all are fine. setup_install_server worked fine too.

I've tried using sun4u and SUNW,UltraSPARC-IIi-Engine as the platform,
no difference there.

>From the output of tcpdump and the server's console, it would seem
that the Netra is getting an IP (I can ping it) from rarpd and /etc/
ethers, and a boot image from /tftpboot, but then it just seems to sit
there when it gets to the NFS bit, here's some of the dump:

20:00:51.969246 IP 192.168.0.79.nfs > netra.157583: reply ok 80
getattr
20:00:51.969407 IP 192.168.0.79.nfs > netra.33685760: reply ok 1448
20:00:51.969519 IP 192.168.0.79.nfs > netra.0: reply ok 1448
20:00:51.969618 IP 192.168.0.79.nfs > netra.0: reply ok 1448
20:00:51.969689 IP 192.168.0.79.nfs > netra.978: reply ERR 1448
20:00:51.969757 IP 192.168.0.79.nfs > netra.1345: reply ERR 1448
20:00:51.969828 IP 192.168.0.79.nfs > netra.0: reply ERR 952
20:00:51.969831 IP 192.168.0.79.nfs > netra.0: reply ERR 952
20:00:51.985618 IP netra.0 > 192.168.0.79.nfs: 0 proc-1888936968
20:00:52.793511 IP 192.168.0.79.nfs > netra.33685760: reply ok 1448

I can mount the NFS shares/tftp from Linux OK (except for Linux's
broken NFSv4 of course!)

The bootparam/rarp/nfs/tftp services are all running according to svcs

Can anyone help (or do you need more info?) as I have about a week to
get this box co-located before my other web hosting contract runs out,
so could do with getting on with securing the OS, not mucking around
trying to install it!

Cheers ;-)

From: Casper H.S. Dik on 24 Feb 2007 09:20
simoninusa2001(a)yahoo.co.uk writes:

>ok boot net - install
>Boot device: /pci(a)1f,0/pci@1,1/network@1,1 File and args: - install
>38e00 |

This message indicates it download all (or most?) of the tftp boot
file. Was it the correct file? Check the boot server.

>add_install_client seems to have worked properly (on Solaris/VMWare)
>and creates pretty much the same bootparams/dfstab/ethers/hosts/
>tftpboot entries as the Linux tutorials. It couldn't find adb, but the
>IP addresses all are fine. setup_install_server worked fine too.

What worked appeared to be RARP and tftpboot; now it will try
RARP again.


>I've tried using sun4u and SUNW,UltraSPARC-IIi-Engine as the platform,
>no difference there.

>>From the output of tcpdump and the server's console, it would seem
>that the Netra is getting an IP (I can ping it) from rarpd and /etc/
>ethers, and a boot image from /tftpboot, but then it just seems to sit
>there when it gets to the NFS bit, here's some of the dump:

>20:00:51.969246 IP 192.168.0.79.nfs > netra.157583: reply ok 80
>getattr
>20:00:51.969407 IP 192.168.0.79.nfs > netra.33685760: reply ok 1448
>20:00:51.969519 IP 192.168.0.79.nfs > netra.0: reply ok 1448
>20:00:51.969618 IP 192.168.0.79.nfs > netra.0: reply ok 1448
>20:00:51.969689 IP 192.168.0.79.nfs > netra.978: reply ERR 1448
>20:00:51.969757 IP 192.168.0.79.nfs > netra.1345: reply ERR 1448
>20:00:51.969828 IP 192.168.0.79.nfs > netra.0: reply ERR 952
>20:00:51.969831 IP 192.168.0.79.nfs > netra.0: reply ERR 952
>20:00:51.985618 IP netra.0 > 192.168.0.79.nfs: 0 proc-1888936968
>20:00:52.793511 IP 192.168.0.79.nfs > netra.33685760: reply ok 1448

>I can mount the NFS shares/tftp from Linux OK (except for Linux's
>broken NFSv4 of course!)

Is it shared with "norootsquash" or whatever the name of the option
is which allows for root access?

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
From: simoninusa2001 on 24 Feb 2007 10:52
On 24 Feb, 15:20, Casper H.S. Dik <Casper....(a)Sun.COM> wrote:

> >ok boot net - install
> >Boot device: /pci(a)1f,0/pci@1,1/network@1,1 File and args: - install
> >38e00 |

> This message indicates it download all (or most?) of the tftp boot
> file. Was it the correct file? Check the boot server.

How do I check the boot server - you mean for a log or something? The
LOM had a kind of counter going until it got to 38e00, I guess that's
download progress, lots of UDP traffic in the tcpdump.

The hex version of the IP address and the symlinks created by
add_install_client seem OK, and you can't go wrong with the sun4u
platform:

bash-3.00# ls -l /tftpboot/
total 454
lrwxrwxrwx 1 root root 27 Feb 24 11:31 C0A80008 ->
inetboot.SUN4U.Solaris_10-1
lrwxrwxrwx 1 root root 27 Feb 24 11:31 C0A80008.SUN4U -
> inetboot.SUN4U.Solaris_10-1
-rwxr-xr-x 1 root root 216680 Feb 24 11:31
inetboot.SUN4U.Solaris_10-1
-rw-r--r-- 1 root root 318 Feb 24 11:31 rm.192.168.0.8

[snip]
> What worked appeared to be RARP and tftpboot; now it will try
> RARP again.

[snip]
> Is it shared with "norootsquash" or whatever the name of the option
> is which allows for root access?

When I try no_root_squash the NFS server won't start on Solaris (think
its a Linux-ism) and I get the following from LOM:

ok boot net - install
Boot device: /pci(a)1f,0/pci@1,1/network@1,1 File and args: - install
38e00 panic - boot: Could not mount filesystem.
Program terminated
ok

I don't get the error when it's setup like the following, so I guess
this is okay, anon=0 is also a root access flag:

bash-3.00# more /etc/dfs/dfstab
share -F nfs -o ro,anon=0 /export/home/jumpstart/install
share -F nfs -o ro,anon=0 /export/home/jumpstart/config

What is it supposed to do after the 38e00 bit - kick off the installer
(language selection etc)?

From: Bruce Porter on 24 Feb 2007 11:39
On Sat, 24 Feb 2007 07:52:20 -0800, simoninusa200 wrote:

> On 24 Feb, 15:20, Casper H.S. Dik <Casper....(a)Sun.COM> wrote:
>
>> >ok boot net - install
>> >Boot device: /pci(a)1f,0/pci@1,1/network@1,1 File and args: - install
>> >38e00 |
>
>> This message indicates it download all (or most?) of the tftp boot file.
>> Was it the correct file? Check the boot server.
>
> How do I check the boot server - you mean for a log or something? The LOM
> had a kind of counter going until it got to 38e00, I guess that's download
> progress, lots of UDP traffic in the tcpdump.

Check your /etc/bootparams file to see if the settings are correct / as
expected


You could also try snooping and see what point it stops at

>
> The hex version of the IP address and the symlinks created by
> add_install_client seem OK, and you can't go wrong with the sun4u
> platform:
>
> bash-3.00# ls -l /tftpboot/
> total 454
> lrwxrwxrwx 1 root root 27 Feb 24 11:31 C0A80008 ->
> inetboot.SUN4U.Solaris_10-1
> lrwxrwxrwx 1 root root 27 Feb 24 11:31 C0A80008.SUN4U -
>> inetboot.SUN4U.Solaris_10-1
> -rwxr-xr-x 1 root root 216680 Feb 24 11:31
> inetboot.SUN4U.Solaris_10-1
> -rw-r--r-- 1 root root 318 Feb 24 11:31 rm.192.168.0.8
>
> [snip]
>> What worked appeared to be RARP and tftpboot; now it will try RARP
>> again.
>
> [snip]
>> Is it shared with "norootsquash" or whatever the name of the option is
>> which allows for root access?
>
> When I try no_root_squash the NFS server won't start on Solaris (think its
> a Linux-ism) and I get the following from LOM:
>
> ok boot net - install
> Boot device: /pci(a)1f,0/pci@1,1/network@1,1 File and args: - install 38e00
> panic - boot: Could not mount filesystem. Program terminated
> ok
>
> I don't get the error when it's setup like the following, so I guess this
> is okay, anon=0 is also a root access flag:
>
> bash-3.00# more /etc/dfs/dfstab
> share -F nfs -o ro,anon=0 /export/home/jumpstart/install share -F nfs -o
> ro,anon=0 /export/home/jumpstart/config
>
> What is it supposed to do after the 38e00 bit - kick off the installer
> (language selection etc)?

It should start to boot
Then ask the Q's

--
Bruce

"The internet is a huge and diverse community and
not every one is friendly"
http://www.ytc1.co.uk

From: Bruce Porter on 24 Feb 2007 11:43
On Sat, 24 Feb 2007 05:09:20 -0800, simoninusa200 wrote:

> I've just bought a Netra T1 105 and as it has no CD-ROM, I want to
> Jumpstart it.
>
> I've tried setting up a Jumpstart server using Linux (Fedora5) and also
> from a Solaris 10 11/06 x86 VMWare instance, and both time the "boot net
> - install" fails at the same point, with a "38e00 |" prompt, here's the
> LOM output (serial/mac/hostid removed):
>
> lom>
> LOM event: power on
> .
> Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard OpenBoot 3.10.27 ME, 1024 MB
> memory installed, Serial xxxxxx. Ethernet address xxxxxx, Host ID: xxxxxx.
>
> Drive not ready
> Boot device: sec-disk File and args: Drive not ready
> Evaluating: boot
>
> Can't open boot device
>
> ok boot net - install
> Boot device: /pci(a)1f,0/pci@1,1/network@1,1 File and args: - install 38e00
> |
>
> Swapping out the drives from a D130 makes no difference, other than the
> "drive not ready" bit from LOM gets replaced with:
>
> "Boot device: pri-disk File and args:
> :217: The file just loaded does not appear to be executable."
>
> add_install_client seems to have worked properly (on Solaris/VMWare) and
> creates pretty much the same bootparams/dfstab/ethers/hosts/ tftpboot
> entries as the Linux tutorials. It couldn't find adb, but the IP addresses
> all are fine. setup_install_server worked fine too.
>
> I've tried using sun4u and SUNW,UltraSPARC-IIi-Engine as the platform, no
> difference there.
>
>>From the output of tcpdump and the server's console, it would seem
> that the Netra is getting an IP (I can ping it) from rarpd and /etc/
> ethers, and a boot image from /tftpboot, but then it just seems to sit
> there when it gets to the NFS bit, here's some of the dump:
>
> 20:00:51.969246 IP 192.168.0.79.nfs > netra.157583: reply ok 80 getattr
> 20:00:51.969407 IP 192.168.0.79.nfs > netra.33685760: reply ok 1448
> 20:00:51.969519 IP 192.168.0.79.nfs > netra.0: reply ok 1448
> 20:00:51.969618 IP 192.168.0.79.nfs > netra.0: reply ok 1448
> 20:00:51.969689 IP 192.168.0.79.nfs > netra.978: reply ERR 1448
> 20:00:51.969757 IP 192.168.0.79.nfs > netra.1345: reply ERR 1448
> 20:00:51.969828 IP 192.168.0.79.nfs > netra.0: reply ERR 952
> 20:00:51.969831 IP 192.168.0.79.nfs > netra.0: reply ERR 952
> 20:00:51.985618 IP netra.0 > 192.168.0.79.nfs: 0 proc-1888936968
> 20:00:52.793511 IP 192.168.0.79.nfs > netra.33685760: reply ok 1448
>
> I can mount the NFS shares/tftp from Linux OK (except for Linux's broken
> NFSv4 of course!)
>
> The bootparam/rarp/nfs/tftp services are all running according to svcs
>
> Can anyone help (or do you need more info?) as I have about a week to get
> this box co-located before my other web hosting contract runs out, so
> could do with getting on with securing the OS, not mucking around trying
> to install it!
>

You could try a dhcp install instead. Or do you have no other Solaris box
available to try a true JumpStart on ?

> Cheers ;-)

--
Bruce

"The internet is a huge and diverse community and
not every one is friendly"
http://www.ytc1.co.uk

 |  Next  |  Last
Pages: 1 2 3 4 5 6
Prev: Cannot boot x4200 via dhcp (from another x4200)
Next: Solaris 10 tape drive permission issues...