Page 6 of 8 FirstFirst ... 45678 LastLast
Results 51 to 60 of 76

Thread: Welcome to emergency mode!

  1. #51

    Default Re: Welcome to emergency mode!

    Quote Originally Posted by tsu2 View Post
    To support my interpretation, I believe it's necessary for the OP to restate and clarify that with his original post (and subject line) that he has always been booting to emergency mode from the beginning, and any modifications to the Windows /E partition has been ineffective in fixing his basic problem... He's not booting into Normal mode.
    TSU
    I actually stated in the first line of this thread that I usually boot into emergency mode, and regret having to report that this still seems to be so. It happens that two of my normal modes have occurred just after I tried the suggestion by AlmostAWhisper and just after tsu2 seems to have been successful in overcoming the problem with starting Show Plymouth Boot Screen. In both cases, however, it only lasted one session.

    The error spotted by the Carlos' eagle eye was probably by me, not my computer.

    As I don't know how long it would take me to work out how to access and use SUsE Paste, and it doesn't seem to be considered outrageous, I'm taking the liberty of posting some of my latest output from journalctl -b here. To fit into the character limit, I'm starting at the point where the problems started before tsu2's recommendation, and curtailing what follows. It still contains more errors and failures than I'd wish:
    Code:
    Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Show Plymouth Boot Screen.
    Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch.
    Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
    Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start timed out.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for /windows/E.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Local File Systems.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Remote File Systems (Pre).
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job remote-fs-pre.target/start failed with result 'dependency'.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job local-fs.target/start failed with result 'dependency'.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job windows-E.mount/start failed with result 'dependency'.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start failed with result 'timeout'.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Unmounted /home.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Kernel Device Manager...
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped CUPS Printer Service Spool.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping Apply Kernel Variables...
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped Apply Kernel Variables.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd-journal[205]: Journal stopped
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd-journal[273]: Allowing runtime journal files to grow to 100.3M.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Starting Emergency Shell...
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Started Emergency Shell.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Starting Emergency Mode.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Reached target Emergency Mode.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped udev Kernel Device Manager.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping Create dynamic rule for /dev/root link...
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped Create dynamic rule for /dev/root link.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping create /dev/root symlink with dynamic rule...
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped create /dev/root symlink with dynamic rule.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Kernel Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Closed udev Kernel Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Control Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Closed udev Control Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Kernel Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Closed udev Kernel Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Control Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Closed udev Control Socket.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Starting Journal Service...
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped Collect Read-Ahead Data.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd-journald[205]: Received SIGTERM
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Starting Journal Service...
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Started Journal Service.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd-journal[273]: Journal started
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Stopped LSB: Set default boot entry if called.
    Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Startup finished in 5s 976ms 554us (kernel) + 1min 31s 208ms 636us (userspace) = 1min 37s 185ms 190us.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Replay Read-Ahead Data...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Collect Read-Ahead Data...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Syslog.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Reached target Syslog.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Remote File Systems.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Reached target Remote File Systems.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting create /dev/root symlink with dynamic rule...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Create dynamic rule for /dev/root link...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting udev Control Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Listening on udev Control Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting udev Kernel Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Listening on udev Kernel Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting udev Coldplug all Devices...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Delayed Shutdown Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Listening on Delayed Shutdown Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Stopping Emergency Mode.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Stopped target Emergency Mode.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Stopping Emergency Shell...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting LSB: Set default boot entry if called...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting Encrypted Volumes.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Reached target Encrypted Volumes.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting udev Kernel Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Listening on udev Kernel Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Starting udev Control Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Listening on udev Control Socket.
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart5.device...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart6.device...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart1.device...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart7.device...
    Apr 08 15:23:44 UsrFriendesktop.Lisheen systemd[1]: Expecting device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Collect Read-Ahead Data.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Replay Read-Ahead Data.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Set Up Additional Binary Formats.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting Setup Virtual Console...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting Load Kernel Modules...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started File System Check on Root Device.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting Remount Root and Kernel File Systems...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd-modules-load[311]: libkmod: kmod_config_parse: /etc/modprobe.d/10-unsupported-modules.conf line 10: ignoring bad line starting with 'allow_unsupported_modules'
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd-modules-load[311]: Module 'loop' is already loaded
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Load Kernel Modules.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting Apply Kernel Variables...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Mounted Configuration File System.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Mounted FUSE Control File System.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started create /dev/root symlink with dynamic rule.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Apply Kernel Variables.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Create dynamic rule for /dev/root link.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting udev Kernel Device Manager...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started udev Kernel Device Manager.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd-udevd[335]: starting version 195
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started LSB: Set default boot entry if called.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started udev Coldplug all Devices.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Remount Root and Kernel File Systems.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting Load Random Seed...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting Local File Systems (Pre).
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Reached target Local File Systems (Pre).
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Load Random Seed.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: EXT4-fs (sda2): re-mounted. Opts: acl,user_xattr
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: ACPI: Power Button [PWRB]
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: ACPI: Sleep Button [SLPB]
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: ACPI: Power Button [PWRF]
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: parport_pc 00:08: reported by Plug and Play ACPI
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: parport0: PC-style at 0x378, irq 7 [PCSPP]
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: Floppy drive(s): fd0 is 1.44M
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: skge 0000:00:0a.0: PCI: Disallowing DAC for device
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: skge: 1.14 addr 0xfdf00000 irq 17 chip Yukon-Lite rev 7
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: skge 0000:00:0a.0 eth0: addr 00:11:d8:4d:be:ef
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: FDC 0 is a post-1991 82077
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: via_rhine: v1.10-LK1.5.0 2010-10-09 Written by Donald Becker
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: wmi: Mapper loaded
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: via-rhine 0000:00:0c.0 eth1: VIA Rhine III at 0xfdd00000, 00:11:95:83:bc:59, IRQ 17
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: via-rhine 0000:00:0c.0 eth1: MII PHY found at address 1, status 0x786d advertising 05e1 Link 41e1
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: pata_via 0000:00:0f.1: version 0.3.4
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: scsi2 : pata_via
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: [drm] Initialized drm 1.1.0 20060810
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: scsi3 : pata_via
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: MCE: In-kernel MCE decoding enabled.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen mtp-probe[361]: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:10.1/usb3/3-2"
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Started Setup Virtual Console.
    Apr 08 15:23:45 UsrFriendesktop.Lisheen systemd[1]: Starting udev Coldplug all Devices...
    Apr 08 15:23:45 UsrFriendesktop.Lisheen kernel: input: PC Speaker as /devices/platform/pcspkr/input/input5
    Apr 08 15:23:45 UsrFriendesktop.Lisheen mtp-probe[361]: bus: 3, device: 2 was not an MTP device
    Apr 08 15:23:45 UsrFriendesktop.Lisheen mtp-probe[362]:

  2. #52
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,564
    Blog Entries
    38

    Default Re: Welcome to emergency mode!

    Quote Originally Posted by peterichardavis View Post
    As I don't know how long it would take me to work out how to access and use SUsE Paste, and it doesn't seem to be considered outrageous,
    The 'code' method you used works well ! Thankyou for using that format.

    wrt SUSE Paste , it is incredibly easy, ... copy the content that you wish to post, ... paste into the 'your paste' box, optionally fill in the "author" and "title" name, and optionally change the default "delete after 1 week" to something a bit longer ... and then press "create". It gives you a URL where the new paste page has been created. Copy that URL. Post it here.

    Its intutive and simple.

    (but again - the code tags that you used also works VERY well - thankyou).

  3. #53
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Welcome to emergency mode!

    On 2013-04-08 17:36, peterichardavis wrote:

    > to have been successful in overcoming the problem with starting Show
    > Plymouth Boot Screen. In both cases, however, it only lasted one
    > session.


    So, you mean that you still have the problem with dumping to emergency mode?

    I'll assume the answer is affirmative. If negative, then ignore the rest
    of this post.


    Do you get any messages on the screen if you press "ESC" while the boot
    process is running, as you said on a previous message? I would like to
    see them, they should be illustrative. Make a photo if you can, with
    camera (better that hand typing). Post in in susepaste.org or elsewhere.


    > The error spotted by the Carlos' eagle eye was probably by me, not my
    > computer.


    Ah, ok.


    > As I don't know how long it would take me to work out how to access and
    > use SUsE Paste, and it doesn't seem to be considered outrageous, I'm
    > taking the liberty of posting some of my latest output from journalctl
    > -b here.


    I don't understand the problem you have with susepaste. I see oldcpu has
    given you some explanations about that. By all means, pasting here is
    fine, when done inside code tags. It's only when the text is large that
    we we suggest susepaste instead.

    > To fit into the character limit, I'm starting at the point
    > where the problems started before tsu2's recommendation, and curtailing
    > what follows. It still contains more errors and failures than I'd wish:


    I'm not enough acquainted with systemd verbosity to understand all it
    says. The section that interests me is at the start - I'll delete the rest:

    Code:
    
    > --------------------
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Show Plymouth Boot Screen.
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch.
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start timed out.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for /windows/E.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Local File Systems.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Remote File Systems (Pre).
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job remote-fs-pre.target/start failed with result 'dependency'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job local-fs.target/start failed with result 'dependency'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job windows-E.mount/start failed with result 'dependency'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start failed with result 'timeout'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Unmounted /home.
    And I'll also paste your fstab for easier comparison:

    Code:
    
    >     /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part5 swap                 swap       defaults              0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part2 /                    ext4       acl,user_xattr        1 1
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part6 /home                ext3       defaults              1 2
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part1 /windows/C           ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8 0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part7 /windows/D           ntfs-3g    users,gid=users,fmask=337,dmask=007,locale=en_GB.UTF-8 0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part8 /windows/E           ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8 0 0
    >   proc                 /proc                proc       defaults              0 0
    >   sysfs                /sys                 sysfs      noauto                0 0
    >   debugfs              /sys/kernel/debug    debugfs    noauto                0 0
    >   usbfs                /proc/bus/usb        usbfs      noauto                0 0
    >   devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

    Now, does the phrase "Dependency failed for /windows/E" means that
    "/windows/E" failed, or that something that it needs failed previously?
    The message just above it has to be important: "Timed out waiting for
    device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device."

    That's the identifier for "/windows/E".

    Then it says "Unmounted /home". Why? Did "/home" fail, or is it some
    thing that emergency mode does because it is in a list of things to do
    when in emergency? I think the later.

    My guess, and it is only an educated guess, is that there is some
    problem with mounting /windows/E. I have no idea what.

    I only have a suggestion, a temporary change - edit "/etc/fstab" (please
    use "joe", it is easier), and change that line thus:

    Code:
    
    >>  # /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part8 /windows/E           ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8 0 0
    That is, comment out the line writing a '#' in front. The system will
    not attempt to mount "/windows/E". The idea is not to have it permanent,
    I just want to know if that is the cause of dropping into emergency
    mode. It is a diagnostic, not a solution.

    And then tell us the results.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.1 x86_64 "Asparagus" at Telcontar)

  4. #54

    Default Re: Welcome to emergency mode!

    Quote Originally Posted by tsu2 View Post
    @AlmostAWhisper - I very much welcome you to participate as much as you would like in these Forums. Everyone will make mistakes and I can point to many erroneous posts I've made over the years. I would also suggest that when you post your recommendations in the future to describe how you came to your recommendation if the problem is complex like this one.

    And i apologize for coming down hard on something I recognize is likely an honest mistake but also based on simple mis-interpretation and not completely without basis... And, if it should be shown that I am even more incorrect that the OP's system actually is making progress then i'm sure I'm due for an even bigger apology.
    Hi TSU,

    Thank you very much to welcome my participation in these Forums! I feel quite confident when I‘m here whatever reading or writing, because I'm a user of openSUSE and I know exactly that openSUSE Forums are our all users' ones not someone's own property. When I had problems I would go over here automatically to find solutions, suggestions or some tips or some users who had the same or similar problems. And I saw many people here are ready to do their best to help others very friendly. I often got some helps directly or indirectly. I'm very thankful to them and to the openSUSE Forums as well for offering this platform. It goes without saying that I would like to share my experiences with others to help them solve the same or similar problems someday in return.

    Thank you for your suggestion to describe more details when I post recommendations. As I posted my suggestions I thought the user is terribly waiting for a solution. The suggestions are my own experiences and they worked very well in my machine. The description of the recommendations may come later when necessary. BTW, thank you very much for your message! I appreciate the way you deal with things like that. I didn't mean to offend you but if I did
    it unintentionally I apologize!

    Quote Originally Posted by tsu2 View Post
    First,
    I'll back off decrying that no evidence existed which suggested that any Windows/E partition recommendations came out of left field and was completely without basis. I will merely suggest it's <likely> (yes, I won't state in absolute terms) that you only mis-interpreted the information.

    To support my interpretation, I believe it's necessary for the OP to restate and clarify that with his original post (and subject line) that he has always been booting to emergency mode from the beginning, and any modifications to the Windows /E partition has been ineffective in fixing his basic problem... He's not booting into Normal mode.

    I'd also ask any reader of this Thread to think a bit about what the effect of a NTFS (Windows) partition not mounting with how a Linux system boots. If you look at a working Linux system, it should not be any surprise that no part of a working Linux system is mounted on NTFS, so if it fails so what? It shouldn't affect how a Linux system boots.

    As for the error relating to unable to start Plymouth, that jumps out at me mainly because I've spent plenty of time troubleshooting a system that fails at exactly that point and know its consequences... Which can be what the OP described.

    And, because I have been troubleshooting almost exactly the same type of problem i've spent considerable time trying to understand exactly what is happening on a system during this critical juncture when GRUB hands off to the OS proper, so I can describe concrete steps to gathering information about a problem experienced at this point in the boot process (see my bugzilla which describes in excruciating detail the many commands and logfiles I gathered and submitted for analysis).
    First, Is an interpretation also a guess? Yes, I think so and I believe that learning by practicing, trying, guessing, speculating and interpreting is a scientific approach towards solving problems. You can do it and I too. A suggestion or a workaround in our forums is more practical than theoretical, IMHO. A simplest solution, for example, a parameter or a code line, is the best solution even for a problem of complex, IMO. The criteria of a good solution is that by using it a problematic system gets rescued and functions again. All in all, it works!

    Second, I read the thread again carefully from the first post to my first two posts and didn't find anything to do with windows/E partition. The topic of the thread is
    Quote Originally Posted by peterichardavis View Post
    Since upgrading to openSUSE 12.3 (Dartmouth) (x86_64) with Linux 3.7.10-1.1-desktop and KDE 4.10.00 "release1" on an AMD Athlon 64 Processor 3200+, I usually boot into emergency mode! I don't think systemctl has ever failed me, but would be glad to escape this diversion, so would be grateful to anybody who can understand the following system boot log and advise me what I have to do to return to normal
    Or a short but much clear version:
    Quote Originally Posted by arvidjaar View Post
    We are discussing the case when system drops into emergency mode as result of boot time error.
    As I saw this thread I thought I could do something based on my own experience to help peterichardavis to get rid of the emergency mode. Therefore I gave my two suggestions.

    You might have misunderstood or misinterpreted the information of the thread or I might have misunderstood or misinterpreted your comments. I didn't find any relation with your comments on my suggestions in the post (#35) and I don't know why you always combined the emergency mode with windows/E partition together. I'm quite sure this is a wrong direction. peterichardavis has Windows and openSUSE dual boot. I have just openSUSE 12.3 on my computer. Both, however, landed in the emergency mode. That means the situation has nothing to do with Windows partitions. The information about Windows partition/E is just a superficial phenomenon and there must be something more essential behind. The problem must lie in the /home partition, IMHO. I also commented this somewhere in Bugzilla. If you want to continue just uncomment all lines with windows partitions in the fstab file and dig in. If you want to do a systematic research my suggestion were to check the change of systemd between openSUSE 12.3 RC1 and final release to find parts including /home partition, IMHO.

  5. #55
    Join Date
    Sep 2012
    Posts
    5,132

    Default Re: Welcome to emergency mode!

    Quote Originally Posted by AlmostAWhisper View Post

    peterichardavis has Windows and openSUSE dual boot. I have just openSUSE 12.3 on my computer. Both, however, landed in the emergency mode.
    Show your logs then.

  6. #56

    Default Re: Welcome to emergency mode!

    I seem to be sliding downhill faster than I'm climbing at the moment.
    Quote Originally Posted by robin_listas View Post
    you mean that you still have the problem with dumping to emergency mode?
    Yes

    Quote Originally Posted by robin_listas View Post
    I would like to
    see them, they should be illustrative. Make a photo if you can, with
    camera (better that hand typing). Post in in susepaste.org or elsewhere.
    I get a fairly steady flow of what appears to be my journal. I wasn't optimistic of photographing anything useful, because the lines between timing out and being dumped into emergency mode flash very briefly onto the screen. I did try, but found the camera more of a distraction than an aid.

    Quote Originally Posted by robin_listas View Post
    > As I don't know how long it would take me to work out how to access and
    > use SUsE Paste,


    I don't understand the problem you have with susepaste. I see oldcpu has
    given you some explanations about that.
    When I wrote that, I'd clicked on Login, and didn't know what OpenID meant, or what might follow. I still don't know what an OpenID is, but, following the kind intervention of oldcpu, tried posting without it, and found several more ways that didn't work than the one that did. The error messages I've seen are
    Code:
    openSUSE Paste > Error
    An Error Was Encountered
    You are spammer!!!
    and
    Code:
    openSUSE Paste > Error
    An Error Was Encountered
    Uploading failed!!!
    Only gif|jpg|png|jpeg|svg files smaller then 2048k are allowed for this time interval. Allowed file size depends on expiration time.
    The latter resulted from the one photograph I did succeed in taking, but never posting. I did find a way of posting the output of journalctl -b.

    Quote Originally Posted by robin_listas View Post
    The section that interests me is at the start - I'll delete the rest:

    Code:
    
    > --------------------
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Show Plymouth Boot Screen.
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch.
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
    >   Apr 08 15:22:00 UsrFriendesktop.Lisheen systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start timed out.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for /windows/E.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Local File Systems.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Remote File Systems (Pre).
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job remote-fs-pre.target/start failed with result 'dependency'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job local-fs.target/start failed with result 'dependency'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job windows-E.mount/start failed with result 'dependency'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start failed with result 'timeout'.
    >   Apr 08 15:22:57 UsrFriendesktop.Lisheen systemd[1]: Unmounted /home.
    Now, does the phrase "Dependency failed for /windows/E" means that
    "/windows/E" failed, or that something that it needs failed previously?
    The message just above it has to be important: "Timed out waiting for
    device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device."

    Then it says "Unmounted /home". Why? Did "/home" fail, or is it some
    thing that emergency mode does because it is in a list of things to do
    when in emergency? I think the later.

    My guess, and it is only an educated guess, is that there is some
    problem with mounting /windows/E.

    I only have a suggestion, a temporary change - edit "/etc/fstab" ), and change that line thus:

    Code:
    
    >>  # /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part8 /windows/E           ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8 0 0
    I agree that "joe" is easier, and followed your suggestion. As seems to be standard procedure, my next boot seemed normal. I could see windows/E in Dolphin but not access the partition. The boot journal is at SUSE Paste, and shows that Dependency failed for /windows/D! As the colours in my Konsole don't show in SUSE Paste, I've noted that lines 664-7, 871, 874, 893-4, 911, 839-42, 1210, 1262, 1335-6, 1339, 1342, 1362-5, 1367-8 and 1372 are all red. The lines that have attracted interest in the past are:
    Code:
    Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Started Show Plymouth Boot Screen.
    Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch.
    Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
    Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart7.device/start timed out.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart7.device.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for /windows/D.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Local File Systems.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Remote File Systems (Pre).
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Job remote-fs-pre.target/start failed with result 'dependency'.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Job local-fs.target/start failed with result 'dependency'.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Job windows-D.mount/start failed with result 'dependency'.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart7.device/start failed with result 'timeout'.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Unmounted /home.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped File System Check on /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part6.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping Local File Systems (Pre).
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped target Local File Systems (Pre).
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped Stop Read-Ahead Data Collection 10s After Completed Startup.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Coldplug all Devices...
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped Permit User Sessions.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped Trigger Flushing of Journal to Persistent Storage.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd-journal[219]: Journal stopped
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd-journal[287]: Allowing runtime journal files to grow to 100.3M.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Starting Emergency Shell...
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Started Emergency Shell.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Starting Emergency Mode.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Reached target Emergency Mode.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped udev Kernel Device Manager.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping Create dynamic rule for /dev/root link...
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped Create dynamic rule for /dev/root link.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping create /dev/root symlink with dynamic rule...
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped create /dev/root symlink with dynamic rule.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Kernel Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Closed udev Kernel Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Control Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Closed udev Control Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Kernel Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Closed udev Kernel Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopping udev Control Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Closed udev Control Socket.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Starting Journal Service...
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped Collect Read-Ahead Data.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd-journald[219]: Received SIGTERM
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Starting Journal Service...
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Started Journal Service.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd-journal[287]: Journal started
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Stopped LSB: Set default boot entry if called.
    Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Startup finished in 6s 87ms 503us (kernel) + 1min 31s 189ms 740us (userspace) = 1min 37s 277ms 243us.
    Because I need access to E, and wanted to continue the experiment, I moved the hash up a line to /windows/D. The next time I booted I was dumped into emergency mode, but with a new variation in which the printout jumped to the top of the screen. I couldn't access D, but the Dependency failed for /windows/E, which I could! Moreover, when I tried to move a dialogue box, the screen went blank and started flashing the one printout that I did photograph, adding a line each time about failing to idle channel. The corresponding journal is at SUSE Paste. If it would help, I can tell you which lines are red in Konsole. The photograph shows a selection of lines from the journal, adding a few as shown:
    Code:
    Reached target Local File Systems (Pre).
    Mounting Runtime Directory...
    Mounting Lock Directory...
    Mounting /sys/kernel/debug...
    Mounted Lock Directory.
    Mounted /sys/kernel/debug.
    Mounted Runtime Directory.
    Started Load Random Seed.
    The lines that have attracted interest in the past are:
    Code:
    Apr 09 21:51:59 UsrFriendesktop.Lisheen systemd[1]: Started Show Plymouth Boot Screen.
    Apr 09 21:51:59 UsrFriendesktop.Lisheen systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch.
    Apr 09 21:51:59 UsrFriendesktop.Lisheen systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
    Apr 09 21:51:59 UsrFriendesktop.Lisheen systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start timed out.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for /windows/E.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Local File Systems.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Remote File Systems (Pre).
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Job remote-fs-pre.target/start failed with result 'dependency'.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Job local-fs.target/start failed with result 'dependency'.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Job windows-E.mount/start failed with result 'dependency'.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart8.device/start failed with result 'timeout'.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Unmounted /home.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Stopped LSB: Framebuffer setup.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Stopped Haveged Entropy Gathering Daemon.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Stopped ACPI Event Daemon.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Stopped D-Bus System Message Bus.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Stopped Command Scheduler.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd-journal[221]: Journal stopped
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd-journal[289]: Allowing runtime journal files to grow to 100.3M.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Starting Emergency Shell...
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Started Emergency Shell.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Starting Emergency Mode.
    Apr 09 21:52:56 UsrFriendesktop.Lisheen systemd[1]: Reached target Emergency Mode.
    The end looks like the sort of thing of which tsu2 may have experience, and to escape it I crashed the computer. The next day I was back to the failure of Show Plymouth Boot Screen, as shown at SUSE Paste.
    Today Show Plymouth Boot Screen started again, but I was still dumped. I suppose my next step is to try AlmostAWhisper's suggestion to comment out all Windows partitions in my fstab.
    Peter

  7. #57
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Welcome to emergency mode!

    On 2013-04-11 10:16, peterichardavis wrote:
    >
    > I seem to be sliding downhill faster than I'm climbing at the moment.
    >
    > robin_listas;2545815 Wrote:
    >> you mean that you still have the problem with dumping to emergency mode?

    >
    > Yes


    Oh:-(


    > robin_listas;2545815 Wrote:
    >> I would like to
    >> see them, they should be illustrative. Make a photo if you can, with
    >> camera (better that hand typing). Post in in susepaste.org or
    >> elsewhere.

    >
    > I get a fairly steady flow of what appears to be my journal. I wasn't
    > optimistic of photographing anything useful, because the lines between
    > timing out and being dumped into emergency mode flash very briefly onto
    > the screen. I did try, but found the camera more of a distraction than
    > an aid.


    I want to try on a virtual machine to install 12.3 and experiment with
    emergency mode. My direct experience is with older versions, in 12.3 I'm
    learning as I try to help. It is very difficult to help someone at a
    distance without having access to the machine to look and do things.

    Sorry :-(


    > robin_listas;2545815 Wrote:
    >>
    >> I don't understand the problem you have with susepaste. I see oldcpu has
    >> given you some explanations about that.

    >
    > When I wrote that, I'd clicked on Login, and didn't know what OpenID
    > meant, or what might follow. I still don't know what an OpenID is, but,
    > following the kind intervention of oldcpu, tried posting without it, and
    > found several more ways that didn't work than the one that did. The
    > error messages I've seen are


    I don't know what openid is, either. I would like to know, too.


    > Code:
    > --------------------
    > openSUSE Paste > Error
    > An Error Was Encountered
    > You are spammer!!!
    >
    > --------------------


    Yes, it happens to some people :-(
    An alternative is "pastebin.com" instead. There are several such sites,
    the wikipedia lists a few.


    >
    > and
    >
    > Code:
    > --------------------
    > openSUSE Paste > Error
    > An Error Was Encountered
    > Uploading failed!!!
    > Only gif|jpg|png|jpeg|svg files smaller then 2048k are allowed for this time interval. Allowed file size depends on expiration time.
    >
    > --------------------


    Yes, the larger the photo is, the shorter the time you are allowed to
    publish. You have to compress the photo more: for example, I have my
    camera setup to low compression for high quality, so photos have 5 megs
    or more. So I open up gimp and make a very compressed jpg copy at about
    0.5MiB - there is a slide rule that allows you to adjust the quality
    (click the show preview) while it calculates the estimated file size.


    > robin_listas;2545815 Wrote:

    ....
    >> My guess, and it is only an educated guess, is that there is some
    >> problem with mounting /windows/E.
    >>
    >> I only have a suggestion, a temporary change - edit "/etc/fstab" ),
    >> and change that line thus:
    >>
    >>>

    > Code:
    > --------------------
    > > >
    > > >> # /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part8 /windows/E ntfs-3g users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8 0 0

    > >

    > --------------------
    >>>

    >
    > I agree that "joe" is easier, and followed your suggestion. As seems
    > to be standard procedure, my next boot seemed normal. I could see
    > windows/E in Dolphin but not access the partition.


    Yes, that would be normal.
    But if the system doesn't go to emergency mode, we found something.

    > The boot journal is
    > at 'SUSE Paste' (http://paste.opensuse.org/52964039), and shows that
    > Dependency failed for /windows/D!


    Arghh! :-(

    > As the colours in my Konsole don't
    > show in SUSE Paste, I've noted that lines 664-7, 871, 874, 893-4, 911,
    > 839-42, 1210, 1262, 1335-6, 1339, 1342, 1362-5, 1367-8 and 1372 are all
    > red. The lines that have attracted interest in the past are:


    Lets have a look at them.

    Code:
    
    > Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart7.device.
    > Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for /windows/D.
    > Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Local File Systems.
    > Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Remote File Systems (Pre).
    
    > Apr 09 15:23:39 UsrFriendesktop.Lisheen systemd-udevd[398]: error changing net interface name eth0 to eth1: File exists
    > Apr 09 15:23:39 UsrFriendesktop.Lisheen systemd[1]: Found device ST3160827AS.
    > Apr 09 15:23:39 UsrFriendesktop.Lisheen systemd[1]: Activating swap /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part5...
    > Apr 09 15:23:39 UsrFriendesktop.Lisheen systemd-udevd[399]: error changing net interface name eth1 to eth0: File exists
    
    
    > Apr 09 15:23:40 UsrFriendesktop.Lisheen systemd-udevd[374]: error changing net interface name eth0 to eth1: File exists
    > Apr 09 15:23:40 UsrFriendesktop.Lisheen systemd-udevd[372]: error changing net interface name eth1 to eth0: File exists
    > Apr 09 15:23:40 UsrFriendesktop.Lisheen systemd[1]: Found device ST3160827AS.
    
    > Apr 09 15:23:40 UsrFriendesktop.Lisheen systemd[1]: Found device ST3160827AS.
    > Apr 09 15:23:40 UsrFriendesktop.Lisheen systemd[1]: Mounting /windows/D...
    
    > Apr 09 15:24:18 UsrFriendesktop.Lisheen systemd[1]: network.service: control process exited, code=exited status=7
    > Apr 09 15:24:18 UsrFriendesktop.Lisheen systemd[1]: Failed to start LSB: Configure network interfaces and set up routing.
    > Apr 09 15:24:18 UsrFriendesktop.Lisheen systemd[1]: Unit network.service entered failed state
    > Apr 09 15:24:18 UsrFriendesktop.Lisheen systemd[1]: Starting Network.
    > Apr 09 15:24:18 UsrFriendesktop.Lisheen systemd[1]: Reached target Network.
    >
    > Apr 09 15:24:30 UsrFriendesktop.Lisheen kdm_config[4237]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc
    >
    > Apr 09 15:26:12 UsrFriendesktop.Lisheen pulseaudio[4764]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
    > Apr 09 15:26:47 UsrFriendesktop.Lisheen hp-systray[4887]: hp-systray[4887]: error: option -s not recognized
    >
    > Apr 09 15:26:47 UsrFriendesktop.Lisheen rtkit-daemon[4765]: Successfully made thread 4934 of process 4934 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
    > Apr 09 15:26:47 UsrFriendesktop.Lisheen rtkit-daemon[4765]: Supervising 5 threads of 2 processes of 1 users.
    
    > Apr 09 15:35:57 UsrFriendesktop.Lisheen systemd-tmpfiles[5813]: stat(/run/user/1000/gvfs) failed: Permission denied
    
    > Apr 09 15:35:57 UsrFriendesktop.Lisheen systemd-tmpfiles[5813]: stat(/run/user/1000/gvfs) failed: Permission denied

    I see something interesting, the line about "Found device ST3160827AS"
    about a minute later that the line that said that /windows/D failed. Is
    that disk the same one as the one where Linux is? External disk, perhaps?

    Hum, no, it is the same disk, looking at fstab entries...

    The lines about the network I don't know if they are important or not.
    Let's ignore the ones about pulseaudio, kdm config, etc, at least for
    now. The permission denied on gvfs is a known "problem", just ignore it.


    Code:
    
    > --------------------
    >   Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Started Show Plymouth Boot Screen.
    >   Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch.
    >   Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
    >   Apr 09 15:21:34 UsrFriendesktop.Lisheen systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    >   Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Job dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart7.device/start timed out.
    >   Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Timed out waiting for device dev-disk-by\x2did-ata\x2dST3160827AS_4MT0BNMF\x2dpart7.device.
    >   Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for /windows/D.
    >   Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Local File Systems.
    >   Apr 09 15:22:31 UsrFriendesktop.Lisheen systemd[1]: Dependency failed for Remote File Systems (Pre).
    > --------------------

    > Because I need access to E, and wanted to continue the experiment, I
    > moved the hash up a line to /windows/D. The next time I booted I was
    > dumped into emergency mode, but with a new variation in which the
    > printout jumped to the top of the screen. I couldn't access D, but the
    > Dependency failed for /windows/E, which I could!


    Strange. I'm starting to think that there is some problem with that
    entire disk.

    > Moreover, when I tried
    > to move a dialogue box, the screen went blank and started flashing the
    > one printout that I did photograph, adding a line each time about
    > failing to idle channel.


    Oh. Video problem o top? :-? :-(

    > The corresponding journal is at 'SUSE Paste'
    > (http://paste.opensuse.org/72154599). If it would help, I can tell you
    > which lines are red in Konsole. The photograph shows a selection of
    > lines from the journal, adding a few as shown:
    >
    > Code:
    > --------------------
    > Reached target Local File Systems (Pre).
    > Mounting Runtime Directory...
    > Mounting Lock Directory...
    > Mounting /sys/kernel/debug...
    > Mounted Lock Directory.
    > Mounted /sys/kernel/debug.
    > Mounted Runtime Directory.
    > Started Load Random Seed.
    > --------------------


    Nothing there, I believe.


    > The lines that have attracted interest in the past are:

    ....

    > The end looks like the sort of thing of which tsu2 may have experience,
    > and to escape it I crashed the computer. The next day I was back to the
    > failure of Show Plymouth Boot Screen, as shown at 'SUSE Paste'
    > (http://paste.opensuse.org/56953262).


    About plymouth problems I know next to nothing, sorry.



    > Today Show Plymouth Boot Screen started again, but I was still dumped.
    > I suppose my next step is to try AlmostAWhisper's suggestion to comment
    > out all Windows partitions in my fstab.


    No, he doesn't. He said:

    ]> Second, I read the thread again carefully from the first post to my
    ]> first two posts and didn't find anything to do with windows/E partition.

    He suggested a change to the /home line, and incorrect at that (it has
    an extra space, a syntax error).


    You can try something else, instead - this is your fstab file, taken
    from a previous post:

    Code:
    
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part5 swap                 swap       defaults              0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part2 /                    ext4       acl,user_xattr        1 1
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part6 /home                ext3       defaults              1 2
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part1 /windows/C           ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8 0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part7 /windows/D           ntfs-3g    users,gid=users,fmask=337,dmask=007,locale=en_GB.UTF-8 0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part8 /windows/E           ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8 0 0
    >   proc                 /proc                proc       defaults              0 0
    >   sysfs                /sys                 sysfs      noauto                0 0
    >   debugfs              /sys/kernel/debug    debugfs    noauto                0 0
    >   usbfs                /proc/bus/usb        usbfs      noauto                0 0
    >   devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
    > --------------------
    I would try modifying the windows lines like this:


    Code:
    
    >   #/dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part1 /windows/C     ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8  0 0
    >   #/dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part7 /windows/D     ntfs-3g    users,gid=users,fmask=337,dmask=007,locale=en_GB.UTF-8  0 0
    >   #/dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part8 /windows/E     ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8  0 0
    Or:

    Code:
    
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part1 /windows/C      ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8,nofail  0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part7 /windows/D      ntfs-3g    users,gid=users,fmask=337,dmask=007,locale=en_GB.UTF-8,nofail  0 0
    >   /dev/disk/by-id/ata-ST3160827AS_4MT0BNMF-part8 /windows/E      ntfs-3g    users,gid=users,fmask=117,dmask=007,locale=en_GB.UTF-8,nofail  0 0

    The first version is just to test if booting works without dumping into
    emergency mode. If that works, then the second version will also work -
    however...

    What the second line does (notice that 'nofail' is separated by a comma,
    not a space, as explained in "man fstab") is that in case that the
    system fails to mount that partition, it will continue without giving
    you an error. Silently. You may notice because boot will be slow while
    the system tries.

    The "/windows/X" folders will be there, but empty (if mount failed at
    boot). However, you can at that moment issue commands like this in a
    terminal:

    Code:
    mount -v /windows/C
    ls /windows/C
    If the command succeeds, you get access to the partition. If it fails,
    post it here, maybe it says why. Repeat for 'D' and 'E' as needed.

    If the command fails silently, there maybe a reason recorded in the
    logs. I would try looking a the end of the file "/var/log/messages"


    One thing you can also try is boot Windows, and tell it to verify all
    the Windows "disks". Linux can not mount an NTFS partition with
    problems, and can not repair them either. I would expect a message about
    that problem, though, and I do not see it.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 12.1 x86_64 "Asparagus" at Telcontar)

  8. #58

    Default Re: Welcome to emergency mode!

    Quote Originally Posted by arvidjaar View Post
    Show your logs then.
    Which ones do you need? boot.log?

  9. #59
    Join Date
    Sep 2012
    Posts
    5,132

    Default Re: Welcome to emergency mode!

    Quote Originally Posted by peterichardavis View Post
    The boot journal is at SUSE Paste,
    The immediate problem is that device coldplug is run before udevd is started, so coldplug events are lost and disk aliases never appear:
    Code:
    Apr 09 21:51:28 UsrFriendesktop.Lisheen systemd[1]: Starting udev Coldplug all Devices...
    Apr 09 21:51:28 UsrFriendesktop.Lisheen systemd[1]: Started udev Coldplug all Devices.
    ...
    Apr 09 21:51:29 UsrFriendesktop.Lisheen systemd[1]: Starting udev Kernel Device Manager...
    Apr 09 21:51:29 UsrFriendesktop.Lisheen systemd[1]: Started udev Kernel Device Manager.
    Apr 09 21:51:29 UsrFriendesktop.Lisheen systemd-udevd[271]: starting version 195
    But your log is extremely weird. Services are started out of order and multiple times. Is it new clean installation or update?

  10. #60
    Join Date
    Sep 2012
    Posts
    5,132

    Default Re: Welcome to emergency mode!

    Quote Originally Posted by AlmostAWhisper View Post
    Which ones do you need?
    Did you read previous pages? Output of "journalctl -b" after system drops into emergency mode.

Page 6 of 8 FirstFirst ... 45678 LastLast

Tags for this Thread

Posting Permissions

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