Openboot device path.
ma...@redbrick.dcu.ie
>
> Try just "boot disk" and see if that does the right thing. If the
> Openboot firmware isn't horribly messed up that should know which
> device the hard disk is.
I tired this, it tried to boot off
/pci@1f,0/pci@1,1/ide@3/disk@0
HOwever it simply reports,
"No boot record found"
I'm thinking two things
* Openboot is trying to boot off the wrong disk; is there any way to list the
devices on the system so I can try them manually, or even better which ones
I can boot from.
* Even though I followed all the steps from sysinstall, it's possible that a
boot sector (MBR in intel world), however unlike the normal sysinstall I
wasn't prompted to install a loader after the disk partitioning table.
If I can prove any extra information, please don't hesitate to ask,
Thanks for your time and troubles.
--
regards,
-mark
-
Mark Campbell <mark_c...@redbrick.dcu.ie>
http://mark.redbrick.dcu.ie
-
"Trying is the first step towards Failure"- Homer J. Simpson
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
To unsubscribe, send any mail to "freebsd-sparc...@freebsd.org"
ma...@grogged.dyndns.org
Hmm, well - I don't remember if the Ultra 5 utilizes scsi or ata for disk
i/o, but here's what I do with my Ultrasparcs that are scsi based:
devalias - typing that should bring up a list of the default parameters
for booting disks/cdroms/etc and what their corresponding alias happens to
be.
probe-scsi - best done right after a reset, the Sun will list all drives
connected to any scsi bus on the system (I haven't found an analog for ata
based Ultras yet...).
set-defaults - this will take all default values stored in the nvram and
re-institute the defacto parameters set from the factory. Might not be
any help to you.
I really don't have any advice about verifying the "bootability" of a
disk. If it doesn't have anything critical, and you have a relatively
fast connection, you could always <cringe> download the solaris 9 cd's and
verify proper functionality with those. At least at that point you will
know the hardware is good if things work out. I know it sounds stupid,
but I had a couple ata drives hooked up in an ultra 10 last month, and for
whatever reason the sparc was very angry about the way I had them hooked
up. I successfully booted off a freebsd cdrom, and install the system to
the drive (freebsd detected it, everything looked kosher, sysinstall went
without a hitch), but upon trying to actually boot the system, the
prom/whatever couldn't find the ata disk. Solaris wasn't as forgiving,
and I ended up hooking up the ata drives in a couple different (all valid
in my opinion) configurations before solaris agreed to install itself on
them. Freebsd went on smooth again, and this time booted without a hitch.
-m
dwh...@gumbysoft.com
>
> Hmm, well - I don't remember if the Ultra 5 utilizes scsi or ata for disk
> i/o, but here's what I do with my Ultrasparcs that are scsi based:
Ultra5s are IDE.
> set-defaults - this will take all default values stored in the nvram and
> re-institute the defacto parameters set from the factory. Might not be
> any help to you.
This will reset the devaliases and might help. Ootherwise, I didn't have
to do anything special; just 'boot' worked. You may need to do 'boot
disk' for whatever reason.
--
Doug White | FreeBSD: The Power to Serve
dwh...@gumbysoft.com | www.FreeBSD.org
kens...@cse.buffalo.edu
> I tired this, it tried to boot off
>
> /pci@1f,0/pci@1,1/ide@3/disk@0
>
> HOwever it simply reports,
>
> "No boot record found"
>
> I'm thinking two things
>
> * Openboot is trying to boot off the wrong disk; is there any way to list the
> devices on the system so I can try them manually, or even better which ones
> I can boot from.
Mine says /pci@1f,0/pci@1,1/ide@3/disk@0,0 but I don't *think* the trailing
",0" part is significant enough to cause your problem. Other people have
already mentioned how to reset defaults though and that's worth a try
just in case. If it were the wrong disk I think you would see something
more along the lines of this:
Rebooting with command: boot disk1
Boot device: /pci@1f,0/pci@1,1/ide@3/disk@1,0 File and args:
Can't read disk label.
Can't open disk label package
Evaluating: boot disk1
Can't open boot device
Since you're getting the "No boot record found" I think it's finding the
disk but not anything useful for a boot record.
> * Even though I followed all the steps from sysinstall, it's possible that a
> boot sector (MBR in intel world), however unlike the normal sysinstall I
> wasn't prompted to install a loader after the disk partitioning table.
I'm not sure why you weren't prompted for the install of the boot loader,
I think it should have done that. Would you mind re-attempting the
install and pay particular attention to what happens after you have
finished with the partition layout? If it slips through from where you
quit out of the partition layout with no mention of a boot loader at all
let us know please?
If it really fails to ask you about a boot record at all I should be
able to figure out how to run the boot loader off the CD, but then
have the boot loader boot up the kernel from the hard drive. Once
it's up and running that way you should be able to manually run the
sunlabel command to install the boot record. I forgot to leave a CD
in a test machine before I left work today so I can't walk through
that myself right now like I had planned to. :-(
--
Ken Smith
- From there to here, from here to | kens...@cse.buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
ma...@redbrick.dcu.ie
>
I'm ashamed to say it was the fact that I had no little connector* at the back
of the HDD, this was no problem during the freebsd install, however it then
wasn't being dected at the openboot.
* I know there's a proper word for this little terminator.
Thanks for your help as I get used to the joys of SPARC hardware.
--
regards,
-mark
-
Mark Campbell <mark_c...@redbrick.dcu.ie>
http://mark.redbrick.dcu.ie
-
"Trying is the first step towards Failure"- Homer J. Simpson
dwh...@gumbysoft.com
> On Mon, Mar 22, 2004 at 06:43:20PM -0800, Doug White stated:
> > On Mon, 22 Mar 2004, matt wrote:
> >
>
> I'm ashamed to say it was the fact that I had no little connector* at the back
> of the HDD, this was no problem during the freebsd install, however it then
> wasn't being dected at the openboot.
>
> * I know there's a proper word for this little terminator.
The master/slave jumper? :)
--
Doug White | FreeBSD: The Power to Serve
dwh...@gumbysoft.com | www.FreeBSD.org
obr...@freebsd.org
> probe-scsi - best done right after a reset, the Sun will list all drives
> connected to any scsi bus on the system (I haven't found an analog for ata
> based Ultras yet...).
'probe-ide' also, as most Ultra5's have IDE disks in them.