Thread: [SSI-users] Problems installing on Lenny
Brought to you by:
brucewalker,
rogertsang
From: Sergi B. <hi...@li...> - 2009-03-19 09:01:14
|
Hi, Today I started installation, and I founded my first problem, when installing openssi package it returns me this error: Finding valid ramdisk creators. Using mkinitrd to build the ramdisk. ldd: /cluster/lib/cfstab: No existe el fichero o el directorio mkinitrd failed to create initrd image. cfstab left on this path, what's exactly in this file? A copy of fstab with clusterfs mount points? Thanks -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
From: John H. <john@Calva.COM> - 2009-03-19 09:34:55
|
Sergi Barroso wrote: > Hi, > > Today I started installation, and I founded my first problem, when > installing openssi package it returns me this error: > > Finding valid ramdisk creators. > Using mkinitrd to build the ramdisk. > ldd: /cluster/lib/cfstab: No existe el fichero o el directorio > mkinitrd failed to create initrd image. > > cfstab left on this path, what's exactly in this file? A copy of fstab > with clusterfs mount points? > > cfstab is the table that shows which filesystem types should have cfs layered on top of them: #<fstype> <cluster> <defaults> ext2 cfs ext3 cfs # for ext3 gfs parallel tmpfs cfs # for udev (so we don't layer cfs on top of gfs, each node mounts it in parallel). I've seen this problem before, I think it's because you've missed one of the steps in the installation. You are following my "howto" document step by step? Could you do: $ dpkg -l initrd-tools and send us the output. |
From: Sergi B. <hi...@li...> - 2009-03-19 09:39:01
|
John Hughes escribió: > Sergi Barroso wrote: >> Hi, >> >> Today I started installation, and I founded my first problem, when >> installing openssi package it returns me this error: >> >> Finding valid ramdisk creators. >> Using mkinitrd to build the ramdisk. >> ldd: /cluster/lib/cfstab: No existe el fichero o el directorio >> mkinitrd failed to create initrd image. >> >> cfstab left on this path, what's exactly in this file? A copy of fstab >> with clusterfs mount points? >> >> > cfstab is the table that shows which filesystem types should have cfs > layered on top of them: > > #<fstype> <cluster> <defaults> > ext2 cfs > ext3 cfs # for ext3 > gfs parallel > tmpfs cfs # for udev > > > (so we don't layer cfs on top of gfs, each node mounts it in parallel). > > I've seen this problem before, I think it's because you've missed one > of the steps in the installation. You are following my "howto" > document step by step? > > Could you do: > > $ dpkg -l initrd-tools > > > and send us the output. > Tha'ts the output of dpkg, but initrd it's installed from openssi repos Desired=Unknown/Install/Remove/Purge/Hold | Estado=No/Instalado/Config-files/Desempaquetado/Fallo-config/Medio-inst/espera-disparo/pendiente-disparo |/ Err?=(ninguno)/Retenido/Requiere-reinst/X=ambos problemas (Estado,Err: mayúsc.=malo) ||/ Nombre Versión Descripción +++-=============================================================-=============================================================-========================================================================================================================================== ii initrd-tools 0.1.84.2.ssi4 tools to create initrd image for prepackaged Linux kernel -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
From: John H. <john@Calva.COM> - 2009-03-19 09:57:35
|
Sergi Barroso wrote: > John Hughes escribió: > >> Sergi Barroso wrote: >> >>> Finding valid ramdisk creators. >>> Using mkinitrd to build the ramdisk. >>> ldd: /cluster/lib/cfstab: No existe el fichero o el directorio >>> mkinitrd failed to create initrd image. >>> >>> >> >> I've seen this problem before, I think it's because you've missed one >> of the steps in the installation. You are following my "howto" >> document step by step? >> >> Could you do: >> >> $ dpkg -l initrd-tools >> >> > ii initrd-tools 0.1.84.2.ssi4 tools to create initrd image for prepackaged Linux kernel > > Ok, you've got the right version of initrd-tools. Wait, I have some vague memories... Could you do dpkg -l | grep 64 Do you have some kind of amd64 library installed? That may be screwing up ldd. Could you do: # /bin/sh -x 2>zz-initrd /usr/sbin/mkinitrd -o initrd.img-2.6.12-ssi-686-smp 2.6.12-ssi-686-smp and send me the file "zz-initrd" (gzip it, it may be aound 100K). |
From: Jeroen Q. <Jeroen.Quiros@OrcaGroup.com> - 2009-03-19 10:12:41
|
unsubscribe Met vriendelijke groet, OrcaGroup Jeroen Quiros Software Developer Cereslaan 8, 5384 VT Heesch Postbus 80, 5384 ZH Heesch t +31 (0)412-695100 f +31 (0)412-651995 e Jeroen.Quiros@OrcaGroup.com<mailto:Jeroen.Quiros@OrcaGroup.com> i http://www.OrcaGroup.com<http://www.orcagroup.com/> OrcaGroup: creatief in communicatie From: John Hughes [mailto:john@Calva.COM] Sent: Thursday, March 19, 2009 10:57 To: hi...@li... Cc: ssi...@li... Subject: Re: [SSI-users] Problems installing on Lenny Sergi Barroso wrote: John Hughes escribió: Sergi Barroso wrote: Finding valid ramdisk creators. Using mkinitrd to build the ramdisk. ldd: /cluster/lib/cfstab: No existe el fichero o el directorio mkinitrd failed to create initrd image. I've seen this problem before, I think it's because you've missed one of the steps in the installation. You are following my "howto" document step by step? Could you do: $ dpkg -l initrd-tools ii initrd-tools 0.1.84.2.ssi4 tools to create initrd image for prepackaged Linux kernel Ok, you've got the right version of initrd-tools. Wait, I have some vague memories... Could you do dpkg -l | grep 64 Do you have some kind of amd64 library installed? That may be screwing up ldd. Could you do: # /bin/sh -x 2>zz-initrd /usr/sbin/mkinitrd -o initrd.img-2.6.12-ssi-686-smp 2.6.12-ssi-686-smp and send me the file "zz-initrd" (gzip it, it may be aound 100K). |
From: John H. <john@Calva.COM> - 2009-03-19 10:29:32
|
Sergi Barroso wrote: > John Hughes escribió: >> Ok, you've got the right version of initrd-tools. >> >> Wait, I have some vague memories... >> >> Could you do >> >> dpkg -l | grep 64 >> >> Do you have some kind of amd64 library installed? That may be >> screwing up ldd. >> >> Could you do: >> >> # /bin/sh -x 2>zz-initrd /usr/sbin/mkinitrd -o >> initrd.img-2.6.12-ssi-686-smp 2.6.12-ssi-686-smp >> >> and send me the file "zz-initrd" (gzip it, it may be aound 100K). >> > No, I have no amd64 packages installed, I use 32 bit version. Yes, you're right. That's not the problem: This is the problem: + add_command /cluster/lib/cfstab + '[' -h initrd//cluster/lib/cfstab ']' + echo /cluster/lib/cfstab + xldd /cluster/lib/cfstab + i=/cluster/lib/cfstab + set +e + '[' ']' ++ LD_LIBRARY_PATH= ++ ldd /cluster/lib/cfstab ldd: /cluster/lib/cfstab: No existe el fichero o el directorio No such file or directory. Wierd. You said "cfstab left on this path". Do you mean that cfstab exists? Or that it does not exist? I will check to see where /cluster/lib/cfstab is supposed to be created. |
From: Sergi B. <hi...@li...> - 2009-03-19 10:47:35
|
John Hughes escribió: > Sergi Barroso wrote: >> John Hughes escribió: >>> Ok, you've got the right version of initrd-tools. >>> >>> Wait, I have some vague memories... >>> >>> Could you do >>> >>> dpkg -l | grep 64 >>> >>> Do you have some kind of amd64 library installed? That may be >>> screwing up ldd. >>> >>> Could you do: >>> >>> # /bin/sh -x 2>zz-initrd /usr/sbin/mkinitrd -o >>> initrd.img-2.6.12-ssi-686-smp 2.6.12-ssi-686-smp >>> >>> and send me the file "zz-initrd" (gzip it, it may be aound 100K). >>> >> No, I have no amd64 packages installed, I use 32 bit version. > Yes, you're right. That's not the problem: > > This is the problem: > > + add_command /cluster/lib/cfstab > + '[' -h initrd//cluster/lib/cfstab ']' > + echo /cluster/lib/cfstab > + xldd /cluster/lib/cfstab > + i=/cluster/lib/cfstab > + set +e > + '[' ']' > ++ LD_LIBRARY_PATH= > ++ ldd /cluster/lib/cfstab > ldd: /cluster/lib/cfstab: No existe el fichero o el directorio > > > No such file or directory. Wierd. > > You said "cfstab left on this path". Do you mean that cfstab exists? > Or that it does not exist? > > I will check to see where /cluster/lib/cfstab is supposed to be created. > These is all files inside /cluster/lib/ # ls /cluster/lib/ Clustertab.pm CVIP.pm ssi_arch.pm ssi_distro.pm ssi_mgmt.pm ssi_utils.pm -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
From: John H. <john@Calva.COM> - 2009-03-19 11:35:37
|
Sergi Barroso wrote: > John Hughes escribió: >> Sergi Barroso wrote: >>> John Hughes escribió: >> I will check to see where /cluster/lib/cfstab is supposed to be created. >> > These is all files inside /cluster/lib/ > > # ls /cluster/lib/ > Clustertab.pm CVIP.pm ssi_arch.pm ssi_distro.pm ssi_mgmt.pm > ssi_utils.pm > So, /cluster/lib/cfstab doesn't exist. This is bad. On my system: # dpkg -s /cluster/lib/cfstab mount: /cluster/lib/cfstab # dpkg -l mount Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=================-====================-=============================================== ii mount 2.13.1.1-1.ssi1 Tools for mounting and manipulating filesystems What version of mount do you have installed? What is in your /etc/apt/sources.list file? What is in your /etc/apt/preferences file? |
From: Sergi B. <hi...@li...> - 2009-03-19 14:23:04
|
John Hughes escribió: > Sergi Barroso wrote: >> John Hughes escribió: >>> Sergi Barroso wrote: >>>> John Hughes escribió: >>> I will check to see where /cluster/lib/cfstab is supposed to be >>> created. >>> >> These is all files inside /cluster/lib/ >> >> # ls /cluster/lib/ >> Clustertab.pm CVIP.pm ssi_arch.pm ssi_distro.pm ssi_mgmt.pm >> ssi_utils.pm >> > So, /cluster/lib/cfstab doesn't exist. This is bad. > > On my system: > > # dpkg -s /cluster/lib/cfstab > mount: /cluster/lib/cfstab > # dpkg -l mount > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) > ||/ Name Version Description > +++-=================-====================-=============================================== > ii mount 2.13.1.1-1.ssi1 Tools for mounting and manipulating filesystems > > > > What version of mount do you have installed? > > What is in your /etc/apt/sources.list file? > > What is in your /etc/apt/preferences file? > Yes, that's mount package probleme, thanks you, I modified apt prefrences after installed openssi, that's the problem, thanks! Now I can continue my config. Tnx again -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
From: Sergi B. <hi...@li...> - 2009-03-20 11:06:14
|
Sergi Barroso escribió: > John Hughes escribió: > >> Sergi Barroso wrote: >> >>> John Hughes escribió: >>> >>>> Sergi Barroso wrote: >>>> >>>>> John Hughes escribió: >>>>> >>>> I will check to see where /cluster/lib/cfstab is supposed to be >>>> created. >>>> >>>> >>> These is all files inside /cluster/lib/ >>> >>> # ls /cluster/lib/ >>> Clustertab.pm CVIP.pm ssi_arch.pm ssi_distro.pm ssi_mgmt.pm >>> ssi_utils.pm >>> >>> >> So, /cluster/lib/cfstab doesn't exist. This is bad. >> >> On my system: >> >> # dpkg -s /cluster/lib/cfstab >> mount: /cluster/lib/cfstab >> # dpkg -l mount >> Desired=Unknown/Install/Remove/Purge/Hold >> | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend >> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) >> ||/ Name Version Description >> +++-=================-====================-=============================================== >> ii mount 2.13.1.1-1.ssi1 Tools for mounting and manipulating filesystems >> >> >> >> What version of mount do you have installed? >> >> What is in your /etc/apt/sources.list file? >> >> What is in your /etc/apt/preferences file? >> >> > Yes, that's mount package probleme, thanks you, I modified apt > prefrences after installed openssi, that's the problem, thanks! > > Now I can continue my config. > > Tnx again > > Hi! This is the config of my cluster: The following configuration has been entered: Node number: 1 NIC for interconnect: eth1 IP address: 10.0.0.1 Network hardware addr: 00:11:95:D7:57:87 Network boot protocol: PXE Local boot device: UUID="a8b94708-85d6-46c8-be1a-34d01ba3f994" Clustername: test-cluster Root failover: No Potential initnode: Yes NFS support: yes Then I get this error: inding valid ramdisk creators. Using mkinitrd to build the ramdisk. /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed FATAL: Module skge not found. WARNING: This failure MAY indicate that your kernel will not boot! but it can also be triggered by needed modules being compiled into the kernel. cpio: initrd/lib/i686/cmov/libc.so.6 not created: newer or same age version exists cpio: initrd/lib/libcluster.so.0 not created: newer or same age version exists This command requires a CI/OpenSSI kernel. This command requires a CI/OpenSSI kernel. 6280+0 records in 6280+0 records out 6430720 bytes (6,4 MB) copied, 0,0196778 s, 327 MB/s FATAL: Could not load /lib/modules/2.6.26-1-686/modules.dep: No such file or directory mke2fs 1.40-WIP (14-Nov-2006) check_mntent_file: Can't open /proc/1/where check_mntent_file: Can't open /proc/1/where cpio: ./dev/ide: Cannot stat: No existe el fichero o el directorio cpio: ./dev/cciss: Cannot stat: No existe el fichero o el directorio cpio: ./dev/ida: Cannot stat: No existe el fichero o el directorio cpio: ./dev/md: Cannot stat: No existe el fichero o el directorio cpio: ./dev/mapper: Cannot stat: No existe el fichero o el directorio cpio: ./dev/scsi: Cannot stat: No existe el fichero o el directorio 9825 blocks /boot/initrd.img-2.6.12-ssi-686-smp.new: 69.7% -- replaced with /boot/initrd.img-2.6.12-ssi-686-smp.new.gz Running postinst hook script update-grub. After I reboots the system, on howto step 15 it halts on boot, after devfs problem message. Any help here? -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
From: Sergi B. <hi...@li...> - 2009-03-24 13:15:29
|
John Hughes escribió: > John Hughes wrote: >> Sergi Barroso wrote: >> >>> Using mkinitrd to build the ramdisk. >>> /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed >>> FATAL: Module skge not found. >>> WARNING: This failure MAY indicate that your kernel will not boot! >>> but it can also be triggered by needed modules being compiled into >>> >>> >> What ethernet card are you using for the cluster interconnect? It >> looks like it doesn't have a driver in our version of the kernel. >> >> (I'm guessing it's a "SysKonnect GigaEthernet") >> >> If that's the problem maybe I can backport a version of the driver >> for you. >> > Actually I don't think I need to backport anything. > > What do you have in your /etc/mkinitrd/modules? skge? > > Try replacing skge with sk98lin, our version of the kernel has the > older drivers. > Yes this is one of my problems, but not only, because after starts I can't login because PS2 or usb keyboard doesn't work.... -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
From: John H. <john@Calva.COM> - 2009-03-25 10:40:12
|
Sergi Barroso wrote: > John Hughes escribió: > >> Try replacing skge with sk98lin, our version of the kernel has the >> older drivers. >> >> > Yes this is one of my problems, but not only, because after starts I > can't login because PS2 or usb keyboard doesn't work.... > What have you got running at the moment? One node? With the sk98lin driver? But the keyboard doesn't work? Can you connect to the system via ssh? |
From: John H. <john@Calva.COM> - 2009-03-21 08:53:51
|
Sergi Barroso wrote: > Sergi Barroso escribió: > >> John Hughes escribió: >> >> >>> Sergi Barroso wrote: >>> >>> >>>> John Hughes escribió: >>>> >>>> >>>>> Sergi Barroso wrote: >>>>> >>>>> >>>>>> John Hughes escribió: >>>>>> >>>>>> >>>>> I will check to see where /cluster/lib/cfstab is supposed to be >>>>> created. >>>>> >>>>> >>>>> >>>> These is all files inside /cluster/lib/ >>>> >>>> # ls /cluster/lib/ >>>> Clustertab.pm CVIP.pm ssi_arch.pm ssi_distro.pm ssi_mgmt.pm >>>> ssi_utils.pm >>>> >>>> >>>> >>> So, /cluster/lib/cfstab doesn't exist. This is bad. >>> >>> On my system: >>> >>> # dpkg -s /cluster/lib/cfstab >>> mount: /cluster/lib/cfstab >>> # dpkg -l mount >>> Desired=Unknown/Install/Remove/Purge/Hold >>> | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend >>> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) >>> ||/ Name Version Description >>> +++-=================-====================-=============================================== >>> ii mount 2.13.1.1-1.ssi1 Tools for mounting and manipulating filesystems >>> >>> >>> >>> What version of mount do you have installed? >>> >>> What is in your /etc/apt/sources.list file? >>> >>> What is in your /etc/apt/preferences file? >>> >>> >>> >> Yes, that's mount package probleme, thanks you, I modified apt >> prefrences after installed openssi, that's the problem, thanks! >> >> Now I can continue my config. >> >> Tnx again >> >> >> > Hi! > > This is the config of my cluster: > > > The following configuration has been entered: > Node number: 1 > NIC for interconnect: eth1 > IP address: 10.0.0.1 > Network hardware addr: 00:11:95:D7:57:87 > Network boot protocol: PXE > Local boot device: UUID="a8b94708-85d6-46c8-be1a-34d01ba3f994" > Clustername: test-cluster > Root failover: No > Potential initnode: Yes > NFS support: yes > > Then I get this error: > > inding valid ramdisk creators. > Using mkinitrd to build the ramdisk. > /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed > FATAL: Module skge not found. > WARNING: This failure MAY indicate that your kernel will not boot! > but it can also be triggered by needed modules being compiled into > What ethernet card are you using for the cluster interconnect? It looks like it doesn't have a driver in our version of the kernel. (I'm guessing it's a "SysKonnect GigaEthernet") If that's the problem maybe I can backport a version of the driver for you. |
From: John H. <john@Calva.COM> - 2009-03-21 09:06:33
|
John Hughes wrote: > Sergi Barroso wrote: > >> Using mkinitrd to build the ramdisk. >> /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed >> FATAL: Module skge not found. >> WARNING: This failure MAY indicate that your kernel will not boot! >> but it can also be triggered by needed modules being compiled into >> >> > What ethernet card are you using for the cluster interconnect? It looks > like it doesn't have a driver in our version of the kernel. > > (I'm guessing it's a "SysKonnect GigaEthernet") > > If that's the problem maybe I can backport a version of the driver for you. > Actually I don't think I need to backport anything. What do you have in your /etc/mkinitrd/modules? skge? Try replacing skge with sk98lin, our version of the kernel has the older drivers. |
From: John H. <john@Calva.COM> - 2009-03-19 10:05:38
|
Sergi Barroso wrote: > John Hughes escribió: > >> Sergi Barroso wrote: >> >>> Finding valid ramdisk creators. >>> Using mkinitrd to build the ramdisk. >>> ldd: /cluster/lib/cfstab: No existe el fichero o el directorio >>> mkinitrd failed to create initrd image. >>> Ok, the problem is that you have libc6-amd64 installed. That screws up ldd for some reason. I'm reporting this as a bug in the lenny libc6. Script started on Thu 19 Mar 2009 11:00:48 AM CET lenny-node1:~# ldd /cluster/lib/cfstab ldd: exited with unknown exit code (126) lenny-node1:~# dpkg --purge libc6-amd64 (Reading database ... 88427 files and directories currently installed.) Removing libc6-amd64 ... Purging configuration files for libc6-amd64 ... lenny-node1:~# ldd /cluster/lib/cfstab not a dynamic executable lenny-node1:~# exit Script done on Thu 19 Mar 2009 11:01:22 AM CET Just purge libc6-amd64 and it should work. |