| Author |
mount or boot DEC alpha disk |
splu
Member
Posts: 12
Joined: 07.11.13 |
| Posted on November 09 2013 21:51 |
|
|
Hi:
Recently, my friend asks me to help him migrating S/W from DEC alpha PC.
Unfortunately, he just passes me a dump disk image file.
Dec alpha PC is made by Meiden, a Japanese company.
There is a SCSI add-on card, converts SCSI to IDE.
There are 2 IDE HD as RAID, mirror.
OS version is 4.0D (Rev.878)
I tried to boot this disk image in emulator, emuvm, but failed.
I send mail for help. They told me the version is too old.
So, would you please advise how to boot it in any emulator,
Or how can I mount this disk image file under linux or any Unix?
Thanks. |
|
|
| Author |
RE: mount or boot DEC alpha disk |
Bruce Claremont
Member
Posts: 623
Joined: 07.01.10 |
| Posted on November 10 2013 03:36 |
|
|
|
If the disk image is intact, "b dka0" would do the job under FreeAXP. |
|
|
| Author |
RE: mount or boot DEC alpha disk |
splu
Member
Posts: 12
Joined: 07.11.13 |
| Posted on November 10 2013 12:22 |
|
|
I've tried couple emulator and here is result:
emuvm
---------- emuvm message after b dka0 -----------
Digital UNIX boot - Mon Dec 29 18:50:44 EST 1997
Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x10538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x10002013e>
Sizes:
text = 4578896
data = 757632
bss = 1311808
Starting at 0xfffffc00005370a0
Loading vmunix symbol table ... [1276224 bytes]
WARNING: proc_type 0xd / sys_type 0x22 unknown
No B-cache detected
Alpha boot: available memory from 0xc1c000 to 0x8000000
Digital UNIX V4.0D (Rev. 878); Wed May 17 16:11:04 JST 2000
physical memory = 128.00 megabytes.
available memory = 115.89 megabytes.
using 483 buffers containing 3.77 megabytes of memory
** Watchdog Timer can't be set unless it is disabled
AlphaServer ES40 833 MHz system
Alpha 21164A/833MHz CPU 128MB Memory 1MB External Cache
Firmware revision: 13.0-0
OSF/1 PALcode version 1.62
pci0 at nexus
lvm0: configured.
lvm1: configured.
configure_console: No serial driver from get_info
No kernel console driver installed
bootdevice_parser: unknown protocol name 'SCSI'
setconf: Bootdevice parser failed to translate bootdevice SCSI 0 1 0 0 2 0 0.
panic (cpu 0): setconf: bootdevice_parser failed
DUMP: No primary swap, no explicit dumpdev.
-------------- end of emuvm mesage ----------
The following result is in PersonalAlpha
------- message after "b dka0" -----------
Digital UNIX boot - Mon Dec 29 18:50:44 EST 1997
Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x100538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x2012d>
Sizes:
text = 4578896
data = 757632
bss = 1311808
Starting at 0xfffffc00005370a0
Loading vmunix symbol table ... [1276224 bytes]
Machine Check SYSTEM Fatal Abort
Machine Check Code = 15
Unknown machine check code 0x15
<then cpu dump data>
----------------- end of message ---------
Then I tried in stromasys
---------- message in putty ------------------
block 0 of dka0.0.0.6.0 is a valid boot block
reading 16 blocks from dka0.0.0.6.0
bootstrap code read in
base = 1f2000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1e4000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Digital UNIX boot - Mon Dec 29 18:50:44 EST 1997
Loading vmunix ...
Loading at fffffc0000230000
Current PAL Revision <0x1000000010538>
Switching to OSF PALcode Succeeded
New PAL Revision <0x100000002012e>
Sizes:
text = 4578896
data = 757632
bss = 1311808
Starting at 0xfffffc00005370a0
Loading vmunix symbol table ... [1276224 bytes]
Alpha boot: available memory from 0xc1c000 to 0x7ffe000
Digital UNIX V4.0D (Rev. 878); Wed May 17 16:11:04 JST 2000
physical memory = 128.00 megabytes.
available memory = 115.88 megabytes.
using 484 buffers containing 3.78 megabytes of memory
---------------------- end of message ------------
Then a title "FreeAXP Failure" windows pops up.
----------- following is message inside the window ------
An error has occurred in FreeAXP.
ESL-F-RTM: Runtime error in 'class CEv4'.'cpu0' thread
Runtime exception: AXP-F-CPUEXC: cp(control).alpha(alpha(AS400)).cpu0(EV4): Exception in CPU thread: Not implemented:
AC4-F-RDUNKCSR: ReadCsr 1280(a000): ..\..\src\alpha\Dc21071Ca.cpp line 539, function 'CDc21071Ca:ReadCsr'.
:
:
--------- end of message ------
|
|
|
| Author |
RE: mount or boot DEC alpha disk |
splu
Member
Posts: 12
Joined: 07.11.13 |
| Posted on November 10 2013 12:25 |
|
|
|
I think this disk image should be intact. Am I right? |
|
|
| Author |
RE: mount or boot DEC alpha disk |
Bruce Claremont
Member
Posts: 623
Joined: 07.01.10 |
| Posted on November 11 2013 01:47 |
|
|
|
Try "b -fl a dka0" |
|
|
| Author |
RE: mount or boot DEC alpha disk |
splu
Member
Posts: 12
Joined: 07.11.13 |
| Posted on November 11 2013 03:29 |
|
|
"boot dka0 -flags A"
I've tried, result is same.
From the message of emuvm,
bootdevice_parser: unknown protocol name 'SCSI'
then halt.
I think, vmunix can not mount swap, other partition, so OS halt.
The reason probably is:
1. SCSI card is different with real one. So, OS halt.
2. SCSI lun, id is different with real one. So OS halt.
|
|
|
| Author |
RE: Try the generic kernel or the CD |
John Manger
Member
Posts: 63
Location: nr Heathrow, Middlesex, UK
Joined: 18.03.10 |
| Posted on November 11 2013 03:31 |
|
|
You have two choices when moving from one Alpha type to another.
1) Boot from the o/s CD, build a new system disk and restore/merge the files from your original system, or disks.
OR
2) Boot from the old system disk using the Generic kernel /genvmunix, and build a new kernel that supports the new Alpha's architecture (ie. the platform type).
For '2', you could do something like :
>>> boot dkaXXX -flags 1 -file /genvmunix
That should take you to single user with the hardware recognised, and root mounted read-only.
If that works, you could either run from genvmunix 'for ever', or rebuild yourself a new kernel.
Section 5 of the Tru64 System Admin manual has good discussion of how to do this. The V4 doc set is still online at HP. For example :
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/APS2RFTE/CNFGMNTC.HTM#device-config-sec
You will need to run bcheckrc, sizer -n, do some editing of the new config file, and use doconfig to build a new 'vmunix', as per section 5.4.1 of the V4 manual above. Do not delete or overwrite genvmunix.
regards,
John M |
|
|
| Author |
RE: mount or boot DEC alpha disk |
splu
Member
Posts: 12
Joined: 07.11.13 |
| Posted on November 12 2013 14:50 |
|
|
boot into single user mode works in one of the emulators.
Thanks.
|
|
|
| Author |
RE: mount or boot DEC alpha disk |
splu
Member
Posts: 12
Joined: 07.11.13 |
| Posted on November 12 2013 16:03 |
|
|
OK. Now I've already figure out what's going on.
I summary the procedures what I've done.
For those who encounter same problem as me can refer.
In the beginning boot genvmunix into single user mode by command
"boot dka0 -file /genvmunix -flags 1"
After shell "#" appear,
Check the file /etc/fstab to see where /usr is located in which SCSI lun.
Then shutdown switch disk to original SCSI lun position.
And boot by command
"boot dkaXX -file /genvmunix
Now , enter unix multi-tasking env. You may do what you want to do next.
Thanks for help. |
|
|
