[SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

Mache73k · 2020-06-22 00:55:33

Hello Lovely People,

I didn't want to post this at first as I like to find solutions for things myself, but I must say I exhausted all my options with this one. I've searched everywhere, and reinstalled Arch using different configs like a couple of times, (single vs multiple partitions). I got the legacy BIOS and this is the output of bootinfoscript:

                 Boot Info Script 0.78      [09 October 2019]


============================= Boot Info Summary: ===============================

 => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    for (,msdos1)/grub. It also embeds following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos biosdisk
    ---------------------------------------------------------------------------

sda1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        /grub/grub.cfg /grub/i386-pc/core.img

sda2: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info: 

sda3: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Arch Linux
    Boot files:        /etc/fstab

sda4: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________
Disk /dev/sda: 149.5 GiB, 160041885696 bytes, 312581808 sectors
Disk model: ST9160314AS     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1               2,048       411,647       409,600  83 Linux
/dev/sda2             411,648     6,703,103     6,291,456  83 Linux
/dev/sda3           6,703,104    59,131,903    52,428,800  83 Linux
/dev/sda4          59,131,904   312,581,807   253,449,904  83 Linux


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/sda1        068a60f1-3fe3-4eab-8e5c-b1cb07a3f385   ext4       
/dev/sda2        57223f6b-72c1-47e3-b149-5b916bc02b46   swap       
/dev/sda3        95883bea-8a62-4267-a5a6-e168a9fbd4c9   ext4       
/dev/sda4        3cb82157-acfa-4c7e-b685-81792fad5df8   ext4       

========================= "ls -l /dev/disk/by-id" output: ======================

total 0
lrwxrwxrwx 1 root root  9 Jun 21 15:01 ata-ST9160314AS_5VCM9NM6 -> ../../sda
lrwxrwxrwx 1 root root 10 Jun 21 15:02 ata-ST9160314AS_5VCM9NM6-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jun 21 15:01 ata-ST9160314AS_5VCM9NM6-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jun 21 15:01 ata-ST9160314AS_5VCM9NM6-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jun 21 15:02 ata-ST9160314AS_5VCM9NM6-part4 -> ../../sda4
lrwxrwxrwx 1 root root  9 Jun 21 15:01 wwn-0x5000c50037df0df3 -> ../../sda
lrwxrwxrwx 1 root root 10 Jun 21 15:02 wwn-0x5000c50037df0df3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jun 21 15:01 wwn-0x5000c50037df0df3-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jun 21 15:01 wwn-0x5000c50037df0df3-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jun 21 15:02 wwn-0x5000c50037df0df3-part4 -> ../../sda4

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/sda1        /boot                    ext4       (rw,relatime)
/dev/sda3        /                        ext4       (rw,relatime)
/dev/sda4        /home                    ext4       (rw,relatime)


============================= sda1/grub/grub.cfg: ==============================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos3' --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3  95883bea-8a62-4267-a5a6-e168a9fbd4c9
else
  search --no-floppy --fs-uuid --set=root 95883bea-8a62-4267-a5a6-e168a9fbd4c9
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-95883bea-8a62-4267-a5a6-e168a9fbd4c9' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  068a60f1-3fe3-4eab-8e5c-b1cb07a3f385
	else
	  search --no-floppy --fs-uuid --set=root 068a60f1-3fe3-4eab-8e5c-b1cb07a3f385
	fi
	echo	'Loading Linux linux ...'
	linux	/vmlinuz-linux root=UUID=95883bea-8a62-4267-a5a6-e168a9fbd4c9 rw  loglevel=3 quiet
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-95883bea-8a62-4267-a5a6-e168a9fbd4c9' {
	menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-95883bea-8a62-4267-a5a6-e168a9fbd4c9' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  068a60f1-3fe3-4eab-8e5c-b1cb07a3f385
		else
		  search --no-floppy --fs-uuid --set=root 068a60f1-3fe3-4eab-8e5c-b1cb07a3f385
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=95883bea-8a62-4267-a5a6-e168a9fbd4c9 rw  loglevel=3 quiet
		echo	'Loading initial ramdisk ...'
		initrd	/initramfs-linux.img
	}
	menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-95883bea-8a62-4267-a5a6-e168a9fbd4c9' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_msdos
		insmod ext2
		set root='hd0,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,msdos1' --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  068a60f1-3fe3-4eab-8e5c-b1cb07a3f385
		else
		  search --no-floppy --fs-uuid --set=root 068a60f1-3fe3-4eab-8e5c-b1cb07a3f385
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=95883bea-8a62-4267-a5a6-e168a9fbd4c9 rw  loglevel=3 quiet
		echo	'Loading initial ramdisk ...'
		initrd	/initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=================== sda1: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)

   0.010699272 = 0.011488256    grub/grub.cfg                                  4
   0.071588516 = 0.076867584    grub/i386-pc/core.img                          1
   0.017683983 = 0.018988032    vmlinuz-linux                                  1
   0.059570312 = 0.063963136    initramfs-linux-fallback.img                   4
   0.028320312 = 0.030408704    initramfs-linux.img                            3

=============================== sda3/etc/fstab: ================================

--------------------------------------------------------------------------------
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda3
UUID=95883bea-8a62-4267-a5a6-e168a9fbd4c9	/         	ext4      	rw,relatime	0 1

# /dev/sda1
UUID=068a60f1-3fe3-4eab-8e5c-b1cb07a3f385	/boot     	ext4      	rw,relatime	0 2

# /dev/sda4
UUID=3cb82157-acfa-4c7e-b685-81792fad5df8	/home     	ext4      	rw,relatime	0 2

# /dev/sda2
UUID=57223f6b-72c1-47e3-b149-5b916bc02b46	none      	swap      	defaults  	0 0

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

This is the output of systemd-analyze:

 
Startup finished in 6.260s (kernel) + 14.078s (userspace) = 20.338s
graphical.target reached after 13.180s in userspace

systemd-analyze blame output:

 
12.054s man-db.service                                                                    >
 6.193s dev-sda3.device                                                                   >
 3.838s systemd-journal-flush.service                                                     >
 2.169s polkit.service                                                                    >
 1.976s systemd-fsck@dev-disk-by\x2duuid-068a60f1\x2d3fe3\x2d4eab\x2d8e5c\x2db1cb07a3f385.>
 1.905s systemd-udevd.service                                                             >
 1.495s systemd-fsck@dev-disk-by\x2duuid-3cb82157\x2dacfa\x2d4c7e\x2db685\x2d81792fad5df8.>
 1.478s systemd-journald.service                                                          >
 1.457s systemd-logind.service                                                            >
 1.153s NetworkManager.service                                                            >
  958ms ldconfig.service                                                                  >
  830ms systemd-sysusers.service                                                          >
  656ms user@1000.service                                                                 >
  625ms systemd-rfkill.service                                                            >
  567ms systemd-random-seed.service                                                       >
  439ms systemd-tmpfiles-setup.service                                                    >
  409ms modprobe@drm.service                                                              >
  329ms systemd-udev-trigger.service                                                      >
  321ms systemd-tmpfiles-clean.service                                                    >
  228ms wpa_supplicant.service                                                            >
  227ms dev-disk-by\x2duuid-57223f6b\x2d72c1\x2d47e3\x2db149\x2d5b916bc02b46.swap         >
  208ms systemd-journal-catalog-update.service                                            >
  180ms rtkit-daemon.service                                                              >
  172ms systemd-tmpfiles-setup-dev.service                                                >
  169ms systemd-sysctl.service                                                            >
  165ms boot.mount                                                                        >
   72ms dev-mqueue.mount                                                                  >
   69ms sys-kernel-debug.mount                                                            >
   67ms sys-kernel-tracing.mount                                                          >
   66ms kmod-static-nodes.service                                                         >
   65ms systemd-update-utmp.service                                                       >
   61ms systemd-user-sessions.service                                                     >
   60ms dev-hugepages.mount                                                               >
   60ms systemd-backlight@backlight:acpi_video0.service                                   >
   47ms systemd-remount-fs.service                                                        >
   44ms home.mount                                                                        >
   39ms sys-kernel-config.mount                                                           >
   36ms user-runtime-dir@1000.service                                                     >
   27ms systemd-backlight@backlight:intel_backlight.service                               >
   26ms systemd-update-done.service                                                       >
    8ms tmp.mount                                                                         >
lines 1-41/41 (END)

I'd say the output of systemd-analyze seems reasonable to me.. the problem seems to be before the system get over loading the initial ramdisk which takes up a ridiculous amount of time, I had othe distros on this pc and the boot time was never alarming to the point of me having to look it up..

If any one got a hint, it'd be really cool.. thank y'all.

Last edited by Mache73k (2020-06-27 10:01:29)

twelveeighty · 2020-06-22 15:12:27

Take a look at your journal for your last boot (journalctl -b -1), it looks like something is timing out during startup. The default "timeout" is 90s or so, so it's likely a service that fails or never completes.

Scimmia · 2020-06-22 15:14:25

Get rid of 'quiet' in the kernel command line, see what's actually happening.

Mache73k · 2020-06-22 23:05:03

twelveeighty wrote:

Take a look at your journal for your last boot (journalctl -b -1), it looks like something is timing out during startup. The default "timeout" is 90s or so, so it's likely a service that fails or never completes.

Thanks for the tip. I've tried to change the default timeout in systemd.conf but for some reason it didn't work.. it just kept on counting up to 90s and the system boots with no errors (when taking out 'quiet' param in grub settings). So you're probably right, there's some kind of service or unit that is causing this behavior in systemd. I ran the journalctl -b -1 command, but I can't quite pinpoint what causing this issue form its output. here it is anyway:

 
https://throwbin.io/1Zfx8zK

I'm analyzing the output as I'm writing this, but hopefully someone with more experience will be able to spot the faulty service before I do.. Thank you for the response

Mache73k · 2020-06-22 23:07:08

Scimmia wrote:

Get rid of 'quiet' in the kernel command line, see what's actually happening.

I've done that at some point, it shows loading initial ramsidk for like 90s and then it begins booting normally with no errors.

loqs · 2020-06-22 23:44:27

Was some time lost before the journal started? I am interpreting the following as from boot to loading systemd off the root filesystem was performed in under a second.

Jun 22 22:11:29 Architype kernel: Linux version 5.7.4-arch1-1 (linux@archlinux) (gcc version 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PREEMPT Thu, 18 Jun 2020 16:01:07 +0000

....
Jun 22 22:11:29 Architype systemd[1]: systemd 245.6-7-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)

Mache73k · 2020-06-23 00:00:34

loqs wrote:

Was some time lost before the journal started? I am interpreting the following as from boot to loading systemd off the root filesystem was performed in under a second.

Jun 22 22:11:29 Architype kernel: Linux version 5.7.4-arch1-1 (linux@archlinux) (gcc version 10.1.0 (GCC), GNU ld (GNU Binutils) 2.34.0) #1 SMP PREEMPT Thu, 18 Jun 2020 16:01:07 +0000

....
Jun 22 22:11:29 Architype systemd[1]: systemd 245.6-7-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)

That's weird.. not sure how to respond to your question as I didn't quite understand it.. I have configured grub to have 0s timeout and no menu, but not really sure if this could be relevant to your question

Last edited by Mache73k (2020-06-23 00:04:21)

loqs · 2020-06-23 00:14:52

Do you also have auto root login enabled?

Jun 22 22:11:47 Architype login[325]: ROOT LOGIN ON tty1

If the timing is correct that login was 18 seconds after startup.

Mache73k · 2020-06-23 00:24:25

loqs wrote:

Do you also have auto root login enabled?
Jun 22 22:11:47 Architype login[325]: ROOT LOGIN ON tty1
If the timing is correct that login was 18 seconds after startup.

No I haven't set up auto root.. but after I booted, I logged in as root and edited systemd.conf then rebooted, then logged in as secondary user where I ran the journalct -b -1 command.. is this helpful?

twelveeighty · 2020-06-23 15:36:38

When I recommended 'journalclt -b - 1' I may have made things more complicated that it had to, since you would use that if your system crashes during boot, which isn't happening. In your case, it may be easier to explore 'journalctl -b 0', which is the logs from the *current* boot.

What loqs is saying is it looks like that the delay happens BEFORE the first entry in the journal. Because the time lapsed between the kernel start line and systemd reporting to be running in system mode is within the second. I think we're barking up the wrong tree with systemd, the delay happens before systemd kicks in.

Can you turn on Grub debug messages: https://wiki.archlinux.org/index.php/GR … g_messages and see what rolls by? Not sure if you can persist that to a log (I don't use Grub myself).

Mache73k · 2020-06-24 00:12:25

twelveeighty wrote:

When I recommended 'journalclt -b - 1' I may have made things more complicated that it had to, since you would use that if your system crashes during boot, which isn't happening. In your case, it may be easier to explore 'journalctl -b 0', which is the logs from the *current* boot.
What loqs is saying is it looks like that the delay happens BEFORE the first entry in the journal. Because the time lapsed between the kernel start line and systemd reporting to be running in system mode is within the second. I think we're barking up the wrong tree with systemd, the delay happens before systemd kicks in.
Can you turn on Grub debug messages: https://wiki.archlinux.org/index.php/GR … g_messages and see what rolls by? Not sure if you can persist that to a log (I don't use Grub myself).

I had suspected that Grub is the cause of the issue, and you mentioning it has confirmed my doubts, I tried changing it to LILO before but with no success. I turned on the Debug mode in Grub and it just kept puking its heart out with nothing that I could undestand tbh. It also made the system unbootable, so I plugged in my Bootable ISO and chrooted into the system.. uninstalled Grub and installed Syslinux.

There's definitely significant change in the time between loading the kernel and booting Systemd. from 90s-ish to somewhere between 20s nad 40s. It's good, but still not perfect..

What I'm noticing now is that the boot hangs a little bit after showing this message:

Probing EDD (edd=off to disable)...ok

and then boots into systemd.

I'm looking into it now anf I'm guessing disabling EDD from kernel will hopefully fix but not really sure..

Mache73k · 2020-06-24 01:00:21

Quick Update

I found out that the delay has something to do with ACPI, when I turn it off using acpi=off, it boots after like 7s into systemd. However, systemd seems to be broken when I do this, it shows some random lines of code in places where they shouldn't be, and when I get to the login screen, it doesn't let me enter my login credentials, instead it keeps showing some hardware related informations.

Does anyone have a clue how to deal with this?

seth · 2020-06-24 05:58:18

Pass "acpi.debug_layer=0x2 acpi.debug_level=0xffffffff earlyprintk=vga,keep log_buf_len=16" instead of quiet, https://wiki.archlinux.org/index.php/Ge … bug_output

There're also more finegrained acpi values, see https://raw.githubusercontent.com/torva … meters.txt

Mache73k · 2020-06-26 00:43:47

seth wrote:

Pass "acpi.debug_layer=0x2 acpi.debug_level=0xffffffff earlyprintk=vga,keep log_buf_len=16" instead of quiet, https://wiki.archlinux.org/index.php/Ge … bug_output
There're also more finegrained acpi values, see https://raw.githubusercontent.com/torva … meters.txt

Thanks for the tip. I'm going to call it quit for now, Syslinux reduced the delay to half and I'll take that as a win untill I get the energy to deal with this again. Thank you all for the help.

Mache73k · 2020-06-27 10:00:05

Update

It seems that the issue in essence has something to do with systemd. I switched to Runit and the whole boot process now takes 15s from start to login prompt.

Last edited by Mache73k (2020-06-27 10:00:23)

Krygen · 2021-10-06 12:02:03

Simply disable man-db service.

2ManyDogs · 2021-10-06 12:22:04

Closing this old solved topic.

Arch Linux

#1 2020-06-22 00:55:33

[SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#2 2020-06-22 15:12:27

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#3 2020-06-22 15:14:25

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#4 2020-06-22 23:05:03

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#5 2020-06-22 23:07:08

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#6 2020-06-22 23:44:27

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#7 2020-06-23 00:00:34

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#8 2020-06-23 00:14:52

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#9 2020-06-23 00:24:25

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#10 2020-06-23 15:36:38

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#11 2020-06-24 00:12:25

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#12 2020-06-24 01:00:21

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#13 2020-06-24 05:58:18

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#14 2020-06-26 00:43:47

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#15 2020-06-27 10:00:05

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#16 2021-10-06 12:02:03

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

#17 2021-10-06 12:22:04

Re: [SOLVED] Boot Is Too Slow (> 2m) at Loading Initial Ramdisk

Board footer