Re: hard disk mount count thread

and can use that now ok.

As far as using it now instead, I guess I could.

I think I installed and then uninstalled VirtualBox
recently and was wondering if this could be the source
of the problems - creating virtual memory locs and such.

Any opinion on this theory?

But I all I can say is give it a try. I doubt it though.

Thank you and to myself I give the world's most patient penguin award.

I re-installed, formatting root only and everything is back to normal.
Even my "old" desktop was perfectly restored.

I have just cut and pasted your suggested new repos and presume it will be smooth sailing from here on out.

BTW, I had to re-install because, due to the bug all I got in response to "urpmi" commands from tty3 was the same error message over and over again "Bus error".

Is keeping a "note pad" type of documents with the Repos that I like. So next time that I restore any system just copy and paste the commands.

The new Mandriva 2010.1 just came out, so for that, you need to reload new repository. Just go to http://easyurpmi.zarb.org/ and use the Old Interface. Choose the Servers that you want and all the commands will show on the bottom. Highlight and copy/paste on a Text Doc for later use.

Doing it this way is that you have control on what servers you use. Automatic, choose the closest to you (download speed).

I like to keep the same servers for PLF and Main.

If you wish, you can login on GNOME if you choose at the logon applet the desktop that you will like to use.

On fresh re-install of 2009 went to MCC, updated 272 packages and then on re-boot could not boot.

The following error messages were caught after the boot splash screen....


FATAL: Could not load /lib/modules/2.6.27.45-desktop-1mnb/modules.dep:No such files or directory.

Also not loading were /dev/root (says it does not exist)
no mounting /proc or /sys

And finally the message: "booting has failed"

I've almost run out of patience! This has been happening more than once.

What else can I do? Load the desktop module using the rescue disk seems like a possibility.

Please advise. Apparently during the update the new desktop did not install?

Help!

and the Boot Options do not include the newly updated desktop...

The first option to boot into looks like this:

BOOT IMAGE=linux root=UUID(long string)


Can I enter the new desktop here?

It should autodetect all installed Linux kernels and other OSes.
Check google for tutorial.

however I checked the file system table and no devices were even listed.

the only devices listed were /dev/ram3, /dev/fd0, /dev/cdrom

This is unusual.

Boot on the newest Kernel?

By editing the /boot/menu.lst file with the two kernels that were
not added during installation.

Back in business.

Mandriva Control Center there is a section to fix the boot.

Follow this wiki...

http://wiki.mandriva.com/en/ControlCenter

If you messed up the bootloader, boot with the install disk and do not use the installation section. I think is rescue. On one of those, it uses like DOS program that allows you to reinstall the bootloader.