Why is my sound not working? 5 PC Troubleshooting Tips

Actually, I installed AIX 5.2 on a P630 (4 lanes 5 GB. After
installation received, I received a screen capture license
and set the actual password, date and time, etc. As soon as I leave the screen, it disappears
I got the message “” 0513-059 ctrrmc subsystem
was started. Subsystem PID is 176236″, and the function fails
v. I am not getting a specific login prompt. I tried including
and the server always weighs the system in the same position. Below
some server home screen.

– – – – – – – – – – – – – – – – – – – – – ”———–
– – – – – – – –
Welcome to AIX.
Hiking image timestamp: 19:36 02/08
Current effort and date: 08/03/2006 16:36:00
Number of processors 4: Memory:
5120 MB
Boot device: /pci@400000000110/pci@2.4/scsi@1/sd@8.0
Close standard input and standard output…
– – – – – – – – – – – – – – – – – – – – – – ”———
– – – – – – –

Saving user master data to a boot drive
Starting the main sync daemon
Z Start error daemon
System initialization completed.
Setting up multi-user settings… done
Start initialization
Perform automatic change of volume groups
Enable swap space only
swapon: swap device /dev/hd6 is already active.
/dev/rhd1 (/home): **Simple unmount – unchecked
/dev/rhd10opt (/opt): **Purge not mounted – check removed
They all automount
Multiplayer initialization complete
srcmstr… activity check done
Starting TCP Daemons:
0513-059 The syslogd subsystem is running. Subsystem PID
9294.
0513-059 The sendmail subsystem has started. Subsystem PID
8934.
0513-059 The port map subsystem has started. Subsystem PID
4058.
0513-059 The inetd subsystem is running. Subsystem PID
7886.
0513-059 The snmpd subsystem has been practicing the art of booting. Subsystem PID
7482.
0513-059 Hostmibd subsystem started. Subsystem PID
9556.
0513-059 The snmpmibd subsystem has started. Subsystem PID
definitely 7360.
0513-059 Aixmibd subsystem started. Subsystem PID
8608.
0513-059 The muxatmd subsystem is running. Subsystem PID
9808.
Demo start blockingov TCP.
Starting NFS Services:
05:13-059 Biode subsystem started. Subsystem PID
10890.
0513-059 The rpc.statd subsystem is running. Subsystem PID
12646.
0513-059 The rpc.lockd subsystem is running. Subsystem PID
11896.
NFS services are disabled.
0513-059 The ctrrmc subsystem has started. Subsystem PID
176236.

I would really appreciate https://filemodo.net key suggestions for solving this problem.
I tried commenting out the ctrrmc entry in the inittab file (using
maintenance mode), the server crashes after provisioning
the server.
NFS.

Question

How do you manage Boot i AIX in single user mode for maintenance?

Reply

In AIX, we rarely use single user mode, while many problems require unmounting rootvg filesystems to fix. However, in some cases it is beneficial to use a single user:

  • Policy startup hangs due to TCP/IP, NFS configuration issues type=”disc”>do
  • To troubleshoot /etc/inittab entries
  • In order to play show good results in the system without trying to login fans
  • Runs without launching applications
  • It is considered easy to unmount /tmp as /var if they need to be tracked or rebuilt with fsck
  • If the program boots from rootvg without problems, there are advantages to booting in single user mode right after that, i.e. doing work:

  • Already faster than maintenance mode
  • You can run the normal rootvg procedure without finding the AIX installation media and/or without configuring NIM-SPOT.
  • It allows you to run all the code you would normally have access to in multi-user mode.
  • Unlike maintenance work, renaming hard drives is out of the question.
  • Standalone system (without HMC):
    1. Boot the system without media in this CD/DVD
    drive
    2. Wait for everyone to see the options to select a different exclusion list and listen for what I would say console beeps
    3. Press 6 to start diagnostics

    System with HMC:
    1. Select an LPAR in the HMC GUI
    2. Select “Transactions” -> “Activate”
    .
    3. On the Enable panel, click the Advanced button
    4. Change “Boot Mode” to “Diagnose by Stored Boot List”
    5.Click “OK” to save this change, then click “OK” to activate it.

    IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
    IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM