02-09-2005
server won't boot
Hi all ,
i was trying to upgrade firmware on machine 7028-6E4 and it failed .
Now machine does not boot anymore , i can not get SMC menu either ...
What are my options ?
Thanks,
Rahim
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I've just bought an Ultra 60 running solaris 9 (or so I've been led to believe). When I start up, it looks for a (presumably) domain/network to hook up to and the following messages are displayed:
Boot device: net file and args:
Network link setup failed
Please check cable and try... (3 Replies)
Discussion started by: alarmcall
3 Replies
2. 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
3. Solaris
Solaris system
version 6
I cloned the drive using the DD command.
Using the format command and examining the partitions, all looks the same as the original drive.
Problem:
When I attach the cloned drive as the master, and only drive in system, it will not boot.
Error messages:
... (9 Replies)
Discussion started by: HikerLT
9 Replies
4. Solaris
I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies
5. UNIX for Dummies Questions & Answers
I'm trying to install Fedora 9 on a Dell OptiPlex GX300 machine. The instalation runs properly, but when the computer restarts after the instalation, it simply won't boot, like there's no OS installed.
I tried diffrent Linux distributions, but nothing works.
This are the partitions, maybe it's... (12 Replies)
Discussion started by: teis
12 Replies
6. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
7. Solaris
We changed the IP address (gateway, defaultrouter, nameserver) on our Solaris9 server and moved it to another datacenter. Now the server won't boot and continues to reboot endlessly. No, we didn't use sys-config but manually changed hosts, netmasks, defaultrouter and resolv.conf.
There is a... (3 Replies)
Discussion started by: booshame
3 Replies
8. Red Hat
I dont know what the heck happen but one of our DBAs was working on a cluster for oracle. Rebooted the box and viola, the OS won't load. After the POST message, I get a blinking cursor on the upper left hand corner. Doesn't even say "GRUB" or anything, it just blinks.
I tried going into rescue... (1 Reply)
Discussion started by: sdotsen
1 Replies
9. UNIX for Dummies Questions & Answers
I compiled new kernel in linux 10.04 called linux-2.6.26.8-xenomai, it runs alongside the other kernel, but when I want to boot it I get an error message saying:
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda5 does not exist.
After making the modules and headers
I made the... (4 Replies)
Discussion started by: mdop
4 Replies
10. Hardware
Hello, I am new to the UNIX community, however I have a beginner's level understanding of a majority of the basic commands in UNIX.
Today, my teacher gave me her old AT&T UNIX PC. I brought it home, turned it on, and got a completely green screen. I turned it off, and back on and it booted... (12 Replies)
Discussion started by: _dhoepp
12 Replies
LEARN ABOUT XFREE86
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)