[問題]kernel升級後，無法開機如何救

[Drake]

原因應該是沒有手動更新 lilo.conf 和執行 lilo
這樣一來要如何救?

網路上只記得提醒你要做這兩件事
並沒有提到如何「補救」

[高原之狼]

原因應該是沒有手動更新 lilo.conf 和執行 lilo
這樣一來要如何救?

網路上只記得提醒你要做這兩件事
並沒有提到如何「補救」

Boot from rescue disk, then type at the boot prompt:
boot: linux root=/dev/hd??

Should work, not tested though. Won't do any harm to try, however.

[Drake]

it should work except that you use a unsupported disk device.
the server is using Adaptec S2110 RAID Card and it's not supported yet ><
and the amazing is that I can't preload the driver from floopy successfully.
I am even not sure how I installed that server! I just remembered that there is no server for debian on www.adaptec.com and I got a likely driver floopy image from somewhere. but it doesn't work now~

[Drake]

and I'm sure that the floopy and the image are not broken.
so... how did I solve this driver problem ago

[高原之狼]

and I'm sure that the floopy and the image are not broken.
so... how did I solve this driver problem ago

Mmm... that's tricky. Let's see: if you can't even get the driver work for a reinstallation, then I am afraid nothing can be done software-wise.

I am not sure about RAID disks, but is it possible to open the box, pull out the hard drive, and plug it in another working machine, mount it and drag the working kernel image out?

[Drake]

You suggestion is the last step if I can't solve it and accept that I am defeated by it.

But there is a good news.

It finally reminds me of what I have done while installing. I type 'bf24' to load 2.4 kernel in installation! That's just because the driver of RAID controller can only be loaded into kernel 2.4

But there is another problme to me. I found that lilo.conf is modified by kernel-image-2.4.20-i686 already and all I need to do is 'lilo -v -v -v'. But I can't.

It says~

lilo
/lib/libc.so.6: version 'GLIBC_2.3' not found. (required by /target/sbin/lilo.real)

or

/target/sbin/lilo
/lib/ld-linux.so.2: version 'GLIBC_PRIVATE' not found. (required by /target/lib/libc.so.6)

There is a challenge coming again~

[高原之狼]

lilo
/lib/libc.so.6: version 'GLIBC_2.3' not found. (required by /target/sbin/lilo.real)

or

/target/sbin/lilo
/lib/ld-linux.so.2: version 'GLIBC_PRIVATE' not found. (required by /target/lib/libc.so.6)

Congratulations for the progress.

So it looks that you are using the file system on the rescue CD (since you typed bf24, it can't be the floppies), and there are conflicts between shared libraries.

I don't know how to solve this. But I can think of some workarounds:

1. If possible (i.e., figure out how to preload the RAID driver), directly mount the filesystem on your hard drive while booting from the kernel on rescue CD. This is actally what I mentioned at the very beginning:
boot: linux root=/dev/<hard_drive_device_number>

2. If you updated from apt-get, it should leave your old kernel on your disk instead of erase them. Looking at my /etc/lilo.conf, it says there should be a /vmlinuz.old which symlink to your old kernel (as the /vmlinuz sylinking to your new kernel). It should work to just change the /vmlinuz back to symlinking your old kernel, right?

This is an interesting problem (not that interesting for you though 8-P), please let us know your progress.

[Drake]

我在注意到 Ptrace Vulnerability 後，決定先把正在工作中的 cvs server升級。於是挑了 kernel-image-2.4.20-i686 下手。在最後忘了要執行 lilo造成重開機後的 unable to mount root fs.

因為採用了 Adaptec S2110 RAID Controller ，使得放進 woody 安裝光碟看不到，加上我又忘了當初是怎麼搞定的，最後才想起來要採用 bf24.bin再配合手邊忘了從來抓來的 driver 才可以順利看到硬碟。

我的作法是

• boot: bf24
• preload essential modules from floopy (dtp_i2o.o)

接下來進入 installation 後，我做了幾個嘗試：

1. 試著執行了安裝光碟 shell 下的 lilo 和原硬碟上的 lilo
   
   lilo (belongs to install cd)
   /lib/libc.so.6: version 'GLIBC_2.3' not found.
   (required by /target/sbin/lilo.real)
   
   /target/sbin/lilo (belongs to hdd)
   /lib/ld-linux.so.2: version 'GLIBC_PRIVATE' not found.
   (required by /target/lib/libc.so.6)
   
   又遇上了 shared lib 的 version 問題，作罷。
   
2. 在觀查了 server 經過 kernel update 後的 lilo.conf&相關檔案，再和自
   己另一台 kernel 2.2 及系上的 linux1 後，我先嘗試把 lilo.conf 中的
   default 改成 LinuxOLD ，無效。
   
3. 將 default 改回 Linux。但將 /vmlinuz 和 /vmlinuz.old 兩個 symblic
   link 對調，且將 /initrd.img 易名。（此作法是因為發現到手頭的那台
   kernel 2.2 並沒有 /initrd.img 此檔）
   一樣失敗。

題外話，發現了幾件事：

1.安裝光碟下的 shell 只有 nano-tiny 而沒有 vi, emacs, blah~
2.發覺不夠了解 lilo 這支程式到底作什麼事。

[Drake]

1. If possible (i.e., figure out how to preload the RAID driver), directly mount the filesystem on your hard drive while booting from the kernel on rescue CD. This is actally what I mentioned at the very beginning:
boot: linux root=/dev/<hard_drive_device_number>

2. If you updated from apt-get, it should leave your old kernel on your disk instead of erase them. Looking at my /etc/lilo.conf, it says there should be a /vmlinuz.old which symlink to your old kernel (as the /vmlinuz sylinking to your new kernel). It should work to just change the /vmlinuz back to symlinking your old kernel, right?

This is an interesting problem (not that interesting for you though 8-P), please let us know your progress.

I just had the same thougts and it failed again. It seems I am getting close to the goal but need one more step.

[高原之狼]

I am sure modifying /etc/lilo.conf won't have any effect. From my understanding, lilo is reading the configurations in lilo.conf, then write the infomation into a boot block image, and put the image to MBR.

So I'll suggest this: switch /vmlinuz and /vmlinuz.old, look into your /boot, correct all symlinks if any (System.map, config, etc. But I doubt if Debian use any); then DON'T rename initrd image and give it a try. I am suspecting that the kernel is reading the wrong initrd image for some mysterious reason.

[高原之狼]

One more thought:

Does the rescue CD have the /usr/sbin/chroot? If yes, a simple
# /usr/sbin/chroot /target /bin/bash
should give you an environment on your hard drive filesystem.

[Drake]

One more thought:

Does the rescue CD have the /usr/sbin/chroot? If yes, a simple
# /usr/sbin/chroot /target /bin/bash
should give you an environment on your hard drive filesystem.

It works. I mean, it gives me the original environment and I can run 'lilo -v -v -v'.
After 'lilo -v -v- v', I rebooted the system and took it a trial with Linux & LinuxOLD but both failed again

[Drake]

Finally, I make it return to the old kernel.
After I change it to new kernel and figure it out, I think I should post a so called '過程' here.

[訪客]

Finally, I make it return to the old kernel.
After I change it to new kernel and figure it out, I think I should post a so called '過程' here.

post一下嘍...^^

[高原之狼]

Finally, I make it return to the old kernel.

Glad to hear that!