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
format(1M)																format(1M)

NAME
format - format an HP SCSI disk array LUN SYNOPSIS
device_file DESCRIPTION
formats one LUN of the HP SCSI disk array associated with device file, device_file. The format will usually be a soft or zeroing format, in which the controller writes zeroes to the data area and parity area, if any, of the LUN. NOTE: The above should always be true of a sub-LUN, but the controller might decide, based on certain conditions, to do a full format of a regular LUN, which consists of sending a mode select and a media initialization command to the physical drive(s) in question, fol- lowed by zeroing the data and parity area, if any. The conditions which will cause a full format to be done are as follows: 1. The controller received a Mode Select command which requires a drive sector size change. 2. The controller received a Mode Select command which changed a parameter in the Format Device Page(0x03). 3. The LUN contains one or more failed drives. In this case only a certain subset of the drives containing the failed drives will be formatted. 4. Either the FmtData or the CmpLst bit in the Format Unit CDB is set. RETURN VALUE
returns the following values: 0 Successful completion. -1 Command failed. DIAGNOSTICS AND ERRORS
Errors can originate from problems with: o o SCSI (device level) communications o system calls Error messages generated by format: An error in command syntax has occurred. Enter command again with all required arguments, in the order shown. To ensure that does not modify a disk array that is being used by another process, attempts to obtain exclusive access to the disk array. If the disk array is already opened by another process (for example, LVM -- the Logical Volume Manager), a "" error message is returned by the driver. To eliminate the "" condition, determine what process has the device open. In the case of LVM, it is necessary to deactivate the volume group containing the array before formatting array LUNs (see vgchange(1M)). The LUN number, which is derived from the device file name, is out of range. The addressed LUN is not configured, and thus is not known to the array controller. Utilities must be able to open the device file for raw access. The device being addressed is not an HP SCSI disk array. SCSI (device level) communication errors: Sense data associated with the failed operation is printed. Error messages generated by system calls: uses the following system calls: and Documentation for these HP-UX system calls contains information about the specific error conditions associated with each call. does not alter the value of The interpretation of for printing purposes is performed by the system utility EXAMPLES
To format the HP SCSI disk array LUN on a Series 800: WARNING
The command will destroy all user data on the addressed LUN. DEPENDENCIES
The HP C2425 and HP C2427 disk arrays are only supported on Series 700 systems running HP-UX version 9.0X. The HP C2430 disk array is supported on Series 700 and 800 systems running HP-UX versions 9.0X and 10.0X. AUTHOR
was developed by HP. format(1M)
All times are GMT -4. The time now is 07:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy