ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Topics
    2. Tags
    3. boot issue
    Log in to post
    • All categories
    • 1

      What is this?

      Watching Ignoring Scheduled Pinned Locked Moved Solved IT Discussion boot issue uefi
      6
      1 Votes
      6 Posts
      656 Views
      M

      Is this an onboard controller or an external? A typical external RAID controller (and some internal) have a BIOS that loads on POST which may show you whether it's active or not.
      Otherwise, most BIOS post messages display the IRQ info of onboard components during boot so you should technically see a SATA/SAS/RAID controller there.

      I'd suspect the drive or corrupt boot loader first.

      What OS is this?

    • JaredBuschJ

      Fedora 29 Cinnamon booting slow

      Watching Ignoring Scheduled Pinned Locked Moved Solved IT Discussion fedora 29 cinnamon slow boot issue
      7
      0 Votes
      7 Posts
      680 Views
      JaredBuschJ

      74905B6F-0A48-4495-B22B-98F0AC666E19.jpeg
      CF0F63DD-CC12-4F71-A1EE-17F4E928B0E5.jpeg
      C3BEA56B-8D3D-47CC-8519-793A9F6CF07A.jpeg

    • gjacobseG

      Windows 10 / Fedora: Repair Dual boot

      Watching Ignoring Scheduled Pinned Locked Moved IT Discussion windows windows 10 fedora boot issue mbr dual boot
      5
      0 Votes
      5 Posts
      916 Views
      momurdaM

      @gjacobse https://sourceforge.net/projects/supergrub2/files/2.02s9/super_grub2_disk_2.02s9/super_grub2_disk_hybrid_2.02s9.iso/download

    • DashrenderD

      Windows Server 2003 P2V adventures

      Watching Ignoring Scheduled Pinned Locked Moved IT Discussion p2v windows server 2003 black screen boot issue
      60
      0 Votes
      60 Posts
      9k Views
      DashrenderD

      Considering the solution - I have been thinking for several days that perhaps this issue stemmed from a problem with the disk on the original system. It might be slightly damaged - somehow not enough to prevent it from booting, but enough to cause the seen issues in the clonezilla image.

      If I cared, I could run chkdsk /r on the system a few times, then take a clonezilla image again, and then try restoring that.

      meh.

    • 1 / 1