#97 Problem booting master node in FC3

v1.9.1
closed-fixed
nobody
7
2007-03-25
2005-08-22
cyclone44
No

Installation goes fine, but when re-booting with the
SSI 1.9.1 enabled kernel the following messages appear:

Uncompressing Linux... Ok, booting the kernel.
kbd_cmd[0]: bpa panic_hook
Instruction(i) BP #0 at 0xc0127720 (panic_hook)
is enabled globally adjust 1
kbd_cmd[1]: defcmd archkdb "" "First line arch debuggin"
kbd_cmd[7]: defcmd archkdbcpu "" "archkdb with only
tasks on cpus"
kdb_cmd[13]: defcmd archkdbshort "" "archkdb with less
detailed backtrace"
kdb_cmd[19]: defcmd archkdbcommon "" "Comon arch debugging"
audid(1124731088.390:0): initialized
Kernel panic - not syncing: No init found. Try passing
init= option to kernel.

Entering kdb (current=0xc1bf15b0, pid 2) on processor 0
due to KDB_ENTER()
[0]kdb>

The system is a Dell Dimension 8300, P4 with 1MB RAM.
I've been running FC3 on it with no problems for
several months. I did a clean install of FC3 before
installing OpenSSi.

Discussion

  • Roger Tsang

    Roger Tsang - 2005-08-26
    • labels: 375981 --> Installation
    • milestone: --> v1.9.1
     
  • Roger Tsang

    Roger Tsang - 2005-08-26

    Logged In: YES
    user_id=1246761

    This is an installation bug. Re-run ssi-create then
    `mkinitrd --cfs` and ssi-ksync. Verify the kernel is
    booting the newest initrd image.

     
  • Roger Tsang

    Roger Tsang - 2005-11-04
    • priority: 5 --> 7
     
  • Nobody/Anonymous

    Logged In: NO

    That's exactly what I did.

    System hangs as described above - but - it's also impossible
    to boot up FC3. The links made in /var seem to be not
    correct und the file-system is reported as 'read-only'.

    I've got to do a complete new installation of FC3. I've
    learned to make an image of the partitions bevore.

     
  • Nobody/Anonymous

    Logged In: NO

    Is there someone out there, who's managed to install SSI for
    FC3 ever ?

    As there hasn't happened anything in the last 6 months, I
    doubt that there will be any action to SSI.

    We've got to burry it.
    RIP

     
  • Nobody/Anonymous

    Logged In: NO

    We've had success installing 1.9.2-pre on FC3.

     
  • Nobody/Anonymous

    Logged In: NO

    that won't be your only problem - things such as http also
    panic the kernel... :-(

     
  • cyclone44

    cyclone44 - 2006-01-16

    Logged In: YES
    user_id=1333343

    I did resolve this issue as suggested by rogertsang on
    August 26th.. the installation script was building a broken
    initrd. I've been using SSI successfully since then but the
    lack of NFS support for FC3 (and some issues building a
    kernel driver for my hardware raid controller).. has
    convinced me to try out ROCKS for my cluster. Depending on
    my experience with it, I may or may not go back to OpenSSI.

     
  • Roger Tsang

    Roger Tsang - 2006-01-18

    Logged In: YES
    user_id=1246761

    Going to close this bug. Install bug is fixed in 1.9.2pre.

    NFS fixes have been checked into CVS some time ago (probably
    after 1.9.2pre), and have been verified on the ssic users
    mailing list - NFS is functional.

     
  • Roger Tsang

    Roger Tsang - 2006-01-18
    • status: open --> open-fixed
     
  • Nobody/Anonymous

    Logged In: NO

    did you enable the openssi option in the clustring tab while
    compiling openssi cluster. for this to happen you have to
    select initrd option and also /dev filesystem.

    initrd will be in block devices tab when you do make menuconfig

    and /dev will be in filesystems. there will be seperate tab
    called clustering, just enable it and be cautious in
    selecting packages so that no problem occurs.

    Regards
    Saiganesh

     
  • Roger Tsang

    Roger Tsang - 2007-03-25
    • status: open-fixed --> closed-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks