05-01-2011
Eric,
Do you want to know which disk the server booted off from (Out of the two)? Or, you want to know how to find the boot disks (Disks which are capable of booting the server) out of these two disks?
-DB
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have made my boot disk just as the program has instructed, and when I boot from floppy with dual hard drives it locks up and say's kernal error. What am I doing wrong? (1 Reply)
Discussion started by: bobkat
1 Replies
2. UNIX for Dummies Questions & Answers
I need to know how to make a boot disk to get Solaris 7 to load on a intel machine.
I have checked out Sun.Com, but did not understand how to download and convert the files to a disk.
any help would be appericated
thanks
Bobby (2 Replies)
Discussion started by: Youngadmin
2 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have the situaiton in which primary boot disk has bad sectors in Solaris 9. The other hard disk is mirrored using Solstice DiskSuite 4.2. I can reboot system with the other disk. My question is, when I replaced the boot disk with a new one, how can I create meta db and finally make it... (2 Replies)
Discussion started by: s_aamir
2 Replies
4. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
5. Solaris
Hi once more :p
Yesterday I reinstalled Solaris OS and now I can not mount pcfs HDD
SunOS unknown 5.10 Generic_142901-03 i86pc i386 i86pc
and what has been added in /etc/vfstab is
/dev/dsk/c1t0d0p1:c - /podaci - pcfs - yes rw
But as I said , my disk is... (4 Replies)
Discussion started by: solaris_user
4 Replies
6. Solaris
Hello All, I got a question, but I can't find where to set it up. I need your help.
The systems are with solaris 10 and with two boot devices (disk 0 and disk1). When the operator wants to boot the different disk then the previous one, i want to get the user intervention to ask operator if... (3 Replies)
Discussion started by: shuhuichen
3 Replies
7. Solaris
So I have mirrored disk already set up from c1t0d0 to c1t1d0. Is there some special procedures that I need to do before I do and then try to boot from the mirrored disk? I am using a V490 if that helps... (7 Replies)
Discussion started by: drew_1980
7 Replies
8. Solaris
Update:
The / file system (/dev/rdsk/c1t0d0s0) is being checked
fsck unable to stat
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0).
Root password for system maintenance (control-d to bypass):
I am unable to hit control-d to by pass.
I... (50 Replies)
Discussion started by: br1an
50 Replies
9. Solaris
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
Hi,
I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies
LEARN ABOUT MOJAVE
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)
systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)