I've upgraded from 2010.2 to 2012.

I've completed the installation and have run urpmi update, and urpmi states that the system is up to date.

The desktop will start up but it takes several minutes. When I get to the boot menu and select 2012, the boot process starts but gets stalled at a screen that says:

The system will pause at this screen for 5-10 minutes and then seemingly continue to boot normally to the desktop, where everything seems to work.

Does anyone know what's causing the problem with this?

Upgrades are pron to failure. Clean installs are the way to go. That said, it is your choice to fix the upgrade, or format the root partition, and do a clean install.

If you decide to fix it, autofs and ipv6 are kernel modules the system is not finding. The upgrade process has not installed the modules. You can go into MCC and install software and search on autofs, and install what you find not installed, and the same with ipv6. Hopefully that will fix those problems.

The last one, I would go into MCC again, and look for the firewall settings. I guess the question is, do you need a firewall on your system? If you have one in a router, probably not. If this is the only firewall you have, then yes.

I would google the error, and see what you can find. Probably something is not installed; as with the earlier errors. As I remember it, Mandy has more than one firewall option. Try one of the others.

Best of luck.

Well, I do prefer clean installs, but since this is my home file server I had hoped the upgrade to 2012 would be fairly painless and save me from having to backup my home directory configurations and multiple other config files (xorg, samba, fstab, etc.). If I can't repair this install then my next move will be a clean install of 2012.


This part didn't make sense to me, and my thinking was that this is the result of a left-over config file rather than missing modules. I say that because, if I did a complete upgrade and urpmi is reporting that all packages are up to date, how is it that I am missing modules? When the 2012 upgrade installed the new kernel, wouldn't it have updated all required modules? Of course I realize that this could easily fall under "upgrades are prone to failure".


I noticed that 2012 only offers autofs v5 and installing it did not resolve the issue.

And I'm not sure which ipv6 packages are related to ipv6 modules.


According to Software Management I don't have a firewall installed - the MMC firewall setting is "Everything (no firewall)". I installed invictus but that didn't fix the problem.

I have already spent quite a bit of time searching for solutions, and on this upgrade as a whole, so if I can't resolve this soon I'll just just reformat and install 2012 fresh.

Thanks.

Use the locate command to see if autofs.ko and ipv6.ko are there. If you have never used slocte, as root, run the command 'updatedb' ( without the quotes ). That will take a few minutes to complete. Once done do a 'locate autofs.ko' and a 'locate ipv6.ko' If you get no output, then you know the modules are missing. You may find the ones for the old kernel.

If, by chance you find them, ( they should be in /lib/modules/version#kernel/ path) then try to modprobe the modules one at a time. They have to match your current kernel version. If you have old kernels from the previous install, the modules for those kernels will not work.

I see you think you don't have a firewall installed. Last time I installed mandy, there was one installed by default. Things may have changed.

1 members found this post helpful.

I do have those files and they are in the path of "/lib/modules/kernel-version..." - and they are the same version as my kernel (3.4.1-1.4). After running modprobe on them I rebooted but still have the same startup errors.

At least when the system finally starts it works/runs very well.

Why did you boot? That will unload the modules. You will have to find out how Mandy normally inserts modules during the boot process. I don't run it any more, and can not tell you how, exactly.

Slack makes it simple. There are scripts in /etc/rc.d/ and one is called rc.autofs. All I have to do is make it executable. It will insert autofs at the correct time during boot. Problem is, every distro does this their own way.

One thing that you can do. In MCC, there was an app that allowed you to start and stop daemons. You might look there to see if autofs and ipv6 are listed. Just a guess though.

1 members found this post helpful.

I guess I misunderstood modprobe. Since I found the modules and they seemed to load without error with modprobe, I rebooted to see if the modules would now load at boot (which they didn't). So, as you indicate, there is apparently another way to determine which modules load at boot... now I just need to find that.


Under startup services, there is an autofs but it is already enabled on boot. There is no ipv6 listed.


EDIT
P.S. - After boot errors, booting and system start, lsmod reports that autofs4 and ipv6 are loaded (in spite of error messages).

Today I booted up my Magia2 system. It is a fork of Mandriva, and is very much similar. What I have been trying to determine, is how autofs4 and ipv6 normally get loaded. So far, I have not figured that out.

If I go back to your first post, and look at the error messages, you will see it is systemd that is reporting the errors. We now know the modules do infact get loaded, form your last post;

So, what is loading them? Don't know. I believe systemd should be, however, by the error messages that appers not to be the case.

I suspect there may be some broken symlinks; however, that is difficult to track down.

I think you are going to need the help of someone with more knowledge of the boot process of Mandriva to track down the source of the problems. May I suggest you post on the Mandriva users board? There are some very knowedgable people there on Mandriva. BTW, I'm not trying to abandon this thread, I think I'm able not to help where the help is needed. I will continue to follow your postings here.

1 members found this post helpful.

I have posted this issue at the Mandriva forums - aside from that forum being much quieter than this one, there wasn't much help offered and I was reminded that 2012 is a "Tech Preview" that isn't even at the Alpha stage yet and is only for testing purposes.

At this point I'm just going to run the system as-is. I uninstalled the 2.x kernel which improved boot time - the system loads reasonably fast, in spite of the errors. After the desktop has started the system runs normally and is not sluggish. If I really want to get rid of the errors I will just do a fresh install.

Thanks for your help.