Troubleshooting

From MineOS
Revision as of 19:06, 16 June 2011 by Hexparrot (Talk | contribs)

Jump to: navigation, search

Contents

Installation issues

Boot issues

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
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 System.map to /boot, did you run lilo?
      • Running lilo should report no errors.
    • In fdisk</t>, type <tt>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

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