2012/11/27 Vincent Miszczak <vmiszczak@ankama.com>

Hi,

 

I have the exact same problems with the latest 2.5.5-0.1.

 

1.       I’m unable to install from USB stick because after installation, the system does not find it’s root volume.

2.       Using a CDROM, the installation hangs. First time it hanged at 75%. Second time I tried, it hanged at 25%. No message at all, but keyboard is responsive (lock num, console switch).

 

I could try to do some debug for you. Having the root account used during the installation would help. What is it?

 

With the CDROM installation, I’ve tried with 2 different hard drives and the server was running fine with its previous OS, so no hardware issue here.

I was running the installation on a Poweredge 1950 server.

 

Vince

 

De : users-bounces@ovirt.org [mailto:users-bounces@ovirt.org] De la part de Alexandre Santos
Envoyé : jeudi 11 octobre 2012 22:57
À : Mike Burns
Cc : users@ovirt.org
Objet : Re: [Users] ovirt-node install hangs

 

 

2012/10/11 Alexandre Santos <santosam72@gmail.com>

2012/10/11 Mike Burns <mburns@redhat.com>

On Thu, 2012-10-11 at 11:12 +0100, Alexandre Santos wrote:
> Hi,
> yesterday I tried the new oVirt Node 2.5.3. I tried installing it
> without the quiet flag but no luck. It hanged again and the kernel
> didn't show any error on console (tty2).
> Later will test without the rhgh flag.

Default options? TUI install? Hardware? UEFI or legacy bios?


I always choose the troubleshooting option and then do an install with basic video. The only thing I changed from the default kernel boot line was the quiet flag.

Yes, TUI.

Hardware: this is an old MSI P35Neo MB with 4 GB RAM and a Xeon 3040. The SATA disk is connected to the onboard controller. The same problem occurred with an IDE HDD.


Without rhgb and quiet no luck at all. Tomorrow will try with a SATA PCI Card with a Sil chip.
 

 


>
> Alex
>
> BTW, now the hostname works on 2.5.3 :-) The network configuration is
> still tricky... sometimes I have an "Apply" sometimes only a "Back"
> choice.

I *think* this is a feature of being registered to ovirt-engine.  Once
you are registered, you can't change the network through the TUI
anymore.

If you're not registered with Engine, please elaborate a bit and I'll
try to figure out what is going on.


What you're saying makes sense. The problem I had was that my node was booting with DHCP and the IP changed. When I got to the engine / web administrator, my Host was not detected and I couldn't change it's IP, only the hostname... On the TUI I can't change the IP because I'm registered but can't change it also on the engine. Is this correct?


Mike


