Extremely slow boot of Leap 42.1 from SSD over USB 3.0

English Install/Boot/Login
#1

Hi Suse folks,

I have installed Leap 42.1 on an SSD which sits external to my Lenovo T530 laptop in a SATA to USB 3.0 adapter.

If I connect this drive to a USB 2.0 port all is good. I can boot from the drive and I am in Leap 42.1.

If I connect this drive to a USB 3.0 port, I see these messages at boot:

[OK] Started Show Plymouth Boot Screen.
[OK] Reached target Paths.
[OK] Reached target Basic System.

… and then nothing happens … for a very long time. More than ten minutes. Maybe twenty minutes?

But after this very long time, I do finally see my beautiful bright shiny log-in screen for Leap 42.1 And everything works great.

So I am quite encouraged. I just need to know what is interfering with booting and get this installation to boot properly in good time.

Why would this happen in a USB 3.0 port, and not in a USB 2.0 port?

Thank you very much for any advice!

Laurel Sinclair

#2

Try suystemctl-blme it may show what is holding things up

#3

Hi gogalthorp,

Thanks for responding. I can’t figure out what you mean.
I am trying

> sudo systemctl -blme

but “b” is not a valid option …

Regards,

laurelsinclair

#4

oops it is systemd-analyze blame

#5

Hmm. I don’t have that. cnf doesn’t find it. YAST Software Management doesn’t find it. Google searching doesn’t find it.

Is it possibly an alias or a script that you have?

#6

Oh sorry - messages crossed - yes I do have systemd-analyze blame.

here is what I get (and I am looking at it too but if you see something it would be great to know )

> sudo systemd-analyze blame

      1.981s display-manager.service
      1.581s systemd-tmpfiles-clean.service
      1.432s ModemManager.service
      1.375s postfix.service
      1.069s SuSEfirewall2.service
       858ms dev-mqueue.mount
       856ms sys-kernel-debug.mount
       855ms dev-hugepages.mount
       804ms systemd-remount-fs.service
       804ms dev-sdb2.device
       711ms polkit.service
       708ms avahi-daemon.service
       699ms systemd-logind.service
       698ms SuSEfirewall2_init.service
       379ms apparmor.service
       258ms systemd-tmpfiles-setup.service
       229ms var-lib-libvirt-images.mount
       226ms boot-grub2-i386\x2dpc.mount
       222ms var-lib-mysql.mount
       221ms var-crash.mount
       219ms opt.mount
       215ms var-lib-pgsql.mount
       214ms var-lib-named.mount
#7

I don’t think there’s anything helpful in there. That all looks really fast. The delay I am experiencing in booting my SSD over USB 3.0 is about 25 minutes. It just sits and does nothing for that long. The light on the USB 3.0 adapter is solid on. Over USB 2.0 it is fast and the light blinks.

Thanks if you can think of anything else …

#8

Ah - look - it is initrd :

> sudo systemd-analyze time

Startup finished in 2.323s (kernel) + 18min 36.490s (initrd) + 4.002s (userspace) = 18min 42.816s

Still don’t know how to find out what is causing initrd to sit for 18 minutes though …

#9

Try

journalctl -p err -b

journalctl -p warning -b

Maybe give a clue

#10

Ok, maybe there are some clues:

> sudo journalctl -p err -b
– Logs begin at Sun 2016-11-13 22:33:53 EST, end at Mon 2016-11-14 17:25:26 EST. –
Nov 14 14:17:03 linux-k8di kernel: INFO: task systemd-udevd:255 blocked for more than 480 seconds.
Nov 14 14:17:03 linux-k8di kernel: Not tainted 4.1.12-1-default #1
Nov 14 14:17:03 linux-k8di kernel: “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
Nov 14 14:19:42 linux-k8di systemd-udevd[549]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 (’’)
Nov 14 14:19:42 linux-k8di kernel: kvm: disabled by bios
Nov 14 14:19:42 linux-k8di kernel: thinkpad_acpi: Unsupported brightness interface, please contact ibm-acpi-devel@lists.sourceforge.net
Nov 14 14:19:43 linux-k8di audispd[876]: No plugins found, exiting
Nov 14 14:19:43 linux-k8di bluetoothd[1061]: Failed to obtain handles for “Service Changed” characteristic

> sudo journalctl -p warning -b
– Logs begin at Sun 2016-11-13 22:33:53 EST, end at Mon 2016-11-14 17:26:07 EST. –
Nov 14 14:01:05 linux-k8di kernel: ACPI: RSDP 0x00000000000F0120 000024 (v02 LENOVO)
Nov 14 14:01:05 linux-k8di kernel: ACPI: XSDT 0x00000000DF7FE170 0000BC (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: FACP 0x00000000DF7E6000 00010C (v05 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: DSDT 0x00000000DF7E8000 0104B1 (v01 LENOVO TP-G4 00002670 INTL 20061109)
Nov 14 14:01:05 linux-k8di kernel: ACPI: FACS 0x00000000DF75A000 000040
Nov 14 14:01:05 linux-k8di kernel: ACPI: SLIC 0x00000000DF7FD000 000176 (v01 LENOVO TP-G4 00002670 PTL 00000001)
Nov 14 14:01:05 linux-k8di kernel: ACPI: TCPA 0x00000000DF7FC000 000032 (v02 PTL LENOVO 06040000 LNVO 00000001)
Nov 14 14:01:05 linux-k8di kernel: ACPI: SSDT 0x00000000DF7FB000 000408 (v01 LENOVO TP-SSDT2 00000200 INTL 20061109)
Nov 14 14:01:05 linux-k8di kernel: ACPI: SSDT 0x00000000DF7FA000 000033 (v01 LENOVO TP-SSDT1 00000100 INTL 20061109)
Nov 14 14:01:05 linux-k8di kernel: ACPI: SSDT 0x00000000DF7F9000 000797 (v01 LENOVO SataAhci 00001000 INTL 20061109)
Nov 14 14:01:05 linux-k8di kernel: ACPI: HPET 0x00000000DF7E4000 000038 (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: APIC 0x00000000DF7E3000 000098 (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: MCFG 0x00000000DF7E2000 00003C (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: ECDT 0x00000000DF7E1000 000052 (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: FPDT 0x00000000DF7E0000 000064 (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: ASF! 0x00000000DF7E7000 0000A5 (v32 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: UEFI 0x00000000DF7DF000 00003E (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: UEFI 0x00000000DF7DE000 000042 (v01 PTL COMBUF 00000001 PTL 00000001)
Nov 14 14:01:05 linux-k8di kernel: ACPI: POAT 0x00000000DF7DD000 000055 (v03 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: SSDT 0x00000000DF7DC000 000C31 (v01 PmRef Cpu0Ist 00003000 INTL 20061109)
Nov 14 14:01:05 linux-k8di kernel: ACPI: SSDT 0x00000000DF7DB000 000A83 (v01 PmRef CpuPm 00003000 INTL 20061109)
Nov 14 14:01:05 linux-k8di kernel: ACPI: UEFI 0x00000000DF7DA000 0002A6 (v01 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: DBG2 0x00000000DF7D9000 0000E9 (v00 LENOVO TP-G4 00002670 PTL 00000002)
Nov 14 14:01:05 linux-k8di kernel: ACPI: All ACPI Tables successfully acquired
Nov 14 14:01:05 linux-k8di kernel: ENERGY_PERF_BIAS: Set to ‘normal’, was ‘performance’
Nov 14 14:01:05 linux-k8di kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov 14 14:01:05 linux-k8di kernel: #2 #3 #4 #5 #6 #7
Nov 14 14:01:05 linux-k8di kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Nov 14 14:01:05 linux-k8di kernel: ACPI: Dynamic OEM Table Load:
Nov 14 14:01:05 linux-k8di kernel: ACPI: SSDT 0xFFFF88011855F800 000303 (v01 PmRef ApIst 00003000 INTL 20061109)
Nov 14 14:01:05 linux-k8di kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State _S1_] (20150410/hwxface-580)
Nov 14 14:01:05 linux-k8di kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State _S2_] (20150410/hwxface-580)
Nov 14 14:01:05 linux-k8di kernel: ACPI: Enabled 4 GPEs in block 00 to 3F
Nov 14 14:01:05 linux-k8di kernel: pnp 00:01: disabling [mem 0xfffff000-0xffffffff] because it overlaps 0000:01:00.0 BAR 6 [mem 0xfff80000-0xffffffff pref]
Nov 14 14:01:05 linux-k8di kernel: ACPI Warning: _SB_.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
Nov 14 14:01:05 linux-k8di kernel: ACPI Warning: _SB.PCI0.PEG_.VID_.DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
Nov 14 14:01:05 linux-k8di kernel: nouveau W PFB][0000:01:00.0][0x00000000] reclocking of this ram type unsupported
Nov 14 14:17:03 linux-k8di kernel: INFO: task systemd-udevd:255 blocked for more than 480 seconds.
Nov 14 14:17:03 linux-k8di kernel: Not tainted 4.1.12-1-default #1
Nov 14 14:17:03 linux-k8di kernel: “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
Nov 14 14:17:03 linux-k8di kernel: ffff88003733fcd8 ffff880118852390 ffff8800372ce390 0000000000000000
Nov 14 14:17:03 linux-k8di kernel: ffff880037340000 0000000000000000 ffffffffa0026530 ffff8800cd2cf7c0
Nov 14 14:17:03 linux-k8di kernel: 0000000000000001 ffff88003733fcf8 ffffffff8165b177 0000000000000286
Nov 14 14:17:03 linux-k8di kernel: Call Trace:
Nov 14 14:17:03 linux-k8di kernel: <ffffffff8165b177>] schedule+0x37/0x90
Nov 14 14:17:03 linux-k8di kernel: <ffffffff810892b5>] async_synchronize_cookie_domain+0x55/0x130
Nov 14 14:17:03 linux-k8di kernel: <ffffffff816545f3>] do_init_module+0xb5/0x1d3
Nov 14 14:17:03 linux-k8di kernel: <ffffffff810ed9a8>] load_module+0x1cd8/0x2530
Nov 14 14:17:03 linux-k8di kernel: <ffffffff810ee3c5>] SYSC_finit_module+0x75/0xa0
Nov 14 14:17:03 linux-k8di kernel: <ffffffff8165f032>] system_call_fastpath+0x16/0x75
Nov 14 14:17:03 linux-k8di kernel: <00007f46ef2fbfd9>] 0x7f46ef2fbfd9
Nov 14 14:19:42 linux-k8di systemd-udevd[549]: invalid key/value pair in file /usr/lib/udev/rules.d/51-android.rules on line 115,starting at character 57 (’’)
Nov 14 14:19:42 linux-k8di kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (_SB.
Nov 14 14:19:42 linux-k8di kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (_SB_.
Nov 14 14:19:42 linux-k8di kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (_SB_.
Nov 14 14:19:42 linux-k8di kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (_SB_.
Nov 14 14:19:42 linux-k8di kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 14 14:19:42 linux-k8di kernel: kvm: disabled by bios
Nov 14 14:19:42 linux-k8di kernel: iwlwifi 0000:03:00.0: can’t disable ASPM; OS doesn’t have ASPM control
Nov 14 14:19:42 linux-k8di kernel: thinkpad_acpi: Unsupported brightness interface, please contact ibm-acpi-devel@lists.sourceforge.net
Nov 14 14:19:42 linux-k8di kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2
Nov 14 14:19:43 linux-k8di audispd[876]: No plugins found, exiting
Nov 14 14:19:43 linux-k8di bluetoothd[1061]: Failed to obtain handles for “Service Changed” characteristic

…] … not sending the rest of the messages because they seem to be from after I was happily into my session …

Hmmm. There is some sort of message about systemd-udevd blocked for more than 480 seconds. But that is only 8 minutes. I have some kind of block for 18 minutes.

Do you have an idea what to look at next?

#11

For a start, show full messages; otherwise anything is just guesswork. Upload them to http://susepaste.org/ and post link here.

#12

Ok, here is the output of

> sudo journalctl -p warning -b

URL: http://susepaste.org/16216119

Thank you for looking at it.

#13

USB2 boots ok?? Are you fully updated? Some USB3 ports seem to be problematic on some machines. Maybe try 42.2 it has a newer kernel

#14

Oh I was all excited this morning. Leap 42.1 did a huge number of updates this morning. (Yes, I always do all recommended updates promptly.) Then when I brought my laptop into work I decided to put it in the USB 3.0 port which is on the docking station. And it came up fast! 22 seconds or something like that for initrd!

So I thought well somehow that’s fixed.

But when I tried to reproduce it - no. I’ve gone back to the 18 minute delay during boot over USB 3.0 - including in the port on the docking station.

I checked USB 2.0 port again to see if that effect is reproducible and it is - I boot up at a normal speed, within a couple of minutes, when I use the SSD in the USB 2.0 port.

Weird that it worked fast that one time this morning over USB 3.0, eh?

Ok, I will try 42.2. But I am a little worried that what I may need is an older kernel not a newer one. My laptop is four years old. I’ll let you know what happens with 42.2.

#15

Oh, I found some more info! I managed to catch a screen shot just now on the slow boot over USB 3.0 just minutes before the system sorted itself out and came up the rest of the way lightning fast. Here is what I saw:

[OK] Started Show Plymouth Boot Screen.
[OK] Reached target Paths.
[OK] Reached target Basic System.
961.086927] INFO: task systemd-udevd:254 blocked for more than 480 seconds.
961.086949] Not tainted 4.1.34-33-default #1
961.086958] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message

#16

I asked for full log, not arbitrary filtered.

#17

Hi,

? I did post a full log. In my post of today at 11:49 I included the full log
of
> sudo journalctl -p warning -b

at
URL: http://susepaste.org/16216119

Why did you think that I “arbitrarily filtered” it?

I am very appreciative of any help you can give. I need this laptop to work for a trip I am going on leaving Saturday and I am spending my time re-installing not doing analysis. So I am quite desperate for help and entertaining any suggestion!

Currently, I have destroyed my Leap 42.1. I tried Leap 42.2. Situation is worse. Will put in a separate post.

#18

do it without parameters that is the filter

just journalctl

I had you filter as a first pass since without it can be very large

#19

NOW WITH LEAP 42.2

Trying to boot SSD over USB 3.0, I get this:

TIME ] Timed out waiting for device dev-disk-by/x2uuid-c…].device.device (1min 29s / 1min 30s)
DEPEND] Dependency failed for Resume from hibernation using device /dev/disk/by-uuid/c0…].
OK ] Reached target Local File System (Pre).
OK ] Reached target Local File System.
OK ] Reached target System Initialization.
OK ] Reached target Basic System.
*** ] A start job is running for dev-desk-by\x2duuid-32f0…].device (15min 1s / no limit)

… and now I am up in Leap 42.2. (I don’t know what the messages are that came after "A start job is running " because the boot into the desktop when it finally resumes booting is very fast, I can’t catch the messages.)

But after like an intolerable 20 minute wait.

Note that I had this same behaviour a few installations ago - with Tumbleweed. (I had tried going back to Leap 42.1 to get to something less bleeding edge for my poor older laptop.)

When I was trying to debug this with the Tumbleweed installation I had checked those UUIDs and they were correct. That was not the problem.

It seems like there is a start job running that I just don’t need to run. But what is that job - how do I turn it off?

#20

Hi,

Ok, here is the output of
> journalctl

http://susepaste.org/64417224

Thank you for looking at it.
[NOTE this is now a new installation of Leap 42.2 - not the Leap 42.1 that I was looking at yesterday. The boot time messages are different (and more informing perhaps) but the general problem behaviour of booting taking over twenty minutes is the same - so I presume probably the same problem in both distros. And it also happened in Tumbleweed.]