Much can go wrong and this is the start of a growing list of symptoms, problems and solutions:
Cannot find disk
How to find what drive letter corresponds to what disk/partition
Remember Linux does not use drive letters but device names. More information can be found in Drive names.
Cannot partition disk
Most likely wrong input to the command line for fdisk
or similar tool.
Remember to use /dev/hda
rather than just hda
. Also
do not use numbers behind hda
, those indicate partitions.
Cannot format disk.
Strictly speaking you format partitions not disks.
Make sure you add the partition number after the device name
of the disk, for instance /dev/hda1
to the command line.
Number keep scrolling up the screen.
Possibly corrupt disk.
Try another disk, you might have to reinstall. Check for loose cables and possible data corruption.
Get LI
and then it hangs.
You use LILO to load Linux but LILO cannot find your root.
Read the LILO HOWTO.
Kernel panics, something about missing root file system.
The kernel does not know where the root partition is.
Use rdev
or (if applicable) LILO to add information
to the kernel image where your root is.
System boots but get into a root shell in single user mode.
Something went wrong in the later stages of booting and the system has come far enough to let you open a shell to repair the system.
Locate the problems from the boot log. Note that file system
can be in read-only mode. Remount read-write if you have to. Often the
reason is that the /etc/fstab
contained an entry that was mismapped
such as trying to mount a swap partition as your normal file space.
Short on memory
Swap space is not available
Type free and check the output. If you get
total used free shared buffers cached
Mem: 46920 30136 16784 7480 11788 5764
-/+ buffers/cache: 12584 34336
Swap: 128484 9176 119308
then system is running normal. If the line with Swap:
contains zeros
you have either not mounted the swap space (partition or swap file)
(see swapon(8)
)
or not formatted the swap space (see mkswap(8)
).
No room amidst plenty 1
Partitionitis:Underdimensioned partition sizes has caused overflow in some areas
Examine your partition usage using df(1)
and locate
problem areas. Normally the problem can be solved by removing old junk but
you might have to repartition your system,
see section
Repartitioning.
No room amidst plenty 2
Running out of i-nodes has caused overflow in some ares, often in areas with many small files such as news spool.
Examine your partition usage using df -i
and locate
problem areas. Normally the problem is solved by reformatting using
a higher number of i-nodes, see mkfs(8)
and related man pages.
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |