Sponsored Content
Top Forums UNIX for Advanced & Expert Users Virtualizing SCO v5 - interesting project/nightmare, could use some help Post 302696335 by jgt on Tuesday 4th of September 2012 09:36:18 PM
Old 09-04-2012
I wouldn't bother trying. I have done 5 of these systems (see attachment) this year and I know that 5.0.7 and 6.0.0 both run well on this configuration. 5.0.6 should run, 5.0.5 and older probably will not. If you have 5.0.7 or newer you should also install the multiprocessor software. You do not have to license it.
The last one I did replaced a P4 1.8ghz with 1gb of ram and Mylex RAID controller with 68 pin scsi drives. The new system is at least 4 times faster, and takes up about the same amount of space as a shoe box.

Last edited by jgt; 09-04-2012 at 10:50 PM..
 

7 More Discussions You Might Find Interesting

1. HP-UX

Viewcvs...a nightmare on HP-UX!!!

Hello I'm new on this forum but I have a big problem. I've installed Subversion 1.1.1 and Apache 2.0.52 on a HP-UX. This is the uname: HP-UX xxxx B.11.11 U 9000/800 4169945236 unlimited-user license Now I must to install a software to browse the svn repositories. My choice is Viewcvs. ... (3 Replies)
Discussion started by: goblin79
3 Replies

2. UNIX for Dummies Questions & Answers

is unix really such a nightmare... or is it me?

i rue the day that my server manager and i parted company... the start of a long journey.... :( sometimes i find myself daydreaming about the days when i could say... "this dont work, can u fix it?".... and 2 mins later it worked! i have a new way of "cursing" at ppls.... i just say "failed... (10 Replies)
Discussion started by: mickeymouse
10 Replies

3. BSD

FreeBSD nightmare!!!

Dear friends out there, i hope u'll have enough time to read this problem of mine and try to help me solve it. well, i've been a long time user of microsoft products and happened to come across FreeBSD when one fellow referred me to it saying that it was a wonderful OS which one could use for web... (6 Replies)
Discussion started by: kenyatta
6 Replies

4. Shell Programming and Scripting

ftp nightmare

Hi everyone I have a Fedora FTP server (lets call it FTP-SERVER1) and files are constantly being uploaded to it from a 3rd party. Once every 15 minutes I need to "move" the files from the FTP server to another server (lets call it SVR-WINDOWS) where it will be processed and then deleted. ... (3 Replies)
Discussion started by: soliberus
3 Replies

5. UNIX for Advanced & Expert Users

Help with old DG/UX machine, virtualizing?

Hey all, We have an old Data General Unix system (DG/UX) on an old AViiON machine. That DG system is Intel-based (PentiumPro) and we are trying to virtualize / emulate it. DG was a clever system, as it cannot be installed on a 'regular' x86 machine, only on an AViiON box. I think I figured out... (2 Replies)
Discussion started by: dgux
2 Replies

6. AIX

Virtualizing the Fiber card (VFC) on P595

Hi, We have a P595 machine with a dual port Fiber card per VIOs. We have two VIOs in the box. VIO1: ---> 2 port Fiber Card VIO2: ---> 2 port Fiber Card One port on each fiber card is utilized. Connected to SAN switches. We are getting all disks from SAN both for VIOs and LPARs. Now... (0 Replies)
Discussion started by: aixromeo
0 Replies

7. AIX

Virtualizing Physical Machine

Hi Experts - we have power710 (no VIOs) that is already connected to hmc and everything . I already have a Physical LPAR in there and network configured . Now I plan to delete that LPAR and then put Virtualization code (COD) to virtualize that machine by building VIO servers and stuff.Also ordered... (9 Replies)
Discussion started by: JME2015
9 Replies
MLX(4)							   BSD Kernel Interfaces Manual 						    MLX(4)

NAME
mlx -- Mylex DAC-family RAID driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device pci device mlx Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): mlx_load="YES" DESCRIPTION
The mlx driver provides support for Mylex DAC-family PCI to SCSI RAID controllers, including versions relabeled by Digital/Compaq. HARDWARE
Controllers supported by the mlx driver include: o Mylex DAC960P o Mylex DAC960PD / DEC KZPSC (Fast Wide) o Mylex DAC960PDU o Mylex DAC960PL o Mylex DAC960PJ o Mylex DAC960PG o Mylex DAC960PU / DEC PZPAC (Ultra Wide) o Mylex AcceleRAID 150 (DAC960PRL) o Mylex AcceleRAID 250 (DAC960PTL1) o Mylex eXtremeRAID 1100 (DAC1164P) o RAIDarray 230 controllers, aka the Ultra-SCSI DEC KZPAC-AA (1-ch, 4MB cache), KZPAC-CA (3-ch, 4MB), KZPAC-CB (3-ch, 8MB cache) All major firmware revisions (2.x, 3.x, 4.x and 5.x) are supported, however it is always advisable to upgrade to the most recent firmware available for the controller. Compatible Mylex controllers not listed should work, but have not been verified. DIAGNOSTICS
Controller initialisation phase mlx%d: controller initialisation in progress... mlx%d: initialisation complete The controller firmware is performing/has completed initialisation. mlx%d: physical drive %d:%d not responding The drive at channel:target is not responding; it may have failed or been removed. mlx%d: spinning up drives... Drive startup is in progress; this may take several minutes. mlx%d: configuration checksum error The array configuration has become corrupted. mlx%d: mirror race recovery in progress mlx%d: mirror race on a critical system drive mlx%d: mirror race recovery failed These error codes are undocumented. mlx%d: physical drive %d:%d COD mismatch Configuration data on the drive at channel:target does not match the rest of the array. mlx%d: system drive installation aborted Errors occurred preventing one or more system drives from being configured. mlx%d: new controller configuration found The controller has detected a configuration on disk which supersedes the configuration in its nonvolatile memory. It will reset and come up with the new configuration. mlx%d: FATAL MEMORY PARITY ERROR Firmware detected a fatal memory error; the driver will not attempt to attach to this controller. mlx%d: unknown firmware initialisation error %x:%x:%x An unknown error occurred during initialisation; it will be ignored. Driver initialisation/shutdown phase: mlx%d: can't allocate scatter/gather DMA tag mlx%d: can't allocate buffer DMA tag mlx%d: can't allocate s/g table mlx%d: can't make initial s/g list mapping mlx%d: can't make permanent s/g list mapping mlx%d: can't allocate interrupt mlx%d: can't set up interrupt A resource allocation error occurred while initialising the driver; initialisation has failed and the driver will not attach to this con- troller. mlx%d: error fetching drive status The current status of all system drives could not be fetched; attachment of system drives will be aborted. mlx%d: device_add_child failed mlx%d: bus_generic_attach returned %d Creation of the system drive instances failed; attachment of one or more system drives may have been aborted. mlxd%d: detaching... The indicated system drive is being detached. mlxd%d: still open, can't detach The indicated system drive is still open or mounted; the controller cannot be detached. mlx%d: flushing cache... The controller cache is being flushed prior to detach or shutdown. Operational diagnostics: mlx%d: ENQUIRY failed - %s mlx%d: ENQUIRY2 failed mlx%d: ENQUIRY_OLD failed mlx%d: FLUSH failed - %s mlx%d: CHECK ASYNC failed - %s mlx%d: REBUILD ASYNC failed - %s mlx%d: command failed - %s The controller rejected a command for the reason given. mlx%d: I/O beyond end of unit (%u,%d > %u) mlx%d: I/O error - %s An I/O error was reported by the controller. mlx%d: periodic enquiry failed - %s An attempt to poll the controller for status failed for the reason given. mlx%d: mlx_periodic_enquiry: unknown command %x The periodic status poll has issued a command which has become corrupted. mlxd%d: drive offline mlxd%d: drive online mlxd%d: drive critical The system disk indicated has changed state. mlx%d: physical drive %d:%d reset mlx%d: physical drive %d:%d killed %s mlx%d: physical drive %d:%d error log: sense = %d asc = %x asq = %x mlx%d: info %4D csi %4D The drive at channel:target has been reset, killed for the given reason, or experienced a SCSI error. mlx%d: unknown log message type %x mlx%d: error reading message log - %s An error occurred while trying to read the controller's message log. mlxd%d: consistency check started mlx%d: consistency check completed A user-initiated consistency check has started/completed. mlx%d: drive rebuild started for %d:%d mlx%d: drive rebuild completed A user-initiated physical drive rebuild has started/completed. mlx%d: background check/rebuild operation started mlx%d: background check/rebuild operation completed An automatic system drive consistency check or physical drive rebuild has started/completed. mlx%d: channel %d pausing for %d seconds mlx%d: channel %d resuming mlx%d: pause command failed - %s mlx%d: pause failed for channel %d mlx%d: resume command failed - %s mlx%d: resume failed for channel %d Controller/channel pause operation notification. (Channel pause is not currently supported on any controller.) mlx%d: controller wedged (not taking commands) The controller is not responding to attempts to submit new commands. mlx%d: duplicate done event for slot %d mlx%d: done event for nonbusy slot %d Corruption has occurred in either the controller's onboard list of commands or in the driver. SEE ALSO
mlxcontrol(8) AUTHORS
The mlx driver was written by Michael Smith <msmith@FreeBSD.org>. This manual page was written by Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org> and Michael Smith <msmith@FreeBSD.org>. BUGS
The driver does not yet support EISA adapters. The DEC KZPSC has insufficient flash ROM to hold any reasonably recent firmware. This has caused problems for this driver. The driver does not yet support the version 6.x firmware as found in the AcceleRAID 352 and eXtremeRAID 2000 and 3000 products. BSD
August 10, 2004 BSD
All times are GMT -4. The time now is 05:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy