Hi Mark, Oops. It turns out the rdsosreport.txt isn't saved properly. So after the reboot we lost this.
I ran journalctl and watched for an eyecatcher. I noticed the LVM2_member missing message and not checking dasdl1. I can't remember any obvious message prior to that. Unfortunately the regular console log doesn't provide more information on that either. In fact, it's even more confusing as this has no apparent problem with dasdl1. Below the console, copied from the PROP log, but the last message before "Generating.." is lost. dasdm:(nonl) dasdm1 OK Found device /dev/dasdl1. OK Started dracut initqueue hook. Starting File System Check on /dev/dasdl1... OK Reached target Remote File Systems (Pre). OK Reached target Remote File Systems. OK Started File System Che Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. I have re-enabled the file system check for the LVM disk, let's see if this will once again introduce the error. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven -----Original Message----- From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> On Behalf Of Mark Post Sent: Monday, July 01, 2019 11:19 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: fsck failed during reboot On 7/1/19 11:05 AM, van Sleeuwen, Berry wrote: > Hi All, > > Today we have restarted an SLES12 guest. It fails the filesystem check, it > looks like on an LVM disk. I have disabled the filesystem check for the LVM > disk and then a new boot is successful. > > During reboot I get the error: > systemd[1]: Reached target Remote File Systems. > systemd-fsck[482]: fsck.LVM2_member doesn't exist, not checking file system > on /dev/dasdl1. > systemd[1]: Started File System Check on /dev/dasdl1. > systemd[1]: Mounting /sysroot... > mount[485]: mount: you must specify the filesystem type > systemd[1]: sysroot.mount: Mount process exited, code=exited status=1 > systemd[1]: Failed to mount /sysroot. > > The /dev/dasdl1 is the root disk and is not part of any LVM. > > What can cause this failure? I'm not sure. The messages prior to these may provide a clue. 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 https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CBerry.vanSleeuwen%40atos.net%7Cf78fac326ec44166c6c008d6fe6a8b9b%7C33440fc6b7c7412cbb730e70b0198d5a%7C0%7C0%7C636976130910985464&sdata=WAb2xQEs3VFJgQTMnnLGn7O3q4XIGdSV4YjoRoZlILI%3D&reserved=0 This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request. ---------------------------------------------------------------------- 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
