Sponsored Content
Operating Systems Solaris Solaris x86 installation using jumpstart does not local boot ( boot from hdd) Post 302547623 by hemalsid on Tuesday 16th of August 2011 07:53:42 AM
Old 08-16-2011
Yes. Changing the boot order in BIOS helps.
However, I am looking for a complete unattend installation. Is it possible to boot from local hdd when the machine reboots after the installation ??
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

dual boot solaris off of 2nd HDD

I did a search on the board, but I could not find anything specific to dual booting windows and solaris, with solaris being placed on a second hard drive. I have solaris 8 intel, and I am trying to dual boot, but the Solaris installation process is quite intimidating. I am afraid I am going to do... (3 Replies)
Discussion started by: dangral
3 Replies

2. Solaris

Solaris 10 x86 1/06 CD1 boot fail

Hello all. I download last version from sun.com, unzip iso's and burn their to cd's. When i try to load (on different machines) from first cd i receive this errors: /kernel/fs/specfs: undefined symbol '' /kernel/fs/specfs: undefined symbol '' ... several screens same message ....... (1 Reply)
Discussion started by: mozheyko_d
1 Replies

3. Solaris

Solaris 10 x86 Installation Will Not Boot From CD Disks

Problem: Am trying to install Solaris 10 x86 on a desktop PC (PC details unspecified) from downloaded iso images (5 in all) on 5 CD disks. These were downloaded from the Sun website and unzipped. I install Disk 1of 5 into the CD drive and then restart the machine, thinkng that it will launch... (5 Replies)
Discussion started by: RobSand
5 Replies

4. Solaris

Installation of Solaris 10 11/06 on X86 Platform with Xp SP2 as dual boot

Please help to install Solaris 10 11/06 on X86 platform with XP Sp2 as dual boot . Iam not unable to complete the installation as it shows that NO DISK AVAILABLE even i have assigned the unpartioned space of 30 GB PLz help me as my life was tired to do Installation before i retire from the... (2 Replies)
Discussion started by: skargarika
2 Replies

5. Solaris

One time network boot of Jumpstart x86 client

I am trying to find an approach that has been effective for automating the installation of Solaris 10 x86 using Jumpstart technology. I have configured an Jumpstart server and a Solaris dhcp server with appropriate macros for passing the client information about its boot environment. The problem is... (7 Replies)
Discussion started by: chajo19
7 Replies

6. Solaris

Solaris X86 grub boot menu

I have a x4200 m2 that I've installed Solaris 10 on. I've created a raid 1 mirror using disk0 and disk1. I'm trying to add the mirror bootblk to the grub menu so in case of a failure of disk0, I can simply boot from the mirrored disk1. I'm looking for the syntax to add the alternate boot path to... (5 Replies)
Discussion started by: gonzotonka
5 Replies

7. Solaris

x86 Solaris 8 does not boot.

Hello, First of all I must say that I have 0 solaris experience and only some average linux knowledge. One of my friends came to ask for my help today with a Solaris 8 x86 station that would not boot. The system is a pentium 4 1.6 ghz, 1gb ram, 40 gb hdd. When I turn it on, I get ... (3 Replies)
Discussion started by: gogusrl
3 Replies

8. Solaris

Problems cloning Solaris 10 x86 Installation to bigger HDD

Dear All, I have been trying to move my existing Solaris Installation (x86, 10/08) to a bigger HDD. So I created a 22 cylinder boot partition and used the rest of the space for a Solaris2 partition. Then I created slices same size like on my current disk. I copied all files with cpio and... (3 Replies)
Discussion started by: BigT79
3 Replies

9. Solaris

How to specify local boot up disk in CD boot Grub?

Hi Solaris 10 Experts, I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk... (0 Replies)
Discussion started by: gjackson123
0 Replies

10. Solaris

Boot Solaris 10 U1 for x86 from DVD

Is it possible to boot an existing Solaris 10 update 1 from boot dvd that I run on p3(1 ghz -512 mb ram). I have got a dual boot sys - the other os is win xp that I need to reinstall but that removes the mbr so, is there any way to recover mbr after the installation of xp? Thanks. (3 Replies)
Discussion started by: vectrum
3 Replies
MACHINE-ID(5)                                                       machine-id                                                       MACHINE-ID(5)