>
> 2012/10/9 Alexandre Santos <santosam72@gmail.com>
>         It's working now :-)
>
>         Thanks a lot all!
>
>         Alex
>
>         P.S. I haven't tried installing it on my SATA disk because I
>         have there a Local Node already running but I'm going to try
>         again on another one to see if I can send to you the error
>         log.
>
>
>         2012/10/8 Mike Burns <mburns@redhat.com>
>                 On Mon, 2012-10-08 at 09:54 +0100, Alexandre Santos
>                 wrote:
>                 >
>                 >
>                 > 2012/10/8 Fabian Deutsch <fabiand@redhat.com>
>                 >         Am Montag, den 08.10.2012, 09:24 +0100
>                 schrieb Alexandre
>                 >         Santos:
>                 >         > 2012/10/8 Fabian Deutsch
>                 <fabiand@redhat.com>
>                 >         >         Hey,
>                 >         >
>                 >         >         Am Sonntag, den 07.10.2012, 15:29
>                 +0100 schrieb
>                 >         Alexandre
>                 >         >         Santos:
>                 >         >         > Hi,
>                 >         >         > I'm trying to install the
>                 ovirt-node iso image on
>                 >         a SATA
>                 >         >         disk and when
>                 >         >         > it gets to the screen where it
>                 shows 25% completed
>                 >         the
>                 >         >         kernel hangs. I
>                 >         >         > can't connect using a serial
>                 console to see what
>                 >         has
>                 >         >         happened. If I
>                 >         >         > reboot using a usb linux disk I
>                 see that the SATA
>                 >         disk has
>                 >         >         been
>                 >         >         > formated and the partitions that
>                 existed before
>                 >         disappeared,
>                 >         >         being
>                 >         >         > there just one partition of type
>                 "ee"
>                 >         >
>                 >         >
>                 >         >         Is there any error displayed when
>                 kernel hangs at
>                 >         25%? And it
>                 >         >         can take
>                 >         >         some time to pass the 25% (up to
>                 ~2min or so).
>                 >         >
>                 >         > No, I think it's a kernel hang because the
>                 lights on the
>                 >         keyboard halt
>                 >         > and I can't change to tty2, etc.. I even
>                 changed to tty2 and
>                 >         waited to
>                 >         > see if there were some errors but nothing.
>                 I've read that
>                 >         "tty8" was
>                 >         > the logging console but no luck also.
>                 >         > BTW, I tried with an IDE disk and the
>                 result was the same.
>                 >
>                 >
>                 >         Mh, okay.
>                 >         Could you try booting without the rhgb and
>                 quiet kernel
>                 >         arguments. I
>                 >         hope that some errors will be displayed on
>                 the screen so we
>                 >         get an idea
>                 >         about the problem.
>                 >
>                 >         >
>                 >         >         > If I use a 8 GB usb pen-drive
>                 instead of the SATA
>                 >         disk, the
>                 >         >         > installation comes to an end and
>                 I reboot but then
>                 >         I get
>                 >         >         some error
>                 >         >         > about not
>                 getting /dev/mapper/by-name/Root and the
>                 >         boot
>                 >         >         fails to a
>                 >         >         > dracut shell.
>                 >         >         > Any ideas?
>                 >         >
>                 >         >
>                 >         >         In the dracut shell, could you run
>                 blkid and post
>                 >         the results?
>                 >         >
>                 >         > I noticed that the USB Disk was named
>                 RootBackup instead of
>                 >         Root... I
>                 >         > then rebooted and chose uninstall and then
>                 installed oVirt
>                 >         Node from
>                 >         > scratch and now it worked.
>
>
>                 Glad it worked the second time.  There should be 4
>                 partitions on the
>                 disk.
>
>                 Partition 1 is for UEFI or bios_boot depending on your
>                 machine type.
>                 Partition 2 and Partition 3 are Root and RootBackup.
>                  So seeing a
>                 RootBackup is correct.  Not seeing a Root is
>                 incorrect.  If you rebooted
>                 the host in the middle of the install, or if the
>                 install hung for some
>                 reason, I can see that situation happening and see it
>                 working after
>                 uninstall/install.
>
>                 >         > I can't activate Networking because I have
>                 that "no
>                 >         hostname" error
>                 >         > mentioned in another post. I think it's
>                 related to that...
>
>
>                 You can't activate networking at all?  That is news to
>                 me.  The node
>                 should work perfectly fine with or without a FQDN.
>
>
>                 >
>                 >
>                 >         Yes, I've also seen the hostname error. And
>                 I've also seen
>                 >         some problems
>                 >         with the rootfs lately.
>
>
>                 Have you seen these issues with the 2.5.2 build?  Or
>                 only master branch
>                 builds?
>
>                 >         Could you provide a screenshot/dump of the
>                 console with that
>                 >         error?
>                 >
>                 >         - fabian
>                 >
>                 >
>                 > Ok! I'll send them as soon as possible.
>                 >
>                 > Alex
>                 >
>                 >
>
>                 > _______________________________________________
>                 > Users mailing list
>                 > Users@ovirt.org
>                 > http://lists.ovirt.org/mailman/listinfo/users
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

 



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

I had the problem you mentioned about not finding the root volume. It's a Fedora issue that you can solve on the boot, changing the root to /dev/sr0, for instance.

About the setup hanging, I had a kernel panic (I think), because my keyboard stopped responding.

Alex