|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
||||
|
||||
|
I have a Sun Ultra 60 that was purchased without a CD-Rom. I have bought a Plextor 40x scsi cdrom which I have installed. I did a probe-scsi-all and the system sees it on SCSI ID#4. There is no OS on the installed hard drive. After doing the probe-scsi-all I tried doing a "boot cdrom" where I have the Solaris 9 Install CD. After hitting enter it gives an error saying it failed to boot the device.
I was wondering what I am doing wrong. Can anyone shed some light on what I need to do at this point to get this working? Thanks in advance! Regards, jlk |
|
#2
|
|||
|
|||
|
you probably need to change the devalias to point to 4 instead of 6 (which I beleive is the default)
or jumper the cdrom to id6 |
|
#3
|
||||
|
||||
|
Thanks for the info stevengs.
In case anyone is wondering, I did a search on google for devalias and came up with this link. I basically went to my machine and did a 'probe-scsi-all' to find out what device the cd-rom was and it was at device 4. So, I entered the following at the ok? prompt: boot /pci@1f,4000/scsi@3/disk@4,0:f and after I hit enter, I heard the CD-Rom fire up and I am installing Solaris 9 now. Thanks again stevengs for the push in the right direction!!! Regards, jlk |
|
#4
|
|||
|
|||
|
great, I couldn't remember the syntax, it's been a few years...
generally this is done like this: Code:
devalias cdrom /pci@1f,4000/scsi@3/disk@4,0:f which will remain in memory. now you can boot with: Code:
boot cdrom or your can reconfigure the cdrom to Id-6. That way the devalias "cdrom" will always be pointing to your cd, even if your nv gets wiped out. -Steven |
|
#5
|
||||
|
||||
|
Quote:
The only problem with this is that the cdrom does not have the diagram to say what jumper is what ID. I threw it on the right most one and prayed. There are only 3 jumpers for ID's. Who knows what the others are. I may have to find the drives specs online and look at what each setting is. Thanks again!!! Regards, jlk |
|
#6
|
|||
|
|||
|
that is an easy one....
With SCSI devices, the jumpering is binary. If the far right was 4, then the middle one is 2 and the left one is 1. Add em up. Middle and Right add up to six. So just leave the Left one out. Voila. (this listing is reversed) Code:
RML #Right - Middle - Left due to the arrangement on the Drive. 000 = 0 001 = 1 010 = 2 011 = 3 100 = 4 101 = 5 110 = 6 111 = 7 watch out, 7 is traditionally the controller. -Steven _________ My mother always told me to stand up to homocidal maniacs. -Baldric, The Black Adder Sorry 'bout all the changes, got a bit carried away... |
|
#7
|
||||
|
||||
|
You know, I had a sneaky suspision it was just like the permissions scheme, but didn't want to assume and mess myself up. Now all I need to do is dig up another jumper and I won't need to alter devalias.
Thanks yet again!!! jlk |
|
#8
|
|||
|
|||
undefinedIf someone has changed the "cdrom" alias in the firmware PROM settings (by putting a devalias command in nvramrc), thenyou may need to reset the firmware settings. at the firmware "ok" prompt:- set-defaults factory default settings. for the appropriate path(s); at the "ok" prompt: probe-scsi-all To work around :- ----------------------- > set-defaults To set back to factory details >probe-scsi-all This will show a proper path. Take note. We did :- ====== >boot /pci@1f, 4000/scsi@3,1/disk@6,0:f Devalias was missing the ,1 just after the 3 which is why it wasn't working. Cheers, Tugrul Ozbay |
|
#9
|
|||
|
|||
If someone has changed the "cdrom" alias in the firmware PROM settings (by putting a devalias command in nvramrc), then you may need to reset the firmware settings. at the firmware "ok" prompt:- set-defaults factory default settings. for the appropriate path(s); at the "ok" prompt: probe-scsi-all To work around :- ----------------------- > set-defaults To set back to factory details >probe-scsi-all This will show a proper path. Take note. We did :- ====== >boot /pci@1f, 4000/scsi@3,1/disk@6,0:f Devalias was missing the ,1 just after the 3 which is why it wasn't working. Cheers, Tugrul Ozbay |
|
#10
|
|||
|
|||
|
This thread was extremely helpful, I have an Ultra 60 with an external Sun SCSI drive and external SCSI CD-ROM (LaCie enclosure, Yamaha drive). They're daisy chained with going to the hard drive first then to the CD-ROM. The drive device I have set for the "high" numbers, 9-14 (as opposed to 1-6). Thanks to this article, I changed the CD-ROM to ID #6. probe-scsi-all has always found the devices, but until now no matter how I tried booting, I kept getting the error, "Can't open boot device" and I'd get no response from the CD drive no matter what path I tried. Now that it's set for ID 6, when I do a boot cdrom it does start spinning up, but now I get an error that states:
"The file just loaded does not appear to be executable." I tried a burned copy of Solaris 8 SPARC, the installation disc, and I've tried both the Solaris 9 Install and Software 1 discs. All 3 give the same error. Note: I was messing with an Ultra 10 trying to install Solaris 9 and getting the same error. I swapped out the IDE CD drive (an LG Electronics 32x drive for the record) in the Ultra 10 with the Samsung from my Dell/WinXP desktop, and it started working just fine with no changes to the aliases or probe-ide or anything. The WinXP system saw the LG drive and it's working just fine. I'm wondering if the Solaris 9 CD's are printed in some unusual fashion that makes certain CD-ROM drives not see them correctly? I'm brand new on this job and these little snags are making me look like an idiot (not that I'm not, but I was hoping I'd hide the fact better than this! heh) Any help would be greatly appreciated. P.S. I just tossed in a Solaris 7 CD (retail, not CD-R), and it's starting to install just fine. I'm really suspicious of the Solaris 9 CD's. Anyone else have this sort of problem with them? P.P.S. No, it's *not* the Solaris 9 DVD. ![]() Figured it out, I think. I tried the Sol 9 CD again, this time when I did a boot cdrom, instead of just trying to boot, it reset the system first, then tried booting (I think it was because I did a Stop-A during the Sol 7 install), when it reset and started booting, the install started no problem. When it was trying to boot without resetting first, that's when it was failing. |
![]() |
| Viewing: Dev Shed Forums > Operating Systems > UNIX Help > Need assistance with Sun Ultra 60 |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|