Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

OS Not Booting Up

Aug 6, 2013 5:16AM PDT

I have a linux/ubuntu box I built in 2008 that doesn't want to boot up now. I took the HD out of it and put it in another box that I built a couple months ago. It'll boot up in that box, so I'm assuming it's going to be something wrong with the MOBO, or the CPU, maybe both. Is there a way to isolate it to find out what it is? Here's everything I have in it excluding the optical drives.

XFX MOBO, Intel Pentium D processor and a Seagate 500 GB HD.

Discussion is locked

- Collapse -
Answer
Look at how a shop approaches it.
Aug 6, 2013 5:23AM PDT

The tech looks it over for obvious burn or scorch marks, BAD CAPS (see google) and sees if it powers up. The better tech gets out the Volt meter to check the power supplies.

At that point they have found it or begin to swap out the part they suspect.
Bob

- Collapse -
Not A Tech
Aug 6, 2013 8:20AM PDT

I'm not a computer tech, I'm an HVAC technician. I just built these myself for my own personal use. Thanks for the advice, I'll check it out.

- Collapse -
Now you're a PC Tech.
Aug 6, 2013 8:47AM PDT

There are buckets of discussions about broken PCs and here's the bottom line. There is no exact process to fix a dead PC. Sure we could take the old swap it piece by piece approach but let's upgrade that a little.

1. Some parts are not needed to boot. A keyboard, CD/DVD drive, and then one stick of ram.

2. When swapping parts and no one knows which is bad, I have advice for our techs. Ready? It's a wowser.
-> Change the cheapest part first.
Bob

- Collapse -
Answer
soution
Sep 6, 2013 12:32AM PDT

The following describes how you can install Ubuntu onto a client machine, using just its network card to boot an Ubuntu installation image which will install Ubuntu. The way this works, in summary is: you set up and configure bootp, tftp, dhcp, and internet gateway services. Your client machine will

'netboot' via its network adapter, using pxe/bootp protocol,
get passed a kernel and installer via tftp. It will boot into that kernel, which will run an installation of Ubuntu onto your client machine.
Most of the packages installed come from latest versions from the Ubuntu repositories on the internet.

Set up the servers
Ensure that you have a bootp server, a tftp (eg tftp-hpa) server, and access to your router/gateway.

Configure the router and its dhcp server. Get the mac address of the new machine you will be installing ubuntu onto (the 'client machine' ). It is easiest if you decide on a fixed ip address for the client machine and set it into the router, as a fixed ip address, eg 192.168.1.42. Note also the gateway address of the router.
Configure a bootp service on a linux host. The same ip address as above needs to be assigned by the bootp service to the client machine.
Install bootp.

Edit /etc/bootptab. Here is an example.

client:\
ha="00:00:39:2B:54:B5":\
ip=192.168.1.42:\
gw=192.168.1.1:\
sm=255.255.255.0:\
td=/: hd=/: bf=pxelinux.0
ha = the mac address of the client machine (set this to its value)
ip = the ip address assigned in the router to the client machine
gw = the address of the router
sm = the subnet mask for your lan
td = the directory on the tfptboot server where the pxe files reside, relative to the tftpboot server's root.
hd = a further path which ends at either the pxe boot file or a link to it. (this is probably ok as is)
bf = the pxe boot file (this is probably ok as is)
For further help: man bootpd; man bootptab and also found in the etc/bootptab file itself as comments.

If you don't know the hardware address, or which ip address the dhcp server of the router will assign, start the client machine. Make sure its bios is set to boot first from its network adapter. You should then be able to get the hardware mac address as it attempts to boot via the network adapter. Update /etc/bootptab on the bootp server with the client's mac address and the ip address for it as set in the dhcp server (eg in the router), then restart bootpd.

Start bootp: Here is a wrapper to start and stop bootpd from the command line.

vDaemon=bootpd
vCd=/var/lib/tftpboot

Start () {
echo -n "Starting $vDaemon: default current directory is at $vCd ... :"
/usr/sbin/$vDaemon -d 4 -c $vCd >/tmp/$vDaemon.log 2>/tmp/$vDaemon.err &
sleep 1
Status
}

Stop () {
echo "Stopping $vDaemon ..."
kill `pidof $vDaemon`
}

Reload () {
if [ "`pidof $vDaemon`" ] ; then
echo "Reloading config file for $vDaemon ..."
kill -HUP "`pidof $vDaemon`"
fi
Status
}

Status () {
vPid="`pidof $vDaemon`"
if [ "$vPid" ] ; then
echo "$vDaemon running, pid=$vPid"
else
echo "$vDaemon not running"
fi
}

case "$1" in
start) Start ;;
stop) Stop ;;
reload) Reload ;;
restart) Stop ; sleep 2; Start ;;
status) Status ;;
""|*) echo `basename $0` parameter: start stop status reload or restart ;;
esac
Preparing Files for TFTP Net Booting, Section "Setting up BOOTP server" has more info on bootp, including instructions for starting bootp using the inetd alternative.

Configure the tftp server:
Install tftpd-hpa. Its config in /etc/default/tftpd-hpa should be

RUN_DAEMON="yes"
OPTIONS="-l -s /var/lib/tftpboot"
The -s parameter is your tftp server file root.
Download the netboot installer tarfile from the Ubuntu Archives (karmic, jaunty), and extract its contents into the tftpboot server file root as per above.