Announcement

Collapse
No announcement yet.

Empty "starting" messages on boot

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Empty "starting" messages on boot

    Hi, I've messed around with my Kubuntu installation a little, and I've only just noticed that my boot screen is displaying empty "starting" messages. I won't go into the full details of my mess unless it's useful, but I just wanted to see if other people see similar "empty" messages in /var/log/boot.log . Specifically, I'm referring to the six entries where the line merely reads "* Starting [ OK ]". Thanks in advance.

    Code:
    Begin: Loading essential drivers ... done.
    Begin: Running /scripts/init-premount ... done.
    Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
    Begin: Running /scripts/local-premount ... done.
    Begin: Running /scripts/local-bottom ... done.
    done.
    Begin: Running /scripts/init-bottom ... done.
    fsck from util-linux 2.20.1
    fsck from util-linux 2.20.1
    fsck from util-linux 2.20.1
    root: clean, 312735/1638400 files, 2488421/6553600 blocks
    home: recovering journal
    linuxHDD: recovering journal
    home: clean, 43376/7208960 files, 7265623/28835840 blocks
    linuxHDD: Clearing orphaned inode 27658176 (uid=1000, gid=1000, mode=0100664, size=2522500)
    linuxHDD: Clearing orphaned inode 27658174 (uid=1000, gid=1000, mode=0100664, size=2522500)
    linuxHDD: Clearing orphaned inode 27658157 (uid=1000, gid=1000, mode=0100664, size=2522524)
    linuxHDD: Clearing orphaned inode 27658154 (uid=1000, gid=1000, mode=0100600, size=4104)
    linuxHDD: Clearing orphaned inode 27657957 (uid=1000, gid=1000, mode=0100600, size=2056)
    linuxHDD: Clearing orphaned inode 27658136 (uid=0, gid=0, mode=0100640, size=3648)
    linuxHDD: Clearing orphaned inode 27658133 (uid=0, gid=0, mode=0100640, size=375)
    linuxHDD: Clearing orphaned inode 27657960 (uid=1000, gid=1000, mode=0100600, size=8200)
    linuxHDD: Clearing orphaned inode 27658143 (uid=1000, gid=1000, mode=0100600, size=2048)
    linuxHDD: Clearing orphaned inode 27658142 (uid=1000, gid=1000, mode=0100600, size=2056)
    linuxHDD: Clearing orphaned inode 27658141 (uid=1000, gid=1000, mode=0100600, size=512)
    linuxHDD: Clearing orphaned inode 27658140 (uid=1000, gid=1000, mode=0100600, size=2048)
    linuxHDD: Clearing orphaned inode 27658139 (uid=1000, gid=1000, mode=0100600, size=2056)
    linuxHDD: Clearing orphaned inode 27657746 (uid=1000, gid=1000, mode=0100600, size=512)
    linuxHDD: clean, 554217/29491200 files, 64459650/117964800 blocks
    modem-manager[1256]: <info>  ModemManager (version 0.6.0.0) starting...
    
     * Starting mDNS/DNS-SD daemon [ OK ]
     * Starting network connection manager [ OK ]
     * Stopping Flush boot log to disk [ OK ]
     * Stopping save udev log and update rules [ OK ]
    Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
    Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
     * Starting AppArmor profiles [ OK ]
    Loading the saved-state of the serial devices... 
     * Stopping System V initialisation compatibility [ OK ]
     * Starting System V runlevel compatibility [ OK ]
     * Starting  [ OK ]
     * Starting  [ OK ]
     * Starting Bumblebee supporting nVidia Optimus cards [ OK ]
     * Starting LightDM Display Manager [ OK ]
     * Starting anac(h)ronistic cron [ OK ]
     * Starting  [ OK ]
     * Starting  [ OK ]
     * Starting save kernel messages [ OK ]
     * Starting  [ OK ]
     * Starting  [ OK ]
     * Starting ACPI daemon [ OK ]
     * Starting regular background program processing daemon [ OK ]
     * Starting deferred execution scheduler [ OK ]
     * Starting dictionary server dictd [ OK ]
     * Starting CPU interrupts balancing daemon [ OK ]
     * Stopping anac(h)ronistic cron [ OK ]

    #2
    Nothing to worry about, I've seen that for years. I suspect the services are missing some kind of string someplace.

    BTW, does fsck always have to do some work every time you boot your computer?

    Comment


      #3
      Thanks for the response. And I'm glad that there's nothing to worry about.

      Are you referring to the "Clearing orphaned inode" lines? I don't have that every time, just after the computer crashes. Which happens about a third of time I try to hibernate (to swap)…

      Comment


        #4
        Alas, hiberate and suspend in Linux seem to be eternally troublesome. Every hardware manufacturer likes to implement it a bit differently, and of course they never document it completely, if at all. Some computers have no problems, others won't work.

        Comment


          #5
          Yes, I thought as much. Fortunately for me (Dell XPS 17 L702X), suspend to RAM works fine. It's just hibernate that often breaks. I'm just waiting for the "Steam for Linux" revolution to be complete, then I can ditch Windows forever!

          Thanks again for your response.

          Comment

          Working...
          X