Member Avatar for frickinaj

I just built my first computer, with some help from everyone on the hardware forums. Now, I'm trying to install some derivation of Linux. I tried installing Debian with the net-install, but everyone I try to it tells me my CD is corrupted.

After trying 3 different Debian cd's, i decided to try and install Ubuntu. It goes a little smoother than the Debian install, until it goes to "running Boot Scripts", where it finishes that and stops. Anybody know what the problem might be? I've installed Ubuntu on a computer that already had windows on it, installing a second hard for Linux, but never on a self-build PC.

  • 4 Contributors
  • 4 Replies
  • 136 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

Short summary and practical steps for the hang at "running Boot Scripts" (build-new-PC, Debian/Ubuntu installs): the message appears while the installer runs init scripts; common root causes include corrupted media, device/driver failures (storage, optical, or video), or BIOS settings that interfere with the installer. The replies from and point toward hardware and BIOS as likely vectors; the checklist below adds concrete diagnostics and workarounds.

Verify image and media

  • Confirm the ISO checksum against the official Ubuntu releases (see Ubuntu releases).
  • Prefer a USB installer over a burned CD. Example (careful to use the correct target device):
    sudo dd if=ubuntu-XX.YY.iso of=/dev/sdX bs=4M status=progress && sync
  • If using optical media, burn at the slowest reliable speed and verify the disc on a second machine.

Capture installer logs and live diagnostics

  • Switch to another virtual console during the hang (Ctrl+Alt+F2..F6) and inspect kernel and installer logs:
    dmesg | tail -n 100
sudo tail -n 200 /var/log/syslog
sudo less /var/log/installer/syslog
  • These logs usually show the failing module or device.

Quick boot-time workarounds

  • Add kernel options at the boot prompt if the hang appears just after kernel load: nomodeset, acpi=off, noapic, irqpoll, or libata.force=noncq (one at a time, for testing). nomodeset is commonly effective for video-related freezes.
  • Try the Alternate/Server (text-mode) installer or the Live "Try Ubuntu" session to isolate GUI vs core-install issues.

Hardware and BIOS checks

  • Run memtest86+ from the boot menu to rule out RAM errors.
  • Inspect BIOS/UEFI for SATA mode (AHCI/IDE/Compat), any drive-protection or security features, and temporary-disable features that might block bootloader or disk access.

If the installer logs show specific driver/module failures, those messages give the best next step (module blacklisting, different kernel option, or trying a different installer image).

Recommended Answers

All 4 Replies

Member Avatar for Stylish

I had similar problems on an old computer. Turns out, I had a bad cd-rom drive or a bad IDE2 connector on the motherboard or a bad BIOS. I never really isolated the problem. I got a minimal debian net install to succeed and then the onboard NIC toasted itself somehow and I scrapped it.

If you are having consistent cd-related issues, you may consider looking at your hardware or the source of your install cds.

Member Avatar for jbennet

Check that you have Bootsector/MBR Antovirus protection OFF in the BIOS. It prevents the bootloader being written to the MBR.

Member Avatar for hari001

Hi,

I am newbie in this forum. Ubuntu is most powerful version of the Linux. It is developed by the most popular company HCL.
I would like to know more about it.

Jimmy

<snip> Fake signature removed. Please check the rules about advertising </snip>

Member Avatar for jbennet

Banned.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.