Sponsored Content
Operating Systems SCO Migrate SCO 5.0.6 to different hardware Post 302442826 by ccc on Thursday 5th of August 2010 02:13:11 PM
Old 08-05-2010
I've done an image of SCO 5.0.6 using g4l and recovered on another hardware.

Now if I try to start then I'm getting this kernel panic:
Code:
CONFIG: No Sdsk SCSI devices configured (unit 0 missing)

WARNING: Test open Failed "hd=Sdsk", no root disk controller

PANIC: srmountfun - Error 6 mounting rootdev hd (1/42)

Error6 opening dumpdev hd(1/41)

Knows someone howto solve this problem?

Last edited by ccc; 08-05-2010 at 05:45 PM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to migrate ?

Currently, I am planning a migration between machine which under True64UNIX. The new machine will run with higher version O/S. My question is, is there any solution on migrating one machine to another which with different O/S version? My goal is keeping minimum impact to the users. Excuse my... (1 Reply)
Discussion started by: coolmans
1 Replies

2. Solaris

Migrate oracle solaris 5.8 5.9

If I have an oracle 9 database environment on a san running solaris 5.8 as the os. Can I plug the san into a Solaris 5.9 environment and have the database work ? - as long as binaries are on the san (1 Reply)
Discussion started by: tim-carroll@com
1 Replies

3. Linux

Mysql Migrate

Hi , I would like to (MYSQL) migrate the all the data from solari's to linux box. I have checked whether mysql is installed or not. rpm -qa | grep -i mysql I confirmed !!!! I want to know the following points. 1) How can get to know what are mysql data files and location as well.... (4 Replies)
Discussion started by: Mani_apr08
4 Replies

4. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies

5. SCO

Migrate UNIXWare from old machine to new machine (different hardware)

Good afternoon all, I'm a bit stuck... I honestly don't know very much about Unix let alone UnixWare for that matter. I have a system that's very old and could fail really at any time. I have another server I'd like to move everything to yet I don't know what's possible. The current server is... (2 Replies)
Discussion started by: rubiks015
2 Replies

6. SCO

SCO 5.0.7v VM Hardware

I run SCO 5.0.7v in ESXi 5.5 and am looking at ways to increase performance. I notice that the VM hardware is still set to 4 and wondered if there was an advantage in raising it or will this cause issues? (0 Replies)
Discussion started by: stewartg
0 Replies

7. SCO

Recommendation for hardware to run SCO OSR 5.0.7 natively

Looking for a modern server to run SCO OSR 5.0.7 without VM (native), h/w must have manufacturers warranty. Requirements would be to accommodate light loads of up to 15 users, app does not take more than 30 - 40 MB of RAM and data stored takes up to 15 - 20 GB, no internet connections... (3 Replies)
Discussion started by: migurus
3 Replies

8. Linux

How to migrate a running lvm.?

Hi all, Please explain how do i. Migrate and backup a running lvm..!! Thanks, Sent from my LG-D802 using Tapatalk (3 Replies)
Discussion started by: lordkizzo
3 Replies

9. AIX

Migrate AIX to new Hardware

Hello Friends/AIXgurus, When you have time, could you please look into below. We're planning to migrate AIX LPARs on to new Hardware. Requirement: Migrate AIX LPARs from POWER 6 to POWER 8 Hardware (*everything should run as is after the transition) Below is our thought process. Ours... (5 Replies)
Discussion started by: System Admin 77
5 Replies
DUMPON(8)						    BSD System Manager's Manual 						 DUMPON(8)

NAME
dumpon -- specify a device for crash dumps SYNOPSIS
dumpon [-v] special_file dumpon [-v] off dumpon [-v] -l DESCRIPTION
The dumpon utility is used to specify a device where the kernel can save a crash dump in the case of a panic. Calls to dumpon normally occur from the system multi-user initialization file /etc/rc, controlled by the ``dumpdev'' variable in the boot time configuration file /etc/rc.conf. The default type of kernel crash dump is the mini crash dump. Mini crash dumps hold only memory pages in use by the kernel. Alternatively, full memory dumps can be enabled by setting the debug.minidump sysctl(8) variable to 0. For systems using full memory dumps, the size of the specified dump device must be at least the size of physical memory. Even though an additional 64 kB header is added to the dump, the BIOS for a platform typically holds back some memory, so it is not usually necessary to size the dump device larger than the actual amount of RAM available in the machine. Also, when using full memory dumps, the dumpon utility will refuse to enable a dump device which is smaller than the total amount of physical memory as reported by the hw.physmem sysctl(8) vari- able. The -l flag causes dumpon to print the current dump device or _PATH_DEVNULL ("/dev/null") if no device is configured. The -v flag causes dumpon to be verbose about its activity. IMPLEMENTATION NOTES
Since a panic(9) condition may occur in a situation where the kernel cannot trust its internal representation of the state of any given file system, one of the system swap devices, and not a device containing a file system, should be used as the dump device. The dumpon utility operates by opening special_file and making a DIOCSKERNELDUMP ioctl(2) request on it to save kernel crash dumps. If special_file is the text string: ``off'', dumpon performs a DIOCSKERNELDUMP ioctl(2) on /dev/null and thus instructs the kernel not to save crash dumps. Since dumpon cannot be used during kernel initialization, the dumpdev variable of loader(8) must be used to enable dumps for system panics which occur during kernel initialization. FILES
/dev/{ada,da}?s?b standard swap areas /etc/rc.conf boot-time system configuration SEE ALSO
fstab(5), rc.conf(5), config(8), init(8), loader(8), rc(8), savecore(8), swapon(8), panic(9) HISTORY
The dumpon utility appeared in FreeBSD 2.1. BUGS
Because the file system layer is already dead by the time a crash dump is taken, it is not possible to send crash dumps directly to a file. BSD
October 8, 2014 BSD
All times are GMT -4. The time now is 06:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy