Sponsored Content
Operating Systems Solaris Can v240 disks be moved to v440 and have a chance of working? Post 302696899 by jlliagre on Wednesday 5th of September 2012 04:07:51 PM
Old 09-05-2012
Disks are using the same interface and technology so would be pluggable on the new system. If they are the system disks, I wouldn't bet they successfully boot on the v440 though without some tweaking.

As an alternative, you should consider flash archives which are designed to clone a system to another.
 

6 More Discussions You Might Find Interesting

1. Solaris

migrate complete OS from v240 to v440

We are concluding development of a new application on a v240 and would like to migrate the entire Solaris10 OS on the v240 to a v440 that is currently live with Solaris 9. The steps outlined in my head are as follows: 1) Flash archive the v440 and v240 and store the flar file on a different... (6 Replies)
Discussion started by: dangral
6 Replies

2. Shell Programming and Scripting

no chance to input passwd when create new user in loop

Hi Dears, I have one script to create new users with information in one plain text file. This script will read all lines in the file and create one users for one line. Sample file: #action;login,full name title,expire date,project +;gmwen,Bruce Wen QA,04/01/2012,BT +;xxdeng,Shown Deng... (4 Replies)
Discussion started by: crest.boy
4 Replies

3. Solaris

How to get spare disks working

Dears how can i make this spare disks working online to replace a defective disks vxdisk list DEVICE TYPE DISK GROUP STATUS c0t10d0s2 sliced - - error c0t11d0s2 sliced disk08 rootdg online c1t16d0s2 sliced ... (3 Replies)
Discussion started by: thecobra151
3 Replies

4. Solaris

Hot swapping disks on V240 - blue light not lit after cfgadm -c unconfigure

Hot swapping a drive on V240. So, I do cfgadm -c unconfigure <disk>. Then cfgadm -al reports disk as unconfigured as expected. format then tells me there is no disk. BUT, blue light does not come on. Done the exact same command on my V440 and blue light does come on. V240 Server Admin... (0 Replies)
Discussion started by: psychocandy
0 Replies

5. Programming

How to make C++ give me a chance to inter a number while excuting?

Iam Trying to simulate a hardware "pci" by visual c++ program..... " i don't have the hardware right now so i want to test my program" the hardware is about to inter a number for example from switches compare it to other number also from switches.."which iam gonna take it from 1 textbox"... 1-... (0 Replies)
Discussion started by: fwrlfo
0 Replies

6. Solaris

Sun Fire 480 - devfsadm -C not working after replacing one of the boot disks

Our SunFire 480 - one of the boot disks failed. It is mirrored with VxVm. I followed the exact steps that is detailed in the veritas and sun guides (I can not post the URL since I don't have 5 posts yet.) After removing the failed disk, I ran devfsadm -C -c disk and it still shows the device... (7 Replies)
Discussion started by: jtamminen
7 Replies
SCSI(7) 						 Miscellaneous Information Manual						   SCSI(7)

NAME
SCSI, RAID - Small Computer System Interface SYNOPSIS
dsk#, tape#_d#, cdrom# DESCRIPTION
The operating system interfaces to disk and tape devices through the Small Computer System Interface (SCSI). SCSI support is limited to the Compaq-supplied storage devices and certain third-party devices. To determine which named devices are supported in the default system, refer to the file /etc/ddr.dbase. For example, the following devices are listed therein: Winchester disks: RZ24L, RZ25, RZ25L, RZ25M, RZ28M, RZ29B, RZ55, RZ56, RZ58, RZ73, RZ74, RX23, RX26, RX33, IOMEGA ZIP, RAID (Redundant Arrays of Independent Disks) SCSI controllers: HSZ10, HSZ40, HSZ80 Magnetic tapes: TZ30, TZK11, TLZ06, TKZ09, TKZ60, DLT8000, SDT-10000 Media Changers: TL800, ESL9000 Optical disks: RRD42, RRD43, RRD44 Vendors can add their own devices to ddr.dbase. Refer to the Software Product Description (SPD) for a given release of the operating system for more information on processor-specific device support. Under the operating system, a SCSI device is referred to by a device identifier that is assigned by the operating system. This name has no relationship to the descriptive name of the device, although in previous releases of the operating system disks such as the RZ74 mapped to a system-assigned rz# logical name (where # was the instance number of that disk. Current logical names for SCSI disks and tapes take the forms specified in the rz(8) and tz(7) reference pages, such as dsk? and tape?. Refer to the dsfmgr(8) reference page for the naming conventions for disks, tapes and other devices, such as CD-ROM readers. Refer to the hwmgr(8) reference page for information on determining device names and other device data. SCSI Device Limits The number of possible target device IDs is determined by the controller type and method of connection, such as a multibus connection using fibre channel. Refer to the emx(7) reference page for an example of device addressing. Device Special Files The dsfmgr command creates device special files for all the devices that are attached to SCSI controllers. This event occurs automatically on system startup, and no administrative intervention is required unless an event requires that a device be renamed or its I/O be reas- signed. In such cases, you can use dsfmgr and hwmgr to manage SCSI devices and their associated device special files without the need to calculate values from their Bus, Target ID, and LUN data. RESTRICTIONS
The SCSI device driver is not warrantied to operate with optical disks other than the devices listed in /etc/ddr.dbase/. The SCSI driver attempts to support, on a best-effort basis, disks and magnetic tapes supplied by other vendors. The following notes apply to the driver's handling of disks from other vendors: These disks are identified using the following command: # hwmgr -get attribute -a name This command will return the device name SCSI-WWID (World-Wide Identifier) for all devices on the system, which includes the model name of the device. You can filter the output by specifying categories of devices. Disks are assigned a default partition table. The default table can be modified by editing the ccmn_rzxx_sizes[8] entry in the /usr/sys/data/cam_data.c file. The disklabel command can also be used to modify the partition table on an RZxx disk. RELATED INFORMATION
atapi_ide(7), dsfmgr(8), emx(7), hwmgr(8), rz(7), tz(7), disklabel(8), ddr.dbase(4) delim off SCSI(7)
All times are GMT -4. The time now is 07:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy