Results 1 to 5 of 5

Thread: failure to load or mount certain aspects of the file system on boot

  1. #1
    Join Date
    Apr 2016
    Location
    North America
    Posts
    537

    Default failure to load or mount certain aspects of the file system on boot

    One of the first things I see:




    It then tells me to log in for maintenance or press control-d.
    Control-d tells me I'm in emergency mode and to check journalctl -xb
    This is the first thing I could find that seems like a problem:





    If I log in as root, 'ls' only lists a few hidden files.
    'snapper list' gives a generic 'dbus error'

    The 5 snapshots available via grub all produce the same results.
    One (only one time) gave a unique popup:



    It actually loaded the X login screen,
    but after logging into Openbox no programs would load via hotkey,
    and the Openbox menus didn't appear.

    Things I did differently yesterday:

    - tried dual monitors for the first time (both hdmi) -- everything seemed to work fine
    - did a lot of setup / messing around to get rosegarden working
    - installed official qjackctl and timidity packages
    - installed unofficial qsynth package https://build.opensuse.org/package/show/home:rncbc/qsynth

    I chose that version of qsynth because it uses Qt5,
    and it is seemingly from the main developer.
    It seemed to work fine.
    After a lot of hassle I got rosegarden working! >_<

    When I logged out of Openbox I got a single blinking keyboard caret in the top left.
    This was unusual, but logging out of Openbox randomly won't properly logout back to the login screen.
    There isn't the blinking caret usually -- just a blank screen.
    My options are usually to ctrl+alt+f1 then ctrl+alt+f7, or ctrl+alt+backspace*2
    I tried both, but it seemed to freeze the system, without showing anything new, so I ended up flipping the power switch.
    Then I realized it was just past midnight... monday... would ctrl+alt+backspace trigger the weekly cron job?
    Did I cut power in the middle of a disk cleanup?
    I get the same blinking caret now, directly after grub, then it goes to a grey screen with three questions marks,
    then the first screenshot, then the message about logging in for maintenance.

    Do I have any options other than a fresh install?

  2. #2
    Join Date
    Jun 2008
    Location
    Canada
    Posts
    453

    Default Re: failure to load or mount certain aspects of the file system on boot

    Quote Originally Posted by ravas View Post
    One of the first things I see:




    It then tells me to log in for maintenance or press control-d.
    Control-d tells me I'm in emergency mode and to check journalctl -xb
    This is the first thing I could find that seems like a problem:





    If I log in as root, 'ls' only lists a few hidden files.
    'snapper list' gives a generic 'dbus error'

    The 5 snapshots available via grub all produce the same results.
    One (only one time) gave a unique popup:



    It actually loaded the X login screen,
    but after logging into Openbox no programs would load via hotkey,
    and the Openbox menus didn't appear.

    Things I did differently yesterday:

    - tried dual monitors for the first time (both hdmi) -- everything seemed to work fine
    - did a lot of setup / messing around to get rosegarden working
    - installed official qjackctl and timidity packages
    - installed unofficial qsynth package https://build.opensuse.org/package/show/home:rncbc/qsynth

    I chose that version of qsynth because it uses Qt5,
    and it is seemingly from the main developer.
    It seemed to work fine.
    After a lot of hassle I got rosegarden working! >_<

    When I logged out of Openbox I got a single blinking keyboard caret in the top left.
    This was unusual, but logging out of Openbox randomly won't properly logout back to the login screen.
    There isn't the blinking caret usually -- just a blank screen.
    My options are usually to ctrl+alt+f1 then ctrl+alt+f7, or ctrl+alt+backspace*2
    I tried both, but it seemed to freeze the system, without showing anything new, so I ended up flipping the power switch.
    Then I realized it was just past midnight... monday... would ctrl+alt+backspace trigger the weekly cron job?
    Did I cut power in the middle of a disk cleanup?
    I get the same blinking caret now, directly after grub, then it goes to a grey screen with three questions marks,
    then the first screenshot, then the message about logging in for maintenance.

    Do I have any options other than a fresh install?
    your file system is btrfs?
    www.laboiteaprog.com

  3. #3
    Join Date
    Apr 2016
    Location
    North America
    Posts
    537

    Default Re: failure to load or mount certain aspects of the file system on boot

    Yes btrfs.

    I also forgot to mention that "home/mount.start failed" is just one of a long list.

  4. #4
    Join Date
    Apr 2016
    Location
    North America
    Posts
    537

    Default Re: failure to load or mount certain aspects of the file system on boot

    Alrighty then... looks like it's time to try leap. ;-]

  5. #5
    Join Date
    Apr 2016
    Location
    North America
    Posts
    537

    Default Re: failure to load or mount certain aspects of the file system on boot

    Lucky for me I chose a different user name, because my old home folder is accessible after a "fresh install" (but Leap instead of TW).


    How is that explained?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •