Mount segfaluts in rc.sysinit

Hi everyone,
since my last pacman -Syu last night I'm experiencing problems at boot time with the "Mounting Local Filesystems" phase.
I managed to find the problem:
/bin/mount -a -t $NETFS -O no_netdev
causes mount command to segfault.
Actually mount seems to his job correctly on common cases, the problem rises when I try to use the "-O no_netdev" option or the "-O _netdev" as found in /etc/rc.d/netfs.
here is strace output for "mount -a -O _no_netfs":
execve("/bin/mount", ["mount", "-a", "-O", "_netdev"], [/* 52 vars */]) = 0
brk(0) = 0xd96000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa3fb31a000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=198493, ...}) = 0
mmap(NULL, 198493, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fa3fb2e9000
close(3) = 0
open("/lib/libblkid.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220b\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=149256, ...}) = 0
mmap(NULL, 2244376, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fa3faeda000
mprotect(0x7fa3faefb000, 2097152, PROT_NONE) = 0
mmap(0x7fa3fb0fb000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x21000) = 0x7fa3fb0fb000
close(3) = 0
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\200\20\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1420688, ...}) = 0
mmap(NULL, 3529416, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fa3fab7c000
mprotect(0x7fa3facd0000, 2097152, PROT_NONE) = 0
mmap(0x7fa3faed0000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x154000) = 0x7fa3faed0000
mmap(0x7fa3faed5000, 19144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fa3faed5000
close(3) = 0
open("/lib/libuuid.so.1", O_RDONLY) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\24\0\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=15400, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa3fb2e8000
mmap(NULL, 2110424, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fa3fa978000
mprotect(0x7fa3fa97b000, 2097152, PROT_NONE) = 0
mmap(0x7fa3fab7b000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7fa3fab7b000
close(3) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa3fb2e6000
arch_prctl(ARCH_SET_FS, 0x7fa3fb2e6740) = 0
mprotect(0x7fa3faed0000, 16384, PROT_READ) = 0
mprotect(0x7fa3fb31b000, 4096, PROT_READ) = 0
munmap(0x7fa3fb2e9000, 198493) = 0
brk(0) = 0xd96000
brk(0xdb7000) = 0xdb7000
open("/usr/lib/locale/locale-archive", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2035552, ...}) = 0
mmap(NULL, 2035552, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fa3fa787000
close(3) = 0
umask(022) = 022
open("/dev/null", O_RDWR) = 3
close(3) = 0
getuid() = 0
geteuid() = 0
umask(077) = 022
open("/etc/fstab", O_RDONLY) = 3
umask(022) = 077
fstat(3, {st_mode=S_IFREG|0644, st_size=1718, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa3fb319000
read(3, "# \n# /etc/fstab: static file sys"..., 4096) = 1718
read(3, "", 4096) = 0
close(3) = 0
munmap(0x7fa3fb319000, 4096) = 0
--- {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} (Segmentation fault) ---
+++ killed by SIGSEGV +++
Segmentation fault
I tried to downgrade util-linux to 2.19-4 version an this solves the problem.
Is anyone having the same troubles?
Bye
Stripe

https://bugs.archlinux.org/task/24261

Similar Messages

  • Install arch on a read-only filesystem

    Hi to all, I have an idea about installing arch in a particular way, a way that makes the system more secure.
    I want to install a host archlinux system on a hard disk or ssd but I want no data can be written to the storage. The host system will have a predefined set of programs and should use a ramdisk to store temporary data. It is something very similar to a ISO.
    The real computation will be handled through a series of virtualbox instances of linux ( the virtualbox images will be stored on an external hard disk, a read/write volume ).
    How could I achieve this? Through unionfs? AUFS? or some other thing?
    Last edited by pabloski (2011-02-16 16:18:11)

    I want to mount my sda2 read-only and union it with a tmpfs, so the machine is secure and the file system is the same every boot.
    I installed aufs3 with 3.2.6-1-aufs_friendly, I made a hook (as some-guy94 adviced), but it doesn't work.
    The code is:
    1. mkdir -p /root/ro /root/rw
    2. mount /dev/sda2 /root/ro
    3. mount -t tmpfs root.rw /root/rw
    4. mount -t aufs -o "dirs=/root/rw=rw:/root/ro=ro" root.union /
    At 2. it says: "mount: mounting /dev/sda2 on /root/ro failed: No such file or directory" Both files exist - I can list them just before the mount.
    3. & 4. work, but it doesn't matter as sda2 gets mounted rw on / right after (by initramfs's init, I gues).
    Can you help me with this, or point some useful howtos?
    Btw: is there a better way of debugging a hook, other than making the image and rebooting each change?
    Update: This is how they did it in larch: http://git.berlios.de/cgi-bin/gitweb.cg … cpio/hooks
    mount -t ext3 /dev/sda2 /root/ro works now.
    I used exec /sbin/switch_root as in larch3 hook and for loop from /lib/initcpio/init:109 to move /proc /dev /sys /run to the new root
    So the union mount works just fine now, my sda2/sbin/init & sda2/etc/rc.sysinit run, but the latter fails with following:
    * Mounting Root Read-Only - this is actually quite acceptable
    * Starting UDev Daemon
    * Loading Modules
    * Remounting Root Read/Write - acceptable as well
    After boot X opens and system freezes immediately (no reaction to keyboard, doesn't ping). No useful information in logs. I don't think system can run well without udev/modules. So this is udev not liking / mounted rw (as tmpfs is rw) or maybe /dev /proc /sys /run fault.
    I tried to make union mount only in rc.sysinit when /dev/sda2 is already mounted on /, but mount --move / other-dir fails.
    Any ideas what can be wrong?
    My code:
    run_hook ()
    read -p "Union mount root (y/N)? " answer
    if [[ "$answer" == "y" ]]; then
    modprobe aufs
    ro="/root/ro"
    rw="/root/rw"
    un="/root/un"
    rob="${un}/ro"
    rwb="${un}/rw"
    mkdir -p $ro $rw $un
    mount -t ext3 /dev/sda2 $ro
    mount -t tmpfs -o "size=20%" root.rw $rw
    mount -t aufs -o "dirs=${rw}=rw:${ro}=ro" root.union $un
    mkdir -p $rob $rwb
    mount --bind $ro $rob
    mount --bind $rw $rwb
    mkdir ${un}/media
    mkdir ${un}/sys
    mkdir ${un}/proc
    mkdir ${un}/dev
    /bin/mknod ${un}/dev/console c 5 1
    echo "rootfs / rootfs rw 0 0" >${un}/etc/mtab
    [ -z "${init}" ] && init="/sbin/init"
    if [ -e "${un}/${init}" ]; then
    mount
    read
    for d in proc sys dev run; do
    if [ -d ${un}/${d} ]; then
    mount --move /${d} ${un}/${d}
    else
    umount /${d}
    fi
    done
    exec /sbin/switch_root -c /dev/console ${un} ${init} ${CMDLINE}
    fi
    fi
    Last edited by kaos (2012-02-22 17:14:18)

  • Arch 0.7 ISO: wrong udev setup?

    I recently installed a PC for a friend with the Arch 0.7 ISO. I have 2 questions on the default udev setup.
    1) lilo.conf
    Our bootloader was lilo. When we changed the udev permissions, our changes were ignored. We solved the problem by appending "devfs=nomount" to our boot line in the lilo.conf (thanks Wiki ). That was missing in the default lilo.conf
    Could that option be added to the default lilo.conf?
    2) fstab
    in the default fstab, sysfs is mounted. On the wiki (http://wiki.archlinux.org/index.php/UdevHowTo) it is said to unmount sysfs.
    Which is better: keep sysfs, or unmount it?
    Thanks is advance!

    zezaz wrote:
    I recently installed a PC for a friend with the Arch 0.7 ISO. I have 2 questions on the default udev setup.
    1) lilo.conf
    Our bootloader was lilo. When we changed the udev permissions, our changes were ignored. We solved the problem by appending "devfs=nomount" to our boot line in the lilo.conf (thanks Wiki ). That was missing in the default lilo.conf
    Could that option be added to the default lilo.conf?
    Yea, you have to add the "devfs=nomount" part manually.  I'm still on the fence on that one, as I don't want to have the defaults break things for kernel 2.4.x users (udev won't work for them, afaik).
    2) fstab
    in the default fstab, sysfs is mounted. On the wiki (http://wiki.archlinux.org/index.php/UdevHowTo) it is said to unmount sysfs.
    Which is better: keep sysfs, or unmount it?
    Doesn't matter, actually.  You can remove it from your /etc/fstab altogether, as it (and /proc) will be explicitly mounted in /etc/rc.sysinit at boot-up.

  • Unmounting Filesystem Failing

    After the recent initscripts upgrade, whenever I poweroff or reboot my EeePC 901, the root filesystem is not unmounted, and at reboot the disk is fscked.
    Unmounting Filesystem [Fail]
    Remounting Root Filesystem Read-only [Fail]
    All of the daemons are successfully reported stopped (including Laptop-mode which I stop with a script in rc.local.shutdown when on battery: https://bbs.archlinux.org/viewtopic.php … 14#p930314).
    The laptop is completely up-to-date. How would I go about diagnosing what is preventing the clean shutdown?

    jasonwryan wrote:
    Sure.
    # <file system> <dir> <type> <options> <dump> <pass>
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs defaults 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    UUID=78b9738e-dd5b-4616-a6dc-1ca8c96e0209 / ext2 defaults,noatime 0 1
    UUID=f1e7eedd-66e0-4e86-821d-f57b1fa2c0ca /home ext2 defaults,noatime 0 1
    tmpfs /var/log tmpfs size=1M 0 0
    Hmm, nothing at all stands out here, and we we explicitly don't unmount API filesystems or anything else mounted on a RAM based FS. I'd be curious what's running right before the call to umount. Just before line 55 of /etc/rc.shutdown where everything is unmounted, can you stick in a call to ps and lsof?
    /bin/ps aux > /ps.out; /usr/sbin/lsof > /lsof.out
    Unrelated -- you don't need those /dev/{pts,shm} entries anymore. They're mounted by /etc/rc.sysinit. Also, your home should have a passno of 2, not 1, meaning fsck it after root. (reference fstab(5)).

  • Filesystem won't mount in rc.sysinit

    My RAID card won't mount with the other filesystems in rc.sysinit, it displays
    mount: special device /dev/sda1 does not exist.
    However, I took it out of fstab and added the line
    mount -t reiserfs /dev/sda1 /var/lib/mysql
    to rc.multi, so it mounts the filesystem right before it starts the mysql daemon, and it works just fine.
    Any ideas as to what would cause this?

    Hi Olaf,
    No, it hasn't gone away. I only have those two iPod menu items: HDSpecs and HDSMARTData.
    But I don't think there's anything wrong with the iPod; it works on other machines. And no other iOS devices will work on this Mac; I've tried an iPad and an iPhone. I spent 20 minutes on the Apple support chat yesterday. They suggested I zap the NVRAM and the SMC but I've tried both of those. They gave up after that and suggested it was something to do with the Mac's logic board or power management chip. But that doesn't explain why it works perfectly well with my Android phone and my Kindle.
    I don't want to take it in and find out the logic board is failing, so I'm just going to have to carry on listening to old music on my iPod, and never buy an iPad or iPhone!

  • [SOLVED] Root mounted as "Read-only filesystem". mkinitcpio issue?

    I am currently in the middle of setting up system encryption with LUKS. I have been making good progress so far, but I do have one remaining issue.
    After typing my LUKS password, the Linux kernel starts to complain that root is a read-only filesystem. "Starting NetworkManager... cannot touch file XYZ: Read-only filesystem". When it has finally finished booting, I am dropped into a TTY. I can log in and cat my files, but I cannot write to any files our use any programs that do (like pacman).
    I wonder if this is an mkinitcpio issue, but I am not sure. For whatever it's worth, here's my basic setup:
    * /dev/sda1: Boot
    * /dev/sda2: Swap
    * /dev/sda3: Root (LUKS/ext4)
    * menu.lst looks like this
    * /etc/fstab contains this line:
    /dev/mapper/root / ext4 defaults 0 1
    * /etc/mkinitcpio.conf contains these lines:
    MODULES="ext4"
    HOOKS="base udev pata scsi sata encrypt filesystems"
    edit: I should note that I did reinstall the kernel after making those edits to mkinitcpio.conf.
    Any idea what I'm doing wrong? As always, I really do appreciate the help. Thanks in advance!
    Last edited by jalu (2011-04-16 22:14:20)

    So it looks like this major problem was caused by a minor mistake. The file /etc/rc.sysinit was not executable. This made it impossible for the kernel to run the script, which in turn made it impossible for the kernel to mount /dev/sda2 (the swap partition) at /dev/mapper/swap. For some unknown reason, this in turn caused /dev/sda2 to be mounted at /, messing everything up.
    Anyway, a simple sudo chmod +x /etc/rc.sysinit fixed the problem. Thanks for the help, MadTux!

  • [SOLVED] Initramfs fails to properly mount luks partition

    Hello All,
    As I foreshadowed in my intro, I'm having trouble getting encrypted Archlinux to work on my Acer Aspire 5750. I've previously had encrypted Debian Netinst and encrypted Aptosid working on this device. The arch iso I'm using is 2011.08.19-core-i686.
    https://bbs.archlinux.org/viewtopic.php?id=124415 appears similar and Tallahassee offers a workaround, but it doesn't work for me (unless I'm doing something wrong?)
    I suspect there is a bug in the init scripts used by the initramfs. I would like to first of all determine whether I really should file a bug report (and if so where), and secondly whether we can find a workaround to get things up and running in the meantime.
    Now for the meaty bits.
    Old grub doesn't appear to support lvm or luks, so I first of all prepare for grub 2 by installing the gptfdisk package into the iso environment. I use gdisk to set up a 1 or 2 mb bios boot partition at the start of /dev/sda, followed by a 256mb partition (/dev/sda2) for /boot, with the rest of the drive given to the partition intended for the encrypted root partition (/dev/sda3).
    I use cfdisk to toggle the partition type for /dev/sda3 to 8e (Linux LVM).
    Run the following commands, with credits to Aptosid: Installing to a Cryptroot:
    pvcreate /dev/sda3
    vgcreate vg /dev/sda3
    lvcreate -n crypt --extents 100%FREE vg
    cryptsetup --verify-passphrase -c aes-xts-plain:sha512 luksFormat /dev/mapper/vg-crypt
    cryptsetup luksOpen /dev/mapper/vg-crypt cryptroot
    pvcreate /dev/mapper/cryptroot
    vgcreate cryptvg /dev/mapper/cryptroot
    lvcreate -n swap --size 2g cryptvg
    lvcreate -n root --extents 25%FREE cryptvg
    lvcreate -n home --extents 100%FREE cryptvg
    /arch/setup
    Go through the arch setup as normal. At the bit where you configure hard-drives, you'll find all your encrypted partitions ready waiting to be labelled and formatted. Stop after installing packages.
    After installing packages, press CTL-ALT-F2 and log in. Edit /mnt/etc/rc.conf and /mnt/etc/mkinitcpio.conf. CTL-ALT-F1 and reinstall packages. Proceed with the configure step.
    Don't install a boot loader; just quit after configuring everything.
    Follow the steps here: Grub 2 During Archlinux Installation.
    The automatically generated grub.cfg doesn't include things necessary to lvm and luks. Before running grub_bios-install, I edit the grub.cfg to insmod lvm and flag the kernel with cryptdevice=/dev/mapper/vg-crypt:cryptvg-root and rootfstype=ext4 (because that is the encrypted root's filesystem).
    At this point, I would expect the system to be bootable, so reboot.
    Grub2 loads up. I can verify the changes I made to grub.cfg by pressing `e'. So boot and see the messages,
    Loading Linux linux ...
    Loading initial ramdisk ...
    A password is required to access the cryptvg-root volume:
    Enter passphrase for /dev/mapper/vg-crypt:
    So far so good. I enter my passphrase. The following messages ensue:
    vgscan: unrecognized option '--sysinit'
    Error during parsing of command line.
    device-mapper: create ioctl failed: Device or resource busy
    mount: mounting /dev/mapper/cryptvg-root on /new_root failed: Device or resource busy
    ERROR: Failed to mount he real root device.
    Bailing out, you are on your own. Good luck.
    So I get dumped into the ramfs. That ain't much fun.
    Does anyone have some ideas on things to try next? Should I file a bug report?
    Last edited by /dev/zero (2011-10-22 00:28:52)

    Not sure what you mean by difficult and buggy to work with... at this low level, if a VM is having issues replicating this sort if thing, it's not a very useful VM. Find one that doesn't suck. I tend to use KVM because it's terminal friendly via emulation of a serial console.
    Anyways, I can reproduce your issue and fix it. There's 2 things you'll need to change:
    1) You're naming your unlocked cryptdevice the same thing as your root. That's creating a clash with the name you've given your root logical volume. Since the name isn't really important, just change your cryptdevice declare to "cryptdevice=/dev/mapper/vg-crypt:root"
    2) Since you're doing the xzibit thing and nesting lvm inside of the crypt device (i still think its really bizzare to do this, but it looks like mkinitcpio supports it anyways), you'll need to add the lvm2 hook a second time to HOOKS in /etc/mkinitcpio.conf after the encrypt hook.
    Last edited by falconindy (2011-10-22 00:19:10)

  • [solved] crypttab partitions will not mount without "ASK"

    I have three LUKS partitions on a hard drive (root, home, and swap) where the second two are controlled through /etc/crypttab. Boot fails on fsck because the home partition has not been mounted; if I change the crypttab entry from the password to "ASK" I am prompted for the password prior to fsck and the system boots fine. I obviously don't want to have to enter three passwords on boot, so I want the correct entries in crypttab.
    What am I doing incorrectly?
    Last edited by joshdmiller (2011-08-12 20:08:22)

    siriusb wrote:Since LUKS provides the management of multiple password why don't you add one more simple key without any fancy character? Just to be sure that this isn't about your password. And other than that I can't think of anything else
    I do not have any extra hard disks and the partition is in use, so I just reformatted my swap partition as a test with a simple "password", which worked flawlessly. So the problem is obviously the characters in the password. Thanks your help.
    After further manual investigation (running read_crypttab from rc.sysinit) it appears that passwords cannot contain hash marks or the remaining part of the line is considered a comment - I think this is due to the use of eval in read_crypttab - and bash complains about an unexpected EOF due to a missing matching double quote. That is
    swap /dev/sda2 "password#hash"
    is evalled as
    swap /dev/sda2 "password
    which obviously can't work. But the double-quotes should take care of this; the top of the crypttab file says "to use special characters, surround it by quotes, the usual bash quoting rules apply".
    And wouldn't you know it - I found a corresponding bug report. And the patch does fix the issue. Wonder why this hasn't been fixed yet...

  • Initscripts 2011.10.2-1 / rc.sysinit Issues on Bootup

    Since upgrading initscripts from version 2011.07.3-1 to 2011.10.2-1, the following messages appear during the bootup process:
    /etc/rc.sysinit: line 35: minilogd: command not found
    /usr is not mounted. This is not supported.
    Attached is the following screen capture from bootup:

    Raynman wrote:Did you read the messages (especially the second)?
    Of course, did you?
    Raynman wrote: Do you have a concrete question?
    No, this is only an observation which might prove useful for others to see.
    Last edited by ejmarkow (2011-10-23 11:57:34)

  • [SOLVED] Mounting /tmp as a ramdisk with systemd

    Hi, how would one go about setting up /tmp to be a ramdisk when using systemd?  (I'm entirely new to systemd, but since Arch is switching to it I guess I need to learn it.)  With rc.sysinit it was simple; I just added a call to "mount" early on in the script.
    Last edited by jlindgren (2012-08-28 00:16:56)

    jlindgren wrote:There was some reason I was mounting it earlier on than it would have been from /etc/fstab with initscripts -- but I can't remember what that reason was.   Possibly it would not even matter for systemd; anyway, I'll try it.  Thanks.
    If you really need it early you should add a hook for the initrd and rebuild it. (similar to the usr-hook I think)
    Last edited by progandy (2012-08-27 23:16:31)

  • Bootup: long delay before sysinit.target.

    My system seems to have a strange delay during boot that I don't know how to account for. In the SVG plot, there is a long delay before `sysinit.target` comes on, but it doesn't seem that anything is blocking it.
    Also, systemd-blame shows everything starting prety quickly.
    1.332s lightdm.service
    1.255s systemd-logind.service
    1.254s avahi-daemon.service
    1.150s systemd-update-utmp.service
    539ms NetworkManager.service
    437ms [email protected]
    393ms accounts-daemon.service
    360ms systemd-udev-trigger.service
    323ms systemd-tmpfiles-setup.service
    316ms systemd-vconsole-setup.service
    316ms dev-hugepages.mount
    316ms dev-mqueue.mount
    316ms sys-kernel-debug.mount
    295ms kmod-static-nodes.service
    276ms ntpd.service
    231ms systemd-sysctl.service
    224ms [email protected]
    216ms systemd-user-sessions.service
    176ms polkit.service
    170ms systemd-journal-flush.service
    127ms systemd-random-seed.service
    127ms rtkit-daemon.service
    111ms upower.service
    98ms colord.service
    90ms sys-kernel-config.mount
    82ms systemd-backlight@acpi_video0.service
    67ms sys-fs-fuse-connections.mount
    66ms systemd-tmpfiles-setup-dev.service
    55ms wpa_supplicant.service
    53ms dev-sda2.swap
    33ms alsa-restore.service
    30ms udisks2.service
    3ms systemd-remount-fs.service
    2ms tmp.mount
    2ms systemd-udevd.service
    2ms systemd-tmpfiles-clean.service
    And here is what the journal says in that time gap (nothing):
    Dec 26 07:39:51 yvne systemd[1]: Starting Swap.
    Dec 26 07:39:51 yvne systemd[1]: Reached target Swap.
    Dec 26 07:40:26 yvne systemd[1]: Starting System Initialization.
    Dec 26 07:40:26 yvne systemd[1]: Reached target System Initialization.
    Last edited by shawnjgoff (2013-12-26 13:13:19)

    My system seems to have a strange delay during boot that I don't know how to account for. In the SVG plot, there is a long delay before `sysinit.target` comes on, but it doesn't seem that anything is blocking it.
    Also, systemd-blame shows everything starting prety quickly.
    1.332s lightdm.service
    1.255s systemd-logind.service
    1.254s avahi-daemon.service
    1.150s systemd-update-utmp.service
    539ms NetworkManager.service
    437ms [email protected]
    393ms accounts-daemon.service
    360ms systemd-udev-trigger.service
    323ms systemd-tmpfiles-setup.service
    316ms systemd-vconsole-setup.service
    316ms dev-hugepages.mount
    316ms dev-mqueue.mount
    316ms sys-kernel-debug.mount
    295ms kmod-static-nodes.service
    276ms ntpd.service
    231ms systemd-sysctl.service
    224ms [email protected]
    216ms systemd-user-sessions.service
    176ms polkit.service
    170ms systemd-journal-flush.service
    127ms systemd-random-seed.service
    127ms rtkit-daemon.service
    111ms upower.service
    98ms colord.service
    90ms sys-kernel-config.mount
    82ms systemd-backlight@acpi_video0.service
    67ms sys-fs-fuse-connections.mount
    66ms systemd-tmpfiles-setup-dev.service
    55ms wpa_supplicant.service
    53ms dev-sda2.swap
    33ms alsa-restore.service
    30ms udisks2.service
    3ms systemd-remount-fs.service
    2ms tmp.mount
    2ms systemd-udevd.service
    2ms systemd-tmpfiles-clean.service
    And here is what the journal says in that time gap (nothing):
    Dec 26 07:39:51 yvne systemd[1]: Starting Swap.
    Dec 26 07:39:51 yvne systemd[1]: Reached target Swap.
    Dec 26 07:40:26 yvne systemd[1]: Starting System Initialization.
    Dec 26 07:40:26 yvne systemd[1]: Reached target System Initialization.
    Last edited by shawnjgoff (2013-12-26 13:13:19)

  • Hook not being executed before sysinit

    Hi,
    I'm trying a hook before sysinit but it's not working. I created a file called 'custom_hook' in /etc/rc.d/functions.d like this one:
    test_hook() {
        /bin/echo 'it works' > /opt/testing
    add_hook sysinit_start test_hook
    But it does not execute because file 'testing' is not being created.
    Is there anything else to consider?
    Thanks in advance!
    Matt.

    unformatt wrote:@falconindy
    Thanks for your clarifications,
    1) I didn't know that / is mounted as readonly when sysinit_start runs. How can I write a file before starting daemons? Is there a way to accomplish that?
    Look at /etc/rc.sysinit then. root is remounted read only 2-3 lines above where the hook runs. At this point, /run is mounted on tmpfs and writable. This is why it exists.
    unformatt wrote:2) I put the absolute path because I wasn't sure if PATH was loadad in that time.
    Builtin means that it isn't executing a file on disk. It's an intrinsic of the shell (most shells have this, even lightweight POSIX shells like dash).
    # mv /bin/echo{,~}
    $ echo 'your shell knows how to do this'
    your shell knows how to do this

  • Missing loopback interface and modules, and isofs mounting [SOLVED!]

    In my new archlinux istallation, isofs and loopback facilities are not present and when installed by hand do not seem to work. [See FINAL SOLUTION below. Thanks for the suggestions I got].
    Now, I was under the impression that such facilities should be automatically available at the end of a normal installation.
    For instance, in an installation I made last fall, I can mount .iso filesystem through the loopback interface with no problems (and that even without using -t, with just 'mount image.iso /mnt/iso').  In that installation, lsmod shows the modules
      loop                  18526  2
      isofs                  32946  1
    (also, a module isofs is present in /lib/modules, though I cannot find a loop module there)
    and eight loopback devices are available as /dev/loop0 ... /dev/loop7
    On the other hand, in the new installation no /dev/loop devices are present, and no loop and isofs modules show up either
    as installed (as reported by lsmod) or at least in the libraries. Has something changed recently? Do I need to install a package that will set up my installation for loopack mounting and mounting of .iso filesystems?
    INTERIM SOLUTION
    I mentioned above that in my older Linux box, on an Arch Linux installed months ago but not upgraded for many weeks, I had loopback devices running and isofs and loop modules installed, and all working well by itself. Today I did an upgrade, and noticed that it came with a new kernel (3.3?), probably the same I had on the new machine. So I rebooted after that---and found the exact problem as on the new machine: /dev/loop* missing, no modules isofs or loop appearing in lsmod. So I installed by hand a loopback interface, with 'mknod /dev/loop0 b 7 0'. Then I made sure I had the isofs package installed, and installed the isofs module with modprob; this time isofs showed on lsmod, but loop didn't yet. Finally I mounted a data DVD (note that the incantation -t iso9660 is no longer necessary), and as a last thing I mounted an .iso file; both worked. Only after this did a module loop show up in lsmod.
    So probably something subtle changed in the dependencies between installed packages, installed modules, and installed loopback devices, so that something is out of sync and has to be nursed manually. Better experts than I may throw
    some light on this problem and hopefully fix it.
    FINAL AND SATISFACTORY SOLUTION
    Whatever may have happened before, the following works like a charm:
    I upgrade Arch; it installs 3.3.1-1-ARCH as a kernel in /boot.
    I reboot to let the new kernel "take".
    No loop0,...,loop7 devices show up in /dev; no isofs or loop show up with lsmod; isofs (but no loop) present in /lib/modules
    I do 'mount /dev/sr0 /iso' (NOTE: no -t iso9660' option) with a CD in the sr0 drive; the CD filesystem shows up in /iso.
       After this, isofs shows up in 'lsmod|grep isofs', but no loop device yet.
    I unmount /iso and do 'mount ~tt/ markov.iso /iso' (NOTE: no -t iso9660' option); the markov filesystem shows up in /iso.
      After this, loop0,...,loop7 devices show up in /dev, and a loop module (wherever that camefrom) appears in lsmod.
    In other words, everything required for isofs automounts as necessary and remains mounted until new reboot.
    The '-t iso9660' option is not necessary. As noted by an other Arch post, this option may be detrimental and might have been the culprit; this is an issue I will explore on the next reboot.
    Last edited by rugantino (2012-04-11 20:11:55)

    When /etc/rc.sysinit is invoked during the bootprocess; it should automatically start a loopback interface (unless you've specifically disabled it in /etc/rc.d/network or so).
    Check your logs to see if your find any related errors.

  • Filesystem Check Failed - Mounted

    After having a little trouble getting XFCE to start automatically like KDE did, I played around with some settings using a SLAX LiveCD.  Since then, I'm unable to boot for a different reason: Filesystem Check Failed.
    The only thing that seems to be the problem is that /dev/sdb1 is, as it says, "mounted".  When I am prompted to fix it myself, I find that the system is confused as to whether it is mounted.
    Typing "mount" produces
    /dev/sdb1 on /mnt/sto type ext3 (rw,noexec,nosuid,nodev)
    Yet typing "umount /dev/sdb1" produces
    umount: dev/sdb1: not found
    umount /mnt/sto: not found
    umount: dev/sdb1: not found
    umount /mnt/sto: not found
    cd to /mnt/sto and using dir or ls -a also shows me nothing.
    The following is displayed upon "reboot"
    shutdown: /dev/initctl: No such file or directory
    init: /dev/initctl: No such file or directory
    Finally, the files I remember having edited in SLAX and partially ARCH.  I'm not sure how correct these are, but I didn't think trying to fix up XFCE was going to create such a problem:
    /etc/X11/xinit/xinit.rc
    #!/bin/sh
    # $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $
    userresources=$HOME/.Xresources
    usermodmap=$HOME/.Xmodmap
    sysresources=/etc/X11/xinit/.Xresources
    sysmodmap=/etc/X11/xinit/.Xmodmap
    # merge in defaults and keymaps
    if [ -f $sysresources ]; then
    xrdb -merge $sysresources
    fi
    if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
    fi
    if [ -f $userresources ]; then
    xrdb -merge $userresources
    fi
    if [ -f $usermodmap ]; then
    xmodmap $usermodmap
    fi
    # start some nice programs
    #twm &
    #xclock -geometry 50x50-1+1 &
    #xterm -geometry 80x50+494+51 &
    #xterm -geometry 80x20+494-0 &
    #exec xterm -geometry 80x66+0+0 -name login
    exec startxfce4
    /etc/inittab
    # /etc/inittab
    # Runlevels:
    # 0 Halt
    # 1(S) Single-user
    # 2 Not used
    # 3 Multi-user
    # 4 Not used
    # 5 X11
    # 6 Reboot
    id:5:initdefault:xdm
    rc::sysinit:/etc/rc.sysinit
    rs:S1:wait:/etc/rc.single
    rm:2345:wait:/etc/rc.multi
    rh:06:wait:/etc/rc.shutdown
    su:S:wait:/sbin/sulogin -p
    c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
    c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
    c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
    c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
    c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
    c6:2345:respawn:/sbin/agetty 38400 vc/6 linux
    ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    x:5:respawn:/opt/xfce4/bin/startxfce4
    # End of file
    Please let me know if I'm missing any information.  I'm currently running Windows, but luckily have full access to my root partition.
    Thanks in advance.
    P.S. /dev/sdb1 is no longer being shown in Windows OR SLAX.  I predicted Windows, but can't think why it won't show up in SLAX.
    Last edited by Newnux (2007-06-30 20:54:08)

    Never mind, the fsck seemed to complete just fine .
    fsck 1.39 (29-May-2006)
    e2fsck 1.39 (29-May-2006)
    Storage has been mounted 29 times without being checked, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    Storage: 23560/24903680 files (22.3% non-contiguous), 41462978/49785427 blocks
    It didn't take that long, I just expected a progress bar, like with other drives.
    Thanks anyway!  Time to see if Arch boots without problems.

  • Arch64 auto reboot on rc.sysinit

    I use multi-boot system, both ArchLinux and Windows 2003 server were installed.
    Whenever my windows partition is dirty ( required to do chkdsk ),   my archlinux can NOT successful boot.
    It is always automatic-reboot during the boot  on the rc.sysinit, i insert some check point, it hangs between 'L4' and 'L5'.
    ---- some lines in /etc/rc.sysinit
    stat_busy "Mounting Local Filesystems"
    read -t 2 -p "L1:" x
    /bin/mount -n -o remount,rw /
    read -t 2 -p "L2:" x
    /bin/rm -f /etc/mtab*
    read -t 2 -p "L3:" x
    # make sure / gets written to /etc/mtab
    read -t 2 -p "L4:" x
    /bin/mount -o remount,rw /
    # re-mount /proc , /sys  and usbfs so they can be written to /etc/mtab
    read -t 2 -p "L5:" x
    umount /proc/bus/usb
    read -t 2 -p "L6:" x
    if [ -e /proc/mounts ]; then
            grep -e "/proc " -e "/sys " -e "/dev " /proc/mounts >> /etc/mtab
    fi
    I'm wonder why the mount -o remount will to checking my ntfs and caused my system hang.
    (I have already set ntf's partions as noauto in /etc/fstab).

    I forgot to said. Even on arch64's boot cdrom, it also have such problem.
    That forced me must recover my windows partition at first.

Maybe you are looking for

  • Question bout the new Fios speed that might come.

    So I have the 25/25 connection will I get upgraded to 50/25 for free or will there be a increase in monthly fee if you choose to?

  • Mobile Printer ( Zebra RW420 ) Not Working with Cisco AP

    Good Morning everyone,   In cold area -3 inside a warehouse I am trying to connect  a mobile printer ( Zebra RW420 ) to cisco access points of model AIR-LAP1242AG-A-K9  and AIR-LAP1252AG-E-K9  which are woking through WLAN controlar version  6.0.202.

  • Calling setLocation(-2000,-2000) on JFrame kills the app without exception

    Hi All, I am working on a Java appliction which is supposed to run a specialized hardware. JDK Version 1.5 Windows version Win 2000 The environment in which this app is supposed to run is strictly controlled by another application (for e.g. user shou

  • Oracle Error Code -3113

    Hi All I am working on an application which needs to handle the sql error code -3113 ("end-of-file on communication channel"). When the application (PRO C) gets a -3113 error from the database it should run a series of steps. To simulate this feature

  • Same Link on Multiple Pages

    I have a link to an excel spreadsheet that needs weekly updating. The same link is throughout my site... what is the best way to make this update once and have it effect all my pages that have the same link? After I made my changes outside of Contrib