*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
We had the issue with two more servers today, one of them did not have a
separate /var partition.
The real reason for the immediate death of the boot process was
/etc/default/locale which contained the line
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Ah, I see. I must have misunderstood your post, sorry. It is interesting
and disturbing that there seem to be so many conditions that could
result in a server not booting correctly.
--
kernel 2.6.32-32 makes
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Andreas, please note that I did not report a mount problem but (suspectedly)
some sort of a race condition.
Pressing 's' or 'm' did NOT help in our case either! - Presumably because
ureadahead hung itself up
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Fionn, glad you solved your problem, but it is not this particular
problem.
I want to remind everyone that any kind of mounting problems have
nothing to do with the issue this bug report describes, namely tha
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
See also: bug #638228
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Oh, well, for the records:
We encountered this problem with linux-image-2.6.32-24-server.
It seems to have been fixed by moving /var up to the top in fstab.
--
kernel 2.6.32-32 makes machine hang during boot
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Do you happen to have /var on a separate partition?
If yes, try moving the /var entry in fstab up to the top and let us know if it
helps.
I suspect this has to do something with like ureadahead in initialisa
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
I agree with Andreas, the fstab setup we are using here, is the default,
and only contains local disks. Further more I see no such error message
as "mountall: Filesystem could not be mounted: ...".
We still h
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Thanks for the update Andreas. Glad to hear that the 2.6.32-24 server
kernel isn't causing any more problems for you.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
This bug is not a duplicate of #571444. At least not in the
characteristic that I and others who reported here have experienced it.
My /etc/fstab was always in the pristine state that is the result of a
fresh
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
** This bug has been marked a duplicate of bug 571444
Boot hangs and unable to continue when automount disk in fstab is not
available (Off or Disconnected)
* You can subscribe to bug 571444 by following t
Thanks for the info Thomas. I wonder what the difference between the
-server and the -generic kernels are that could be causing the machines
to hang.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a memb
Experiences the exact same problem here, with an clean install + apt-get
dist-upgrade. Seem to have problems with both the 2.6.32-21-server and
2.6.32-24-server. However using the 2.6.32-24-generic seems to work
fine, as others described. The server is also the HP Proliant DL380 G6.
Also have a HP
First I had the 2.6.32-21-generic-pae and now, after an dist-upgrade to
2.6.32-24-generic-pae the problem seems to be solved. I'll continue
rebooting the server to see if it keeps coming up or crashes again.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
Chiming in again I am cautiously optimistic that with the latest -server
packages (-23 and recently -24) the problem went away. I have installed
and upgraded two identical DL380 G6 servers and performed many
consecutive reboots since and have yet to experience any hangs. I just
rebooted one of the
Which version of the -server package do you have? And have you yet
performed a dist-upgrade to get the latest -server packages?
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I experienced the same problem. I have an the following server
configuration:
HP DL380 G3
2 x Intel Xeon 2.8GHz
6GB RAM
6 x 36.4GB SCSI in a RAID5 array (no spares)
I did a standard installation (checked the OpenSSH server so I installed
software) and did an apt-get update and apt-get upgrade. I
I'll just add that this is also a problem for me on an HP DL380G6 on
10.04 LTS server. Typically I eventually get in after several reboots,
although I'm having trouble on this last go round.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received thi
Thanks Andreas. I've filed a bug report about the "no error message
being displayed" part.
Keep us updated. :-)
I'm just glad I figure out why my server would appear to hang, and I
hope that the problem has been fixed for you.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.laun
Charles, that's definitely a bug. I believe there have been efforts in
Plymouth to fix it but you need to the splash screen for those error
messages to be displayed. A default server install, or one where the
kernel is instructed to boot with as much text output as possible
(GRUB_CMDLINE_LINUX_DEFA
Upgraded to 2.6.32-24-server after commenting out the RAID array in
fstab, rebooted into the new kernel and built the drivers, then mounted
the array without any problems.
Is it a bug that there is no error message displayed when the OS cannot
find a device listed in fstab?
--
kernel 2.6.32-32 m
Tried the same test with Lucid Desktop i386, and the same thing
happened, except that it prompted to hit "s" or "m."
See attachment.
I don't really want to have to comment out any entries in fstab before I
upgrade the kernel, especially if I don't have physical access to the
machine to hit "s" if
I did a clean install using the x64 version of Lucid, kernel 2.6.32-31.
The only thing I did before upgrading to the new kernel (2.6.32-32) was
build the drivers for my RAID card (Highpoint Technologies RocketRAID
2640x1) and added an entry to fstab to mount the array on boot.
It's now sitting at
We have USB-attached hard drives so that would add another line to
fstab. Does anyone know if the -server build has behaviour changes when
it comes to fstab mount points?
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification b
I just stumbled across a thread that mentioned having Ubuntu hang if
there is something other than /proc, / and swap were in fstab:
http://ubuntuforums.org/showthread.php?t=1480113
I don't know if that was the case for me, since I added my RAID array to fstab
before I upgraded to the new kernel
jgreenso, I will try a -generic kernel image hopefully next week or the
week after that, when I get my hands on one of the machines on which we
experienced the problems.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification be
I've changed the status given there's no evidence that the problem has
been identified yet alone a fix released.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Andreas, have you tried a -generic kernel build? That's what's working
on our two 10.04 servers, the -server kernel causes the problem for us.
** Changed in: linux (Ubuntu)
Status: Fix Released => Incomplete
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bug
Charles, I'll be trying your idea as soon as I get one of the machines
back (next week probably). Maybe I can find some pattern :)
But I really don't think this is in any way "fixed". All we know is that
there are at least five people affected by it and no solution has been
posted or linked to oth
Ah I see. I usually just use apt-get upgrade for regular package
upgrades and dist-upgrade to get new kernels. I've not really used
aptitude much, if at all. Thanks for the info on that.
Only thing that I know is that it worked when I did a dist-upgrade after
a clean install and without installing
Charles, thanks for the reply. I do not use dist-upgrade for regular
package upgrades. However there should not be any difference between
dist-upgrade (full-upgrade) and safe-upgrade in this case. The kernel
package gets updated either way.
So you don't seem to see any problems even after a few co
Andreas:
I rebooted a few times a while ago, within 30 minutes of each other,
then 8 hours later without any problems.
Here's my uprecords so far:
char...@thor:~$ uprecords
# Uptime | System Boot up
+-
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
I just want to add that I unfortunately have not been able to test this
further (not even using -generic instead of -server kernels) since the
machines in question needed to go into production. We went back to
Ubuntu 9.10 for that. If I'm lucky I can maybe get one or two of these
machines back in p
Jeremy,
Yeah, it's completely up-to-date and has been booting fine. I just don't
know why it had a problem when I went to do the kernel update when I had
packages already installed.
It's been up for around 48 days total (ever since May 5th, when I did
the clean install and dist-upgrade) with peri
Charles,
I'm glad you were able to get it to a known good state. Are you still
updating regularly. and is the machine still booting normally?
Thanks!
~JFo
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because yo
Thanks for replying Jeremy.
I stopped messing with the machine after doing an apt-get dist-upgrade
(after a clean install) and before installing any other packages caused
the problem is not occur. So far, I haven't had any other issues since
then.
--
kernel 2.6.32-32 makes machine hang during bo
jgreenso,
Apologies for the delay. Our process is to verify if there is a difference
in behavior using a generic upstream build of the kernel with only minimal
ubuntu configs added. This enables us to see if there is a commit from stable
that resolves an issue and can be included in kernel up
Almost two weeks since the last comment, the status of this bug remains
'Incomplete'.
It would be good to know what tests are needed to make it 'Complete'.
Presumably someone maintaining the packages may hold a clue as to what
to look at?
Unfortunately our machine has now had to go into productio
Interesting, I hadn't tested using non-server kernel images. Thanks for
the suggestion jgreenso, I'll be trying that on our problematic
machines.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member o
Jeremy: You're asking those affected to test the latest upstream kernel
build. I've looked, and I can only spot -generic builds.
Are you asking us to test this specifically, given we seem to be working
fine with the current released version of -generic anyway? It would seem
more reasonable to have
I think I just reported this bug too - if someone feels confident enough
that we are all in the same boat please mark mine as a duplicate of
this.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588799
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
I just went through that whole mess again and reinstalled one of the
machines. Unfortunately to no avail. Installation went speedy and fine,
aptitude update and aptitude safe-upgrade as well (this includes
installation of the new kernel image), rebooted three or four times and
now it hangs again. I
Wish we had some direction as to what information was needed to help
narrow this down. I was able to get mine back up and running after a
clean install, but I am a bit reluctant to do any kernel upgrades for
the time being, as I don't want to have to go thru that whole mess
again.
--
kernel 2.6.3
Charles, this is exactly what I did in the first place. Clean install of
Ubuntu 10.04 Server, then upgrade to -22-server kernel. More often than
not the system would not come up correctly, as described above.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/57600
Andreas Ntaflos:
Does the same hanging happen if you do a clean install, then upgrade to
the -22 kernel?
Trying to see if the same workaround that worked for me, works for you.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notifi
This is becoming a bit scary. I have continued experimenting with the HP
DL380 machines I have here and even now even the even with the kernel
image 2.6.32-21-server makes the machine hang.
I can still SSH into it and look at the process list, see attachment.
Does anything in there look suspicious
I have had this same issue as well.
After it happened the first time, I did a clean install. I ran apt-get
safe-upgrade to get the kernel updates. Installed mdadm and set up my
raid 6 array without problems. Edited my /etc/mdadm/mdadm.conf and
/etc/fstab files to automatically assemble and moun
Those are the same symptoms that I experienced. Only difference is that
I wasn't able to connect via SSH (the box is running Samba, BIND9, DHCP3
and SSH, and a few other stuff, virtualbox for one).
Ctrl+Alt+Del to force a reboot was recognized and halted all the
processes and rebooted the machine.
I don't think this was a fluke.
Reading the description and the symptoms this seems exactly what we have
been experiencing on three of our HP DL380 G6 servers. These three
server are identical (modulo disk capacity) and serve as our test beds
for Ubuntu Server 10.04 (freshly installed as of yester
After getting back into a workable system I backed up everything and
then did a clean reinstall.
apt-get dist-upgrade to get the new kernel and I now have a logon
prompt. I guess it might have been a fluke, or maybe caused by one of
the packages I had installed.
Any way to narrow it down?
** Ta
I try using the kernel located here: http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.33.1-lucid/linux-
image-2.6.33-02063301-generic_2.6.33-02063301_amd64.deb
Tried installing the headers as well, but it failed with "missing
dependencies."
As for right now, I am unable to even access GRUB, si
Hi Charles,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the 'needs-upst
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/47892247/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/47892248/BootDmesg.txt
** Attachment added: "Card0.Codecs.codec.2.txt"
http://launchpadlibrarian.net/47892249/Card0.Codecs.cod
54 matches
Mail list logo
