系统启动问题,lilo 急 在线等

young19860802

这台机器（Mandriva）运行的时间比较久了,里面的数据比较重要,事情是这样的，机器内存坏了,然后换了一根内存,重启后进入不了系统,lilo报错
Error Duplicated Volume ID
有什么安全的办法解决这个问题吗？谢谢大家

前面找了一篇文章，但是基本看不懂，有谁能帮我一下吗？谢谢
http://www.sfr-fresh.com/linux/m ... 2.8/README.volumeID

本来想发到系统区，但是哪里人实在太少，斑竹包含下,谢谢!!!

iori809

回复 9# young19860802


    那个启动程序比较老了~现在一般都是Grub了。我估计可能是识别硬件出现了问题。
建议你如果实在找不出问题的话。。。就这样用live cd进入系统然后用Grub做启动程序
别在那个了~

young19860802

前面查了下 这段话 应该蛮有用的，英文看的不是很懂，谁能帮我简单说明下，谢谢！！！
  140 VOLUME ID MAINTENANCE
  141 =====================
  142
  143 1. Duplicate Volume ID's
  144
  145 LILO will complain if two disks have duplicate Volume ID's.  This usually
  146 happens when the Volume ID field is a residue of a low-level format, or a
  147 residue of some older boot program which overwrites the Volume ID field.
  148 With duplicated Volume ID's, LILO will be unable to distinguish the two
  149 offending disks at boot-time, hence it may make an error and read the wrong
  150 disk.  Thus, it will refuse to install a boot loader as long as this
  151 condition persists.  Unassigned ID's are automatically overwritten, and a
  152 backup copy of the sector is created, so the fix is to write an "unassigned"
  153 value to one of the duplicated fields.  Say /dev/hda and /dev/hdb have
  154 duplicate Volume ID's.  Choose the disk with the higher BIOS device code,
  155 since it will not be a Windows NT or 2000 disk, and set the Volume ID to
  156 zero; viz.,
  157
  158         lilo -z -M /dev/hdb
  159
  160 The disk will receive a new Master Boot Record (which boots the first active
  161 partition), and the Volume ID will be set to zero.  A subsequent
  162 installation of LILO:
  163
  164         lilo -v
  165
  166 Should no longer complain about duplicated Volume ID's on /dev/hda and
  167 /dev/hdb.  /dev/hdb will at this time receive a newly generated Volume ID,
  168 which will be checked for uniqueness against all other disks in the system.
  169
  170 CAUTION:  NEVER CHANGE THE VOLUME ID OF A WINDOWS 2000 BOOT DISK.
  171
  172 Windows NT, 2000, and XP (presumably), all use the Volume ID during the boot
  173 process.  Changing the ID can render Windows unbootable.  Recovery seems to
  174 be possible by zeroing the Volume ID, although Windows would prefer that the
  175 Boot Volume ID remain unchanged.  No trouble has been encountered with
  176 changing the Volume ID of Windows 2000 data disks, other than the necessity
  177 of resetting the drive letter to its former value.  Basically, if you run
  178 Windows NT or later, your disks probably already have Volume ID's assigned
  179 by Windows.  If they do, leave them alone.  The Windows ID's are completely
  180 compatible with the LILO scheme, and vice versa.
  181
  182 2.  Volume ID check
  183
  184 The following command was added in LILO 22.5.4:
  185
  186         lilo -T vol-ID
  187
  188 The volume ID's will be printed in BIOS order (as of the most recent LILO
  189 boot), based upon the BIOS data check information.  If you did not boot with
  190 LILO the last time, then the information as of the last boot will not be
  191 available.  Any conflicts will be noted, along with the corrective action
  192 LILO will take the next time a boot loader is installed (/sbin/lilo
  193 command).  This is the preferred check of the state of Volume ID's on the
  194 disks.
  195
  196 Sample output from "lilo -T vol-id":
  197
  198   BIOS     Volume ID
  199
  200   0x80     B21AB21A
  201   0x81     EBF5EB74
  202   0x82     EBF5EB7B
  203   0x83     34225390
  204   0x84     78711C09
  205
  206 Volume ID's are all unique.
  207
  208
  209 A volume ID check (Volume S/N) will be printed with the following command:
  210
  211         lilo -t -v2
  212
  213 The "-t" switch means a "test mode" install, with no boot record written,
  214 and your system unmodified.  The "-v2" is needed to set the verbosity of the
  215 output high enough to print the table of BIOS device codes used by LILO (not
  216 necessarily the same as the BIOS itself), and the corresponding disk Volume
  217 ID's.  This information indicates the order of the BIOS device code
  218 translate table, as it would be set up for the next boot.  Disks are
  219 indicated by major/minor device numbers, in hex.
  220
  221 Sample output from "lilo -t -v2 | tail":
  222
  223 ...
  224 Mapped 6 (4+1+1) sectors.
  225 Added Windows
  226
  227  BIOS  Volume S/N  Device
  228   80    B21AB21A    0300
  229   81    EBF5EB74    0340
  230   82    EBF5EB7B    1600
  231   83    34225390    2100
  232   84    78711C09    0800
  233 The boot sector and the map file have *NOT* been altered.
  234
  235
  236 In the two examples above, the Volume ID's are in the same BIOS order,
  237 indicating that the BIOS device codes are being assigned by LILO for the
  238 boot loader in the correct sequence on this 5 disk system.
  239

young19860802

回复 4# ywlscpl


   

前面看了你发的文章，英文不太好，只能看简单的

按照他的说法,应该有2块相同的Volume-ID，这个如何查看?然后对主引导分区清空id(lilo -z -M /dev/hda
),接着重新分类一个新的Volume-ID(lilo -M /dev/hda)
之后的问题 看的不是很明白，能不能帮我解释下那？谢谢！！

young19860802

回复 7# justlooks


    这个如何检查？

justlooks

检查下volume ID是否有重复

lkk2003rty

当时内存坏了，然后就换了，重启后就这样了，而且可能和强行关机有关系
young19860802 发表于 2010-07-07 16:03

    不像是强行关机的问题。。。感觉应该是lilo识别硬件的问题。。。不懂lilo。。。帮顶。。。。

young19860802

谢谢 我先看下

ywlscpl

回复 3# young19860802


    这里看看
http://software.itags.org/linux-unix/271561/

young19860802

当时内存坏了，然后就换了，重启后就这样了，而且可能和强行关机有关系