<div dir="ltr">I'm trying to be helpful, but it could still be an issue with the <span style="background-color:rgb(159,197,232)">systemd-fsck-root.service </span><div>The initrd phase is typically very fast because it doesn't need to load many files. </div><div>You might try booting from a live USB to boot. You can use the Gparted tool to check the root file system for errors. </div><div> </div><div>I'm not clear about what you are saying, when you report "issue is disappeared" Try double checking the dracut logs. </div><div><br></div><div>An error like <span style="color:rgb(31,31,31);font-family:"Google Sans","Helvetica Neue",sans-serif;font-size:16px">"Failed to mount /dev/sda1" indicates there's a problem with the root files system. </span></div><div><span style="color:rgb(31,31,31);font-family:"Google Sans","Helvetica Neue",sans-serif;font-size:16px">"Executing command '/sbin/fsck -C -f /dev/sda1'" would mean the fsck command is executing.</span></div><div><span style="color:rgb(31,31,31);font-family:"Google Sans","Helvetica Neue",sans-serif;font-size:16px">Something like "Command '/sbin/fsck -C -f /dev/sda1' took 10 seconds to execute" might help you find the issue.</span><span style="color:rgb(31,31,31);font-family:"Google Sans","Helvetica Neue",sans-serif;font-size:16px"><br></span></div><div><span style="color:rgb(31,31,31);font-family:"Google Sans","Helvetica Neue",sans-serif;font-size:16px"><br></span></div><div><span style="color:rgb(31,31,31);font-family:"Google Sans","Helvetica Neue",sans-serif;font-size:16px">Benjamin Godfrey</span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, May 9, 2023 at 5:00 AM <<a href="mailto:systemd-devel-request@lists.freedesktop.org">systemd-devel-request@lists.freedesktop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send systemd-devel mailing list submissions to<br> <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a><br> <br> To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br> or, via email, send a message with subject or body 'help' to<br> <a href="mailto:systemd-devel-request@lists.freedesktop.org" target="_blank">systemd-devel-request@lists.freedesktop.org</a><br> <br> You can reach the person managing the list at<br> <a href="mailto:systemd-devel-owner@lists.freedesktop.org" target="_blank">systemd-devel-owner@lists.freedesktop.org</a><br> <br> When replying, please edit your Subject line so it is more specific<br> than "Re: Contents of systemd-devel digest..."<br> <br> <br> Today's Topics:<br> <br> 1. Re: Reg: systemd boot up hung after sysroot.mount in initrd<br> phase (RAJESH DASARI)<br> <br> <br> ----------------------------------------------------------------------<br> <br> Message: 1<br> Date: Tue, 9 May 2023 10:24:56 +0300<br> From: RAJESH DASARI <<a href="mailto:raajeshdasari@gmail.com" target="_blank">raajeshdasari@gmail.com</a>><br> To: <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a><br> Subject: Re: [systemd-devel] Reg: systemd boot up hung after<br> sysroot.mount in initrd phase<br> Message-ID:<br> <CAPXMrf-uH14BXEeJVmOz=<a href="mailto:WapCxe7S2T6-pC5LFL7PLcj%2B0RV0g@mail.gmail.com" target="_blank">WapCxe7S2T6-pC5LFL7PLcj+0RV0g@mail.gmail.com</a>><br> Content-Type: text/plain; charset="UTF-8"<br> <br> Hi ,<br> <br> Could someone please respond ?<br> <br> Thanks,<br> Rajesh Dasari.<br> <br> On Sun, May 7, 2023 at 8:28?PM RAJESH DASARI <<a href="mailto:raajeshdasari@gmail.com" target="_blank">raajeshdasari@gmail.com</a>> wrote:<br> ><br> > Hi ,<br> ><br> > We are issuing reboot with this command systemctl --no-block reboot<br> > and boot up is stuck at initrd phase , we are using dracut and<br> > systemd in initramfs phase. Boot up is stuck after sysroot.mount is<br> > executed(Issue is always reproducible), I have enabled debug logs by<br> > passing systemd.log_level=debug systemd.log_target=console to kernel<br> > command line , issue is disappeared and I also tried to enable the<br> > dracut debug logs rd.debug=1, issue is disappeared. Then I have added<br> > sleep 1 in the systemd-fsck-root.service , then the issue is not seen.<br> > So it looks like a timing issue.<br> ><br> ><br> > Starting [0;1;39msystemd-fsck-root.service[0m - File System Check on<br> > /dev/disk/by-label/rootfs...<br> > Finished [0;1;39msystemd-fsck-root.service[0m - File System Check on<br> > /dev/disk/by-label/rootfs.<br> > Mounting [0;1;39msysroot.mount[0m - /sysroot...<br> > EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)<br> > Mounted [0;1;39msysroot.mount[0m - /sysroot. -> boot up stuck after this.<br> ><br> ><br> > We are using systemd version-251.13 and with systemd version-249.14<br> > we didn't notice this. Is there any new issue with this version or Is<br> > there any known issue if not Could you please let me know how to debug<br> > this further.<br> ><br> > Regards,<br> > Rajesh.<br> <br> <br> ------------------------------<br> <br> Subject: Digest Footer<br> <br> _______________________________________________<br> systemd-devel mailing list<br> <a href="mailto:systemd-devel@lists.freedesktop.org" target="_blank">systemd-devel@lists.freedesktop.org</a><br> <a href="https://lists.freedesktop.org/mailman/listinfo/systemd-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br> <br> <br> ------------------------------<br> <br> End of systemd-devel Digest, Vol 157, Issue 8<br> *********************************************<br> </blockquote></div>