[Yaird-devel] Booting fails after moving to another hardware: unable to find root partition

[Reiner Benedikt Nix]

Hi,

Thanks for your response.

Problem for using dpkg-reconfigure: as on the new hardware the system is yet 
not running, regeneration cannot determine the targent hardware and vice 
versa :-(

Fo me it was sufficient to regenerate the initial ram disk manually. Of course 
I need the SATA driver to access the hard disk. Otherwise it seemed to be 
enough to just changing the root partition name. Funtunately, the generated 
initial ram disk has a very clear structure, so applying the change could be 
done easily.

It would be nice, if the root partition name passed as boot parameter could be 
used. This would be helpfull as I use to make copies of the root partition 
for backup purpose, regularly on the same hardware but on another hard disk.

Reiner

> > after moving the contents of my root partition to another host,
> > the root partition ist not found while booting.
> >
> > What is the best practice to get the host booting?
> > Probably, I need to create a new inital ram disk, how to do this in
> > this environment?
>
> Sorry for the late response.
>
> This is a known limitation of yaird: The initial ramdisk is optimized
> for your current hardware setup only. So if changing things around you
> need to regenerate your ramdisk (easiest done with the command
> dpkg-reconfigure linux-image-2.6.15-1-486 (or whatever the name of your
> kernel package).
>
>
>  - Jonas