Sponsored Content
Operating Systems Solaris Move root disk to new identical hardware Post 303040914 by hicksd8 on Saturday 9th of November 2019 04:59:56 AM
Old 11-09-2019
You don't say which version of Solaris this is. Please post your OS version.

Firstly, whilst it's up and running, and before you do anything with the existing system, make sure you know the hostid exactly!! If you move the root disk(s) and cannot get the original hostid, to set it you'll need to inject the required value into the kernel module. If you don't know what hostid you need at that time you are screwed.

Also, blatantly obvious thing to say I know is, you need to ensure that you are also moving the metadb (which is usually on a very small disk partition) otherwise SVM won't work on the new machine. If metadb is on a non-root disk then you'll have to move that too.

If the root disk is SVM mirrored then I guess you mean to move a pair of disks??

There's likely no EPROM on this hardware to allow you to move the NIC address, etc, and the hostid is hashed from the NIC address on SPARC hardware. So it's quite likely IMHO that you will need to forcibly change the hostid on the new box. The code to do that I posted on this forum a long time ago so you can search for it. REMEMBER THOUGH, that the code is different for SPARC vs X86 and both are published on here. Make sure you use the right method.

If you've been professional and have a full backup I don't see any harm in giving it a try.

(If you cannot find the relevant hostid discussion on this forum drop me (hicksd8) or moderator gull04 a PM and prompt one of us to post back on this thread. We know how to do this.)

Last edited by hicksd8; 11-09-2019 at 06:38 AM..
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Move a disk to Sol. 2.6

I removed an external Sun disk (with data on it) from an old 2.6 system and added the disk to another 2.6 system. The new system seems to recognize the system (verified by the format command). When try to mount I am getting, I got the error: mount: /dev/dsk/c1t1d0s6 is not this fstype. I... (3 Replies)
Discussion started by: sunshine
3 Replies

2. UNIX for Dummies Questions & Answers

Multi disk hardware

Hi all, I purchased a pci controller card and a 3rd hard drive to put Linux on my machine. The card did not enable me to boot to the 3rd drive so I could not get Mandrake to install. My motherboard is a Gigabyte GA-7DXR+. Can anyone point me to a reasonable card/connector which will allow me... (2 Replies)
Discussion started by: onestepto
2 Replies

3. Solaris

Move root disk to new server

Hi, I need to do an installation where I have identical hardware at both sites and create the installation at one site and take the disk to the other site. Question: Do I need to do anything special for the OS to come up properly? thanks. (18 Replies)
Discussion started by: VirginiaSA
18 Replies

4. Solaris

Move root filesystem to other slice

Hi, df -h display: # df -h Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% / /proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab fd 0K 0K 0K 0% /dev/fd swap 1.0G 152K 1.0G 1% /var/run swap 1.1G 24M 1.0G 3% /tmp /dev/dsk/c1t0d0s3 57G 13G 43G 24%... (4 Replies)
Discussion started by: lamoul
4 Replies

5. Solaris

Move partition to new disk

Hi, The disks of my servers are getting full and I need to move the /export/home partition on to a new set of disks. I already have 2 mirrored disks and have added 2 more and mirrored them after creating the filesystem on them. Do I just need to edit the /etc/vfstab and point the /export/home... (1 Reply)
Discussion started by: run_time_error
1 Replies

6. Solaris

Hardware RAID not recognize the new disk [Sun T6320]

We have hardware RAID configured on Sun-Blade-T6320 and one of the disk got failed. Hence we replaced the failed disk. But the hot swapped disk not recognized by RAID. Kindly help on fixing this issue. We have 2 LDOM configured on this server and this server running on single disk. #... (8 Replies)
Discussion started by: rock123
8 Replies

7. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

8. UNIX for Dummies Questions & Answers

Move os from 1 disk to the other

Hi, I have server with 2 active disk, but disk 1 contain big part of os is falling, how can i move everything to disk 2 and then remove the disk 1? Thanks (4 Replies)
Discussion started by: prpkrk
4 Replies

9. Solaris

[solved] How to blink faulty disk in Solaris hardware?

Hi Guys, One of two disks in my solaris machine has failed, the name is disk0, this is SUN physical sparc machine But I work remotely, so people working near that physical server are not that technical, so from OS command prompt can run some command to bink faulty disk at front panel of Server.... (9 Replies)
Discussion started by: manalisharmabe
9 Replies

10. Linux

Move OS to storage disk

Hi We have RHEL 7.3 running from local disk and we want to move it to storage. I am unable to find any proper procedure to do this activity. Please help. (4 Replies)
Discussion started by: powerAIX
4 Replies
vxbootsetup(1M) 														   vxbootsetup(1M)

NAME
vxbootsetup - set up system boot information on a Veritas Volume Manager disk SYNOPSIS
/etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ] DESCRIPTION
The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk. All of these volumes must be contiguous with only one subdisk. The -g option may be used to specify the boot disk group. If no medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to be bootable. If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable. vxbootsetup requires that: o The root volume must be named rootvol and must have a usage type of root. o The swap volume must be named swapvol and must have a usage type of swap. o The volumes containing /usr and /var (if any) must be named usr and var, respectively. See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on how the system boots and how VxVM impacts the system boot process. The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically. If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to make the disk bootable. ARGUMENTS
medianame Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable. SEE ALSO
disksetup(1M), edvtoc(1M), vxassist(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M), vxrootmir(1M) Veritas Volume Manager Troubleshooting Guide VxVM 5.0.31.1 24 Mar 2008 vxbootsetup(1M)
All times are GMT -4. The time now is 09:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy