Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
how to install the system in a old new disk with data
- Thread starter dmarfil
- Start date
- Thread starter
- #3
altsystems
IS-IT--Management
Hi,
Please note - this will erase the disk. You cannot use a HFS filesystem as a boot drive for the SGI. If you have data on this disk and need it, GET ANOTHER DISK for your boot drive.
Access the PROM command monitor. When you turn on the O2, shortly after the monitor initiates, the system provides a pop up prompt that reads something like "Starting Up System" and a secondary prompt reading "stop for maintenance". At this point either use the mouse to select the prompt or hit the escape key.
After a moment, the system will present you with six graphical selections. The fifth one is "Enter the Command Prompt". Select this either with the mouse or by hitting the F5 key. Insert your IRIX 6.3 CD into the CDROM. Use the hinv command to find out what CPU you have. It is the second line. If it is an R10000 or higher you will use drive 2. If it is an R5000 or similar, use drive 1. Issue the following command from the prompt:
> boot -f dksc(0,4,8)sashARCS dksc(0,4,7)/stand/fx.ARCS
It will prompt you to see if you want the expert mode... you do. It will ask you to identify the disk you want to format.
device name = dksc
ctlr = 0
drive = 1 or 2 depending on which CPU you have.
lun = 0
l/c/a
r/ro
l/sy
exit
What have we done?
We have invoked the stand alone shell (sashARCS) to place minimal required system software in RAM. We have then invoked the disk formatter for IRIX (fxARCS). We then selected the boot drive to partition.
l/c/a - This creates a SGI label in the volume header of the drive so that the O2 can recognize it. The slashes chase up directory trees without changing to a new directory. The tree is: label/create/all.
r/ro - This creates a root partition (0). This is the boot partition that you are trying to create. The tree is: repartition/root only.
l/sy - This writes the disk label back to the disk and changes the parameters in the driver.
exit - This exits the Disk Formatting utility. The disk is ready to load software. I am not sure if exiting fx drops you back into sash or to the graphical selection level. If it drops you back to sash (prompt is sash
use the quit command to get back to the graphical interface.
Select the second item "Load System Software". Install from the CDROM (your 6.3 disk should still be in there). The system will obtain the installation tools and load miniroot. it will then complain that the disk /dev/dsk/dks0d1s0 does not have a viable filesystem on it. You will either be prompted to make a filesystem now, or to open a shell and fix this problem.
If you have to open a shell, use the following command inside the shell:
mkfs /dev/dsk/dks0d1s0 Assuming the disk is number 1
Exit the shell to return to the inst program in miniroot. The inst program will now mount your drive. From inst, use the following command:
f /CDROM/dist
This will open the software distribution and read information. I am going to be lazy at this time:
i *
g
This tells the inst program to install all software. Then it tells it to begin installing that request. You will get a list of installation conflicts - wrong architecture, missing prereqs, etc. Clear the conflicts by not installing anything that complains ( usually the first choice). if you don't want to look at the entire set of choices, hit q to break out of the listing.
Clear conflicts with the following command example. Let's say inst reported 5 conflicts. it would just about fill the screen with stuff. Use the following command:
c 1a 2a 3a 4a 5a
This selects the first choice (don't install) for each conflict. Any new conflicts would then be reported. When all conflicts have been resolved, the inst program will report:
no conflicts
now hit g (for go). The inst program will now correctly load system software. Since you are only loading from one source, it will not ask for other disks. When complete, it will ask if you want to load more software - you will want to do that from swmgr (a graphical interface once you have X up).
The inst program will now prepare the kernel. Eventually it will want to restart. You now have a bootable O2 for IRIX. You will want to load your other disks (applications, NFS and required patches) once you have logged in as root.
Whew - that was a lot of typing. Hope it helps
JGSmall
Sr Engineer
Alt Systems
Please note - this will erase the disk. You cannot use a HFS filesystem as a boot drive for the SGI. If you have data on this disk and need it, GET ANOTHER DISK for your boot drive.
Access the PROM command monitor. When you turn on the O2, shortly after the monitor initiates, the system provides a pop up prompt that reads something like "Starting Up System" and a secondary prompt reading "stop for maintenance". At this point either use the mouse to select the prompt or hit the escape key.
After a moment, the system will present you with six graphical selections. The fifth one is "Enter the Command Prompt". Select this either with the mouse or by hitting the F5 key. Insert your IRIX 6.3 CD into the CDROM. Use the hinv command to find out what CPU you have. It is the second line. If it is an R10000 or higher you will use drive 2. If it is an R5000 or similar, use drive 1. Issue the following command from the prompt:
> boot -f dksc(0,4,8)sashARCS dksc(0,4,7)/stand/fx.ARCS
It will prompt you to see if you want the expert mode... you do. It will ask you to identify the disk you want to format.
device name = dksc
ctlr = 0
drive = 1 or 2 depending on which CPU you have.
lun = 0
l/c/a
r/ro
l/sy
exit
What have we done?
We have invoked the stand alone shell (sashARCS) to place minimal required system software in RAM. We have then invoked the disk formatter for IRIX (fxARCS). We then selected the boot drive to partition.
l/c/a - This creates a SGI label in the volume header of the drive so that the O2 can recognize it. The slashes chase up directory trees without changing to a new directory. The tree is: label/create/all.
r/ro - This creates a root partition (0). This is the boot partition that you are trying to create. The tree is: repartition/root only.
l/sy - This writes the disk label back to the disk and changes the parameters in the driver.
exit - This exits the Disk Formatting utility. The disk is ready to load software. I am not sure if exiting fx drops you back into sash or to the graphical selection level. If it drops you back to sash (prompt is sash
use the quit command to get back to the graphical interface.Select the second item "Load System Software". Install from the CDROM (your 6.3 disk should still be in there). The system will obtain the installation tools and load miniroot. it will then complain that the disk /dev/dsk/dks0d1s0 does not have a viable filesystem on it. You will either be prompted to make a filesystem now, or to open a shell and fix this problem.
If you have to open a shell, use the following command inside the shell:
mkfs /dev/dsk/dks0d1s0 Assuming the disk is number 1
Exit the shell to return to the inst program in miniroot. The inst program will now mount your drive. From inst, use the following command:
f /CDROM/dist
This will open the software distribution and read information. I am going to be lazy at this time:
i *
g
This tells the inst program to install all software. Then it tells it to begin installing that request. You will get a list of installation conflicts - wrong architecture, missing prereqs, etc. Clear the conflicts by not installing anything that complains ( usually the first choice). if you don't want to look at the entire set of choices, hit q to break out of the listing.
Clear conflicts with the following command example. Let's say inst reported 5 conflicts. it would just about fill the screen with stuff. Use the following command:
c 1a 2a 3a 4a 5a
This selects the first choice (don't install) for each conflict. Any new conflicts would then be reported. When all conflicts have been resolved, the inst program will report:
no conflicts
now hit g (for go). The inst program will now correctly load system software. Since you are only loading from one source, it will not ask for other disks. When complete, it will ask if you want to load more software - you will want to do that from swmgr (a graphical interface once you have X up).
The inst program will now prepare the kernel. Eventually it will want to restart. You now have a bootable O2 for IRIX. You will want to load your other disks (applications, NFS and required patches) once you have logged in as root.
Whew - that was a lot of typing. Hope it helps
JGSmall
Sr Engineer
Alt Systems
- Status
Similar threads
- Locked
- Question