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
SMARTPQI(4)						     Linux Programmer's Manual						       SMARTPQI(4)

NAME
smartpqi - Microsemi Smart Family SCSI driver SYNOPSIS
modprobe smartpqi [disable_device_id_wildcards={0|1}] [disable_heartbeat={0|1}] [disable_ctrl_shutdown={0|1}] [lockup_action={none|reboot|panic}] DESCRIPTION
smartpqi is a SCSI driver for Microsemi Smart Family controllers. Supported ioctl() operations For compatibility with applications written for the cciss(4) and hpsa(4) drivers, many, but not all of the ioctl(2) operations supported by the hpsa driver are also supported by the smartpqi driver. The data structures used by these operations are described in the Linux kernel source file include/linux/cciss_ioctl.h. CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD These operations all do exactly the same thing, which is to cause the driver to re-scan for new devices. This does exactly the same thing as writing to the smartpqi-specific host rescan attribute. CCISS_GETPCIINFO This operation Returns the PCI domain, bus, device and function and "board ID" (PCI subsystem ID). CCISS_GETDRIVVER This operation returns the driver version in four bytes, encoded as: (major_version << 28) | (minor_version << 24) | (release << 16) | revision CCISS_PASSTHRU Allows BMIC and CISS commands to be passed through to the controller. Boot options disable_device_id_wildcards={0|1} Disables support for device ID wildcards. The default value is 0. disable_heartbeat={0|1} Disables support for the controller's heartbeat check. This parameter is used for debugging purposes. The default value is 0, leaving the controller's heartbeat check active. disable_ctrl_shutdown={0|1} Disables support for shutting down the controller in the event of a controller lockup. The default value is 0. lockup_action={none|reboot|panic} Specifies the action the driver takes when a controller lockup is detected. The default action is none. parameter action --------------------------------------------- none take controller offline only reboot reboot the system panic panic the system FILES
Device nodes Logical drives are accessed via the SCSI disk driver (sd), tape drives via the SCSI tape driver (st), and the RAID controller via the SCSI generic driver (sg), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively. SmartPQI-specific host attribute files in /sys /sys/class/scsi_host/host*/rescan The host rescan attribute is a write-only attribute. Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g., hot-plugged tape drives, or newly configured or deleted logical drives) and notify the SCSI mid-layer of any changes detected. Usually this action is triggered automatically by configuration changes, so the user should not normally have to write to this file. Doing so may be useful when hot-plugging devices such as tape drives or entire storage boxes containing pre- configured logical drives. /sys/class/scsi_host/host*/version The host version attribute is a read-only attribute. This attribute contains the driver version and the controller firmware ver- sion. For example: $ cat /sys/class/scsi_host/host1/version driver: 1.1.2-126 firmware: 1.29-112 /sys/class/scsi_host/host*/lockup_action The host lockup_action attribute is a read/write attribute. This attribute will cause the driver to perform a specific action in the unlikely event that a controller lockup has been detected. See OPTIONS above for an explanation of the lockup_action values. SmartPQI-specific disk attribute files in /sys In the file specifications below, c stands for the number of the appropriate SCSI controller, b is the bus number, t the target number, and l is the logical unit number (LUN). /sys/class/scsi_disk/c:b:t:l/device/raid_level The raid_level attribute is read-only. This attribute contains the RAID level of each logical drive. For example: $ cat /sys/class/scsi_disk/4:0:0:0/device/raid_level RAID 0 /sys/class/scsi_disk/c:b:t:l/device/sas_address The sas_address attribute is read-only. This attribute contains the unique identifier of the disk. For example: $ cat /sys/class/scsi_disk/1:0:3:0/device/sas_address 0x5001173d028543a2 /sys/class/scsi_disk/c:b:t:l/device/ssd_smart_path_enabled The ssd_smart_path_enabled attribute is read-only. This attribute is for ioaccel-enabled volumes. (Ioaccel is an alternative driver submission path that allows the driver to send I/O requests directly to backend SCSI devices, bypassing the controller firmware. This results in an increase in performance. This method is used for HBA disks and for logical volumes comprised of SSDs.) Contains 1 if ioaccel is enabled for the volume and 0 otherwise. For example: $ cat /sys/class/scsi_disk/1:0:3:0/device/ssd_smart_path_enabled 0 VERSIONS
The smarpqi driver was added in Linux 4.9. NOTES
Configuration To configure a Microsemi Smart Family controller, refer to the User Guide for the controller, which can be found by searching for the spe- cific controller at <https://storage.microsemi.com/>. SEE ALSO
cciss(4), hpsa(4), sd(4), st(4) Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source tree. Linux 2017-10-19 SMARTPQI(4)
All times are GMT -4. The time now is 04:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy