Bug#305230: workaround does work (for sarge errata?). A precision.
Just to be most precise.
On Sun, May 15, 2005 at 06:43:09PM +0200, lehobey wrote:
> On Thu, Apr 21, 2005 at 11:23:37PM -0700, Blars Blarson wrote:
> > In article <20050421142818.GA3820@melusine> Frederic.Lehobey@free.fr writes:
> > >> > We tried to install RC3 on an Ultra5 machine. It failed with both kernels.
> > >> > VFS: Cannot open root device "hda2" or 03:02
> > I've seen this on one of my ultra 5's before they both decieded to die.
> > I think it's a reoccurance of the silo initrd loading bug (or something
> > related) that can be worked around by changing the memory configuration.
> > What memory configuration do you have? What CPU speed? If 4 sticks,
> > try removing 2. If 2, try moving to the other pair of slots. (Mine
> > had 4x32M, d-i worked with 2x32M in slots closest to disk. After
> > install the system booted fine with all 4 sticks.)
> Your workaround (removing the 2 x 64 MB sticks) worked both times.
> Installation is successful with the following steps:
> 1/ netinstall with RC3 (netboot) default 2.4 kernel and default
> partitioning (all system in one partition). Still with 384 MB (4
> After first reboot failure with:
> VFS: Cannot open root device "hda2" or 03:02
> 2/ Removal of 2 sticks (128 MB), now only 256 MB (2 sticks).
Actually, the 2 sticks we have removed were the ones on the left slots
on the mainbord (same as you did). We have left the two most external
ones (closest to disk on Ultra 5).
> 3/ Reboot and successful completion of second step installation.
> 4/ Switch off the machine and put back of the 2 previously removed
> 5/ After power up, the machine now works properly with 384 MB (kernel
> I believe this workaround deserves at least an explanation in the
> release notes (errata).
Thanks again and best regards,