Array CD 3, "HEAD" (and, probably, Array CD 4) hal issues

[Matt Zimmerman]

On Sun, Feb 06, 2005 at 12:00:21PM +0100, Shot (Piotr Szotkowski) wrote:

> Ok, I'm attaching the /var/log/kern.log file. Can you tell, by looking
> at it, whether it's one of the bugs you mentioned or should I file a new
> one?

OK, I see the problem.  This is a known bug, but it may not be filed in
Bugzilla yet.  Sometimes, the udev infrastructure seems to get into a loop,
and a huge number of udev processes are spawned.  This seems to be what is
causing your slowdown.

There seems to be a race condition involved, which is why this does not
happen every time.

I've opened this bug:

https://bugzilla.ubuntu.com/show_bug.cgi?id=6235

if you create a Bugzilla account, you can assist us in the troubleshooting
effort there.

> > A copy of /var/log/debian-installer/syslog
> > from your system might be enlightening,
> 
> Attached.
> 
> > but please provide precise details about what actions you
> > took in the installer, and what error messages you saw.
> 
> With Array CD 3, I booted with server-expert and in the partition stage
> I chose multiuser workstation. This resulted in a couple partitions,
> all of them (except swap) set to ext3. I changed them to ReiserFS and
> installed the system without a problem.
> 
> With Array CD 4, the same course resulted in a "GRUB cannot be
> installed, continue?"-kind of error in the bootloader installation
> stage (even before trying to put GRUB in the MBR). The same happened
> when I tried installing LILO.

Ah, I see.  So the grub package actually failed to install, as opposed to
grub failing to install itself in the MBR.

Please file a bug in Bugzilla, using component 'grub-installer'.

> When I went back to the partitioning stage and changed the partition
> with the / mount point to ext3 (and left all of the rest at ReiserFS)
> GRUB installed without a problem and made its way to MBR flawlessly.

I find it very strange that changing the filesystem fixed this.  Did you see
anything on console #3 at this point?  If so, include details in your bug
report.

-- 
 - mdz