From MineOS Wiki
Jump to navigation Jump to search

Installation issues

My kernel won't boot! How do I rebuild it?

If you broke your kernel and can no longer reboot, either by removing a necessary feature for booting or maybe making it a [M] module instead of [*] built-in, you will need to re-enter your installed environment by using the original CRUX installation iso (rescue procedure).

  1. Remount your CRUX Linux iso
  2. Reboot your system and boot from the ISO
  3. Type in CRUX and press enter
  4. Log in as root
  5. Type in the following commands:
# mount /dev/sda1 /mnt
# setup-chroot
# cd /usr/src/linux-
# make menuconfig
# make all
# make modules_install
# cp arch/x86/boot/bzImage /boot/vmlinuz
# cp /boot/
# lilo
# shutdown now

Finally, unmount the iso and reboot the system.

Boot issues

General boot issue

Many problems can occur at boot-time, but may not have sufficient information to diagnose and fix. You can get additional information by removing the 'quiet' word from /etc/lilo.conf. This will have Linux produce all initialization output which should make debugging much easier. Also, you can check the files in /var/log, such as boot, messages, etc. which will give additional insight to boot problems.

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)

This issue can arise from one of two reasons:

  1. The boot partition's filesystem was not built into the kernel (e.g., EXT4/ReiserFS)
  2. The kernel does not have the appropriate SATA/hard disk controller drivers in order to recognize the boot partition

To fix this, follow the rescue boot instructions.

Kernel panic - no syncing

"error: couldn't mount because of unsupported optional features (240/244)"

This is more of a warning than an error. It occurs because the boot sequence attempts to read the boot partition with EXT3/EXT2, which is not the actual filesystem. It then continues by attempting ReiserFS/EXT4 and successfully locates the kernel. Since it gives the impression of an unclean installation, you can suppress these errors most easily by removing EXT3/EXT2 support in the kernel--neither filesystems will be used in MineOS. Otherwise, you can simply ignore it.

error: couldn't mount

"FATAL: No bootable medium found! System halted."

Depending on what steps you have completed, this can mean different things.

  • If are starting from the very, very beginning, it simply means the CRUX Linux iso is not mounted
  • If you have already compiled and copied the kernel as /boot/vmlinuz, check two places:
    • After copying vmlinuz and to /boot, did you run lilo?
      • Running lilo should have reported no errors. To fix this, follow the rescue boot instructions.
    • In fdisk, type p <enter> to see the master boot record. Is partition one marked with an asterisk (*) as bootable?
      • If not, mark it as bootable with:
a <enter>
1 <enter>
p <enter> (verify bootable flag set)
w <enter>

Ports issues

=======> ERROR: Footprint mismatch found:
MISSING -rwxr-xr-x root/root usr/lib/python2.7/lib-dynload/
MISSING -rwxr-xr-x root/root usr/lib/python2.7/lib-dynload/
Building /usr/ports/ppc/opt/python#2.7.2-1.pkg.tar.gz' failed.

This issue must be fixed at the port maintainers end, updating the port to expect different/compatible-old versions of libraries. To get through this issue, you may suppress footprint mismatch errors and continue through. More accurately, it ignores the footprint check step.

  1. vi /etc/pkgmk.conf
  2. Uncomment and adjust the line: PKGMK_IGNORE_FOOTPRINT="yes"

Scripts issues

Connectivity issues

"Network error: Connection timed out" -- cannot SSH

SSH connection timed out

This can be caused for numerous reasons.

  1. Server is currently down
  2. attempting to connect to incorrect IP address
  3. Network routing not set up
  4. SSH server not enabled/inbound connections not allowed
  5. sshd (SSH background daemon process) not running
  6. iptables (firewall) prohibiting connection

Issued an IP address but unable to connect to internet/ping destination

If ifconfig reports an IP address issued to your interface, but you are unable to access the internet, there are a few places to check. Such behavior like this dropping 100% packets during ping.

  1. iptables -F - flushes any existing IP tables filtering rules to allow all traffic.
  2. Network routing (ethernet) not set up. Check specifically the route add default via line.
  3. Wireless routing (wifi) improperly set up. Check specifically the route add default gw line.