Re: [systemd-devel] How to debug this strange issue about "systemd"?
On Sat, 01.08.15 12:51, sean (x...@suse.com) wrote: > On Fri, 2015-07-17 at 10:43 +0100, Colin Guthrie wrote: > > >> See "man dracut" and the "Debugging dracut" section. Also see "man > > >> dracut.cmdline" and the "rd.break" bits. > > >> > > > > > > Was it not man dracut.kernel? > > > > dracut.kernel == dracut.cmdline here (the latter seems to be the > > preferred name as it's the title in the manpage) and indeed: > > > > lrwxrwxrwx 1 root root 19 Jun 5 17:11 > > /usr/share/man/man7/dracut.kernel.7.xz -> dracut.cmdline.7.xz > Thanks very much for all help. > The root cause is that 64 bit libraries were not included in the real > ext4 file system. > > But now a new issue appears, Boot failed at "[ ok ] Reached target > System Initialization". > How to debug it? > > > The attachment is the full log message. > > [FAILED] Failed to start Postfix Mail Transport Agent. > See "systemctl status postfix.service" for details. > Starting Command Scheduler... > [ OK ] Started Command Scheduler. > Starting smfpd.service... > [ OK ] Started smfpd.service. > Starting /etc/init.d/boot.local Compatibility... > [ OK ] Started /etc/init.d/boot.local Compatibility. > Starting Wait for Plymouth Boot Screen to Quit... > Starting Terminate Plymouth Boot Screen... Your boot shows tons of failed services. It might be a good idea to look into those services with "systemctl status" and then talk to your distro about this, as downstream services are not really something we can help you with at systemd upstream. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to debug this strange issue about "systemd"?
On Fri, 2015-07-17 at 10:43 +0100, Colin Guthrie wrote: > >> See "man dracut" and the "Debugging dracut" section. Also see "man > >> dracut.cmdline" and the "rd.break" bits. > >> > > > > Was it not man dracut.kernel? > > dracut.kernel == dracut.cmdline here (the latter seems to be the > preferred name as it's the title in the manpage) and indeed: > > lrwxrwxrwx 1 root root 19 Jun 5 17:11 > /usr/share/man/man7/dracut.kernel.7.xz -> dracut.cmdline.7.xz Thanks very much for all help. The root cause is that 64 bit libraries were not included in the real ext4 file system. But now a new issue appears, Boot failed at "[ ok ] Reached target System Initialization". How to debug it? The attachment is the full log message. [FAILED] Failed to start Postfix Mail Transport Agent. See "systemctl status postfix.service" for details. Starting Command Scheduler... [ OK ] Started Command Scheduler. Starting smfpd.service... [ OK ] Started smfpd.service. Starting /etc/init.d/boot.local Compatibility... [ OK ] Started /etc/init.d/boot.local Compatibility. Starting Wait for Plymouth Boot Screen to Quit... Starting Terminate Plymouth Boot Screen... -- Sean. XinRong Fu Dedicate System Engineer SUSE x...@suse.com (P)+86 18566229618 line SUSE [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.1.0-rc2-7-desktop+ (s...@linux-dunz.site) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #7 SMP PREEMPT Sat Jul 4 23:39:33 CST 2015 [0.00] Command line: root=UUID=20059b62-2542-4a85-80cf-41da6e0c1137 rootflags=rw rootfstype=ext4 console=ttyS0,115200n8 console=tty0 systemd.unit=default.target systemd.confirm_spawn=auto systemd.show_status=ture systemd.log_level=debug [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x3ffd] usable [0.00] BIOS-e820: [mem 0x3ffe-0x3fff] reserved [0.00] BIOS-e820: [mem 0xfeffc000-0xfeff] reserved [0.00] BIOS-e820: [mem 0xfffc-0x] reserved [0.00] earlycon: no match for ttyS0,115200n8 [0.00] earlycon: no match for tty0 [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.8 present. [0.00] Hypervisor detected: KVM [0.00] AGP: No AGP bridge found [0.00] e820: last_pfn = 0x3ffe0 max_arch_pfn = 0x4 [0.00] PAT not supported by CPU. [0.00] found SMP MP-table at [mem 0x000f0ec0-0x000f0ecf] mapped at [880f0ec0] [0.00] Scanning 1 areas for low memory corruption [0.00] init_memory_mapping: [mem 0x-0x000f] [0.00] init_memory_mapping: [mem 0x3d80-0x3d9f] [0.00] init_memory_mapping: [mem 0x2000-0x3d7f] [0.00] init_memory_mapping: [mem 0x0010-0x1fff] [0.00] init_memory_mapping: [mem 0x3da0-0x3ffd] [0.00] RAMDISK: [mem 0x3da25000-0x3ffe] [0.00] Allocated new RAMDISK: [mem 0x3b45a000-0x3da2417f] [0.00] Move RAMDISK from [mem 0x3da25000-0x3ffef17f] to [mem 0x3b45a000-0x3da2417f] [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F0CD0 14 (v00 BOCHS ) [0.00] ACPI: ?ɳ� 0x3FFE1854 8A476AE6 (v251 �??� ? ??�&�^�? 318ACCAB e8�? 6D99E0DB) [0.00] [ cut here ] [0.00] WARNING: CPU: 0 PID: 0 at mm/early_ioremap.c:136 __early_ioremap.constprop.0+0x11f/0x1f2() [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.0-rc2-7-desktop+ #7 [0.00] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5-0-ge51488c-20141015_183547-build31 04/01/2014 [0.00] 81a3ad65 81c03ca8 8169d79b 0198 [0.00] 81c03ce8 81066d8a 30783020cfb3c93f [0.00] 0008a478 8163 ca45833a [0.00] Call Trace: [0.00] [] dump_stack+0x4c/0x6e [0.00] [] warn_slowpath_common+0x8a/0xc0 [0.00] [] warn_slowpath_null+0x1a/0x20 [0.00] [] __early_ioremap.constprop.0+0x11f/0x1f2 [0.00] [] early_ioremap+0x13/0x15 [0.00] [] __acpi_map_table+0x13/0x18 [0.00] [] acpi_os_map_iomem+0x27/0x151 [0.00] [] acpi_os_map_memory+0xe/0x10 [0.00] [] acpi_tb_parse_root_table+0x16d/0x29b [0.00] [] acpi_initialize_tables+0xcc/0xf8 [0.00] [] acpi_table_init+0x50/0xc
Re: [systemd-devel] How to debug this strange issue about "systemd"?
Andrei Borzenkov wrote on 17/07/15 10:22: > On Fri, Jul 17, 2015 at 12:18 PM, Colin Guthrie wrote: >> sean wrote on 17/07/15 09:33: >>> On Fri, 2015-07-17 at 06:55 +0300, Andrei Borzenkov wrote: В Wed, 15 Jul 2015 23:03:02 +0800 sean пишет: > Hi All: > I am trying to test the latest upstream kernel, But i encounter a > strange issue about systemd. > When the "systemd" extracted from initrd image mounts the real root file > system "hda.img" on "/sysroot" and changes root to the new directory, it > can not found "/sbin/init" and "/bin/sh". > In fact, These two files exist in the "hda.img". > How to debug this issue? > Why does not it enter emergency mode? > If enter emergency mode, maybe this issue become easy. > You can stop in dracut just before switch root step and examine environment. At this point root should already be mounted. >>> Thanks very much! >>> How to stop the booting process before switch root? >> >> See "man dracut" and the "Debugging dracut" section. Also see "man >> dracut.cmdline" and the "rd.break" bits. >> > > Was it not man dracut.kernel? dracut.kernel == dracut.cmdline here (the latter seems to be the preferred name as it's the title in the manpage) and indeed: lrwxrwxrwx 1 root root 19 Jun 5 17:11 /usr/share/man/man7/dracut.kernel.7.xz -> dracut.cmdline.7.xz :) Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to debug this strange issue about "systemd"?
On Fri, Jul 17, 2015 at 12:18 PM, Colin Guthrie wrote: > sean wrote on 17/07/15 09:33: >> On Fri, 2015-07-17 at 06:55 +0300, Andrei Borzenkov wrote: >>> В Wed, 15 Jul 2015 23:03:02 +0800 >>> sean пишет: >>> Hi All: I am trying to test the latest upstream kernel, But i encounter a strange issue about systemd. When the "systemd" extracted from initrd image mounts the real root file system "hda.img" on "/sysroot" and changes root to the new directory, it can not found "/sbin/init" and "/bin/sh". In fact, These two files exist in the "hda.img". How to debug this issue? Why does not it enter emergency mode? If enter emergency mode, maybe this issue become easy. >>> >>> You can stop in dracut just before switch root step and examine >>> environment. At this point root should already be mounted. >> Thanks very much! >> How to stop the booting process before switch root? > > See "man dracut" and the "Debugging dracut" section. Also see "man > dracut.cmdline" and the "rd.break" bits. > Was it not man dracut.kernel? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to debug this strange issue about "systemd"?
sean wrote on 17/07/15 09:33: > On Fri, 2015-07-17 at 06:55 +0300, Andrei Borzenkov wrote: >> В Wed, 15 Jul 2015 23:03:02 +0800 >> sean пишет: >> >>> Hi All: >>> I am trying to test the latest upstream kernel, But i encounter a >>> strange issue about systemd. >>> When the "systemd" extracted from initrd image mounts the real root file >>> system "hda.img" on "/sysroot" and changes root to the new directory, it >>> can not found "/sbin/init" and "/bin/sh". >>> In fact, These two files exist in the "hda.img". >>> How to debug this issue? >>> Why does not it enter emergency mode? >>> If enter emergency mode, maybe this issue become easy. >>> >> >> You can stop in dracut just before switch root step and examine >> environment. At this point root should already be mounted. > Thanks very much! > How to stop the booting process before switch root? See "man dracut" and the "Debugging dracut" section. Also see "man dracut.cmdline" and the "rd.break" bits. HTHs Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to debug this strange issue about "systemd"?
On Fri, 2015-07-17 at 06:55 +0300, Andrei Borzenkov wrote: > В Wed, 15 Jul 2015 23:03:02 +0800 > sean пишет: > > > Hi All: > > I am trying to test the latest upstream kernel, But i encounter a > > strange issue about systemd. > > When the "systemd" extracted from initrd image mounts the real root file > > system "hda.img" on "/sysroot" and changes root to the new directory, it > > can not found "/sbin/init" and "/bin/sh". > > In fact, These two files exist in the "hda.img". > > How to debug this issue? > > Why does not it enter emergency mode? > > If enter emergency mode, maybe this issue become easy. > > > > You can stop in dracut just before switch root step and examine > environment. At this point root should already be mounted. Thanks very much! How to stop the booting process before switch root? > > > qemu command line: > > qemu-kvm -D /tmp/qemu-kvm-machine.log -m 1024M -append > > "root=UUID=20059b62-2542-4a85-80cf-41da6e0c1137 rootflags=rw > > rootfstype=ext4 debug debug_objects console=ttyS0,115200n8 console=tty0 > > rd.debug rd.shell=1 log_buf_len=1M systemd.unit=emergency.target > > systemd.log_level=debug systemd.log_target=console" -kernel > > ./qemu_platform/bzImage -hda ./qemu_platform/hda.img > > -initrd ./qemu_platform/initrd-4.1.0-rc2-7-desktop+ -device > > e1000,netdev=network0 -netdev user,id=network0 -serial > > file:/home/sean/work/source/upstream/kernel.org/ttys0.txt > > > ... > > > > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> sudo mount > > -o loop ./hda.img ./hda > > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> ls -l > > ./hda/sbin/init > > lrwxrwxrwx 1 sean users 26 Jul 14 22:49 ./hda/sbin/init -> > > ../usr/lib/systemd/systemd > > Do you have separate /usr? No, Only one disk partition. > > > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> ls -l > > ./hda/bin/sh > > lrwxrwxrwx 1 sean users 4 Oct 26 2014 ./hda/bin/sh -> bash > > > > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> lsinitrd > > ./initrd-4.1.0-rc2-7-desktop+ |grep "sbin\/init" > > -rwxr-xr-x 1 root root 1223 Nov 27 2014 sbin/initqueue > > lrwxrwxrwx 1 root root 26 Jul 14 21:00 sbin/init -> > > ../usr/lib/systemd/systemd > > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> lsinitrd > > ./initrd-4.1.0-rc2-7-desktop+ |grep "bin\/sh" > > lrwxrwxrwx 1 root root4 Jul 14 21:00 bin/sh -> bash > > > > > > > > -- Sean. XinRong Fu Dedicate System Engineer SUSE x...@suse.com (P)+86 18566229618 line SUSE ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to debug this strange issue about "systemd"?
В Wed, 15 Jul 2015 23:03:02 +0800 sean пишет: > Hi All: > I am trying to test the latest upstream kernel, But i encounter a > strange issue about systemd. > When the "systemd" extracted from initrd image mounts the real root file > system "hda.img" on "/sysroot" and changes root to the new directory, it can > not found "/sbin/init" and "/bin/sh". > In fact, These two files exist in the "hda.img". > How to debug this issue? > Why does not it enter emergency mode? > If enter emergency mode, maybe this issue become easy. > You can stop in dracut just before switch root step and examine environment. At this point root should already be mounted. > qemu command line: > qemu-kvm -D /tmp/qemu-kvm-machine.log -m 1024M -append > "root=UUID=20059b62-2542-4a85-80cf-41da6e0c1137 rootflags=rw rootfstype=ext4 > debug debug_objects console=ttyS0,115200n8 console=tty0 > rd.debug rd.shell=1 log_buf_len=1M systemd.unit=emergency.target > systemd.log_level=debug systemd.log_target=console" -kernel > ./qemu_platform/bzImage -hda ./qemu_platform/hda.img > -initrd ./qemu_platform/initrd-4.1.0-rc2-7-desktop+ -device > e1000,netdev=network0 -netdev user,id=network0 -serial > file:/home/sean/work/source/upstream/kernel.org/ttys0.txt > ... > > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> sudo mount > -o loop ./hda.img ./hda > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> ls -l > ./hda/sbin/init > lrwxrwxrwx 1 sean users 26 Jul 14 22:49 ./hda/sbin/init -> > ../usr/lib/systemd/systemd Do you have separate /usr? > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> ls -l > ./hda/bin/sh > lrwxrwxrwx 1 sean users 4 Oct 26 2014 ./hda/bin/sh -> bash > > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> lsinitrd > ./initrd-4.1.0-rc2-7-desktop+ |grep "sbin\/init" > -rwxr-xr-x 1 root root 1223 Nov 27 2014 sbin/initqueue > lrwxrwxrwx 1 root root 26 Jul 14 21:00 sbin/init -> > ../usr/lib/systemd/systemd > sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> lsinitrd > ./initrd-4.1.0-rc2-7-desktop+ |grep "bin\/sh" > lrwxrwxrwx 1 root root4 Jul 14 21:00 bin/sh -> bash > > > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] How to debug this strange issue about "systemd"?
Hi All: I am trying to test the latest upstream kernel, But i encounter a strange issue about systemd. When the "systemd" extracted from initrd image mounts the real root file system "hda.img" on "/sysroot" and changes root to the new directory, it can not found "/sbin/init" and "/bin/sh". In fact, These two files exist in the "hda.img". How to debug this issue? Why does not it enter emergency mode? If enter emergency mode, maybe this issue become easy. qemu command line: qemu-kvm -D /tmp/qemu-kvm-machine.log -m 1024M -append "root=UUID=20059b62-2542-4a85-80cf-41da6e0c1137 rootflags=rw rootfstype=ext4 debug debug_objects console=ttyS0,115200n8 console=tty0 rd.debug rd.shell=1 log_buf_len=1M systemd.unit=emergency.target systemd.log_level=debug systemd.log_target=console" -kernel ./qemu_platform/bzImage -hda ./qemu_platform/hda.img -initrd ./qemu_platform/initrd-4.1.0-rc2-7-desktop+ -device e1000,netdev=network0 -netdev user,id=network0 -serial file:/home/sean/work/source/upstream/kernel.org/ttys0.txt Job initrd-switch-root.target/start finished, result=done Accepted new private connection. Got message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/agent interface=org.freedesktop.systemd1.Agent member=Released cookie=1 reply_cookie=0 error=n/a Got disconnect on private connection. Received SIGCHLD from PID 520 (plymouth). Child 520 (plymouth) died (code=exited, status=0/SUCCESS) Child 520 belongs to plymouth-switch-root.service plymouth-switch-root.service: main process exited, code=exited, status=0/SUCCESS plymouth-switch-root.service changed start -> dead Job plymouth-switch-root.service/start finished, result=done plymouth-switch-root.service: cgroup is empty ConditionPathExists=/etc/initrd-release succeeded for initrd-switch-root.service. About to execute: /usr/bin/systemctl --no-block --force switch-root /sysroot Forked /usr/bin/systemctl as 527 initrd-switch-root.service changed dead -> start Accepted new private connection. Got message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=SwitchRoot cookie=1 reply_cookie=0 error=n/a Sent message type=method_return sender=n/a destination=n/a object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a Serializing state to /run/systemd Switching root. Closing left-over fd 21 Closing left-over fd 22 Closing left-over fd 23 Closing left-over fd 26 Closing left-over fd 27 No /sbin/init, trying fallback Failed to execute /bin/sh, giving up: No such file or directory sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> sudo mount -o loop ./hda.img ./hda sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> ls -l ./hda/sbin/init lrwxrwxrwx 1 sean users 26 Jul 14 22:49 ./hda/sbin/init -> ../usr/lib/systemd/systemd sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> ls -l ./hda/bin/sh lrwxrwxrwx 1 sean users 4 Oct 26 2014 ./hda/bin/sh -> bash sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> lsinitrd ./initrd-4.1.0-rc2-7-desktop+ |grep "sbin\/init" -rwxr-xr-x 1 root root 1223 Nov 27 2014 sbin/initqueue lrwxrwxrwx 1 root root 26 Jul 14 21:00 sbin/init -> ../usr/lib/systemd/systemd sean@linux-dunz:~/work/source/upstream/kernel.org/qemu_platform> lsinitrd ./initrd-4.1.0-rc2-7-desktop+ |grep "bin\/sh" lrwxrwxrwx 1 root root4 Jul 14 21:00 bin/sh -> bash -- Sean. XinRong Fu Dedicate System Engineer SUSE x...@suse.com (P)+86 18566229618 line SUSE -- Sean. XinRong Fu Dedicate System Engineer SUSE x...@suse.com (P)+86 18566229618 line SUSE ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
