Boot Time Hanging

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
rlives
Level 1
Level 1
Posts: 4
Joined: Tue May 28, 2019 9:05 pm

Boot Time Hanging

Post by rlives » Tue Aug 20, 2019 4:37 pm

I know... another boot time thread.

After searching and reading the forums I had temporary success using the change

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"
Apparently, that was short-lived. I got two faster boots out of it and now seem to be back in the long boot time doldrums. One thing I have noticed is that when I have extended boot times, I am no longer able to access any of my other hard drives and an icon for "Filesystem Root" shows up on my desktop. I have tried to roll back to previous kernels, but didn't have any positive change to the boot time.

So, here's my setup:

Code: Select all

systemd-analyze
Startup finished in 1min 41.303s (kernel) + 1min 40.839s (userspace) = 3min 22.143s
graphical.target reached after 1min 40.825s in userspace

Code: Select all

systemd-analyze blame
    1min 38.044s udisks2.service
         13.531s apt-daily.service
          6.297s NetworkManager-wait-online.service
          2.281s dev-sdc5.device
          1.518s apt-daily-upgrade.service
           481ms systemd-journal-flush.service
           428ms ModemManager.service
           408ms networking.service
           390ms ubuntu-system-adjustments.service
           386ms accounts-daemon.service
           385ms NetworkManager.service
           316ms systemd-udev-trigger.service
           311ms grub-common.service
           298ms systemd-journald.service
           289ms lvm2-monitor.service
           272ms keyboard-setup.service
           260ms avahi-daemon.service
           258ms virtualbox-guest-utils.service
           253ms speech-dispatcher.service
           247ms lm-sensors.service
           242ms cgmanager.service
           240ms systemd-logind.service
           220ms console-kit-log-system-start.service

Code: Select all

System:
  Host: OldPC Kernel: 4.15.0-58-generic x86_64 bits: 64 compiler: gcc 
  v: 7.4.0 Desktop: Cinnamon 4.0.10 dm: LightDM 1.26.0 
  Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic 
Machine:
  Type: Desktop Mobo: Gigabyte model: P35-DS3L v: x.x serial: <filter> 
  BIOS: Award v: F7 date: 11/29/2007 
CPU:
  Topology: Dual Core model: Intel Core2 Duo E6750 bits: 64 type: MCP 
  arch: Core Merom rev: B L2 cache: 4096 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 10666 
  Speed: 2000 MHz min/max: 2000/2667 MHz Core speeds (MHz): 1: 2000 2: 2000 
Graphics:
  Device-1: NVIDIA G84 [GeForce 8600 GT] vendor: ASUSTeK driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:0402 
  Display: x11 server: X.Org 1.19.6 driver: nouveau 
  unloaded: fbdev,modesetting,vesa tty: N/A 
  OpenGL: renderer: NV84 v: 3.3 Mesa 18.2.8 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel 82801I HD Audio vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:1b.0 chip ID: 8086:293e 
  Sound Server: ALSA v: k4.15.0-58-generic 
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter 
  vendor: Belkin F5D5000 driver: 8139too v: 0.9.28 port: d000 
  bus ID: 04:01.0 chip ID: 10ec:8139 
  IF: eth0 state: down mac: <filter> 
  Device-2: Ralink RT5372 Wireless Adapter type: USB driver: rt2800usb 
  bus ID: 2-2:2 chip ID: 148f:5372 
  IF: wlan2 state: up mac: <filter> 
Drives:
  Local Storage: total: 1.05 TiB used: 91.81 GiB (8.6%) 
  ID-1: /dev/sda vendor: Western Digital model: WD3200AAKS-00VYA0 
  size: 298.09 GiB speed: 3.0 Gb/s serial: <filter> rev: 1B02 scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST3808110AS size: 74.53 GiB 
  speed: 1.5 Gb/s serial: <filter> rev: L scheme: MBR 
  ID-3: /dev/sdc vendor: Samsung model: SSD 840 EVO 250GB size: 232.88 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: BB6Q scheme: MBR 
  ID-4: /dev/sdd vendor: Western Digital model: WD5000AAKS-00TMA0 
  size: 465.76 GiB speed: 3.0 Gb/s serial: <filter> rev: 1C01 scheme: MBR 
Partition:
  ID-1: / size: 128.76 GiB used: 91.81 GiB (71.3%) fs: ext4 dev: /dev/sdc5 
  ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdc6 
Sensors:
  System Temperatures: cpu: 52.0 C mobo: N/A gpu: nouveau temp: 60 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 164 Uptime: 11m Memory: 7.79 GiB used: 1.18 GiB (15.2%) 
  Init: systemd v: 237 runlevel: 5 default: 2 Compilers: gcc: 7.4.0 
  alt: 4.7/4.8/5/7 Shell: bash v: 4.4.20 running in: gnome-terminal 
  inxi: 3.0.27 

Code: Select all

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda5 during installation
UUID=bd998525-4203-40fc-95ee-98a074eda3b6 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda6 during installation
UUID=02132c3f-ad59-4452-9f90-8c403e497ec9 none            swap    sw              0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto,exec,utf8 0       0

Code: Select all

swapon --show
NAME      TYPE      SIZE USED PRIO
/dev/sdc6 partition   8G   0B   -2

Code: Select all

lsblk -o +FSTYPE,UUID
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT FSTYPE UUID
fd0    2:0    1     4K  0 disk                   
sda    8:0    0 298.1G  0 disk                   
└─sda1
       8:1    0 298.1G  0 part            ntfs   92D20921D2090B65
sdb    8:16   0  74.5G  0 disk                   
├─sdb1
│      8:17   0   100M  0 part                   
├─sdb2
│      8:18   0  21.2G  0 part                   
├─sdb3
│      8:19   0     1K  0 part                   
├─sdb5
│      8:21   0     8G  0 part                   
├─sdb6
│      8:22   0   7.9G  0 part                   
├─sdb7
│      8:23   0  15.4G  0 part                   
└─sdb8
       8:24   0    22G  0 part                   
sdc    8:32   0 232.9G  0 disk                   
├─sdc1
│      8:33   0   100M  0 part            ntfs   10242C70242C5ACC
├─sdc2
│      8:34   0  93.9G  0 part            ntfs   AEBC2D7BBC2D3F69
├─sdc3
│      8:35   0     1K  0 part                   
├─sdc5
│      8:37   0   131G  0 part /          ext4   bd998525-4203-40fc-95ee-98a074eda3b6
└─sdc6
       8:38   0     8G  0 part [SWAP]     swap   02132c3f-ad59-4452-9f90-8c403e497ec9
sdd    8:48   0 465.8G  0 disk                   
├─sdd1
│      8:49   0 231.8G  0 part            ntfs   7094346694343148
├─sdd2
│      8:50   0     1K  0 part                   
├─sdd5
│      8:53   0 224.5G  0 part            ext3   236bdc04-d7f6-4f48-b6b5-dcf30b627e21
└─sdd6
       8:54   0   9.5G  0 part            swap   68aea700-c862-4d2f-825a-6e559b21ff49

It's a dinosaur of a machine, but until recently, has been very good to me.

ETA: I am still learning, so if it's possible to explain any offered solutions, I would appreciate it.

User avatar
catweazel
Level 19
Level 19
Posts: 9184
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: Boot Time Hanging

Post by catweazel » Tue Aug 20, 2019 4:51 pm

rlives wrote:
Tue Aug 20, 2019 4:37 pm
I know... another boot time thread.

After searching and reading the forums I had temporary success using the change

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"
I think that the fact you had success with that is down to sheer synchronicity. My first reaction is to suspect your hard disk. I recommend backing up your treasured stuff asap, then trying fsck on the drive from within a live media boot.
¡uʍop ǝpısdn sı buıɥʇʎɹǝʌǝ os ɐıןɐɹʇsnɐ ɯoɹɟ ɯ,ı

User avatar
zcot
Level 4
Level 4
Posts: 495
Joined: Wed Oct 19, 2016 6:08 pm

Re: Boot Time Hanging

Post by zcot » Tue Aug 20, 2019 10:58 pm

And after fsck, and when you get that long boot time, get a dmesg | pastebin command and share the url link.

And are you getting the same reaction from live session?

rlives
Level 1
Level 1
Posts: 4
Joined: Tue May 28, 2019 9:05 pm

Re: Boot Time Hanging

Post by rlives » Fri Aug 23, 2019 12:52 am

It took an embarrassingly long time to get the live session up and running. But I'm not certain that I actually did it properly. I wasn't able to get dmesg | pastebin to work, and fsck came back with this:

Code: Select all

fsck /dev/sdb
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
fsck.ext2: Input/output error while trying to open /dev/sdb

The superblock could not be read or does not describe a valid /ext2/ext3/ext4 filesystem. If the device is valid and it

really contains an /ext2/ext3/ext4 filesystem (and not swap ufs or something else), then the superblock is corrupt, and you

might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
 or
e2fsck -b 32768 <device>
I attempted to run it in a recovery session but was not able to due to mount.

TI58C
Level 4
Level 4
Posts: 354
Joined: Tue Jul 18, 2017 5:57 am

Re: Boot Time Hanging

Post by TI58C » Sat Aug 24, 2019 6:02 am

Try running fsck on a partition instead of disk.

fsck is supposed to work on a linux "file system". That's the reason for the error message "The superblock could not be read......."
see man fsck

Oh, and do follow catweazel 's advice, boot from live-usb. That way you will make sure the partition you are checking is not mounted (using fsck on a mounted partition can lead to serious problems).

Robert
Linux is like my late labrador lady-dog: loyal and loving if you treat her lady-like, disbehaving princess if you don't.

Post Reply

Return to “Newbie Questions”