lilo在unstable昇級kernel2.4.24後異常

如果您覺得您的問題不屬於 debian desktop 或是 debian server 版的範圍內,請在這裡發問。

版主: mufa

lilo在unstable昇級kernel2.4.24後異常

文章lueo » 週三 3月 03, 2004 9:27 am

之前直接lilo出現下面的訊息,現在用test測試,訊息還是一樣。請幫幫忙…是昇級kernel 後硬碟在哪它們都認不得了嗎?
代碼: 選擇全部
!ROOT! debian:~# lilo -t
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda'
Added Linux *
Added LinuxOLD
The boot sector and the map file have *NOT* been altered.

第二個問題:用mkboot 製作bootdisk 時,若用Vanilla即預設的lilo.conf製作,沒問題;若用Best即現在的/etc/lilo.conf製作,就會出現
代碼: 選擇全部
!ROOT! debian:~# mkboot
 
Insert a floppy diskette into your boot drive, and press <Return>.
 
Creating a lilo bootdisk...
Kernel is at /boot/vmlinuz-2.4.24-1-686 in /boot
Matching initrd image is /boot/initrd.img-2.4.24-1-686
Found kernel image /vmlinuz in existing /etc/lilo.conf
   but it does not invoke /boot/initrd.img-2.4.24-1-686 .
The mkboot script can probably do better.
 
Here is the proposed lilo.conf:
 
# floppy lilo.conf
        boot = /dev/fd0
        install = boot.b
        map = map
lba32
vga=normal
default=Linux
                                       # kernel-specific:
                                       image=/vmlinuz
label=Linux
initrd=/initrd.img
read-only
root = /dev/hda3
 
You can install the boot-loader from this best guess,
or you can try to install from a `vanilla\' lilo.conf .
 
Which do you choose? (Enter B for best, V for vanilla): B
Installing the best-guess lilo.conf...
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda'
Added Linux *
If you need to modify the floppy's lilo.conf, run the following:
 
        mount /dev/fd0 /mnt
        cd /mnt
        vi lilo.conf            # edit the file
        lilo -C lilo.conf       # run lilo on floppy
        cd
        umount /dev/fd0
...Success.
 

雖然成功了可是軟碟讀很久。應該也是那個Warning的問題。
以下是lilo -v-v-v 的訊息:
代碼: 選擇全部
!ROOT! debian:~# lilo -t -v -v -v
LILO version 22.5.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2003 John Coffman
Released 10-Oct-2003, and compiled at 16:48:46 on Feb 13 2004
Debian GNU/Linux
                                                                               
raid_setup returns offset = 00000000  ndisk = 0
 BIOS   VolumeID   Device
Reading boot sector from /dev/hda5
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part1' -> '/dev/hda1'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part2' -> '/dev/hda2'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part3' -> '/dev/hda3'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part4' -> '/dev/hda4'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part5' -> '/dev/hda5'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part6' -> '/dev/hda6'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part7' -> '/dev/hda7'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part8' -> '/dev/hda8'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part9' -> '/dev/hda9'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part10' -> '/dev/hda10'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part11' -> '/dev/hda11'
pf_hard_disk_scan: ndevs=1
  0300  5F3DBF13  /dev/hda
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
  0300  5F3DBF13  /dev/hda
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 1
device codes (canonical) = 1
Device 0x0305: BIOS drive 0x80, 255 heads, 3649 cylinders,
               63 sectors. Partition offset: 12321918 sectors.
Using Volume ID 5F3DBF13 on bios 80
Device 0x0300: BIOS drive 0x80, 255 heads, 3649 cylinders,
               63 sectors. Partition offset: 0 sectors.
Using Volume ID 5F3DBF13 on bios 80
Device 0x0305: BIOS drive 0x80, 255 heads, 3649 cylinders,
               63 sectors. Partition offset: 12321918 sectors.
Using Volume ID 5F3DBF13 on bios 80
mode = 0x03,  columns = 80,  rows = 25,  page = 0
Using MENU secondary loader
Calling map_insert_data
Secondary loader: 17 sectors (0x3200 dataend).
bios_boot = 0x80  bios_map = 0x80  map==boot = 0  map S/N: 5F3DBF13
BIOS data check was okay on the last boot
 
Boot image: /vmlinuz -> boot/vmlinuz-2.4.24-1-686
Device 0x0305: BIOS drive 0x80, 255 heads, 3649 cylinders,
               63 sectors. Partition offset: 12321918 sectors.
Using Volume ID 5F3DBF13 on bios 80
Setup length is 10 sectors.
Mapped 1682 sectors.
Mapping RAM disk /initrd.img -> boot/initrd.img-2.4.24-1-686
Device 0x0305: BIOS drive 0x80, 255 heads, 3649 cylinders,
               63 sectors. Partition offset: 12321918 sectors.
Using Volume ID 5F3DBF13 on bios 80
RAM disk: 7144 sectors.
Added Linux *
    <dev=0xe0,hd=188,cyl=28,sct=225>
    "ro root=303"
 
Boot image: /vmlinuz.old -> boot/vmlinuz-2.4.18-bf2.4
Device 0x0305: BIOS drive 0x80, 255 heads, 3649 cylinders,
               63 sectors. Partition offset: 12321918 sectors.
Using Volume ID 5F3DBF13 on bios 80
Setup length is 10 sectors.
Mapped 2470 sectors.
Added LinuxOLD
    <dev=0xe0,hd=188,cyl=70,sct=143>
    "ro root=303"
 
 BIOS   VolumeID   Device
  80    5F3DBF13    0300
The boot sector and the map file have *NOT* been altered.

同樣是用testing…

以下是lilo.conf的內容:
代碼: 選擇全部
!ROOT! debian:~# cat /etc/lilo.conf
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.
 
# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+
 
# Support LBA for large hard disks.
#
lba32
 
# Overrides the default mapping between harddisk names and the BIOS'
# 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/hda5
 
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda3
 
# 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' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn'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=/boot/boot-menu.b
 
# Specifies the location of the map file
#
map=/boot/map
 
# You can set a password here, and uncomment the `restricted' 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'
# statement in `lilo.conf', 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',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' 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)'.
#
# 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', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
#       prompt
#       single-key
#       delay=100
#       timeout=100
 
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal
 
# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
#append="video=sisfb:mode:1024x768x16,mem:12288,rate:75"
#append="video=sisfb:mode:1024x768x16"
 
# Boot up Linux by default.
#
default=Linux
 
image=/vmlinuz
        label=Linux
initrd=/initrd.img
        read-only
#       restricted
#       alias=1
 
image=/vmlinuz.old
        label=LinuxOLD
        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' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#       label=HURD
#       restricted
#       alias=3

感謝!
lueo
懵懂的國中生
懵懂的國中生
 
文章: 121
註冊時間: 週六 1月 31, 2004 11:52 pm

Re: lilo在unstable昇級kernel2.4.24後異常

文章Tetralet » 週三 3月 03, 2004 12:38 pm

首先,您的 Kernel 是 Debian 官方的嗎?
您的 LILO 版本是?

再來,請您把 /etc/fstab 的內容貼出來。

另外,
lueo 寫:
代碼: 選擇全部
# 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/hda5


在這裡把 LILO 寫入 /dev/hda5 似乎並不是很理想的做法...
時間並不能治療我心中的疼痛
南方的春天說什麼也溫暖不了我冰冷的血

誦唱大復活咒文,今天的 Tetralet 又在唧唧喳喳了 重生!
Tetralet
俺是博士
俺是博士
 
文章: 3078
註冊時間: 週四 11月 28, 2002 3:02 pm

Re: lilo在unstable昇級kernel2.4.24後異常

文章lueo » 週三 3月 03, 2004 3:23 pm

Tetralet 寫:首先,您的 Kernel 是 Debian 官方的嗎?
您的 LILO 版本是?

是啊!2.4.24-1-686
代碼: 選擇全部
lueo@debian:~$ aptitude search ~ikernel
i A kernel-headers-2.4.24-1         - Header files related to Linux kernel vers
i   kernel-headers-2.4.24-1-686     - Linux kernel headers 2.4.24 on PPro/Celer
i   kernel-image-2.4.24-1-686       - Linux kernel image for version 2.4.24 on
i A kernel-package                  - A utility for building Linux kernel relat
i A linux-kernel-headers            - Linux Kernel Headers for development

代碼: 選擇全部
!ROOT! debian:~# lilo -V
LILO version 22.5.8 (Debian GNU/Linux)
再來,請您把 /etc/fstab 的內容貼出來。
代碼: 選擇全部
!ROOT! debian:/etc# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>               <dump>  <pass>
/dev/hda3       /               ext3    errors=remount-ro       0       1
/dev/hda7       none            swap    sw                      0       0
proc            /proc           proc    defaults                0       0
/dev/fd0        /floppy         auto    user,noauto             0       0
/dev/cdrom      /cdrom          iso9660 ro,user,noauto,utf8=1   0       0
/dev/hda8       /home   ext3    defaults                        0       2
/dev/hda5       /boot   ext3    defaults                        0       2
/dev/hda2       /mnt/vfat/C     vfat    user,utf8=1,umask=000   0       0
/dev/hda2       /mnt/vfat/D     vfat    user,utf8=1,umask=000   0       0
/dev/hda9       /mnt/vfat/E     vfat    auto,user,utf8=1,umask=000      0      0/dev/hda10      /mnt/vfat/F     vfat    auto,user,utf8=1,umask=000      0      0/dev/hda11      /mnt/vfat/G     vfat    auto,user,utf8=1,umask=000      0      0

在這裡把 LILO 寫入 /dev/hda5 似乎並不是很理想的做法...

因為割了一塊30mb的開機磁區,mbr 是留給spfdisk驅動的。
lueo
懵懂的國中生
懵懂的國中生
 
文章: 121
註冊時間: 週六 1月 31, 2004 11:52 pm

re:lilo在unstable昇級kernel2.4.24後異常

文章Tetralet » 週三 3月 03, 2004 6:00 pm

試著把 LILO 降到 stable 再試試看!

還有,請問您有安裝 devfsd 這個套件嗎?
時間並不能治療我心中的疼痛
南方的春天說什麼也溫暖不了我冰冷的血

誦唱大復活咒文,今天的 Tetralet 又在唧唧喳喳了 重生!
Tetralet
俺是博士
俺是博士
 
文章: 3078
註冊時間: 週四 11月 28, 2002 3:02 pm

re:lilo在unstable昇級kernel2.4.24後異常

文章lueo » 週三 3月 03, 2004 6:44 pm

Tetralet 寫:試著把 LILO 降到 stable 再試試看!

還有,請問您有安裝 devfsd 這個套件嗎?
沒有耶…

先謝謝您的回答!

找到了一篇mailist的文章,原來devfs快被udev取代啦…(兩個我都不知是什麼)…最好的作法就是別管它,反正沒出事…!@#!%$!%…
lueo
懵懂的國中生
懵懂的國中生
 
文章: 121
註冊時間: 週六 1月 31, 2004 11:52 pm


回到 debian misc

誰在線上

正在瀏覽這個版面的使用者:Google [Bot] 和 1 位訪客