NAME
machine-id - Local machine ID configuration file SYNOPSIS
/etc/machine-id DESCRIPTION
The /etc/machine-id file contains the unique machine ID of the local system that is set during installation or boot. The machine ID is a single newline-terminated, hexadecimal, 32-character, lowercase ID. When decoded from hexadecimal, this corresponds to a 16-byte/128-bit value. This ID may not be all zeros. The machine ID is usually generated from a random source during system installation or first boot and stays constant for all subsequent boots. Optionally, for stateless systems, it is generated during runtime during early boot if necessary. The machine ID may be set, for example when network booting, with the systemd.machine_id= kernel command line parameter or by passing the option --machine-id= to systemd. An ID is specified in this manner has higher priority and will be used instead of the ID stored in /etc/machine-id. The machine ID does not change based on local or network configuration or when hardware is replaced. Due to this and its greater length, it is a more useful replacement for the gethostid(3) call that POSIX specifies. This machine ID adheres to the same format and logic as the D-Bus machine ID. This ID uniquely identifies the host. It should be considered "confidential", and must not be exposed in untrusted environments, in particular on the network. If a stable unique identifier that is tied to the machine is needed for some application, the machine ID or any part of it must not be used directly. Instead the machine ID should be hashed with a cryptographic, keyed hash function, using a fixed, application-specific key. That way the ID will be properly unique, and derived in a constant way from the machine ID but there will be no way to retrieve the original machine ID from the application-specific one. The sd_id128_get_machine_app_specific(3) API provides an implementation of such an algorithm. INITIALIZATION
Each machine should have a non-empty ID in normal operation. The ID of each machine should be unique. To achive those objectives, /etc/machine-id can be initialized in a few different ways. For normal operating system installations, where a custom image is created for a specific machine, /etc/machine-id should be populated during installation. systemd-machine-id-setup(1) may be used by installer tools to initialize the machine ID at install time, but /etc/machine-id may also be written using any other means. For operating system images which are created once and used on multiple machines, for example for containers or in the cloud, /etc/machine-id should be an empty file in the generic file system image. An ID will be generated during boot and saved to this file if possible. Having an empty file in place is useful because it allows a temporary file to be bind-mounted over the real file, in case the image is used read-only. systemd-firstboot(1) may be used to to initialize /etc/machine-id on mounted (but not booted) system images. When a machine is booted with systemd(1) the ID of the machine will be established. If systemd.machine_id= or --machine-id= options (see first section) are specified, this value will be used. Otherwise, the value in /etc/machine-id will be used. If this file is empty or missing, systemd will attempt to use the D-Bus machine ID from /var/lib/dbus/machine-id, the value of the kernel command line option container_uuid, the KVM DMI product_uuid (on KVM systems), and finally a randomly generated UUID. After the machine ID is established, systemd(1) will attempt to save it to /etc/machine-id. If this fails, it will attempt to bind-mount a temporary file over /etc/machine-id. It is an error if the file system is read-only and does not contain a (possibly empty) /etc/machine-id file. systemd-machine-id-commit.service(8) will attempt to write the machine ID to the file system if /etc/machine-id or /etc are read-only during early boot but become writable later on. RELATION TO OSF UUIDS
Note that the machine ID historically is not an OSF UUID as defined by RFC 4122[1], nor a Microsoft GUID; however, starting with systemd v30, newly generated machine IDs do qualify as v4 UUIDs. In order to maintain compatibility with existing installations, an application requiring a UUID should decode the machine ID, and then apply the following operations to turn it into a valid OSF v4 UUID. With "id" being an unsigned character array: /* Set UUID version to 4 --- truly random generation */ id[6] = (id[6] & 0x0F) | 0x40; /* Set the UUID variant to DCE */ id[8] = (id[8] & 0x3F) | 0x80; (This code is inspired by "generate_random_uuid()" of drivers/char/random.c from the Linux kernel sources.) HISTORY
The simple configuration file format of /etc/machine-id originates in the /var/lib/dbus/machine-id file introduced by D-Bus. In fact, this latter file might be a symlink to /etc/machine-id. SEE ALSO
systemd(1), systemd-machine-id-setup(1), gethostid(3), hostname(5), machine-info(5), os-release(5), sd-id128(3), sd_id128_get_machine(3), systemd-firstboot(1) NOTES
1. RFC 4122 https://tools.ietf.org/html/rfc4122 systemd 237 MACHINE-ID(5)
All times are GMT -4. The time now is 11:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy