Re: GRUB - DRACUT error on SLES 12 SP5
On 10/15/21 11:12 AM, Victor Echavarry wrote: dracut-initqueue[418]: Warning: Could not boot. Starting Dracut Emergency Shell... Warning: /dev/swapvg/swap01lv does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. Give root password for maintenance (or press Control-D to continue): How this happened after patching a guest? There is a way to solve it? I would guess that it's not related to any patching you did. The most frequent cause of this that I've seen is that someone added a new disk to the LVM volume group, and did it in a way that the udev rules for it weren't written out to /etc/udev/rules.d/. You should be able to run vgscan and pvscan to see if those report any missing disks. If they do, then bring the volume online and re-run them. Then "systemctl default" should bring the system up the rest of the way and you can check to see if the necessary udev rules are there, or if they're excluded by cio_ignore, etc., etc. Mark Post -- 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
Re: SystemD question
On 10/15/21 1:13 PM, Tully, Phil (CORP) wrote: In systemd, is it possible to stop bringing any additional services until the network is up and connected? If you're talking about user-defined services, i.e., not something shipped by the Linux distribution provider, than yes. See Dan Horák's email for that. If you're talking about things that were shipped from Linux distribution provider, or an ISV, then you're getting into somewhat dangerous territory. In general, things that come with the distribution _should_ already be set up to start after the network if they depend on that being present. Yes, you can create overrides for the service unit files they send. That may or may not cause problems with other services. If you do that, test thoroughly, and be prepared to be asked to revert that change if your support provider thinks it may be implicated in any service request you've opened. Mark Post -- 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
SystemD question
In systemd, is it possible to stop bringing any additional services until the network is up and connected? Regards, Phil Tully This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system. -- 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
Re: SystemD question
On Fri, 15 Oct 2021 17:13:24 + "Tully, Phil (CORP)" wrote: > In systemd, is it possible to stop bringing any additional services until the > network is up and connected? I believe adding After=network-online.target to your unit file should do what you need. They have good documentation, so you should be able to find the details there. Dan > > Regards, Phil Tully > > > > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. If > the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, notify the sender immediately by return > email and delete the message and any attachments from your system. > > -- > 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 -- 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
GRUB - DRACUT error on SLES 12 SP5
After patching a guest and reboot it, we find the following error: Booting default (grub2) dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: dracut-initqueue timeout - starting timeout scri pts dracut-initqueue[418]: Warning: Could not boot. Starting Dracut Emergency Shell... Warning: /dev/swapvg/swap01lv does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. Give root password for maintenance (or press Control-D to continue): How this happened after patching a guest? There is a way to solve it? Regards, Victor Echavarry System Programmer Operating Systems EVERTEC, LLC WARNING: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of EVERTEC, Inc. or its affiliates. Finally, the integrity and security of this message cannot be guaranteed on the Internet, and as such EVERTEC, Inc. and its affiliates accept no liability for any damage caused by any virus transmitted by this email. -- 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
Velocity Software web sites brief outage on Monday 18 October
Hello everyone, This is cross-posted to IBMVM and LINUX390: Velocity Software will be having a brief outage affecting connectivity beginning on Monday, 18 October at 5:00 AM Eastern / 2:00 AM Pacific time. The impact should last about two hours. The outage will include the following web sites: VELOCITYSOFTWARE.COM WWW.VELOCITYSOFTWARE.COM VMTRACK.VELOCITYSOFTWARE.COM WWW.VELOCITY-SOFTWARE.COM WWW.VMWORKSHOP.ORG WWW.LINUXVM.COM WWW.BAYBUNCH.ORG WWW.CAVMEN.ORG WWW.MVMUA.ORG The Velocity Software problem tracking system (PTRACK) will also be affected. If you have any issues or questions any time the PTRACK system is unavailable, please call us at 650-964-8867 or email supp...@velocitysoftware.com. Thank you! - Rick Barlow Senior z/VM Specialist Velocity Software, Inc. Headquarters: 196 D Castro St, Mountain View, CA 84041 Office Main: (650) 964-8867 http://www.velocitysoftware.com -- 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
