Irix 6.5.22 Install Mercy
maximuslivius
I want to install Irix 6.5.22 on my Indy fresh HD because the
old 6.2 crashed due to the corrupted hard disk.
Actually I have tried it for over a year unsuccessfully.
Installation procedure complains about :
1- missing sash file on dksc(0,1,8) <-- volume header
2- missing unix file on dksc(0,1,1) <-- swap partition
Why the automatic procedure does not write these files to
the correct place ?
Now, I tried to do it step by step by hand with no luck
at all :
1- when I use cp command from sashARCS (loaded
from dksc(0,5,8)) to volume header it gets messed up.
So I have to re-fx it.
2- when I use cp like:
cp -b 32k dksc(0,5,7)/dist/sa(mr) disk(1) partition(1)
it says: file does not exist. IT DOES NOT WORK ! Have MERCY !
But files do exist on CD, /dist partition, I have checked using ls
command.
Alternatively, manual also says that I have to use mkboottape command
to extract the file prior to copy them
which is completely insane since I have no system installed
and running absolutely. (why SGI manuals give wrong or insane
directions ?) I do not have access to a command shell, do I ?
Also, dvhtools can not be used on a fresh install for the same reasons
above !
I have also tried:
6.5.18f no go : same problem of missing installation files...Lord,
have mercy!
6.2 no go : it is all Kernel Panic...panic picnic
Does anyone enlightened enough know how to copy install files to the
right
partitions using commands that work on 6.5.22 ?
By the way, I can install Linux on this Indy machine without problem,
so that,
all its hardware is fully working.
thanks a ton,
Luiz Regis
Toni Grass
>Hi there,
>I want to install Irix 6.5.22 on my Indy fresh HD because the
>old 6.2 crashed due to the corrupted hard disk.
>Actually I have tried it for over a year unsuccessfully.
>Installation procedure complains about :
[....]
http://www.futuretech.blinkenlights.nl/6.5inst.html
http://techpubs.sgi.com/library/manuals/3000/007-3862-008/pdf/007-3862-008.pdf
Special issues how to handle hard disks you find in 'IRIX Admin: Disks
and Filesystems'
You also should have a look into 'IRIX Admin: Software Installation and
Licensing'
Probably the most important question: do you have the original IRIX
installation CDs or at least 100% clones?
You may also start fx in expert mode (with option -x) so you can
initialize the hard disk, and install IRIX on a 'new' disk. In this case
the installtion program will handle to copy necessary files into disk
header after partitioning.
Toni
maximuslivius
> You also should have a look into 'IRIX Admin: Software Installation and
> Licensing'
Thanks for the directions on documents.
> Probably the most important question: do you have the original IRIX
> installation CDs or at least 100% clones?
Correct, I am using 100% clones.
> You may also start fx in expert mode (with option -x) so you can
> initialize the hard disk, and install IRIX on a 'new' disk. In this case
> the installtion program will handle to copy necessary files into disk
> header after partitioning.
I have used fx in expert mode for the disk install. Partitioning is
ok.
Would you please explain what the problems are with clones ?
Thanks in advance
Luiz Regis
Toni Grass
>On 11 dez, 16:40, Toni Grass <t...@fotoni.at> wrote:
[....]
>I have used fx in expert mode for the disk install. Partitioning is
>ok.
Did you initialize the disk?
>Would you please explain what the problems are with clones ?
Also a CD has a volume header and probably this is not correct in case
of a clone. I had a similar problem in the past. I initialized the hard
disk with fx so there was no partition and no volume header, this forced
the installation program to ask me to create partitions and
automatically copied sash and ide into the volume header of the HD and the
'unix' file to root partition.
btw: sash you should find in the volume header of the first CD and in
directory /dist/miniroot/ you find a lot of 'unix' files, choose one ;-)
Check if your installation CD 1 also has this files.
CD 1 from 6.5.14 looks like this:
falcon 9# dvhtool /dev/rdsk/dks2d0vh
Command? (read, vd, write, or quit): vd
(d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)?
l
Current contents:
File name Length Block #
sgilabel 512 32
mr 18688000 33
sash64 267832 36533
sashARCS 342248 37057
good luck
Toni
maximuslivius
> Did you initialize the disk?
I have never heard about it. All manuals I have read have never
mentioned
about initialization of the disk.
How do I do that ?
> Also a CD has a volume header and probably this is not correct in case
> of a clone. I had a similar problem in the past. I initialized the hard
> disk with fx so there was no partition and no volume header, this forced
> the installation program to ask me to create partitions and
> automatically copied sash and ide into the volume header of the HD and the
> 'unix' file to root partition.
Interesting...it makes a lot of sense.
> btw: sash you should find in the volume header of the first CD and in
> directory /dist/miniroot/ you find a lot of 'unix' files, choose one ;-)
> Check if your installation CD 1 also has this files.
You meant for the volume header of the first CD :
dksc(0,5,8) : sgilabel, mr, sash64, sashARCS
but the file on dksc(0,1,8) (volume header of the HD) have to be
sash not sashARCS (they are the same file, I know but different names
in each partition).
Where is the sash file ? Or how do I rename it ?
How do I copy it from the CD to the right partition ?
> CD 1 from 6.5.14 looks like this:
>
> falcon 9# dvhtool /dev/rdsk/dks2d0vh
>
> Command? (read, vd, write, or quit): vd
> (d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)?
> l
>
> Current contents:
> File name Length Block #
> sgilabel 512 32
> mr 18688000 33
> sash64 267832 36533
> sashARCS 342248 37057
Exactly as my 6.5.22 CD1
Thanks
Luiz Regis
maximuslivius
> Did you initialize the disk?
I have never heard about it. All manuals I have read have never
mentioned
about initialization of the disk.
How do I do that ?
> Also a CD has a volume header and probably this is not correct in case
> of a clone. I had a similar problem in the past. I initialized the hard
> disk with fx so there was no partition and no volume header, this forced
> the installation program to ask me to create partitions and
> automatically copied sash and ide into the volume header of the HD and the
> 'unix' file to root partition.
Interesting...it makes a lot of sense.
> btw: sash you should find in the volume header of the first CD and in
> directory /dist/miniroot/ you find a lot of 'unix' files, choose one ;-)
> Check if your installation CD 1 also has this files.
You meant for the volume header of the first CD :
dksc(0,5,8) : sgilabel, mr, sash64, sashARCS
but the file on dksc(0,1,8) (volume header of the HD) have to be
sash not sashARCS (they are the same file, I know but different names
in each partition).
Where is the sash file ? Or how do I rename it ?
How do I copy it from the CD to the right partition ?
> CD 1 from 6.5.14 looks like this:
>
> falcon 9# dvhtool /dev/rdsk/dks2d0vh
>
> Command? (read, vd, write, or quit): vd
> (d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)?
> l
>
> Current contents:
> File name Length Block #
> sgilabel 512 32
> mr 18688000 33
> sash64 267832 36533
> sashARCS 342248 37057
Exactly as my 6.5.22 CD1
Thanks
Luiz Regis
maximuslivius
> Did you initialize the disk?
I have never heard about it. All manuals I have read have never
mentioned
about initialization of the disk.
How do I do that ?
> Also a CD has a volume header and probably this is not correct in case
> of a clone. I had a similar problem in the past. I initialized the hard
> disk with fx so there was no partition and no volume header, this forced
> the installation program to ask me to create partitions and
> automatically copied sash and ide into the volume header of the HD and the
> 'unix' file to root partition.
Interesting...it makes a lot of sense.
> btw: sash you should find in the volume header of the first CD and in
> directory /dist/miniroot/ you find a lot of 'unix' files, choose one ;-)
> Check if your installation CD 1 also has this files.
You meant for the volume header of the first CD :
dksc(0,5,8) : sgilabel, mr, sash64, sashARCS
but the file on dksc(0,1,8) (volume header of the HD) have to be
sash not sashARCS (they are the same file, I know but different names
in each partition).
Where is the sash file ? Or how do I rename it ?
How do I copy it from the CD to the right partition ?
> CD 1 from 6.5.14 looks like this:
>
> falcon 9# dvhtool /dev/rdsk/dks2d0vh
>
> Command? (read, vd, write, or quit): vd
> (d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)?
> l
>
> Current contents:
> File name Length Block #
> sgilabel 512 32
> mr 18688000 33
> sash64 267832 36533
> sashARCS 342248 37057
Exactly as my 6.5.22 CD1
Thanks
Luiz Regis
maximuslivius
> Did you initialize the disk?
I have never heard about it. All manuals I have read have never
mentioned
about initialization of the disk.
How do I do that ?
> Also a CD has a volume header and probably this is not correct in case
> of a clone. I had a similar problem in the past. I initialized the hard
> disk with fx so there was no partition and no volume header, this forced
> the installation program to ask me to create partitions and
> automatically copied sash and ide into the volume header of the HD and the
> 'unix' file to root partition.
Interesting...it makes a lot of sense.
> btw: sash you should find in the volume header of the first CD and in
> directory /dist/miniroot/ you find a lot of 'unix' files, choose one ;-)
> Check if your installation CD 1 also has this files.
You meant for the volume header of the first CD :
dksc(0,5,8) : sgilabel, mr, sash64, sashARCS
but the file on dksc(0,1,8) (volume header of the HD) have to be
sash not sashARCS (they are the same file, I know but different names
in each partition).
Where is the sash file ? Or how do I rename it ?
How do I copy it from the CD to the right partition ?
> CD 1 from 6.5.14 looks like this:
>
> falcon 9# dvhtool /dev/rdsk/dks2d0vh
>
> Command? (read, vd, write, or quit): vd
> (d FILE, a UNIX_FILE FILE, c UNIX_FILE FILE, g FILE UNIX_FILE or l)?
> l
>
> Current contents:
> File name Length Block #
> sgilabel 512 32
> mr 18688000 33
> sash64 267832 36533
> sashARCS 342248 37057
Exactly as my 6.5.22 CD1
Thanks
Luiz Regis
maximuslivius
Sorry, I do not know why google keeps reposting the same message.
I apologize. Perhaps my mistake.
Luiz Regis
maximuslivius
It seems that FX does not write either SASH or UNIX files to the
default partition at all.
>> boot -f dksc(0,5,8)sashARCS dksc(0,5,7)stand/fx.ARCS --x
136336+22752+3248+341792+49344d+4620+6880 entry: 0x97fa5ee0
SGI Version 6.5 ARCS BE Oct 6, 2003
fx: "device-name" = (dksc)
fx: ctlr# = (0)
fx: drive# = (1)
...opening dksc(0,1,0)
...drive selftest...OK
Scsi drive type == QUANTUM ATLAS10K3_18_SCA120G
----- please choose one (? for help, .. to quit this menu)-----
[exi]t [d]ebug/ [l]abel/ [a]uto
[b]adblock/ [exe]rcise/ [r]epartition/
fx> exe
----- please choose one (? for help, .. to quit this menu)-----
[b]utterfly [seq]uential [set]testpat
[e]rrlog [st]op_on_error [sh]owtestpat
[r]andom [m]iscompares [c]omplete
fx/exercise> seq
fx/exercise/sequential: modifier = (rd-only) ?
----- exercise modifiers-----
[rd]-only [ro]-cmp [s]eek [wr-o]nly [wr-c]mp
fx/exercise/sequential: modifier = (rd-only) wr-c
fx/exercise/sequential: starting block# = (0)
fx/exercise/sequential: nblocks = (152756859843903488)
fx/exercise/sequential: nscans = (1)
* * * * * W A R N I N G * * * * *
about to destroy data on disk dksc(0,1,0)! ok? yes
sequential pass 1: scanning [0, 35566478] (35566478 blocks)
0%..........10%..........20%..........30%...
----- please choose one (? for help, .. to quit this menu)-----
[b]utterfly [seq]uential [set]testpat
[e]rrlog [st]op_on_error [sh]owtestpat
[r]andom [m]iscompares [c]omplete
fx/exercise> ..
----- please choose one (? for help, .. to quit this menu)-----
[exi]t [d]ebug/ [l]abel/ [a]uto
[b]adblock/ [exe]rcise/ [r]epartition/
fx> l
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label> c
----- please choose one (? for help, .. to quit this menu)-----
[p]artitions [s]giinfo [b]ootinfo [d]irectory [a]ll
fx/label/create> a
...creating default bootinfo
...created default partitions, use /repartition menu to change
...creating default sgiinfo
...creating default volume directory
----- please choose one (? for help, .. to quit this menu)-----
[p]artitions [s]giinfo [b]ootinfo [d]irectory [a]ll
fx/label/create> d
...creating default volume directory
----- please choose one (? for help, .. to quit this menu)-----
[p]artitions [s]giinfo [b]ootinfo [d]irectory [a]ll
fx/label/create> d
...creating default volume directory
----- please choose one (? for help, .. to quit this menu)-----
[p]artitions [s]giinfo [b]ootinfo [d]irectory [a]ll
fx/label/create> ..
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label> sh
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [b]ootinfo [a]ll
[g]eometry [s]giinfo [d]irectory
fx/label/show> d
----- directory entries-----
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [b]ootinfo [a]ll
[g]eometry [s]giinfo [d]irectory
fx/label/show> s
----- sgi-info-----
serial = name = QUANTUM
ATLAS10K3_18_SCA120G
Created by "SGI Version 6.5 ARCS BE Oct 6, 2003"
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [b]ootinfo [a]ll
[g]eometry [s]giinfo [d]irectory
fx/label/show> b
----- bootinfo-----
root partition = 0 swap partition = 1 bootfile = /unix
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [b]ootinfo [a]ll
[g]eometry [s]giinfo [d]irectory
fx/label/show> ..
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label> ..
----- please choose one (? for help, .. to quit this menu)-----
[exi]t [d]ebug/ [l]abel/ [a]uto
[b]adblock/ [exe]rcise/ [r]epartition/
fx> r
----- partitions-----
part type blocks Megabytes (base+size)
0: xfs 266240 + 35300238 130 + 17236
1: raw 4096 + 262144 2 + 128
8: volhdr 0 + 4096 0 + 2
10: volume 0 + 35566478 0 + 17366
capacity is 35566478 blocks
----- please choose one (? for help, .. to quit this menu)-----
[ro]otdrive [o]ptiondrive [e]xpert
[u]srrootdrive [re]size
fx/repartition> e
Warning: you will need to re-install all software and restore user
data
from backups after changing the partition layout. Changing partitions
will cause all data on the drive to be lost. Be sure you have the
drive
backed up if it contains any user data. Continue? yes
Enter .. when done
fx/repartition/expert: change partition = (0)
before: type xfs block 266240, 130 MB
len: 35300238 blks, 17236 MB
fx/repartition/expert: partition type = (xfs)
fx/repartition/expert: base in megabytes = (130)
fx/repartition/expert: size in megabytes (max 17236) = (17236)
fx/repartition/expert: change partition = (1)
before: type raw block 4096, 2 MB
len: 262144 blks, 128 MB
fx/repartition/expert: partition type = (raw)
fx/repartition/expert: base in megabytes = (2)
fx/repartition/expert: size in megabytes (max 17364) = (128)
fx/repartition/expert: change partition = (6)
before: type xfs block 0, 0 MB
len: 0 blks, 0 MB
fx/repartition/expert: partition type = (xfs)
fx/repartition/expert: base in megabytes = (0)
fx/repartition/expert: size in megabytes (max 17366) = (0)
after: type xfs block 0, 0 MB
len: 0 blks, 0 MB
fx/repartition/expert: change partition = (7)
before: type xfs block 0, 0 MB
len: 0 blks, 0 MB
fx/repartition/expert: partition type = (xfs)
fx/repartition/expert: base in megabytes = (0)
fx/repartition/expert: size in megabytes (max 17366) = (0)
after: type xfs block 0, 0 MB
len: 0 blks, 0 MB
fx/repartition/expert: change partition = (8)
before: type volhdr block 0, 0 MB
len: 4096 blks, 2 MB
fx/repartition/expert: partition type = (volhdr)
fx/repartition/expert: base in megabytes = (0)
fx/repartition/expert: size in megabytes (max 17366) = (2)
----- partitions-----
part type blocks Megabytes (base+size)
0: xfs 266240 + 35300238 130 + 17236
1: raw 4096 + 262144 2 + 128
8: volhdr 0 + 4096 0 + 2
10: volume 0 + 35566478 0 + 17366
capacity is 35566478 blocks
----- please choose one (? for help, .. to quit this menu)-----
[ro]otdrive [o]ptiondrive [e]xpert
[u]srrootdrive [re]size
fx/repartition> ro
fx/repartition/rootdrive: type of data partition = (xfs)
----- partitions-----
part type blocks Megabytes (base+size)
0: xfs 266240 + 35300238 130 + 17236
1: raw 4096 + 262144 2 + 128
8: volhdr 0 + 4096 0 + 2
10: volume 0 + 35566478 0 + 17366
capacity is 35566478 blocks
----- please choose one (? for help, .. to quit this menu)-----
[ro]otdrive [o]ptiondrive [e]xpert
[u]srrootdrive [re]size
fx/repartition> re
After changing the partition, the other partitions will
be adjusted around it to fit the change. The result will be
displayed and you will be asked whether it is OK, before the
change is committed to disk. Only the standard partitions may
be changed with this function. Type ? at prompts for a list
of possible choices
fx/repartition/resize: partition to change = (swap)
current: type raw block 4096, 2 MB
len: 262144 blks, 128 MB
fx/repartition/resize: partitioning method = (megabytes (2^20 Bytes))
fx/repartition/resize: size in megabytes (max 17364) = (128) 512
----- partitions-----
part type blocks Megabytes (base+size)
0: xfs 1052672 + 34513806 514 + 16852
1: raw 4096 + 1048576 2 + 512
8: volhdr 0 + 4096 0 + 2
10: volume 0 + 35566478 0 + 17366
Use the new partition layout? (no) yes
----- partitions-----
part type blocks Megabytes (base+size)
0: xfs 1052672 + 34513806 514 + 16852
1: raw 4096 + 1048576 2 + 512
8: volhdr 0 + 4096 0 + 2
10: volume 0 + 35566478 0 + 17366
capacity is 35566478 blocks
----- please choose one (? for help, .. to quit this menu)-----
[ro]otdrive [o]ptiondrive [e]xpert
[u]srrootdrive [re]size
fx/repartition> ..
----- please choose one (? for help, .. to quit this menu)-----
[exi]t [d]ebug/ [l]abel/ [a]uto
[b]adblock/ [exe]rcise/ [r]epartition/
fx> l
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label> se
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [s]giinfo
[g]eometry [m]anufacturer_params [b]ootinfo
fx/label/set> b
fx/label/set/bootinfo: root partition = (0)
fx/label/set/bootinfo: swap partition = (1)
fx/label/set/bootinfo: "bootfile" = (/unix)
----- bootinfo-----
root partition = 0 swap partition = 1 bootfile = /unix
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [s]giinfo
[g]eometry [m]anufacturer_params [b]ootinfo
fx/label/set> s
fx/label/set/sgiinfo: "serial" = ()
fx/label/set/sgiinfo: "name" = (QUANTUM ATLAS10K3_18_SCA120G)
----- sgi-info-----
serial = name = QUANTUM
ATLAS10K3_18_SCA120G
Created by "SGI Version 6.5 ARCS BE Oct 6, 2003"
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [s]giinfo
[g]eometry [m]anufacturer_params [b]ootinfo
fx/label/set> ..
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label> sy
writing label info to dksc(0,1,0)
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label> sh
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [b]ootinfo [a]ll
[g]eometry [s]giinfo [d]irectory
fx/label/show> a
----- current drive parameters-----
Error correction enabled Enable data transfer on error
Don't report recovered errors Do delay for error recovery
Don't transfer bad blocks Error retry attempts 4
Do auto bad block reallocation (read)
Do auto bad block reallocation (write)
Drive readahead enabled Drive buffered writes disabled
Drive disable prefetch 65535 Drive minimum prefetch 0
Drive maximum prefetch 1497 Drive prefetch ceiling 1497
Number of cache segments 20
Read buffer ratio 0/256 Write buffer ratio 0/256
Command Tag Queueing disabled
----- current drive geometry-----
Tracks/zone = 2 Sect/track = 579
Alt sect/zone = 84 Interleave = 1 Cylinders =
31022
Alt track/volume = 83 Cylinder skew = 23 Heads =
2
Alt track/zone = 0 Track skew = 25 Data bytes/sec =
512
Rotational rate = 10021
----- partitions-----
part type blocks Megabytes (base+size)
0: xfs 1052672 + 34513806 514 + 16852
1: raw 4096 + 1048576 2 + 512
8: volhdr 0 + 4096 0 + 2
10: volume 0 + 35566478 0 + 17366
----- bootinfo-----
root partition = 0 swap partition = 1 bootfile = /unix
----- directory entries-----
0: sgilabel block 2 size 512
----- sgi-info-----
serial = name = QUANTUM
ATLAS10K3_18_SCA120G
Created by "SGI Version 6.5 ARCS BE Oct 6, 2003"
----- please choose one (? for help, .. to quit this menu)-----
[para]meters [part]itions [b]ootinfo [a]ll
[g]eometry [s]giinfo [d]irectory
fx/label/show> ..
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label> ..
----- please choose one (? for help, .. to quit this menu)-----
[exi]t [d]ebug/ [l]abel/ [a]uto
[b]adblock/ [exe]rcise/ [r]epartition/
fx> exit
System Maintenance Menu
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor
Option? 2
Installing System Software...
Press <Esc> to return to the menu.
1) Remote Tape 2) Remote Directory 3)[Local CD-ROM] 4) Local Tape
*a) Local SCSI CD-ROM drive 5
Enter 1-4 to select source type, a to select the source, <esc> to
quit,
or <enter> to start:
Insert the installation CD-ROM, then press <enter>:
Copying installation program to disk.
......... 10% ......... 20% ......... 30% ......... 40% ......... 50%
......... 60% ......... 70% ......... 80% ......... 90% ......... 100%
Copy complete
Okay to power off the system now.
Press any key to restart.
Starting up the system...
To perform system maintenance instead, press <Esc>
Boot file not found on device: scsi(0)disk(1)rdisk(0)partition(8)/
sash.
Unable to boot; press any key to continue:
>> ls
scsi(0)disk(1)rdisk(0)partition(8)/:
sgilabel
>> ls dksc(0,5,8)
dksc(0,5,8):
sgilabel mr sash64 sashARCS
>> ls dksc(0,5,7)/dist
>> ls dksc(0,5,7)
dksc(0,5,7): not a directory
>> hinv
System: IP22
Processor: 150 Mhz R5000, with FPU
Primary I-cache size: 32 Kbytes
Primary D-cache size: 32 Kbytes
Secondary cache size: 512 Kbytes
Memory size: 256 Mbytes
Graphics: Indy 24-bit
SCSI Disk: scsi(0)disk(1)
SCSI Tape: scsi(0)tape(4)
SCSI CDROM: scsi(0)cdrom(5)
Audio: Iris Audio Processor: version A2 revision
4.1.0
>> boot -f dksc(0,5,8)sashARCS
136336+22752+3248+341792+49344d+4620+6880 entry: 0x97fa5ee0
It appears that a miniroot install failed. Either the system is
misconfigured or a previous installation failed.
You may continue booting without fixing the state
You may abort the installation and return to the menu, or you can
fix (reset to normal) the miniroot install state
See the 'Software Installation Guide' chapter on Troubleshooting for
more information
Enter 'c' to continue with no state fixup.
Enter 'f' to fix miniroot install state, and try again
Enter 'a' to abort and return to menu.
Enter your selection and press ENTER (c, f, or a) f
miniroot install state reset to normal
Unable to execute scsi(0)disk(1)rdisk(0)partition(0)/unix: media not
loaded
Autoboot failed.
scsi(0)disk(1)rdisk(0)partition(0)/unix: media not loaded.
Hit Enter to continue.
System Maintenance Menu
1) Start System
2) Install System Software
3) Run Diagnostics
4) Recover System
5) Enter Command Monitor
Option? 5
Command Monitor. Type "exit" to return to the menu.
>> printenv
AutoLoad=Yes
TimeZone=PST8PDT
console=d1
diskless=0
dbaud=9600
volume=80
sgilogo=y
autopower=y
netaddr=192.168.1.222
eaddr=08:00:69:0a:2b:fe
ConsoleOut=serial(0)
ConsoleIn=serial(0)
cpufreq=150
SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
OSLoadFilename=/unix
OSLoader=sash
>> boot -f dksc(0,5,8)sashARCS
136336+22752+3248+341792+49344d+4620+6880 entry: 0x97fa5ee0
Standalone Shell SGI Version 6.5 ARCS Oct 6, 2003 (32 Bit)
sash: ls
scsi(0)disk(1)rdisk(0)partition(8)/:
sgilabel
sash: ls dksc(0,5,7)/dist
dksc(0,5,7)/dist:
. .. mr sa sysadmdesktop_6522m dev_6522m eoe_6522m nfs_6522m
desktop_eoe_6522m.sw print_6522m swmgr.README.html 4Dwm_6522m
roboinst.man
roboinst.idb inst.README x_eoe_6522m.sw Welcome.sw
desktop_eoe_6522m.books
irix_dev_6522m.gifts nfs_6522m.idb nfs_6522m.man eoe_6522m.src
eoe_6522m.man eoe_6522m.idb dev_6522m.idb dev_6522m.man
desktop_eoe_6522m.man .iscd desktop_eoe_6522m.idb
desktop_base_6522m.sw64
dev_6522m.sw pcp_eoe_6522m.sw .prereq_hints x_eoe_6522m
pcp_eoe_6522m
sysmon_6522m desktop_base_6522m.man desktop_base_6522m.idb
desktop_base_6522m sysadmdesktop_6522m.sw pcp_eoe_6522m.man
pcp_eoe_6522m.idb x_eoe_6522m.src x_eoe_6522m.man x_eoe_6522m.idb
miniroot
nfs_6522m.books irix_dev_6522m.idb irix_dev_6522m.man
desktop_tools_6522m.sw dev_6522m.books irix_dev_6522m.sw
Welcome.idb
Welcome.doc desktop_tools_6522m.idb desktop_tools_6522m.man
sysmon_6522m.sw
desktop_tools_6522m sysadmdesktop_6522m.idb sysadmdesktop_6522m.man
4Dwm_6522m.idb 4Dwm_6522m.man Welcome irix_dev_6522m
pcp_eoe_6522m.sw64
.related_dists pcp_eoe_6522m.books sysmon_6522m.books roboinst.sw
desktop_eoe_6522m eoe_6522m.books 4Dwm_6522m.sw roboinst
nfs_6522m.sw
eoe_6522m.sw print_6522m.man print_6522m.idb x_eoe_6522m.sw64
eoe_6522m.sw64 print_6522m.sw desktop_base_6522m.sw dev_6522m.sw64
sysmon_6522m.man sysmon_6522m.idb
sash: cp -b 32k dksc(0,5,7)/dist/miniroot/unix.IP22 dksc(0,1,0)unix
cannot open: dksc(0,1,0)unix: media not loaded
sash: cp -b 32k dksc(0,5,7)/dist/miniroot/unix.IP22 dksc(0,1,0)/unix
cannot open: dksc(0,1,0)/unix: media not loaded
sash: cp -b 32k dksc(0,5,7)/dist/miniroot/unix.IP22 dksc(0,1,0)
................................................................
................................................................
................................................................
....................................................
cp: write error: IO error
offset=0x0 0x7a0000
7995392 (0x7a0000) bytes copied
sash:
Do you have any clue ?
Thanks.
Luiz Regis
Toni Grass
>Here is my FX experience (I did the same many times in the past)
>It seems that FX does not write either SASH or UNIX files to the
>default partition at all.
[....]
>Do you have any clue ?
Not really.
Only one question: you are sure the hard disk is really OK?
And an idea that might work: change the hd volume header. Either move it
into a PC and write a PC header (Windows or Linux makes no difference)
or (if you do not have a PC with SCSI controller) with fx and create an
option disk. After this start installation again and create a boot disk
then. The trick is to prepare the hd in this way that fx does not
recognize the disk to have an IRIX volume header. Do not forget 'mkfs'.
Sorry no other ideas.
Toni
maximuslivius
> Only one question: you are sure the hard disk is really OK?
Yes, I bought two brand new sealed in the box SCSI SCA hard drives and
am using
an adapter 80-60-60-50 with high-byte negation.
> And an idea that might work: change the hd volume header. Either move it
> into a PC and write a PC header (Windows or Linux makes no difference)
> or (if you do not have a PC with SCSI controller) with fx and create an
> option disk. After this start installation again and create a boot disk
> then. The trick is to prepare the hd in this way that fx does not
> recognize the disk to have an IRIX volume header. Do not forget 'mkfs'.
Ok, I will try that.
Thanks
Luiz Regis
Knut Roll-Lund
Sorry, I don't think this is very helpful but:
I have had problems installing 6.5.22 on my Indy too. I'm kind of newbie
though, using Irix (and not too knowledgeable about unix/linux either).
Downloaded the 3 CD's for 6.5.22 from SGI but found no way to recreate
acceptable CD's from them. I instead made the contents available on the
local net, transferred the files to the harddisk and installed from there.
I also have an Indigo2 and I used this method to upgrade it to 6.5.22
from 6.5.10, I think (I needed some more files from SGI then too which
were available same place as 6.5.22, this I found out from Ian's site,
mentioned erlier in the thread). Anyway I later bought a cd set of
6.5.19 and when I got the Indy I upgraded it first to 6.5.19 then to
6.5.22. The install seemed to work ok but after that it refused to boot.
I had to restore a backup (I made before I attempted this) from DAT, and
restart, paying even more attention to the process so I'm certain it all
went ok up until it refuses to boot. It failed in the same way. 6.5.22
should work on an Indy according to all the information I have so I
don't know what is wrong. Note; it is all a while ago I did this so I
have no more details.
6.5.19 works well on the Indy so it is what I'm using on the Indy now. I
gave up, but might reopen "the case" if I get any idea of a solution.
I do all this as upgrades and not clean installs because there is
licensed software on these machines I want to keep... 3d software. BTW I
couldn't change the network name of the machine even, which is IRIS
while I think INDY is a more appropriate name.
On both the machines I have upgraded the harddisk too so I kept the
original disk unchanged as an extra backup from before the upgrading.
--
Knut
(delete 'nogarbage.' for email)
josehill
the volume header? Use fx to lay out your partitions, dvhtool to copy
sash, and mkfs_xfs to create the XFS filesystems on your drive. You
can do all of that by booting from the installation cd (well,
technically, booting from the miniroot created by the installation
cd).
2) Does your Indy have an R5000 cpu? If so, run the following in the
PROM monitor before installing 6.5.22: setenv _R5000_CVT_WAR 0
3) Also while in the PROM monitor, make sure that the PROM environment
variables match your actual hardware environment, particularly the
OSLoad* variables, bootfile, etc. See the man page for PROM (for
example, at http://techpubs.sgi.com) for more info. Consider using the
resetenv command in the PROM monitor to reset the environment variable
to the factory defaults.
4) In IRIX's fx command, "initialize" just means creating a disk's
volume header and partition table. Note that this does not create/
modify filesystems, nor does it check for and remap bad blocks. That's
why sometimes people are surprised when they initialize an IRIX disk
and then find that all of their old files are still on the disk! Use
mkfs after fx to "wipe" a drive clean by making new filesystems. Use
the "auto" command for bad blocks; avoid using the "format" command
unless you really know what you are doing.
-JH
Tristram Scott
The reference I go to for creating a new system disk is IRIX Admin: disks
and filesystems. You can find it on techpubs.sgi.com. Sorry for the long
line, which may wrap.
http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=0650&db=
bks&cmd=toc&pth=/SGI_Admin/IA_DiskFiles
Have a look in chapter 2, particularly the section "Creating a System Disk
From the PROM Monitor"
That contains all the steps you need to follow to set up the new disk.
For installing the operating system, you need to have a complete set of
installation media. Do you have just the four CDs from the Irix 6.5.22
set? These are not sufficient on their own, as they are only overlays, and
do not contain all of what is required for a fresh installation. You will
also need the foundation CDs from a base release of 6.5. Specifically:
Irix 6.5 Foundation 1
Irix 6.5 Foundation 2
Irix 6.5 Applications
Irix 6.5 Development Foundation
Irix 6.5 Development Libraries
As well as this, you will need the set of overlays for 6.5.22 (assuming you
wish to bring the system up to 6.5.22 level). The Development CDs are not
required unless you want to do software development.
If you don't have the foundation CDs and the Applications CD then the
install isn't going to happen. However, it doesn't sound as though you
have made it that far yet, and I think that either you need to go through
the instructions from the disks and filesystems book more carefully, or
that you have a hardware or media problem.
Are you able to boot from the installation CD? If you are, then it
presumably has a working copy of the fx.ARCS. In that case, perhaps it is
the scsi disk at fault. Do you have another scsi disk you can try?
A simple no fuss solution would be to have someone ship you a scsi disk all
set up with Irix on it. Ian Mapleson is a name that springs to mind, but I
am sure others can also help.
--
Dr Tristram J. Scott
Energy Consultant
maximuslivius
> 1) Is there a reason why you are not using dvhtool to copy sash into
> the volume header? Use fx to lay out your partitions, dvhtool to copy
> sash, and mkfs_xfs to create the XFS filesystems on your drive. You
> can do all of that by booting from the installation cd (well,
> technically, booting from the miniroot created by the installation
> cd).
As far as I know dvhtool runs under the IRIX OS fully installed, is
that right ?
Is there a way to run dvhtool on a clean install procedure that is
without
having the OS fully installed.
How to you run dvhtool from sash ?
> 2) Does your Indy have an R5000 cpu? If so, run the following in the
> PROM monitor before installing 6.5.22: setenv _R5000_CVT_WAR 0
Yes,
System: IP22
Processor: 150 Mhz R5000, with FPU
Primary I-cache size: 32 Kbytes
Primary D-cache size: 32 Kbytes
Secondary cache size: 512 Kbytes
Memory size: 256 Mbytes
Graphics: Indy 24-bit
SCSI Disk: scsi(0)disk(1)
SCSI Tape: scsi(0)tape(4)
SCSI CDROM: scsi(0)cdrom(5)
Audio: Iris Audio Processor: version A2 revision
4.1.0
I have set :
setenv _R5000_CVT_WAR 0
> 3) Also while in the PROM monitor, make sure that the PROM environment
> variables match your actual hardware environment, particularly the
> OSLoad* variables, bootfile, etc. See the man page for PROM (for
> example, at http://techpubs.sgi.com) for more info. Consider using the
> resetenv command in the PROM monitor to reset the environment variable
> to the factory defaults.
sash: printenv
AutoLoad=Yes
TimeZone=PST8PDT
console=d1
diskless=0
dbaud=9600
volume=20
sgilogo=y
autopower=y
netaddr=192.168.1.222
eaddr=08:00:69:0a:2b:fe
ConsoleOut=serial(0)
ConsoleIn=serial(0)
cpufreq=150
SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
OSLoadFilename=/unix
OSLoader=sash
OSLoadOptions=INST
Install says:
sash: install
Select device for installation:
1 - tape scsi(0)tape(4)tape(0)
2 - CD-ROM scsi(0)cdrom(5)rdisk(0)
which? 2
Copying installation program to disk.
......... 10% ......... 20% ......... 30% ......... 40% ......... 50%
......... 60% ......... 70% ......... 80% ......... 90% ......... 100%
Copy complete
Unable to load scsi(0)disk(1)rdisk(0)partition(1)/unix: no such file
or directory
Failed to boot
> 4) In IRIX's fx command, "initialize" just means creating a disk's
> volume header and partition table. Note that this does not create/
> modify filesystems, nor does it check for and remap bad blocks. That's
> why sometimes people are surprised when they initialize an IRIX disk
> and then find that all of their old files are still on the disk! Use
> mkfs after fx to "wipe" a drive clean by making new filesystems. Use
> the "auto" command for bad blocks; avoid using the "format" command
> unless you really know what you are doing.
>
> -JH
I am using now a brand new SCSI hard drive out of the anti static bag.
sash: boot -f dksc(0,5,7)stand/fx.ARCS --x
95040+26448+7168+2805248+50056d+5908+8928 entry: 0x97ccea40
SGI Version 6.5 ARCS BE Oct 6, 2003
fx: "device-name" = (dksc)
fx: ctlr# = (0)
fx: drive# = (1)
...opening dksc(0,1,0)
...drive selftest...OK
Scsi drive type == HP 9.10GB C 80-BX02BX02
----- please choose one (? for help, .. to quit this menu)-----
[exi]t [d]ebug/ [l]abel/ [a]uto
[b]adblock/ [exe]rcise/ [r]epartition/
from label:
----- please choose one (? for help, .. to quit this menu)-----
[sh]ow/ [sy]nc [se]t/ [c]reate/
fx/label>
I can not find any "initialize" option on FX.
Would you please inform the directions to the "initialize" option in
FX ?
Thanks.
Luiz Regis
"Lord have mercy"
maximuslivius
> the volume header? Use fx to lay out your partitions, dvhtool to copy
> sash, and mkfs_xfs to create the XFS filesystems on your drive. You
> can do all of that by booting from the installation cd (well,
> technically, booting from the miniroot created by the installation
> cd).
As far as I know dvhtool runs under the IRIX OS fully installed, is
that right ?
Is there a way to run dvhtool on a clean install procedure that is
without
having the OS fully installed.
How to you run dvhtool from sash ?
> 2) Does your Indy have an R5000 cpu? If so, run the following in the
> PROM monitor before installing 6.5.22: setenv _R5000_CVT_WAR 0
Yes,
System: IP22
Processor: 150 Mhz R5000, with FPU
Primary I-cache size: 32 Kbytes
Primary D-cache size: 32 Kbytes
Secondary cache size: 512 Kbytes
Memory size: 256 Mbytes
Graphics: Indy 24-bit
SCSI Disk: scsi(0)disk(1)
SCSI Tape: scsi(0)tape(4)
SCSI CDROM: scsi(0)cdrom(5)
Audio: Iris Audio Processor: version A2 revision
4.1.0
I have set :
setenv _R5000_CVT_WAR 0
> 3) Also while in the PROM monitor, make sure that the PROM environment
> variables match your actual hardware environment, particularly the
> OSLoad* variables, bootfile, etc. See the man page for PROM (for
> example, at http://techpubs.sgi.com) for more info. Consider using the
> resetenv command in the PROM monitor to reset the environment variable
> to the factory defaults.
sash: printenv
Install says:
> 4) In IRIX's fx command, "initialize" just means creating a disk's
> volume header and partition table. Note that this does not create/
> modify filesystems, nor does it check for and remap bad blocks. That's
> why sometimes people are surprised when they initialize an IRIX disk
> and then find that all of their old files are still on the disk! Use
> mkfs after fx to "wipe" a drive clean by making new filesystems. Use
> the "auto" command for bad blocks; avoid using the "format" command
> unless you really know what you are doing.
>
> -JH
I am using now a brand new SCSI hard drive out of the anti static bag.