05-13-2011
EXP400 with 43P machine not booting
Hello
I connected the exp400 & turned on the aix machine which is 7043-150 but now I guess probably ODM is corrupted as it does not boot. Its stuck at 0518 code.
Also, on the console it shows stuck on the kernel, which then it does not want to boot. Is it possible to fix from maintenance mode, if so what are the steps.
I have disconnected the EXP400 form the system now but I was told that it is compatible with the aix machine.
Just to let you know since I just have one scsi cable so I had only one power supply for EXP400 turned on & only 5 hard drives were installed on the same side.
Help would be appreciated
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there any way to backup the bios on a 43P-140 7043? (0 Replies)
Discussion started by: freestyle10269
0 Replies
2. AIX
I have acquired a 43p 120 (7248-120) and I have two questions:
Can anyone remember what is the highest version of AIX which I can install (5.1 I believe)
and
Can anyone remember how to boot this from the CDROM (boot floppy?) (1 Reply)
Discussion started by: johnf
1 Replies
3. AIX
I have a 43p 120 (7248-120) which I am trying to install AIX 5.2 on. I have built a Nimol server on a Linux PC running SUSE LES 10. I have setup the 43p to perfom a network boot (BOOTP) and all the addresses in the network settings under SMS are set to 0.0.0.0. When I power up the 43p it... (15 Replies)
Discussion started by: johnf
15 Replies
4. AIX
I've installed AIX 5.1 on a 43p-140, but am unable to log in. At no point in the install did it ask me for a root password. When it boots to the console prompt, I enter "root" as a username, and then after 1 second it cycles right back to another root prompt.
I am accessing the 43p-140... (4 Replies)
Discussion started by: akbar
4 Replies
5. Solaris
I had a power failure the other day and when my relatively new Solaris 10 machine rebooted it is thrown into maintenance mode.
I've found the following lines in the /var/adm/messages file, I'm assuming this is the root cause of the problem. However, I don't have the slightest idea on how to... (9 Replies)
Discussion started by: cheetobandito
9 Replies
6. AIX
HI all!
this is my problem:
my boss got a Model 43P 7248-100 PowerPC server with the AIX 4.2 os, but some days ago it crashed and now it doesn't want to boot up again, it stops after the initial diagnostic phase with the "PowerPC" screen!
I must recover some important data from the hard disk, so... (6 Replies)
Discussion started by: AKO
6 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have inherited a Ultra 5 SPARC machine that I need to boot from its CD-ROM. WHen I turn on the machine it just boots to its hard drive. How do I get it to boot from the CD-ROM.
I am a Solaris newbie.... (1 Reply)
Discussion started by: mojoman
1 Replies
8. AIX
hi to everybody
I have a problem with the AIX version 4:
I can not get into failsafe session
kindly someone knows how to enter this mode?
thanks in advance (5 Replies)
Discussion started by: elektrospeed
5 Replies
9. UNIX for Dummies Questions & Answers
hello, i am new to this forum and i really could use some help, we have a risc 43p model 150 ibm server and we run prophet 21 on it. after the box boots up and then we activate prophet 21 we get a error message saying
"The data space of the process is not enough for the shm segment (1176) │
... (1 Reply)
Discussion started by: mrhose
1 Replies
10. Solaris
Dear all
Any help would be greatly appreciated, I have Solaris 10 installed on an M5000 SPARC machine. While rebooting it, we are faced with the following message then the OK prompt:
SPARC Enterprise M5000 Server, using Domain console
Copyright (c) 1998, 2010, Oracle and/or its affiliates. All... (25 Replies)
Discussion started by: abohmeed
25 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)