cloned old system (SCO v4.2) from mylex SCSI RAID (mirroring) to an ATA drive
Mixalis Bafiadis
server has 2 SCSI 1GB drives (mirroring). The destination drive is a
simple ATA 40GB drive. The image creation was successful.
The problem is that the system does not boot from the ATA drive,
throwing the following warnings/errors:
F15
WARNING: SCSI boot option(s) ignored: Unknown host adapter driver
F17
WARNING: hd: no root disk controller
H6
PANIC: srmountfun - Error 19 mounting rootdev (1/40)
UNIX is a registered trademark...
SCO UNIX System V/386 Release 3.2v4.2 Operating System
kernel id 93/04/28 on a Pentium(tm) cpu Serial Numer: ...
%fpu - 13 - type:80386
Unexpected trap in kernel mode:
DOUBLE PANIC: k_trap - Kernel mode trap type 0x00000006
I tried using ghost... same results
I tried booting a virtual machine from the Acronis image file using
VMware & virtualbox, same results
It obviously ignoring the SCSI controller (WARNING: SCSI boot options
ignored), which is a good thing since it's no longer attached to the
machine.
It obviously successfully mounted the ATA drive... since it is booting
(up to the point it panics)
Could somebody please enlighten me on what might be wrong, and how may
i fix it.
Thanks in advance!
Steve M. Fabac, Jr.
> I used Acronis to create a clone of an old SCO 3.2v4.2 server. The
> server has 2 SCSI 1GB drives (mirroring). The destination drive is a
> simple ATA 40GB drive. The image creation was successful.
> The problem is that the system does not boot from the ATA drive,
> throwing the following warnings/errors:
>
> F15
> WARNING: SCSI boot option(s) ignored: Unknown host adapter driver
> F17
> WARNING: hd: no root disk controller
> H6
> PANIC: srmountfun - Error 19 mounting rootdev (1/40)
> UNIX is a registered trademark...
> SCO UNIX System V/386 Release 3.2v4.2 Operating System
> kernel id 93/04/28 on a Pentium(tm) cpu Serial Numer: ...
> %fpu - 13 - type:80386
> Unexpected trap in kernel mode:
> DOUBLE PANIC: k_trap - Kernel mode trap type 0x00000006
>
> I tried using ghost... same results
I have used Ghost to move a Compaq SCSI image from old hard disk
to new hard disk on the same Compaq machine.
> I tried booting a virtual machine from the Acronis image file using
> VMware & virtualbox, same results
>
> It obviously ignoring the SCSI controller (WARNING: SCSI boot options
> ignored), which is a good thing since it's no longer attached to the
> machine.
> It obviously successfully mounted the ATA drive... since it is booting
> (up to the point it panics)
> Could somebody please enlighten me on what might be wrong, and how may
> i fix it.
> Thanks in advance!
>
>
Sounds like you don't have WD hard disk drivers linked into the 3.2v4.2 kernel.
My suggestion is to run mkdev hd on the running 3.2v4.2 system and add a second
hard disk using WD as the host controller. Then relink the kernel and do
the ghost copy again.
When you try to boot on the AT controller use the command:
defbootstr Sdsk=wd(0,0,0) (if the ATA disk is master on primary controller).
I have recently moved a client's ATA 3.2v4.2 system from an old hard disk
to a new hard disk using Backup Edge after restoring his full system cpio backup
from tape to my office 5.0.7 system to the /iso/customer subdirectory.
I ran backup edge and created a bootable CD of the client's system.
I had problems restoring it to a 30G hard drive on a system with identical
motherboard as the client (P/I-XP55T2P4). The CD would not boot (5.0.7 kernel).
I was able to boot the cd when the hard drive was installed in an ASUS
P4GMX system with 2.4GHz Celeron and restore the backup to the 30G hard drive.
However, the restored system would not boot on the Celeron, but would
only boot and run on the system that was a copy of the client's
ASUS P/I-XP55T2P4 with 200MHz Pentium processor.
So you may have trouble running your cloned 3.2v4.2 system on modern hardware.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
Robert T. Repko (R Squared Consultants)
Compaq Server running 5.0.7. My client was concerned about their old
server dieing and wanted their programs moved to a newer server.
1) I first installed 5.0.7 on the newer Server.
2) I performed a Lone-Tar backup, to a file, of the old Compaq Server
(I couldn't get their tape drive to work)
3) Performed a non-destructive restore (lone-tar -Nvf tar-file) from
the tar file to the newer Compaq Server.
The system boots just fine. I do see some entries in custom
pertaining to 5.0.4 which I'm removing without any ill effects.
***************************
* Robert T. Repko *
* R Squared Consultants *
* 4 Juniper Ave. *
* Easton, PA 18045 *
* (610) 360-1117 (mobile) *
* (610) 253-0725 (fax) *
***************************
Nico Kadel-Garcia
<r...@rsquared.com> wrote:
> I just 'moved' a 5.0.4 system from an old Compaq Server to a newer
> Compaq Server running 5.0.7. My client was concerned about their old
> server dieing and wanted their programs moved to a newer server.
>
> 1) I first installed 5.0.7 on the newer Server.
> 2) I performed a Lone-Tar backup, to a file, of the old Compaq Server
> (I couldn't get their tape drive to work)
> 3) Performed a non-destructive restore (lone-tar -Nvf tar-file) from
> the tar file to the newer Compaq Server.
>
> The system boots just fine. I do see some entries in custom
> pertaining to 5.0.4 which I'm removing without any ill effects.
The difference between 3.2v4.2, and 5.0.4, is pretty profound. I don't
think you should consider that as any sort of assurance that a similar
procedure will work for such an old OS.
Frankly, I'd consider stuffing it into a VMWare virtualization setup
and get away from the hardware compatibility issues. Alternatively,
I'd shoot it dead and upgrade to something more contemporary, if at
all possible.
John Boland
Morning Mixalis,
The SCO Unix 3.2v4.2 kernel has not mounted the ATA drive at the
point of the panic. The Servers BIOS is used to load the bootstrap
from the
ATA disk, this loads the boot program that then attempts to load
the kernel. The kernel is panicing because its being told to look
for the root filesystem on a SCSI disk connected to a SCSI controller.
Even if you build the wd (ATA) driver into the 3.2v4.2 kernel
its still likely that you will have problems related to the disk
geometry as the geometry of the SCSI disk is going to
be different to the target ATA disk.
If possible, to save yourself time I would recommend doing
a fresh install of the base OS onto the target machine
and then copy across the rest.
John