Page 1 of 3 123 LastLast
Results 1 to 10 of 22

Thread: LiveCd crash at systemd

  1. #1

    Default LiveCd crash at systemd

    Hello there, I'm trying to run Tumbleweed live on my usb drive sadly after 3-5 minutes of booting screen (after I choose if I want to open the os or recovery) it crashes, gives me the input:
    Code:
    [   3.013124] Coudn't get size: 0x8(a lot of 0's)e
    [   3.013164] MODSIGN: Couldn't get UEFI db list
    [   3.013124] Coudn't get size: 0x8(a lot of 0's)e
    [   3.013124] Coudn't get size: 0x8(a lot of 0's)e
    Then it tells things like there is a report text file and I should reboot my system, after that it just sends me to systemd terminal.

    My Computer has gtx1070, i7 and 16gigs of ddr4 ram. And normally runs win10x64.
    The tumbleweed live iso file I downloaded was for x86_x64 and had KDE, although I also tried with gnome, which gave me the same result.
    The usb was formatted as FAT32.

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    13,631
    Blog Entries
    3

    Default Re: LiveCd crash at systemd

    Quote Originally Posted by xanrer View Post
    Hello there, I'm trying to run Tumbleweed live on my usb drive sadly after 3-5 minutes of booting screen (after I choose if I want to open the os or recovery) it crashes, gives me the input:
    Code:
    [   3.013124] Coudn't get size: 0x8(a lot of 0's)e
    [   3.013164] MODSIGN: Couldn't get UEFI db list
    [   3.013124] Coudn't get size: 0x8(a lot of 0's)e
    [   3.013124] Coudn't get size: 0x8(a lot of 0's)e
    Those messages are not important. If it is really crashing, then the crash happens after that, and is not related. You can safely ignore those messages.

    Then it tells things like there is a report text file and I should reboot my system, after that it just sends me to systemd terminal.
    That's the part that might have more useful information about your problem. Can you provide a little detail about what it says?

    My Computer has gtx1070, i7 and 16gigs of ddr4 ram. And normally runs win10x64.
    Possibly that nvidia card is the problem. Can you add "nomodeset" to the kernel boot line? Perhaps that will get you booted.

    When you get to the boot menu, hit 'e'. That should give you an edit screen.

    Scroll down until you find a line that starts "linux" or "linuxefi".
    Hit the END key to get to the end of that line. Enter "nomodeset" (perhaps with a preceding space to separate from other parameters).

    Then hit CTRL-X to resume booting.
    openSUSE Leap 15.2 RC; KDE Plasma 5.18.5;

  3. #3

    Default Re: LiveCd crash at systemd

    Quote Originally Posted by nrickert View Post
    Those messages are not important. If it is really crashing, then the crash happens after that, and is not related. You can safely ignore those messages.


    That's the part that might have more useful information about your problem. Can you provide a little detail about what it says?


    Possibly that nvidia card is the problem. Can you add "nomodeset" to the kernel boot line? Perhaps that will get you booted.

    When you get to the boot menu, hit 'e'. That should give you an edit screen.

    Scroll down until you find a line that starts "linux" or "linuxefi".
    Hit the END key to get to the end of that line. Enter "nomodeset" (perhaps with a preceding space to separate from other parameters).

    Then hit CTRL-X to resume booting.
    Hmm adding that gave me these:



    (sorry for the dramatic, stock image site angle on that second photo)
    Then the usual message.
    Also how do we get the .txt file? i tried to copy using "cp (report files name).txt sdb1"
    Since that didn't do anything i tried to find where the file is located with "ls ~/" and learned that we can't do that in this shell. As you see, i am quite new in this stuff.

  4. #4
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    13,631
    Blog Entries
    3

    Default Re: LiveCd crash at systemd

    The first image doesn't have much that is useful. The "device not accepting address" might be a problem. All of the other lines can usually be ignored.

    The second image suggests that you are actually in a dracut shell. So there is something about your hardware that the system does not like, and it did not complete booting.

    Sorry, I don't see any mention of a txt file -- I guess if is off the edge of the image.

    I don't have any experience using the dracut shell. I'll wait and see if someone else can add further help.
    openSUSE Leap 15.2 RC; KDE Plasma 5.18.5;

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    12,151
    Blog Entries
    2

    Default Re: LiveCd crash at systemd

    IMO all of what you posted are signs of a failed UEFI boot, specifically unable to boot to a USB drive.

    Follow the instructions in the following article (written for booting into MINT, but the important and relevant steps are what you have to do in Windows to boot to first disable Fastboot, and then to reboot to a USB drive (Windows must allow mounting the USB drive).

    https://www.lifewire.com/create-uefi...nt-usb-2202084

    That should take you down to the first part of "Step 03"
    The latter part of "Step 03" appears to be attempts to boot using commands which normally boot to an MBR system.
    In fact, rather than all the complications related to booting through UEFI,
    It's also possible to just switch to MBR in your Windows UEFI configuration (Yes, you will see warnings about possibly never again being able to boot to Windows again. You decide. I've never experienced a problem on several machines but the warning cannot be ingnored). And, then when you are finished experimenting with the LiveCDs, you should be able to switch back to re-enabling UEFI or just leave it booting to MBR. I know of only one quasi-theoretical exploit that attacks an MBR system, I haven't heard of any more.

    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  6. #6
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    13,631
    Blog Entries
    3

    Default Re: LiveCd crash at systemd

    Quote Originally Posted by tsu2 View Post
    IMO all of what you posted are signs of a failed UEFI boot, specifically unable to boot to a USB drive.
    He got past the stage where UEFI is relevant. Otherwise he would not be seeing those "dracut" lines.
    openSUSE Leap 15.2 RC; KDE Plasma 5.18.5;

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    12,151
    Blog Entries
    2

    Default Re: LiveCd crash at systemd

    Quote Originally Posted by nrickert View Post
    He got past the stage where UEFI is relevant. Otherwise he would not be seeing those "dracut" lines.
    There's more... like the Fastboot, and whether the @OP attempted to boot directly into the LiveCD or did the Windows reboot to mount the USB drive.

    All which may be required for success.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  8. #8

    Default Re: LiveCd crash at systemd

    Quote Originally Posted by nrickert View Post
    The first image doesn't have much that is useful. The "device not accepting address" might be a problem. All of the other lines can usually be ignored.

    The second image suggests that you are actually in a dracut shell. So there is something about your hardware that the system does not like, and it did not complete booting.

    Sorry, I don't see any mention of a txt file -- I guess if is off the edge of the image.

    I don't have any experience using the dracut shell. I'll wait and see if someone else can add further help.
    Ah the text file? yeah its called (something)sosreport.txt, it tells me to save that report file however i don't know how to copy it to my disk.

    IMO all of what you posted are signs of a failed UEFI boot, specifically unable to boot to a USB drive.

    Follow the instructions in the following article (written for booting into MINT, but the important and relevant steps are what you have to do in Windows to boot to first disable Fastboot, and then to reboot to a USB drive (Windows must allow mounting the USB drive).

    https://www.lifewire.com/create-uefi...nt-usb-2202084

    That should take you down to the first part of "Step 03"
    The latter part of "Step 03" appears to be attempts to boot using commands which normally boot to an MBR system.
    In fact, rather than all the complications related to booting through UEFI,
    It's also possible to just switch to MBR in your Windows UEFI configuration (Yes, you will see warnings about possibly never again being able to boot to Windows again. You decide. I've never experienced a problem on several machines but the warning cannot be ingnored). And, then when you are finished experimenting with the LiveCDs, you should be able to switch back to re-enabling UEFI or just leave it booting to MBR. I know of only one quasi-theoretical exploit that attacks an MBR system, I haven't heard of any more.

    HTH,
    TSU
    I did those on my bios actually, but i'll re-check, thank you.

  9. #9
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,866

    Default Re: LiveCd crash at systemd

    You say that the USB is FAT formatted. But it should not be after you have properly transferred the ISO. The iso is a boot ready image and should replace any FAT partitioning. You need to do an exact unmodified binary copy of the ISO to the USB device. NOT to a partition on the device.

  10. #10
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    12,151
    Blog Entries
    2

    Default Re: LiveCd crash at systemd

    Quote Originally Posted by xanrer View Post
    Ah the text file? yeah its called (something)sosreport.txt, it tells me to save that report file however i don't know how to copy it to my disk.



    I did those on my bios actually, but i'll re-check, thank you.
    Note that even if you make direct BIOS settings, you still can't boot directly to your LiveCD, you have to follow instructions exactly when you reboot from Windows.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Page 1 of 3 123 LastLast

Posting Permissions

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