Operating Systems Solaris Move root disk to new identical hardware Post 303040921 by hicksd8 on Saturday 9th of November 2019 02:02:16 PM
No, it's not only necessary in x86.

On x86 the hostid is computed at random at installation time. On SPARC the hostid is a hash of the hardware NIC address so in situations where you cannot move an EPROM (ie, newer hardware), the hostid will be different from the original box. Therefore you have to forcibly set it by injection into the kernel module.
This User Gave Thanks to hicksd8 For This Post:
 
Test Your Knowledge in Computers #911
Difficulty: Easy
In C, we can get the address of a variable as follows: pointer = &variable;
True or False?

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
bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME
bootconf - boot device configuration table DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the file manually. There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown: disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following: Indicates that the root disk is in LVM or VERITAS Volume Manager (VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file. Indicates that the root disk is in the "whole disk" format with no partitions, but boot and swap space are reserved outside the file system. device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file that references the entire disk. Blank lines are permitted. Any line beginning with a is considered to be a comment. DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self- explanatory; a few warrant additional explanation: If there are no other messages about the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem is. The specified device file does not point to a disk where there is a lif which contains the file Some character other than or is in the first field of a line. As of release 10.0, the boot areas in must all be on the same type of disk layout. There are characters after the device file specification. EXAMPLES
The boot area is on an LVM root disk: l /dev/disk/disk7_p2 The boot area is on a whole disk layout: w /dev/disk/disk7 WARNINGS
All of the boot devices in the file must have the same disk layout. AUTHOR
was developed by the Hewlett-Packard Company. FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). documentation. bootconf(4)

Featured Tech Videos

All times are GMT -4. The time now is 10:55 AM.
Unix & Linux Forums Content Copyright 1993-2019. All Rights Reserved.
Privacy Policy