SEO

All--

I've got an E450 and a V480 with a boot snag and I was wondering if
anyone has any good pointers, links, suggestions, etc. that could help
me work this out (I'm sorely defficient in OBP). Seems these two won't
boot the usual 'boot-device' suspects w/o manual intervention.

They both will not automatically boot from disk:a. They skip right to
'net' which is a no-go under their circumstances. If I issue 'boot
disk:a' both systems come up fine. Both systems have a full device set
for booting:

boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf990d7a,0:a
disk net

The 450 came from overseas and has had this issue from the get-go. The
480 seems to have *some how* started this on its own, though. I
personally didn't change anything but I do know the 480 auto-booted from
disk:a on previous resets.

Any ideas on how this could have changed? Do I simply rewrite the
boot-device line?

TIA!

Ben--

On Sat, 13 Sep 2003, Ben wrote:

> All--
>
> I've got an E450 and a V480 with a boot snag and I was wondering if
> anyone has any good pointers, links, suggestions, etc. that could help
> me work this out (I'm sorely defficient in OBP). Seems these two won't
> boot the usual 'boot-device' suspects w/o manual intervention.

Check the diag settings on these machines. Many OBPs default
to booting from the net when doing a boot-diag.

--
Rich Teer, SCNA, SCSA

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-online.net

Ben wrote:
> All--
>
> I've got an E450 and a V480 with a boot snag and I was wondering if
> anyone has any good pointers, links, suggestions, etc. that could help
> me work this out (I'm sorely defficient in OBP). Seems these two won't
> boot the usual 'boot-device' suspects w/o manual intervention.
>
> They both will not automatically boot from disk:a. They skip right to
> 'net' which is a no-go under their circumstances. If I issue 'boot
> disk:a' both systems come up fine. Both systems have a full device set
> for booting:
>
> boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf990d7a,0:a
> disk net
>
> The 450 came from overseas and has had this issue from the get-go. The
> 480 seems to have *some how* started this on its own, though. I
> personally didn't change anything but I do know the 480 auto-booted from
> disk:a on previous resets.
>
> Any ideas on how this could have changed? Do I simply rewrite the
> boot-device line?
>
> TIA!
>
> Ben--
>


Ben, check the setting for OBP variable diag-switch? (including "?"
mark). If it is sdet to true, then it will boot diag-device, not
boot-device, and will pass diag-file as an argument, and not boot-file.

I have seen systems revert to booting the "diag" versions due to failed
installations of the OS, but I am sure that there are 17 million other
(better) reasons for it doing so.

Don't worry about being deficient at OBP. Next time you get to the "ok"
prompt, enter "see !" (without the quotes). _Then_ you will feel
deficient (unless you have a SPARC architecture manual handy, and an
understanding of assembly languages) ;^)

--
I have observed that facts cannot be derived from observations - and
that's a fact ;^)

Ben wrote:
> All--
>
> I've got an E450 and a V480 with a boot snag and I was wondering if
> anyone has any good pointers, links, suggestions, etc. that could help
> me work this out (I'm sorely defficient in OBP). Seems these two won't
> boot the usual 'boot-device' suspects w/o manual intervention.
>
> They both will not automatically boot from disk:a. They skip right to
> 'net' which is a no-go under their circumstances. If I issue 'boot
> disk:a' both systems come up fine. Both systems have a full device set
> for booting:
>
> boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf990d7a,0:a
> disk net
>
> The 450 came from overseas and has had this issue from the get-go. The
> 480 seems to have *some how* started this on its own, though. I
> personally didn't change anything but I do know the 480 auto-booted from
> disk:a on previous resets.
>
> Any ideas on how this could have changed? Do I simply rewrite the
> boot-device line?
>
> TIA!
>
> Ben--
>

Thanks for the tips. Here's a silly "gotcha": the keys on both systems
were powered-on in the DIAG position which sent them on their merry way
to booting the specified diag-device on every reboot ('net' by default).

Picked up that tidbit off an old Sun Managers post. The system should
be either ON or LOCK. And LOCK will prevent a break, too.

FWIW the diag-switch? variable was "false" on both systems.

The 450 was somebody else's doing but the 480 was my bag

I'll take a "RTFM" ... as it's said in old Mexico City ... on what those
little "universal" symbols mean.

Ben wrote:

> All--
>
> I've got an E450 and a V480 with a boot snag and I was wondering if
> anyone has any good pointers, links, suggestions, etc. that could help
> me work this out (I'm sorely defficient in OBP). Seems these two won't
> boot the usual 'boot-device' suspects w/o manual intervention.
>
> They both will not automatically boot from disk:a. They skip right to
> 'net' which is a no-go under their circumstances. If I issue 'boot
> disk:a' both systems come up fine. Both systems have a full device set
> for booting:
>
> boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf990d7a,0:a
> disk net
>
> The 450 came from overseas and has had this issue from the get-go. The
> 480 seems to have *some how* started this on its own, though. I
> personally didn't change anything but I do know the 480 auto-booted from
> disk:a on previous resets.
>
> Any ideas on how this could have changed? Do I simply rewrite the
> boot-device line?
>
> TIA!
>
> Ben--
>

Thanks for the info! Here's a little "gotcha": both systems had their
keys in the DIAG position which sent them on their merry way to booting
the specified diag-device (net by default) with every soft-boot.

For the record the 450 was somebody else's doing but the 480 was my bag

Soooo ... I'm feeling pretty silly. Guess it pays to RTFM on what those
little "universal" symbols mean

Ben wrote:
> Ben wrote:
>
>> All--
>>
>> I've got an E450 and a V480 with a boot snag and I was wondering if
>> anyone has any good pointers, links, suggestions, etc. that could help
>> me work this out (I'm sorely defficient in OBP). Seems these two
>> won't boot the usual 'boot-device' suspects w/o manual intervention.
>>
>> They both will not automatically boot from disk:a. They skip right to
>> 'net' which is a no-go under their circumstances. If I issue 'boot
>> disk:a' both systems come up fine. Both systems have a full device
>> set for booting:
>>
>> boot-device=/pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf990d7a,0:a
>> disk net
>>
>> The 450 came from overseas and has had this issue from the get-go. The
>> 480 seems to have *some how* started this on its own, though. I
>> personally didn't change anything but I do know the 480 auto-booted
>> from disk:a on previous resets.
>>
>> Any ideas on how this could have changed? Do I simply rewrite the
>> boot-device line?
>>
>> TIA!
>>
>> Ben--
>>
>
> Thanks for the info! Here's a little "gotcha": both systems had their
> keys in the DIAG position which sent them on their merry way to booting
> the specified diag-device (net by default) with every soft-boot.
>
> For the record the 450 was somebody else's doing but the 480 was my bag
>
> Soooo ... I'm feeling pretty silly. Guess it pays to RTFM on what those
> little "universal" symbols mean
>

Sorry for the double-post. Nutscrape locked up on me and I didn't my
first reply got off.

Ben wrote:
>
> Sorry for the double-post. Nutscrape locked up on me and I didn't my
> first reply got off.

Next time, just cancel the 2nd message. Most (all?) newsreaders have this
feature, and I know Netscape does.

--
Griff Miller II | Why, I think I've got the hang of it now! |
Manager of Information Technology | :w :q :wq :wq! ^d X exit :quitbye :!QUIT! |
Positron Corporation | CtrlAltDel ^E ^X ^I ^T ZZ q help ^X^C :~q |
griff.miller@positron.com | ^Q ^U ^I ^T man vi $#^T$%&WRGG~NO CARRIER |

Griff Miller wrote:
> Ben wrote:
>
>>Sorry for the double-post. Nutscrape locked up on me and I didn't my
>>first reply got off.
>
>
> Next time, just cancel the 2nd message. Most (all?) newsreaders have this
> feature, and I know Netscape does.
>

True, though all that does is send a "cancel" control message. It's up
to each news server administrator whether an individual news server
honours "cancel"s. Google, to name but one, doesn't.

--
Tony