Quote:
Originally Posted by jefro
I'd be more inclined to think that the boot up files may have some values that need to be changed.
|
Which ones specifically? I changed the drive identifiers in the initrd from uuid to standard sdx type, which should make it more general. No luck with that.
Quote:
Originally Posted by jefro
Either boot to a live cd or boot and see if you can install.
|
The thing is that I don't want to reinstall the system. Since my debian systems seem to have no problems with travelling between completely different motherboards, I assumed this will be the case with the SuSE system as well. Unfortunatelly no.
Quote:
Originally Posted by jefro
Also, you can't trust any of the data on that drive.
|
And why is that? As I said, it was tested for errors (quite thoroughly actually), and no errors what-so-ever were detected.
Also, after inserting the HDD to a computer where the chipset is identical to the chipset of the dead motherboard, the system boots w/o problems. This is why I think it is a driver related problem. I think the initrd image simply lacks the needed driver to operate the hdd controller of the new MoBo, thus it is unable to mount any partitions.
So the question remains: how to regenerate the initrd image so that it contains a much wider spectrum of drivers? Right now, the image file only includes a very small amount of drivers (I extracted it and checked the contents), which is definitely a problem.