Mark Gray wrote:
juergen.braukmann@ruhr-west.de writes:
Hello Mark, thanks for comming back on my request... ;-)
Hi,
I am in a kind of frustrated mood. My nice had some troble with the 6.2 installation I made, so I decited to upgrade to 6.4 and give her another harddrive.
I installed the system on my machine -since it is faster- (mounted as hdc), this resulted in some other modules for initrd and USB support that wasn't on the other system.
After which you installed the disk as hda on her system. (?)
yes. And the old (somehow I didn't trust it) 1GB is now hdb.
After repairing lilo.conf I tried to reboot and ended in "unable to mount root fs on 16:07" after rebooting.
This is /dev/hdc7 ---> you did not successfully inform lilo of the new location of your root partition?
well thanks for that, that clarifies it a bit. I thought 16:07 is something like major-minor number, but on the system I installed it (this) hdc7 is 22, 7. I am thankful for that hint, I might have overseen repeatedly something like hda7 versus hdc7. I will have a look.
I could however boot the installed system via CD (boot installed system)
You did remember to run lilo after fixing lilo.conf? (And do so on the new system?) What partitions are on the new disk? If boot is on
countless times. Yes I am aware of that, since I failed to do so a few times in the past.
a seperate partition you may have to have /boot and / mounted when you run lilo -r /mnt from the rescue cdrom
hmm. didn't use the rescue system, just "booted the installed system". Anyway, worth looking at.
I knew this error from my first kernel baking attempts -having a SCSI controle and a nice configured module ;-) - but this time I use the default kernel (tried the special IDE on as well) that works well with *this* system.
I might be overseeing something obvious, but remail clueless. Have a heart, I am her great guru ans have a reputation to loose. My frustration does not anybody help any further. HELP HELP PLEASE!!
Hope this helps.
Well, it's a start. Frustrating is that my reliable system fails and I do not realy know why. Had *fun* with NT today, learned that if I remove the CDROM on one system it will BSOD on the next reboot. I have the nasty feeling Linux is starting those bad tricks on me as well... Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq