Difference between revisions of "Troubleshooting"
(→My kernel won't boot! How do I rebuild it?) |
(→My kernel won't boot! How do I rebuild it?) |
||
| Line 8: | Line 8: | ||
# Type in <tt>CRUX</tt> and press <tt>enter</tt> | # Type in <tt>CRUX</tt> and press <tt>enter</tt> | ||
# Log in as <tt>root</tt> | # Log in as <tt>root</tt> | ||
| − | + | # Type in the following commands: | |
<nowiki> | <nowiki> | ||
# mount /dev/sda1 /mnt | # mount /dev/sda1 /mnt | ||
| Line 21: | Line 21: | ||
# lilo | # lilo | ||
# shutdown now | # shutdown now | ||
| − | |||
</nowiki> | </nowiki> | ||
| + | Finally, unmount the iso and reboot the system. | ||
=== "error: couldn't mount because of unsupported optional features (240/244)" === | === "error: couldn't mount because of unsupported optional features (240/244)" === | ||
Revision as of 15:59, 16 June 2011
Contents |
Installation issues
Boot 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.
- Remount your CRUX Linux iso
- Type in CRUX and press enter
- Log in as root
- Type in the following commands:
# mount /dev/sda1 /mnt # setup-chroot # cd /usr/src/linux-2.6.25.6 # make menuconfig <add necessary features> # make all # make modules_install # cp arch/x86/boot/bzImage /boot/vmlinuz # cp System.map /boot/ # lilo # shutdown now
Finally, unmount the iso and reboot the system.
"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.
"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:
- If not, mark it as bootable with:
- After copying vmlinuz and System.map to /boot, did you run lilo?
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
This can be caused for numerous reasons.
- Server is currently down
- attempting to connect to incorrect IP address
- Network routing not set up
- SSH server not enabled/inbound connections not allowed
- sshd (SSH background daemon process) not running
- iptables (firewall) prohibiting connection
