- Thank you received: 0
FreeAXP-Tru64 UNIX Unmount File
- Paolo_R
- Topic Author
- Visitor
6 years 8 months ago #5657
by Paolo_R
FreeAXP-Tru64 UNIX Unmount File was created by Paolo_R
I'm running Tru64 UNIX on FreeAXP. I am not sure how to relate a FreeAXP file to the appropriate UNIX file system for unmounting.
In the Alpha Configuration facility I have disk0.0 as an image file with a file name of 'Tru64 UNIX 5.1B Associated Products Volume 1.iso (RRD42)' and the CD-ROM box checked.
When I issue a df command I get the following:
# df
Filesystem 512-blocks Used Available Capacity Mounted on
root_domain#root 786432 249080 524480 33% /
/proc 0 0 0 100% /proc
usr_domain#usr 4300800 1668484 2359248 42% /usr
usr_domain#var 4300800 236142 2359248 10% /var
I want to unmount the *.iso file shown above. Issuing a 'sh dev' gives
>>>sh dev
dka0.0.0.6.0 DKA0 RRD42 4.5d
I basically don't know which usr_domain relates to the *.iso and what unmount command to issue.
Thanks
In the Alpha Configuration facility I have disk0.0 as an image file with a file name of 'Tru64 UNIX 5.1B Associated Products Volume 1.iso (RRD42)' and the CD-ROM box checked.
When I issue a df command I get the following:
# df
Filesystem 512-blocks Used Available Capacity Mounted on
root_domain#root 786432 249080 524480 33% /
/proc 0 0 0 100% /proc
usr_domain#usr 4300800 1668484 2359248 42% /usr
usr_domain#var 4300800 236142 2359248 10% /var
I want to unmount the *.iso file shown above. Issuing a 'sh dev' gives
>>>sh dev
dka0.0.0.6.0 DKA0 RRD42 4.5d
I basically don't know which usr_domain relates to the *.iso and what unmount command to issue.
Thanks
Please Log in or Create an account to join the conversation.
- John_Manger
- Offline
- Moderator
Less
More
6 years 8 months ago #5658
by John_Manger
Replied by John_Manger on topic RE: FreeAXP-Tru64 UNIX Unmount File
In your example, if you are running in multi-user mode booted from rz0/dsk0/dka0, you do not have the CD iso mounted.... therefore you cannot unmount it.
A 'showfdmn root_domain' will show the disk name for the root domain... usr_domain for the usr_domain and so on ... The result will probably be rz0x or dsk0x. And, if this is V5.x, a 'hwmgr -v d' will list the available disks and cdroms and show their names.
On all versions, 'scu sho edt' will show the scsi layout and disks as discovered at kernel boot.
Tru64 does not mount iso images 'automatically'. They may be mounted manually, or can be included in /etc/fstab for mounting at boot time (like an ordinary disk or partition).
John M<hr>
A 'showfdmn root_domain' will show the disk name for the root domain... usr_domain for the usr_domain and so on ... The result will probably be rz0x or dsk0x. And, if this is V5.x, a 'hwmgr -v d' will list the available disks and cdroms and show their names.
On all versions, 'scu sho edt' will show the scsi layout and disks as discovered at kernel boot.
Tru64 does not mount iso images 'automatically'. They may be mounted manually, or can be included in /etc/fstab for mounting at boot time (like an ordinary disk or partition).
John M<hr>
Please Log in or Create an account to join the conversation.
- Paolo_R
- Topic Author
- Visitor
6 years 8 months ago #5659
by Paolo_R
Replied by Paolo_R on topic RE: FreeAXP-Tru64 UNIX Unmount File
John
Here is the output of the commands you suggested:
┌─┬─┬─┬─┬─┬─┬─┠V i r t u a l serial0
│F│r│e│e│A│X│P│ A l p h a on emulator ALPHA02 (128 M<img src='../images/smiley/cool.gif' alt='smiley'>
└─┴─┴─┴─┴─┴─┴─┘ x64 version 3.0.0.617
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.ea.e9.e8.e7.e6.....e5.
V7.0-9, built on Mar 18 1999 at 13:25:37
>>>showfdmn root_domain
showfdmn: No such command
>>>hwmgr -v d
hwmgr: No such command
>>>'scu sho edt
'scu: No such command
>>>
The *.iso file is residing on my WIndows desktop which is where the Alpha Configuration Utility is pointing. If I move this *.iso file and try and restart Tru64 UNIX I get this error:
"An error has occurred in FreeAXP:
DFL-F-NOFILE:cp(control).alpha(alpha(AS400)).pcibus(dc21071d).pci6(symbios).disk0.0(file):File does not exist or cannot be opened ... (snip)"
The path to the *.iso file is 'hardcoded' in the ALPHA02.cfg file:
pci6 = symbios
{
disk0.0 = file
{
image = "C:\Users\Paul\Desktop\Tru64 UNIX 5.1B\Tru64 UNIX 5.1B - Disk 2 Associated Products Volume 1 [DEC Alpha]\Tru64 UNIX 5.1B - Associated Products Volume 1.iso"
}
disk0.1 = file
{
vendor = "DEC"
model_num = "RZ29B"
rev_num = "0016"
image = "H:\Tru64UNIX\DISK01.img"
autocreate_size = 4290600960;
}
}
So I'm not sure what to do next.
Paul
Here is the output of the commands you suggested:
┌─┬─┬─┬─┬─┬─┬─┠V i r t u a l serial0
│F│r│e│e│A│X│P│ A l p h a on emulator ALPHA02 (128 M<img src='../images/smiley/cool.gif' alt='smiley'>
└─┴─┴─┴─┴─┴─┴─┘ x64 version 3.0.0.617
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.f4.eb.ea.e9.e8.e7.e6.....e5.
V7.0-9, built on Mar 18 1999 at 13:25:37
>>>showfdmn root_domain
showfdmn: No such command
>>>hwmgr -v d
hwmgr: No such command
>>>'scu sho edt
'scu: No such command
>>>
The *.iso file is residing on my WIndows desktop which is where the Alpha Configuration Utility is pointing. If I move this *.iso file and try and restart Tru64 UNIX I get this error:
"An error has occurred in FreeAXP:
DFL-F-NOFILE:cp(control).alpha(alpha(AS400)).pcibus(dc21071d).pci6(symbios).disk0.0(file):File does not exist or cannot be opened ... (snip)"
The path to the *.iso file is 'hardcoded' in the ALPHA02.cfg file:
pci6 = symbios
{
disk0.0 = file
{
image = "C:\Users\Paul\Desktop\Tru64 UNIX 5.1B\Tru64 UNIX 5.1B - Disk 2 Associated Products Volume 1 [DEC Alpha]\Tru64 UNIX 5.1B - Associated Products Volume 1.iso"
}
disk0.1 = file
{
vendor = "DEC"
model_num = "RZ29B"
rev_num = "0016"
image = "H:\Tru64UNIX\DISK01.img"
autocreate_size = 4290600960;
}
}
So I'm not sure what to do next.
Paul
Please Log in or Create an account to join the conversation.
- Paolo_R
- Topic Author
- Visitor
6 years 8 months ago #5660
by Paolo_R
Replied by Paolo_R on topic RE: FreeAXP-Tru64 UNIX Unmount File
John
Sorry. I issued the commands before the login process. I have now issue them correctly and am trying now to decipher them
Sorry. I issued the commands before the login process. I have now issue them correctly and am trying now to decipher them
Please Log in or Create an account to join the conversation.
- Paolo_R
- Topic Author
- Visitor
6 years 8 months ago #5661
by Paolo_R
Replied by Paolo_R on topic RE: FreeAXP-Tru64 UNIX Unmount File
So :
# hwmgr -v d
HWID: Device Name Mfg Model Location
3: /dev/dmapi/dmapi
4: /dev/scp_scsi
5: /dev/kevm
27: /dev/disk/dsk0c DEC RZ29B bus-0-targ-1-lun-0
28: /dev/random
29: /dev/urandom
33: /dev/disk/dsk1c DEC RZ58 bus-0-targ-0-lun-0 <<<===
The image "C:\Users\Paul\Desktop\Tru64 UNIX 5.1B\Tru64 UNIX 5.1B - Disk 2 Associated Products Volume 1 [DEC Alpha]\Tru64 UNIX 5.1B - Associated Products Volume 1.iso" is shown as a model RZ58 in the Config Utility.
Issuing umount /dev/disk/dsk1c gives /dev/disk/dsk1c: not currently mounted.
So it's not mounted according to UNIX but the *.iso file is being referenced via the *.cfg file.
I'm afraid I'm stuck.
# hwmgr -v d
HWID: Device Name Mfg Model Location
3: /dev/dmapi/dmapi
4: /dev/scp_scsi
5: /dev/kevm
27: /dev/disk/dsk0c DEC RZ29B bus-0-targ-1-lun-0
28: /dev/random
29: /dev/urandom
33: /dev/disk/dsk1c DEC RZ58 bus-0-targ-0-lun-0 <<<===
The image "C:\Users\Paul\Desktop\Tru64 UNIX 5.1B\Tru64 UNIX 5.1B - Disk 2 Associated Products Volume 1 [DEC Alpha]\Tru64 UNIX 5.1B - Associated Products Volume 1.iso" is shown as a model RZ58 in the Config Utility.
Issuing umount /dev/disk/dsk1c gives /dev/disk/dsk1c: not currently mounted.
So it's not mounted according to UNIX but the *.iso file is being referenced via the *.cfg file.
I'm afraid I'm stuck.
Please Log in or Create an account to join the conversation.
- Paolo_R
- Topic Author
- Visitor
6 years 8 months ago #5662
by Paolo_R
Replied by Paolo_R on topic RE: FreeAXP-Tru64 UNIX Unmount File
I've solved the problem.
Please Log in or Create an account to join the conversation.
Moderators: iamcamiel
Time to create page: 0.209 seconds