I had z/VM jerk the rug out from under our zLinux system and now I can't get it 
up.

         Starting Crash recovery kernel arming...
Ý Ý1;31mFAILED Ý0m¨ Failed to start Crash recovery kernel arming.
See 'systemctl status kdump.service' for details.
Ý Ý32m  OK   Ý0m¨ Started Security Auditing Service.
         Starting Update UTMP about System Boot/Shutdown...
Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Boot/Shutdown.
         Starting Update UTMP about System Runlevel Changes...
Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Runlevel Changes.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ¬D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):


  ÝKÝ   Ý31m* Ý1;31m* Ý0m Ý31m*  Ý0m¨ A start job is running for 
dev-mapp...ome.device (1min 20s / 1min 30s)  ÝKÝ  Ý31m* Ý1;31m* Ý0m
Ý31m*   Ý0m¨ A start job is running for dev-mapp...ome.device (1min 21s / 1min 
30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*    Ý0m¨ A start jo
b is running for dev-mapp...ome.device (1min 21s / 1min 30s)  ÝKÝ Ý1;31m* Ý0m 
Ý31m*     Ý0m¨ A start job is running for dev-mapp...o
me.device (1min 22s / 1min 30s)  ÝKÝ Ý0m Ý31m*      Ý0m¨ A start job is running 
for dev-mapp...ome.device (1min 22s / 1min 30s)  ÝKÝ
Ý1;31m* Ý0m Ý31m*     Ý0m¨ A start job is running for dev-mapp...ome.device 
(1min 23s / 1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*    Ý
0m¨ A start job is running for dev-mapp...ome.device (1min 23s / 1min 30s)  ÝKÝ 
 Ý31m* Ý1;31m* Ý0m Ý31m*   Ý0m¨ A start job is runni
ng for dev-mapp...ome.device (1min 24s / 1min 30s)  ÝKÝ   Ý31m* Ý1;31m* Ý0m 
Ý31m*  Ý0m¨ A start job is running for dev-mapp...ome.de
vice (1min 24s / 1min 30s)  ÝKÝ    Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job is 
running for dev-mapp...ome.device (1min 25s / 1min 30
s)  ÝKÝ     Ý31m* Ý1;31m* Ý0m¨ A start job is running for dev-mapp...ome.device 
(1min 25s / 1min 30s)  ÝKÝ      Ý31m* Ý0m¨ A start j
ob is running for dev-mapp...ome.device (1min 26s / 1min 30s)  ÝKÝ     Ý31m* 
Ý1;31m* Ý0m¨ A start job is running for dev-mapp...ome.
device (1min 26s / 1min 30s)  ÝKÝ    Ý31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job 
is running for dev-mapp...ome.device (1min 27s / 1min
30s)  ÝKÝ   Ý31m* Ý1;31m* Ý0m Ý31m*  Ý0m¨ A start job is running for 
dev-mapp...ome.device (1min 27s / 1min 30s)  ÝKÝ  Ý31m* Ý1;31m*
Ý0m Ý31m*   Ý0m¨ A start job is running for dev-mapp...ome.device (1min 28s / 
1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*    Ý0m¨ A star
t job is running for dev-mapp...ome.device (1min 28s / 1min 30s)  ÝKÝ Ý1;31m* 
Ý0m Ý31m*     Ý0m¨ A start job is running for dev-mapp
...ome.device (1min 29s / 1min 30s)  ÝKÝ Ý0m Ý31m*      Ý0m¨ A start job is 
running for dev-mapp...ome.device (1min 29s / 1min 30s)
 ÝKÝ Ý1;31m TIME  Ý0m¨ Timed out waiting for device 
dev-ma...-clefos_mfclef00\x2dhome.device.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for File System 
C...dev/mapper/clefos_mfclef00-home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for /home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Local File Systems.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Mark the need to relabel after reboot.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Migrate local... structure to the new 
structure.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Relabel all filesystems, if necessary.
         Starting Preprocess NFS configuration...

Okay, so I tried the above, but:
         Starting Logout off all iSCSI sessions on shutdown...
Ý Ý32m  OK   Ý0m¨ Reached target Timers.
Ý Ý32m  OK   Ý0m¨ Reached target Login Prompts.
Ý Ý32m  OK   Ý0m¨ Reached target Network is Online.
Ý Ý32m  OK   Ý0m¨ Reached target Paths.
Ý Ý32m  OK   Ý0m¨ Reached target Sockets.
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Import network configuration from initramfs...
Ý Ý32m  OK   Ý0m¨ Started Logout off all iSCSI sessions on shutdown.
         Starting Availability of block devices...
Ý Ý32m  OK   Ý0m¨ Started Availability of block devices.
Ý Ý32m  OK   Ý0m¨ Started Preprocess NFS configuration.
         Starting Notify NFS peers of a restart...
Ý Ý32m  OK   Ý0m¨ Started Tell Plymouth To Write Out Runtime Data.
Ý Ý32m  OK   Ý0m¨ Started Notify NFS peers of a restart.
Ý Ý32m  OK   Ý0m¨ Started Import network configuration from initramfs.
         Starting Create Volatile Files and Directories...
Ý Ý32m  OK   Ý0m¨ Started Emergency Shell.
Ý Ý32m  OK   Ý0m¨ Reached target Emergency Mode.
Ý Ý32m  OK   Ý0m¨ Started Create Volatile Files and Directories.
         Starting Security Auditing Service...
         Mounting RPC Pipe File System...
Ý   94.702979¨ type=1305 audit(1677466513.021:4): audit_pid=3294 old=0 
auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_
t:s0 res=1
Ý   94.709128¨ RPC: Registered named UNIX socket transport module.
Ý   94.709129¨ RPC: Registered udp transport module.
Ý   94.709130¨ RPC: Registered tcp transport module.
Ý   94.709131¨ RPC: Registered tcp NFSv4.1 backchannel transport module.
Ý Ý32m  OK   Ý0m¨ Mounted RPC Pipe File System.
Ý Ý32m  OK   Ý0m¨ Reached target rpc_pipefs.target.
Ý Ý32m  OK   Ý0m¨ Reached target NFS client services.
Ý Ý32m  OK   Ý0m¨ Reached target Remote File Systems (Pre).
Ý Ý32m  OK   Ý0m¨ Reached target Remote File Systems.
         Starting Crash recovery kernel arming...
Ý Ý1;31mFAILED Ý0m¨ Failed to start Crash recovery kernel arming.
See 'systemctl status kdump.service' for details.
Ý Ý32m  OK   Ý0m¨ Started Security Auditing Service.
         Starting Update UTMP about System Boot/Shutdown...
Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Boot/Shutdown.
         Starting Update UTMP about System Runlevel Changes...
Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Runlevel Changes.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ¬D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):
Give root password for maintenance
(or press Control-D to continue): xxxxxxxxxxxxxx

 Ý1;31mroot@mflnxclef00 ~# Ý0m journalctl -xb
journalctl -xb
WARNING: terminal is not fully functional
 -  (press RETURN)
  -- Logs begin at Sun 2023-02-26 20:53:38 CST, end at Sun 2023-02-26 20:55:13 
CST ÝmFeb 26 20:53:38 mflnxclef00.ailife.com systemd-
journalÝ91¨: Runtime journal is u ÝmFeb 26 20:53:38 mflnxclef00.ailife.com 
kernel: Initializing cgroup subsys cpuset ÝmFeb 26 20:53:
38 mflnxclef00.ailife.com kernel: Initializing cgroup subsys cpu Ým
Feb 26 20:53:38 mflnxclef00.ailife.com kernel: Initializing cgroup subsys 
cpuacc ÝmFeb 26 20:53:38 mflnxclef00.ailife.com kernel: Li
nux version 3.10.0-1160.62.1.el ÝmFeb 26 20:53:38 mflnxclef00.ailife.com 
kernel: setup: Linux is running as a z/VM ÝmFeb 26 20:53:38
mflnxclef00.ailife.com kernel: crashkernel=auto resulted in zero ÝmFeb 26 
20:53:38 mflnxclef00.ailife.com kernel: Write protected k
ernel read-only  ÝmFeb 26 20:53:38 mflnxclef00.ailife.com kernel: Zone ranges: 
Ým
Feb 26 20:53:38 mflnxclef00.ailife.com kernel:   DMA      Ýmem 
0x00000000-0x7fff ÝmFeb 26 20:53:38 mflnxclef00.ailife.com kernel:
Normal   empty Ým
Feb 26 20:53:38 mflnxclef00.ailife.com kernel: Movable zone start for each node 
Ým
Feb 26 20:53:38 mflnxclef00.ailife.com kernel: Early memory node ranges Ým
Feb 26 20:53:38 mflnxclef00.ailife.com kernel:   node   0: Ýmem 
0x00000000-0x3ff ÝmFeb 26 20:53:38 mflnxclef00.ailife.com kernel: In
itmem setup node 0 Ýmem 0x00000 ÝmFeb 26 20:53:38 mflnxclef00.ailife.com 
kernel: On node 0 totalpages: 262144 Ým
Feb 26 20:53:38 mflnxclef00.ailife.com kernel:   DMA zone: 4096 pages used for 
m ÝmFeb 26 20:53:38 mflnxclef00.ailife.com kernel:
DMA zone: 0 pages reserved Ým
Feb 26 20:53:38 mflnxclef00.ailife.com kernel:   DMA zone: 262144 pages, LIFO 
ba ÝmFeb 26 20:53:38 mflnxclef00.ailife.com kernel: pe
rcpu: Embedded 18 pages/cpu s33 ÝmFeb 26 20:53:38 mflnxclef00.ailife.com 
kernel: pcpu-alloc: s33792 r8192 d31744 u ÝmFeb 26 20:53:38
mflnxclef00.ailife.com kernel: pcpu-alloc: Ý0¨ 00 Ý0¨ 01 Ý0¨ 02  Ýmlines 1-23
mflnxclef00.ailife.com kernel: pcpu-alloc: Ý0¨ 00 Ý0¨ 01 Ý0¨ 02  Ýmlines 
1-23systemctl reboot
- log file: y ys st te em mc ct tl l   r re eb bo oo ot t  Warning: "ystemctl 
reboot" exists; Overwrite, Append or Don't log? d
lines 1-23 Feb 26 20:53:38 mflnxclef00.ailife.com kernel: pcpu-alloc: Ý0¨ 08 
Ý0¨ 09 Ý0¨ 10  Ýmlines 2-24
Feb 26 20:53:38 mflnxclef00.ailife.com kernel: pcpu-alloc: Ý0¨ 16 Ý0¨ 17 Ý0¨ 18 
 Ýmlines 3-25
Feb 26 20:53:38 mflnxclef00.ailife.com kernel: pcpu-alloc: Ý0¨ 24 Ý0¨ 25 Ý0¨ 26 
 Ýmlines 4-26

Each time I press enter then enter again, I get these lines (sililar).

I'm desparate, I got to get this back running by tomorrow morning.   Ideas?

Frank Ramaekers | Senior Systems Administrator | CIS Mainframe Services
Unisys | O-(512)387-3949 | M-(254(214-1820  | 
francis.ramaek...@unisys.com<mailto:francis.ramaek...@unisys.com>

[cid:image001.png@01D903EE.46B6DFB0]<https://urldefense.com/v3/__http:/www.unisys.com/__;!!GePVz-XrgrDUrw!p5jUPEpGs0mykR1bY5nekYSboDpZWpPwLSzpKp6-NI5TkGfiBC-deXy99AbFvhAJi0-rAn-ci8yPob4Mf7hurjsdIUMlSoQuShe8M-c$>

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is for use only by the intended recipient. If you received this in 
error, please contact the sender and delete the e-mail and its attachments from 
all devices.
[Grey_LI]<https://urldefense.com/v3/__http:/www.linkedin.com/company/unisys__;!!GePVz-XrgrDUrw!p5jUPEpGs0mykR1bY5nekYSboDpZWpPwLSzpKp6-NI5TkGfiBC-deXy99AbFvhAJi0-rAn-ci8yPob4Mf7hurjsdIUMlSoQuFGbyQbE$>
   [Grey_TW] 
<https://urldefense.com/v3/__http:/twitter.com/unisyscorp__;!!GePVz-XrgrDUrw!p5jUPEpGs0mykR1bY5nekYSboDpZWpPwLSzpKp6-NI5TkGfiBC-deXy99AbFvhAJi0-rAn-ci8yPob4Mf7hurjsdIUMlSoQumuZZrZ0$>
    [Grey_YT] 
<https://urldefense.com/v3/__http:/www.youtube.com/theunisyschannel__;!!GePVz-XrgrDUrw!p5jUPEpGs0mykR1bY5nekYSboDpZWpPwLSzpKp6-NI5TkGfiBC-deXy99AbFvhAJi0-rAn-ci8yPob4Mf7hurjsdIUMlSoQuwyQgUH8$>
   [Grey_FB] 
<https://urldefense.com/v3/__http:/www.facebook.com/unisyscorp__;!!GePVz-XrgrDUrw!p5jUPEpGs0mykR1bY5nekYSboDpZWpPwLSzpKp6-NI5TkGfiBC-deXy99AbFvhAJi0-rAn-ci8yPob4Mf7hurjsdIUMlSoQusGfh1_s$>
   [Grey_Vimeo] 
<https://urldefense.com/v3/__https:/vimeo.com/unisys__;!!GePVz-XrgrDUrw!p5jUPEpGs0mykR1bY5nekYSboDpZWpPwLSzpKp6-NI5TkGfiBC-deXy99AbFvhAJi0-rAn-ci8yPob4Mf7hurjsdIUMlSoQuUfEdzCc$>
   [Grey_UB] 
<https://urldefense.com/v3/__http:/blogs.unisys.com/__;!!GePVz-XrgrDUrw!p5jUPEpGs0mykR1bY5nekYSboDpZWpPwLSzpKp6-NI5TkGfiBC-deXy99AbFvhAJi0-rAn-ci8yPob4Mf7hurjsdIUMlSoQua_zH5FE$>

----------------------------------------------------------------------
This message contains information which is privileged and confidential and is 
solely for the use of the intended recipient. If you are not the intended 
recipient, be aware that any review, disclosure, copying, distribution, or use 
of the contents of this message is strictly prohibited. If you have received 
this in error, please destroy it immediately and notify us at 
privacy...@globe.life.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to