Posts by TRR

Just to follow up:
I got rid of the USB stick and installed to an SSD and now boot time is between 20s and 30s.
Thanks again!

Thank you good sir! Good call on the HTPC. It's a Zotac Zbox with nothing in it except RAM. And, yep, I'm using a 4 GB usb stick. It used to work fine, but started having this issue a year or so ago. I'll buy an SSD and throw it in there. Thanks for taking the time to respond! Excellent work over the years, by the way. I really appreciate it!

fsck -fy on both sdb1 and sdb2 show a clean system (I assume...I'm not well versed in fsck usage):

:~$ sudo fsck -f -y /dev/sdb2
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
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: 4522/212160 files (0.5% non-contiguous), 140116/847232 blocks
:~$ sudo fsck -f -y /dev/sdb1
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
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
System: 16/32768 files (6.3% non-contiguous), 64142/131072 blocks

Long-time OE user here (since before 1.0.0), just converted to LE about a month ago.

I'm on 7.90.009, but this problem has been occurring for a while (even with OE stable). I just never bothered to address it, because most of the time, the system is just on.

I need a little help as to why boot is taking so long. Here's a clip of the spot in dmesg where things appear to take forever, but I have no idea why. Notice the 15 second and then 3.5 minute delay. Anyone have a thought? I've seen these messages in other dmesg files on the internet, but there is never a long time period between them. Here are the relevant lines (at least, I assume these are relevant). Where can I find a log of what's going on during the wait time?

Any help is appreciated!

[ 10.352038] EXT4-fs (sdb2): couldn't mount as ext3 due to feature incompatibilities
[ 10.359016] EXT4-fs (sdb2): couldn't mount as ext2 due to feature incompatibilities
[ 12.214025] random: crng init done
[ 27.018256] EXT4-fs (sdb2): recovery complete
[ 27.025022] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
[ 243.127747] ### BIG FAT WARNING
[ 243.127787] ### sdb2 is removable. suspend/resume may not work
[ 243.129962] ### BIG FAT WARNING
[ 243.130027] ### sdb1 is removable. suspend/resume may not work

EDIT: additional poking around and I found the following in journalctl with a large delay. Is the slewing process taking that long to adjust the time? If so, how the heck do I fix it?

Dec 12 20:55:53 Office kernel: snd_hda_intel 0000:03:00.1: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
Dec 12 20:55:54 Office kodi.sh[651]: libEGL warning: DRI2: failed to authenticate
Dec 12 20:55:54 Office kodi.sh[651]: libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/dri)
Dec 12 20:55:57 Office connmand[328]: ntp: time slew +0.001855 s
Dec 12 20:58:10 Office kodi.sh[651]: no talloc stackframe around, leaking memory
Dec 12 20:59:10 Office kernel: r8169 0000:01:00.0: invalid short VPD tag 00 at offset 1