04-02-2009
Error while booting the os
ater successfully completeing my solaris 10 installation
i am not able boot the machine properly .
my machine is continously rebooting after switching on the machine.
what the problem ? is it the boot process problem or some other
if any body got the solution mail it my email id
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello experts,
I have installed solaris 10 on x86. When I try to boot I get an error
with ablue screen
login failed please try again. I am new to this o.s. It used to work
nicely before what did I do wrong?
Any guidance advice will be highly appreciated
Thanks, (5 Replies)
Discussion started by: deepak1
5 Replies
2. Linux
Hi,
We have system 'red hat 9'. While booting I m getting error
"INIT: Id "X" respawning too fast: disabled for 5 minutes"
Can anybody help to solve this problem. (0 Replies)
Discussion started by: namrata5
0 Replies
3. Linux
hi,
in my pc linux and windows was there with 2 hdd in raid.i removed linux partititons.Now my ps is not booting giving grub error 22.Nothing works.I hace my data in windows.Hard disks are RAID.when tried to go to recovery mode from windoes boot cd,it says hard disk not detected.when tried with... (2 Replies)
Discussion started by: pankajd
2 Replies
4. Solaris
Hi,
I wish to install solaris 10 on a target machine (t1000) by using Jumpstart. I have configured by jumpstart environment for the same. When i boot the target with the option "boot net -v install" i get the following error...
{0} ok boot net -v install
Boot device: /pci@7c0/pci@0/network@4... (3 Replies)
Discussion started by: hemalsid
3 Replies
5. Solaris
Solaris 10 5/08 on Ultra 40 M2
It boots fine off primary disk but having issues booting off the mirror disk.
I get this error when booting off mirror disk:
Booting 'Solaris 10 ... Mirror disk'
root (hd1,0,a)
Error 22: No such partition
Press any key to continue...
Any... (7 Replies)
Discussion started by: etc
7 Replies
6. Solaris
Hi.
I need to boot on Sun Blade 150 from scsi-disk, that ran on old Sun Ultra 10.
It is necessary to take some the information from an old disk and something to study.
The workstation is booted and I receive the following issue::mad:
Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard (tip... (3 Replies)
Discussion started by: wolfgang
3 Replies
7. Solaris
Dear All,
After creating ,installing ,configuring zone in my solaris VMware .
I am not able to Ready/Boot the zone.
giving error as :
Please help me out for the same
Core part of zone.xml is as:
Anythng which I missed in configuration..
Do let me know (1 Reply)
Discussion started by: bharat_
1 Replies
8. Solaris
Sun Fire V210, No Keyboard
Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.13.2, 4096 MB memory installed, Serial #61203679.
Ethernet address 0:3:ba:a5:e4:df, Host ID: 83a5e4df.
Boot device: net File and args:
100 Mbps FDX Link up
Timeout waiting for... (5 Replies)
Discussion started by: Mrudhul
5 Replies
9. Solaris
Hi friends,
Due to improper shutdown in t4 sparc server , SVM went to maintenence, below is the SVM output.
root@t4-root # metastat -c
d30 m 32GB d31 (maint) d32 (maint) d33 (maint)
d31 s 32GB /dev/dsk/c0t5000CCA012C58288d0s5
d32 s 32GB... (2 Replies)
Discussion started by: Kathirvel G
2 Replies
10. SCO
Hello Dears,
I have fujitsu tx300 S7 server with installed sco unixware 7.1.4,
Now the /etc is corrupted and the sco cannot boot.
There is no emergency disk or cd, I'm trying to fix this with reinstalling unixware again, but the problem now that when i try to install the HBA driver that i... (26 Replies)
Discussion started by: amr ibrahim
26 Replies
LEARN ABOUT X11R4
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)