Page 3 of 3 FirstFirst 123
Results 21 to 24 of 24

Thread: How to resolve "A start job is running for dev-disk-by\..." problems? Raspberry Pi / openSUSE

  1. #21
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    25,763
    Blog Entries
    15

    Default Re: How to resolve "A start job is running for dev-disk-by\..."problems? Raspberry Pi / openSUSE

    On Wed 15 Feb 2017 08:36:01 PM CST, hdtodd wrote:

    arvidjaar;2812548 Wrote:
    > So your statement about "no impact" is wrong - change to kernel
    > command line did have very visible impact.

    Yep, you're right. Didn't get rid of the "dev-" part, but did change
    the device name.

    > Now, if your system waits for something as simple as /dev/mmcblk0, I
    > suspect that your initrd does not include necessary drivers. Which
    > also may explain your previous problems because initrd also includes
    > "stored command line" which it may attempt to use when you do not
    > supply kernel parameters. So try to chroot and run mkinitrd to
    > recreate it for current root device. It would be helpful if you could
    > capture output (e.g. by running it under "script" command) and show
    > here. Try to reboot without any extra kernel parameters. What
    > happens?


    It hangs with the same "A start job ... dev-mmcblk0p2.device" wait loop.

    Here's the dracut modules file, modified per the instructions on getting
    the WAN service working:

    Code:
    --------------------
    Pi-6w:/mnt # cat tgt/etc/dracut.conf.d/raspberrypi_modules.conf
    add_drivers+=" bcm2835-sdhost bcm2835_dma mmc_block dwc2 "
    # Workaround for Wifi
    omit_drivers+=" sdhci-iproc"
    --------------------



    Here's the log of mounting the sda partitions and doing the mkinitrd.
    More interesting info after this rather lengthy log. I think you've
    found the problem, but I don't know how to fix it.


    Code:
    --------------------
    Pi-6w:~ # lsblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    sda 8:0 1 29.7G 0 disk
    ├─sda1 8:1 1 200M 0 part
    ├─sda2 8:2 1 29G 0 part
    └─sda3 8:3 1 493.7M 0 part
    mmcblk0 179:0 0 30.2G 0 disk
    ├─mmcblk0p1 179:1 0 200M 0 part /boot/efi
    ├─mmcblk0p2 179:2 0 266M 0 part /boot
    ├─mmcblk0p3 179:3 0 29.2G 0 part /
    └─mmcblk0p4 179:4 0 493.6M 0 part [SWAP]
    Pi-6w:~ # mount /dev/sda2 /mnt/tgt
    Pi-6w:~ # mount /dev/sda1 /mnt/tgt/boot/efi
    Pi-6w:~ # cd /mnt/tgt
    Pi-6w:/mnt/tgt # mount --bind /dev dev
    Pi-6w:/mnt/tgt # mount --bind /sys sys
    Pi-6w:/mnt/tgt # mount --bind /proc proc
    Pi-6w:/mnt/tgt # chroot /mnt/tgt
    Pi-6w:/ # mkinitrd --verbose
    Creating initrd: /boot/initrd-4.9.6-1-default
    dracut: Executing: /usr/bin/dracut -v
    --logfile /var/log/YaST2/mkinitrd.log
    --force /boot/initrd-4.9.6-1-default 4.9.6-1-default modinfo: ERROR:
    Module usb_common not found. modinfo: ERROR: Module virt_dma not found.
    modinfo: ERROR: Module bcm2835_sdhost not found. modinfo: ERROR: Module
    bcm2835_thermal not found. modinfo: ERROR: Module bcm2835_cpufreq not
    found. dracut: dracut module 'systemd-bootchart' will not be installed,
    because command '/usr/lib/systemd/systemd-bootchart' could not be
    found! dracut: *** Including module: bash *** dracut: *** Including
    module: systemd *** dracut: *** Including module: warpclock ***
    dracut: *** Including module: systemd-initrd ***
    dracut: *** Including module: i18n ***
    dracut: *** Including module: drm ***
    dracut: Possible missing firmware "a420_pfp.fw" for kernel module
    "msm.ko" dracut: Possible missing firmware "a420_pm4.fw" for kernel
    module "msm.ko" dracut: Possible missing firmware "a330_pfp.fw" for
    kernel module "msm.ko" dracut: Possible missing firmware "a330_pm4.fw"
    for kernel module "msm.ko" dracut: Possible missing firmware
    "a300_pfp.fw" for kernel module "msm.ko" dracut: Possible missing
    firmware "a300_pm4.fw" for kernel module "msm.ko" dracut: *** Including
    module: plymouth *** dracut: *** Including module: kernel-modules ***
    dracut: Possible missing firmware "aic94xx-seq.fw" for kernel module
    "aic94xx.ko" dracut: Possible missing firmware "wd719x-risc.bin" for
    kernel module "wd719x.ko" dracut: Possible missing firmware
    "wd719x-wcs.bin" for kernel module "wd719x.ko" dracut: Possible missing
    firmware "sd8688.bin" for kernel module "libertas_sdio.ko" dracut:
    Possible missing firmware "sd8688_helper.bin" for kernel module
    "libertas_sdio.ko" dracut: Possible missing firmware "sd8686.bin" for
    kernel module "libertas_sdio.ko" dracut: Possible missing firmware
    "sd8686_helper.bin" for kernel module "libertas_sdio.ko" dracut:
    Possible missing firmware "sd8385.bin" for kernel module
    "libertas_sdio.ko" dracut: Possible missing firmware
    "sd8385_helper.bin" for kernel module "libertas_sdio.ko" dracut:
    Omitting driver sdhci_iproc dracut: *** Including module: rootfs-block
    *** dracut: *** Including module: terminfo *** dracut: *** Including
    module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules
    dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev
    rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules
    dracut: Skipping udev rule: 80-drivers-modprobe.rules
    dracut: *** Including module: dracut-systemd ***
    dracut: *** Including module: haveged ***
    dracut: *** Including module: usrmount ***
    dracut: *** Including module: base ***
    dracut: *** Including module: fs-lib ***
    dracut: *** Including module: shutdown ***
    dracut: *** Including module: suse ***
    dracut: *** Including modules done ***
    dracut: *** Installing kernel module dependencies and firmware ***
    dracut: *** Installing kernel module dependencies and firmware done
    *** dracut: *** Resolving executable dependencies ***
    dracut: *** Resolving executable dependencies done***
    dracut: *** Hardlinking files ***
    dracut: *** Hardlinking files done ***
    dracut: *** Stripping files ***
    dracut: *** Stripping files done ***
    dracut: *** Store current command line parameters ***
    dracut: Stored kernel commandline:
    dracut: root=UUID=795b86ba-b1c5-455b-8233-6fe18ba25aa4
    rootfstype=ext4 rootflags=rw,relatime,data=ordered dracut: *** Creating
    image file '/boot/initrd-4.9.6-1-default' *** dracut:
    Image: /var/tmp/dracut.ISSKT3/initramfs.img: 20M dracut:
    ========================================================================
    dracut: Version: dracut-044-20.1 dracut:
    dracut: Arguments: -v --logfile --force
    dracut:
    dracut: dracut modules:
    dracut: bash
    dracut: systemd
    dracut: warpclock
    dracut: systemd-initrd
    dracut: i18n
    dracut: drm
    dracut: plymouth
    dracut: kernel-modules
    dracut: rootfs-block
    dracut: terminfo
    dracut: udev-rules
    dracut: dracut-systemd
    dracut: haveged
    dracut: usrmount
    dracut: base
    dracut: fs-lib
    dracut: shutdown
    dracut: suse
    dracut:
    ========================================================================
    dracut: drwxr-xr-x 16 root root 0 Feb 15 14:33 .
    dracut: crw-r--r-- 1 root root 5, 1 Feb 15 14:32
    dev/console <deleted to reduce posting size> dracut: drwxr-xr-x 5
    root root 0 Feb 15 14:33
    lib/modules/4.9.6-1-default/kernel/drivers/mmc dracut: drwxr-xr-x 2
    root root 0 Feb 15 14:33
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/card dracut:
    -rw-r--r-- 1 root root 68994 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/card/mmc_block.ko
    dracut: drwxr-xr-x 2 root root 0 Feb 15 14:33
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/core dracut:
    -rw-r--r-- 1 root root 311074 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/core/mmc_core.ko dracut:
    drwxr-xr-x 2 root root 0 Feb 15 14:33
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host dracut:
    -rw-r--r-- 1 root root 30450 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/cb710-mmc.ko
    dracut: -rw-r--r-- 1 root root 69626 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/dw_mmc.ko dracut:
    -rw-r--r-- 1 root root 42674 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/mmci.ko dracut:
    -rw-r--r-- 1 root root 47898 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/mtk-sd.ko dracut:
    -rw-r--r-- 1 root root 44266 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/rtsx_pci_sdmmc.ko
    dracut: -rw-r--r-- 1 root root 49954 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/rtsx_usb_sdmmc.ko
    dracut: -rw-r--r-- 1 root root 12426 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci-brcmstb.ko
    dracut: -rw-r--r-- 1 root root 14578 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci_f_sdh30.ko
    dracut: -rw-r--r-- 1 root root 89034 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci.ko dracut:
    -rw-r--r-- 1 root root 24210 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci-msm.ko
    dracut: -rw-r--r-- 1 root root 23386 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci-of-arasan.ko
    dracut: -rw-r--r-- 1 root root 22962 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci-of-esdhc.ko
    dracut: -rw-r--r-- 1 root root 53346 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci-pci.ko
    dracut: -rw-r--r-- 1 root root 16698 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci-pltfm.ko
    dracut: -rw-r--r-- 1 root root 18930 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sdhci-tegra.ko
    dracut: -rw-r--r-- 1 root root 36202 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/sunxi-mmc.ko
    dracut: -rw-r--r-- 1 root root 31346 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/tifm_sd.ko dracut:
    -rw-r--r-- 1 root root 26946 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/toshsd.ko dracut:
    -rw-r--r-- 1 root root 52666 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/usdhi6rol0.ko
    dracut: -rw-r--r-- 1 root root 15618 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/ushc.ko dracut:
    -rw-r--r-- 1 root root 33754 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/via-sdmmc.ko
    dracut: -rw-r--r-- 1 root root 54162 Jan 29 07:57
    lib/modules/4.9.6-1-default/kernel/drivers/mmc/host/vub300.ko ...
    dracut: drwxr-xr-x 2 root root 0 Feb 15 14:32 var/tmp
    dracut:
    ========================================================================
    dracut: *** Creating initramfs image file
    '/boot/initrd-4.9.6-1-default' done *** Pi-6w:/ # lsblk -o name,uuid
    NAME UUID sda ├─sda1 5F76-974D ├─sda2
    795b86ba-b1c5-455b-8233-6fe18ba25aa4 └─sda3
    fa126ee2-3aa3-464b-8bec-56e2dc077ba2 mmcblk0 ├─mmcblk0p1 4479-5615
    ├─mmcblk0p2 c6c03b10-12d7-43cf-9f66-d04fa8e179c1 ├─mmcblk0p3
    0b2c007e-1581-42e2-a05c-4a66eb4c115d └─mmcblk0p4
    59ad7379-fc8b-4e66-a451-9f43bf7ebd5b Pi-6w:/ # --------------------


    So after checking the missing modules logged above, I did this on the
    openSUSE install:

    Code:
    --------------------
    Pi-6w:/mnt # find . -name bcm2835* -print
    ./tgt/lib/modules/4.9.6-1-default/kernel/drivers/dma/bcm2835-dma.ko
    ./tgt/lib/modules/4.9.6-1-default/kernel/drivers/watchdog/bcm2835_wdt.ko
    ./tgt/lib/modules/4.9.6-1-default/kernel/drivers/char/hw_random/bcm2835-rng.ko
    --------------------


    .... and this on the SLES install that was running (and on which the
    openSUSE microSD was mounted as sda2):

    Code:
    --------------------
    Pi-6w:/mnt # find /lib/modules -name bcm2835* -print
    /lib/modules/4.4.21-69-default/kernel/drivers/char/hw_random/bcm2835-rng.ko
    /lib/modules/4.4.21-69-default/kernel/drivers/cpufreq/bcm2835-cpufreq.ko
    /lib/modules/4.4.21-69-default/kernel/drivers/dma/bcm2835-dma.ko
    /lib/modules/4.4.21-69-default/kernel/drivers/mmc/host/bcm2835-sdhost.ko
    /lib/modules/4.4.21-69-default/kernel/drivers/thermal/bcm2835-thermal.ko
    /lib/modules/4.4.21-69-default/kernel/drivers/watchdog/bcm2835_wdt.ko
    /lib/modules/4.4.38-93-default/kernel/drivers/char/hw_random/bcm2835-rng.ko
    /lib/modules/4.4.38-93-default/kernel/drivers/cpufreq/bcm2835-cpufreq.ko
    /lib/modules/4.4.38-93-default/kernel/drivers/dma/bcm2835-dma.ko
    /lib/modules/4.4.38-93-default/kernel/drivers/mmc/host/bcm2835-sdhost.ko
    /lib/modules/4.4.38-93-default/kernel/drivers/thermal/bcm2835-thermal.ko
    /lib/modules/4.4.38-93-default/kernel/drivers/watchdog/bcm2835_wdt.ko

    --------------------


    So if I'm reading this right, there are some critical modules missing
    when I go to do the mkinitrd on openSUSE .

    BUT ... that *was* a running openSUSE before I followed the procedure to
    get the WAN running,
    https://lists.opensuse.org/opensuse-.../msg00018.html, which I
    had followed before, successfully, with an earlier distribution of
    openSUSE (2017.01.03, I think it was).

    I can't imagine that running mkinitrd would have deleted just those
    modules from /lib/modules/..., and they must have been there if they're
    needed, because it booted successfully.

    So ... am I misinterpreting? I'm inclined to wipe this SD with a fresh
    install of openSUSE, verify that it boots successfully, run through the
    WAN install process (link above), and see if I get the same result.

    But before I blow away this install: am I interpreting this correctly,
    and is there another way to fix this install? (I don't have anything on
    this that I need to preserve.)


    Hi
    I just got it working on 42.2, my initial trial failed, I only used
    mkinitrd (no -f) and also checked the date was set (not sure if that
    affects things), but after the date was set wlan0 came up on reboot...

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.1|GNOME 3.16.2|4.1.36-44-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!


  2. #22
    Join Date
    Feb 2017
    Location
    Montana, USA & Vermont, USA
    Posts
    114

    Default Re: How to resolve "A start job is running for dev-disk-by\..."problems? Raspberry Pi / openSUSE

    Quote Originally Posted by malcolmlewis View Post
    Hi
    I just got it working on 42.2, my initial trial failed, I only used
    mkinitrd (no -f) and also checked the date was set (not sure if that
    affects things), but after the date was set wlan0 came up on reboot...
    GM, Malcolm,

    Thanks for the pointer!

    I've downloaded openSUSE-Leap42.2-ARM-XFCE-raspberrypi3.aarch64-2017.02.02-Build1.10.raw.xz, but the date on the file was 15 Feb. If you just downloaded it yesterday, that's probably the one you're using. Do you know the creation date of the one you're using?

  3. #23
    Join Date
    Feb 2017
    Location
    Montana, USA & Vermont, USA
    Posts
    114

    Default Re: How to resolve "A start job is running for dev-disk-by\..."problems? Raspberry Pi / openSUSE

    Quote Originally Posted by malcolmlewis View Post
    Hi
    I just got it working on 42.2, my initial trial failed, I only used
    mkinitrd (no -f) and also checked the date was set (not sure if that
    affects things), but after the date was set wlan0 came up on reboot...
    Ah, and were you using JeOS rather than XFCE? The creation dates for those are different on the repository (or were last night, at least). But I'll try XFCE and if it doesn't work I'll try JeOS.

    Interesting that your initial trial failed. But I'll drop the "-f" on mine, and make sure the time is set, before I start working.

  4. #24
    Join Date
    Feb 2017
    Location
    Montana, USA & Vermont, USA
    Posts
    114

    Default SUCCESS Re: How to resolve "A start job is running for dev-disk-by\..." ? Raspberry Pi / openSUSE

    Quote Originally Posted by arvidjaar View Post
    I'm not really familiar with this hardware, but quick look suggests that BCM2835 is supported by upstream kernel module sdhci-iproc (which you explicitly blacklist) since 4.6. I do not see any bcm2835-sdhost in current upstream Linux sources (of course it may be added as out of tree module by SUSE).
    Code:
    config MMC_SDHCI_IPROC
            tristate "SDHCI support for the BCM2835 & iProc SD/MMC Controller"
    Good Morning, arvidjaar,
    That was a very helpful observation! I don't know which modules do what yet, so if something is "missing" I don't know if it's critical or not. This one was! But the odd thing is: I was just following directions to get WLAN working and instead I got into a boot-loop -- and a two-week sidetrack. :-)

    To correct the boot-loop problem, I booted into SLES, inserted the openSUSE microSD/USB into the USB slot to connect it into /dev/sda, did the usual setup to chroot to /mnt/tgt (the /dev/sda2 partition that is root for this install). I commented out the "omit_drivers+=" sdhci-iproc" " line in the dracut.conf.d/raspberry module and did a "mkinitrd", leaving off the "-f" part. Got a couple of "missing" messages but got rid of most of those I'd seen in the past. exited, powered off, moved the openSUSE microSD to the mmcblk0 slot, and rebooted.

    SUCCESS! No "A start job is ..." wait loop! System came up (4.9.6-1) normally with the XFCE login screen.

    The time was off, so I adjusted network settings, edited ntp settings to make sure I could sync with nist.time.gov, did the mkinitrd again, but this time running under the native OS. Nice, clean log. Rebooted and it again worked just fine.

    That was the good news.

    The bad news is that the reason I got into this, two weeks ago or so, was to get WLAN to work. Well, it doesn't. It looks like the modules are loaded, and the YaST network setup "sees" wlan0 when I go to set up a wireless device, but a scan of the network to connect to an SSID fails to find anything.

    So for those trying this approach: it may not work for you. But if you get hung with the "A start job ..." loop at boot time, arvidjaar's comments (comment out that "omit_drivers" line in the dracut.conf.d/raspberry module) followed by a mkinitrd will get you back to a bootable system.

    I've been working with the Raspberry Pi XFCE distributions. Now, in a forum exchange last night, a comment by Malcolm Lewis reminded me that my one success in getting the WLAN procedure to work *may* have been with the JeOS distribution rather than XFCE. I started this several weeks ago, and I wasn't aware of the alternatives so just picked one, and I'm pretty sure the first distribution I tried was JeOS. So it's quite possible that the procedure would work with different distributions, or with later distributions of openSUSE Raspberry XFCE.

    With all this vast experience under my belt now [ ;-) ], I'll start from scratch with a couple of Raspberry Pi distributions (LEAP 42.2, Tumbleweed upstream current stable) to see if I can 1) get WLAN working and 2) create a USB-bootable drive. If I have any success, I'll document what I learn, but probably start a new thread to do so.

    Thanks for all your help!

    David

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •