Can v240 disks be moved to v440 and have a chance of working? Post: 302697117

Sponsored Content

Operating Systems Solaris Can v240 disks be moved to v440 and have a chance of working? Post 302697117 by hicksd8 on Thursday 6th of September 2012 06:04:10 AM

09-06-2012

Moderator

Just swapping the disks from one platform to the other won't boot but it can be made to work with a bit of engineering, ie, booting single user and editing files on your hard disk filesystem.

The platforms are different so:

Your network interfaces will be different hardware
Your disk controllers will be different and resulting devices (c0t0d0, etc) will be different (this one prevents booting even with errors).

Stuff like vfstab, system file, bootblock, (filesystem) device names, will need sorting running under single user, followed by a boot -r to reconfigure everything (to get Solaris to do the rest of the work!!)

Here's a thread that was started by a member going the other way (by restoring his V440 ufsdumps to a V240) which I subscribed to in helping to sort the issues.............

Restore a server from a ufsdump

Hope that helps.

Last edited by hicksd8; 09-06-2012 at 07:31 AM..

hicksd8

View Public Profile for hicksd8

Find all posts by hicksd8

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...

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...

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 ...

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...

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-...

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...

LEARN ABOUT ULTRIX

installboot

installboot(1M) 														   installboot(1M)

NAME

       installboot - install bootblocks in a disk partition

SYNOPSIS

       installboot bootblk raw-disk-device

       The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition.

       The  ufs  boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be
       found using the -i option of uname(1).

       The installboot utility is a SPARC only program. It is not supported on the  architecture.  users should use installgrub(1M) instead.

       bootblk	       The name of the bootblock code.

       raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is  read-
		       able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive.

       Example 1: Installing UFS Boot Block

       To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use:

	      example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk 
		   /dev/rdsk/c1t0d0s0

       /usr/platform/platform-name/lib/fs/ufs

	   directory where ufs boot objects reside.

       /platform/platform-name/ufsboot

	   second level program to boot from a disk or CD

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

       od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5)

WARNINGS

       The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device.

								    11 Apr 2005 						   installboot(1M)