LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)
-   -   installation problem of mandriva after changing PC (https://www.linuxquestions.org/questions/mandriva-30/installation-problem-of-mandriva-after-changing-pc-486296/)

Nafcom 09-23-2006 01:16 PM

installation problem of mandriva after changing PC
 
I have already searched in google and in the mandriva irc but yet found no answer. Actually, I even made a break of one year because I put so much energy and time in my installation and configuration of my Mandrake, I do not want to re-do all. NO CHANCE

Well, due to various reasons, I had to put my Mandrake HDD into another PC.
And I wanted to update its installation (I just downloaded today Mandrake 2007 Free and also tried with earlier versions before).

So far no problem, it recognizes the previous installation finds it and offers me to update, great so far, but unfortunately due to the fact that the pc in which the HDD has been had 4 HDDs, it cannot find the other drives/partitions and skips with "cannot find [path]" ([path] = path of the partition)
So how can I skip this test/mount of the old partitions/drive or correct that info so the installer will continue?

Well, I am no Linux expert unfortunately so I do not know how I can fix this problem, hope anybody can help!

Thanks in advance!

jchance 09-23-2006 02:38 PM

Honestly just install a fresh copy onto the drive. You won't probably be able to do an update and I wouldn't be surprised if you had one of your necessary partitions on one of those other drives.

Nafcom 09-23-2006 02:52 PM

Quote:

Originally Posted by jchance
Honestly just install a fresh copy onto the drive. You won't probably be able to do an update and I wouldn't be surprised if you had one of your necessary partitions on one of those other drives.

No, they all were on only one drive, I can promise you.
I did this "one HDD for one OS" very stricktly.

Anybody a solution please? There must be a way so it skips the other drives/partitions (and they only had windows data) or edit a file so that it won't search for the other nonexisting drives/partitions.

Nafcom 09-23-2006 09:21 PM

Thanks to a colleague who I met and told me: I simply had to edit the /mnt/etc/fstab file and put a comment (#) infront of each old HDD and CDROM entry. Now it works and it's updating.

.......Update has been done and now it says at configurating the boot loader (LILO):

"no such device, hda2"


So what's next, please? :)

Thanks in advance!

Linux is by the way on hdb5

GlennsPref 09-23-2006 11:27 PM

If you can, reinstall the kernel and it will configure lilo for you.

Find the path to the kernel(ver).rpm, like if it's on cd,

Then from a console type, rpm -ivh kernel-(your version).rpm

These switches might help (--force --nodeps).

Nafcom 09-24-2006 06:18 AM

Quote:

Originally Posted by GlennsPref
If you can, reinstall the kernel and it will configure lilo for you.

Find the path to the kernel(ver).rpm, like if it's on cd,

Then from a console type, rpm -ivh kernel-(your version).rpm

These switches might help (--force --nodeps).

Thanks! Allow me the question, please: Isn't it easier to re-configurate LILO? (Not that I know how) and isn't that what the Update installation probably did already too (and didn't work obviously)?
From what I know re-installing kernel can be tricky and how do I know which one to install

GlennsPref 09-24-2006 09:03 AM

Yes it is easier and much faster, but you'll need to read man-lilo and man-fstab

x86_64 is for 64bit AMD chips

i586 is for current 32bit pentium and AMD

smp is for symetrical multi processors but the old way, used for data servers

i386 will work for most of the PC types.

ppc is for apple macintoshes

there are usually versions for solaris and in some instances digital electronics corp

Some times it is just easier to write over the old setting from something you know is a good source.

Maybe if you just reinstall the same way you upgraded

Nafcom 09-24-2006 09:31 AM

Quote:

Originally Posted by GlennsPref
Yes it is easier and much faster, but you'll need to read man-lilo and man-fstab

x86_64 is for 64bit AMD chips

i586 is for current 32bit pentium and AMD

smp is for symetrical multi processors but the old way, used for data servers

i386 will work for most of the PC types.

ppc is for apple macintoshes

there are usually versions for solaris and in some instances digital electronics corp

Some times it is just easier to write over the old setting from something you know is a good source.

Maybe if you just reinstall the same way you upgraded

Thanks!

Reinstalling is really no option. I need to say it's virtually the same PC., but I had to put the Win HDDs and 1 drive in an other pc.

Anyway, I have done what you said (entered rpm -ivh kernel-(your version).rpm --force --nodeps) what I got was this:

"kernel -2.6.17.5mdv-1-1mdv2007.0.i586.rpm

Headeer V3DSA Signature nokey key 1026752624
prepairing: .... 100%
1: kernel -2.6.17.5 ... 100%

error: unpacking archive failed on file /boot/System.map.2.6.17.5mdv;5416afc2 cpio mkdir failed no such file or directory"

:confused:

GlennsPref 09-24-2006 09:00 PM

I'd say there was something wrong with the package, can you do a check with MD5 sum?

My suspicion was the that file may have been corupted in some way.

You will need to get another copy, you may be able to urpmi it across the web.

Nafcom 09-24-2006 10:05 PM

Quote:

Originally Posted by GlennsPref
I'd say there was something wrong with the package, can you do a check with MD5 sum?

My suspicion was the that file may have been corupted in some way.

You will need to get another copy, you may be able to urpmi it across the web.

I assume it's the drive, because it died right after. I will get a new one Tuesday (at leats I plan to).

Will anyway do a MD5 check. on another PC.

Once I got a new drive, I will try again and report back :)

GlennsPref 09-25-2006 12:32 AM

That could certainly have been the cause,

Nafcom 09-25-2006 07:49 AM

Quote:

Originally Posted by GlennsPref
That could certainly have been the cause,

Yeah, I will get a new one tomorrow.
Before I try your suggestion (thanks), please allow another question:

Since the boot manager currently points to the wrong place, wouldn't reinstalling the kernel just rewrite the boot manager with the same wrong information, or will it detect that the current config is wrong and autodetect the correct place and change it automatically?

Thanks in advance!

I would like to understand why this is supposed to fix it.

Nafcom 09-26-2006 10:03 AM

Quote:

Originally Posted by GlennsPref
That could certainly have been the cause,

I have tried it with the same kernal as above, even tried the enterprise, still error at mkdir, so it's not the DVD and not the drive (but the old one is dead anyway!), as I got a new one today.

I got suggested on another place to edit /etc/grub or lilo I have neither any grub nor any lilo files there
I only can find /mnt/grub showing stage, example and gz files.

Maybe this info helps also: I selected back then to install the boot loader on disk

EDIT: I found out, I can type in "grub" and grub's "editor" starts, however doesn't matter which command I enter, it says "unrecognized device". Maybe this helps


I also had a look at the boot loader config with Mandriva One.
First I looked at the partitons and figured out that none had a mount point, so I set them each to /mnt/*

Then configurating boot up:
This happened: "No boot loader installed", do you want to configure one?"
Then with Grub I get the following error:

"installation of Bootloader failed
Fatal: Trying to map files unamed device 0 x 000f (NTFS/RAID) maybe off?).

Grub just says: "installation of Bootloader failed Checksum error" 5 times in a row".


All times are GMT -5. The time now is 02:06 AM.