<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[Linux Forum &mdash; Проблема с загрузкой нового ядра]]></title>
		<link>https://linuxforum.ru/viewtopic.php?id=15282</link>
		<atom:link href="https://linuxforum.ru/extern.php?action=feed&amp;tid=15282&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[Недавние сообщения в теме «Проблема с загрузкой нового ядра».]]></description>
		<lastBuildDate>Tue, 26 Jul 2011 06:31:15 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197932#p197932</link>
			<description><![CDATA[<p><strong>aliaksei1818</strong>, <br />спасибо, беда была действительно в mdadm.conf (не правильно указана точка монтирования)</p><br /><p>решил проблему здесь <a href="http://www.linux.org.ru/jump-message.jsp?msgid=6537960&amp;cid=6538181">http://www.linux.org.ru/jump-message.js … id=6538181</a></p>]]></description>
			<author><![CDATA[null@example.com (wolverin)]]></author>
			<pubDate>Tue, 26 Jul 2011 06:31:15 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197932#p197932</guid>
		</item>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197927#p197927</link>
			<description><![CDATA[<div class="codebox"><pre><code>УУИД может указываться на софтовый раид?</code></pre></div><p>mdadm.conf</p>]]></description>
			<author><![CDATA[null@example.com (aliaksei1818)]]></author>
			<pubDate>Tue, 26 Jul 2011 06:11:34 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197927#p197927</guid>
		</item>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197897#p197897</link>
			<description><![CDATA[<div class="quotebox"><cite>aliaksei1818 пишет:</cite><blockquote><p>image=/vmlinuz<br />initrd=/initrd.img</p></blockquote></div><p>Да, из /boot/ сделаны симлинки (автоматически при установке ядра)<br />УУИД может указываться на софтовый раид?</p><p><strong>:/$ ls -l</strong><br /></p><div class="codebox"><pre><code>итого 4716
drwxr-xr-x  2 root root     4096 2011-07-21 09:54 bin
drwxr-xr-x  2 root root     4096 2011-07-25 16:21 boot
drwxr-xr-x  1 root root        0 1970-01-01 06:00 dev
drwxrwsr-x  3 root staff    4096 2009-12-07 12:55 home
drwxr-xr-x  2 root root     4096 2004-06-29 11:42 initrd
drwx------  2 root root    16384 2004-06-29 11:35 lost+found
drwxr-xr-x  7 root root     4096 2011-07-25 17:13 root
drwxrwxrwt  3 root root     4096 2011-07-26 09:32 tmp
lrwxrwxrwx  1 root root       28 2011-07-20 16:38 initrd.img -&gt; boot/initrd.img-2.6.18-6-686
-rw-r--r--  1 root root  4729823 2011-07-20 16:38 initrd.img-2.6.18-6-686.bak
lrwxrwxrwx  1 root root       25 2011-07-20 16:38 vmlinuz -&gt; boot/vmlinuz-2.6.18-6-686
lrwxrwxrwx  1 root root       19 2005-06-15 18:50 vmlinuz.old -&gt; boot/vmlinuz-2.4.31
lrwxrwxrwx  1 root root       20 2011-07-20 16:42 vmlinuz.old1 -&gt; /boot/vmlinuz-2.4.26</code></pre></div>]]></description>
			<author><![CDATA[null@example.com (wolverin)]]></author>
			<pubDate>Tue, 26 Jul 2011 02:10:25 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197897#p197897</guid>
		</item>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197779#p197779</link>
			<description><![CDATA[<p>Попробуйте смонтировать раздел с точным указание точки монтирования (UUID)<br />И еще:<br />image=/vmlinuz<br />initrd=/initrd.img<br />Это Ваш путь?</p>]]></description>
			<author><![CDATA[null@example.com (aliaksei1818)]]></author>
			<pubDate>Mon, 25 Jul 2011 14:12:58 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197779#p197779</guid>
		</item>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197626#p197626</link>
			<description><![CDATA[<p><strong>newzenon</strong>, <br />поправил</p>]]></description>
			<author><![CDATA[null@example.com (wolverin)]]></author>
			<pubDate>Mon, 25 Jul 2011 03:15:07 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197626#p197626</guid>
		</item>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197625#p197625</link>
			<description><![CDATA[<p><strong>wolverin</strong>, <span style="color: blue">не начнёте пользоваться тегами code, console, spoiler - вечером закрою тему, поправьте свои сообщения.&nbsp; </span> <a href="http://linuxforum.ru/help.php?section=bbcode">http://linuxforum.ru/help.php?section=bbcode</a></p>]]></description>
			<author><![CDATA[null@example.com (zenon)]]></author>
			<pubDate>Mon, 25 Jul 2011 02:57:38 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197625#p197625</guid>
		</item>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197621#p197621</link>
			<description><![CDATA[<p><strong>aliaksei1818</strong>, <br /><strong>:~# cat /etc/lilo.conf</strong><br /></p><div class="codebox"><pre><code># /etc/lilo.conf - See: `lilo(8)&#039; and `lilo.conf(5)&#039;,
# ---------------       `install-mbr(8)&#039;, `/usr/share/doc/lilo/&#039;,
#                       and `/usr/share/doc/mbr/&#039;.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don&#039;t forget to run `lilo&#039; after you make changes to this     |
# | conffile, `/boot/bootmess.txt&#039;, or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don&#039;t remember to run `lilo&#039;.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS&#039;
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/md/0

# Specifies the device that should be mounted as root. (`/&#039;)
#
root=/dev/md/0

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact&#039; is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn&#039;t always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=menu

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted&#039; lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append&#039;
# statement in `lilo.conf&#039;, the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh&#039;,
# and thus becoming `root&#039; without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr&#039; to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)&#039;.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt&#039;, and this computer may need to reboot unattended, you
# must specify a `timeout&#039;, or it will sit there forever waiting
# for a keypress.  `single-key&#039; goes with the `alias&#039; lines in the
# `image&#039; configurations below.  eg: You can press `1&#039; to boot
# `Linux&#039;, `2&#039; to boot `LinuxOLD&#039;, if you uncomment the `alias&#039;.
#
# message=/boot/bootmess.txt
#       prompt
#       single-key
#       delay=100
#       timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, &lt;mode&gt;)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO&#039; and `kernel-parameters.txt&#039; in
# the Linux kernel `Documentation&#039; directory.
#
# append=&quot;&quot;

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
        label=Linux
        initrd=/initrd.img
        read-only

image=/vmlinuz.old
        label=LinuxOLD
        read-only
#       restricted
#       alias=1

image=/vmlinuz.old1
        label=LinuxOLD1
        read-only
        optional
#       restricted
#       alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other&#039; line to
# where your other OS&#039; partition is.
#
# other=/dev/hda4
#       label=HURD
#       restricted
#       alias=3</code></pre></div><p><strong>lilo.conf.hd*</strong> а этот где искать? поиск ничего не дал.</p>]]></description>
			<author><![CDATA[null@example.com (wolverin)]]></author>
			<pubDate>Mon, 25 Jul 2011 02:13:21 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197621#p197621</guid>
		</item>
		<item>
			<title><![CDATA[Re: Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=197321#p197321</link>
			<description><![CDATA[<p>Покажите lilo.conf и lilo.conf.hd*</p>]]></description>
			<author><![CDATA[null@example.com (aliaksei1818)]]></author>
			<pubDate>Sat, 23 Jul 2011 18:06:15 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=197321#p197321</guid>
		</item>
		<item>
			<title><![CDATA[Проблема с загрузкой нового ядра]]></title>
			<link>https://linuxforum.ru/viewtopic.php?pid=196870#p196870</link>
			<description><![CDATA[<p>Предыстория.<br />Стоял Etch с ядром 2.4 + Firebird 1.5 - возникла проблема - с какой то переодичностью начались биться базы.<br />Решил обновить его до 2.0 хотя бы и Lenny.<br />Поправил соурс лист на архив.Debian, обновился до последних пакетов, поставил ядро 2.6.18 для 686, поправил lilo.conf<br />Перезапускаюсь и ...<br />местный энекейщик присылает мне текст загрузки</p><div class="codebox"><pre><code>begin: Running /scripts/local-premount
done.
Usage: mod probe -и дальши пишуться ключи и х там много прописано потом
modprobe -r [-n] [-i] [v] &lt;modulename&gt; ...
modprobe -l -t &lt;dirname&gt; [ -a &lt;modulename&gt; ...]
mount: Cannont read /etc/fstab: No such file or directory
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/local-bottom ...
mount mounting /root/dev/ on /dev/.static/dev failed: No such file or directorymount
Done
mount mounting /sys om /root/sys failed: No such file or directorymount
mount mounting /proc on /root/proc failed: No such file or directorymount
Target filesystem doesn`t have /sbin/init</code></pre></div><p>Старое ядро грузится без проблем.<br />На системе стоит софтовый раид в зеркало</p><p><strong>:~# fdisk -l</strong><br /></p><div class="codebox"><pre><code>Disk /dev/md/0: 79.9 GB, 79998877696 bytes
2 heads, 4 sectors/track, 19530976 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

This doesn&#039;t look like a partition table
Probably you selected the wrong device.

     Device Boot      Start         End      Blocks   Id  System
/dev/md/0p1   ?   233721421   254807611    84344761   69  Unknown
Partition 1 does not end on cylinder boundary.
/dev/md/0p2   ?   212689936   446425119   934940732+  73  Unknown
Partition 2 does not end on cylinder boundary.
/dev/md/0p3   ?         322         322           0   74  Unknown
Partition 3 does not end on cylinder boundary.
/dev/md/0p4       360710145   360716696       26207+   0  Empty
Partition 4 does not end on cylinder boundary.

Partition table entries are not in disk order

Disk /dev/ide/host0/bus1/target0/lun0/disc: 81.9 GB, 81964302336 bytes
16 heads, 63 sectors/track, 158816 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

                                Device Boot      Start         End      Blocks   Id  System
/dev/ide/host0/bus1/target0/lun0/part1   *           1      155010    78125008+  fd  Linux raid autodetect
/dev/ide/host0/bus1/target0/lun0/part2          155011      158816     1918224   82  Linux swap / Solaris

Disk /dev/ide/host0/bus0/target0/lun0/disc: 81.9 GB, 81963220480 bytes
255 heads, 63 sectors/track, 9964 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

                                Device Boot      Start         End      Blocks   Id  System
/dev/ide/host0/bus0/target0/lun0/part1   *           1        9726    78124063+  fd  Linux raid autodetect
/dev/ide/host0/bus0/target0/lun0/part2            9727        9964     1911735   82  Linux swap / Solaris</code></pre></div><p><strong>:~$ cat /etc/fstab</strong><br /></p><div class="codebox"><pre><code># /etc/fstab: static file system information.
#
# &lt;file system&gt;         &lt;mount point&gt;   &lt;type&gt;  &lt;options&gt;               &lt;dump&gt; &lt;pass&gt;
/dev/md/0               /               ext3    errors=remount-ro       0      0
/dev/discs/disc0/part2  none            swap    sw                      0      0
/dev/discs/disc1/part2  none            swap    sw                      0      0
proc                    /proc           proc    defaults                0      0
/dev/cdrom              /cdrom          iso9660 ro,user,noauto          0      0

По инету поискал, вроде пишут надо fsck -yv запускать, но что то побаиваюсь на рабочей то системе.
[b]:~# fsck /[/b]
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
/dev/md/0 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? no

check aborted.</code></pre></div><p><strong>:/# cat /etc/modules</strong><br /></p><div class="codebox"><pre><code># /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a &quot;#&quot;, and everything on the line after them are ignored.

8139too
ide-scsi
sr_mod
sg
md</code></pre></div>]]></description>
			<author><![CDATA[null@example.com (wolverin)]]></author>
			<pubDate>Fri, 22 Jul 2011 08:25:32 +0000</pubDate>
			<guid>https://linuxforum.ru/viewtopic.php?pid=196870#p196870</guid>
		</item>
	</channel>
</rss>
