I upgraded, and now I have this error...

[mörgæs]

This does not sound like a problem with an upgrade going awry. Please open a new thread in
http://ubuntuforums.org/forumdisplay.php?f=333

and state everything as precise as possible: Your hardware, the driver you tried to install, the exact error message and the steps you have done already to solve the problem.

[tomdkat]

I certainly hope so. My upgrade from 10.04 (64-bit) to 10.10 (64-bit) hasn't gone smoothly at all. Right now, I'm plagued with two main issues:

• Frequent and random hangs (even the mouse won't move and ctrl-alt-del does nothing).
• Not being able to mount the internal SATA drive (bug #634407)

So, I'm going to see if I can give a clean install an attempt on a different hard drive. If the hangs and SATA drive issue persist, I'll revert back to Ubuntu 10.04 and wait for the subsequent release.

Peace...

Well, I've tracked down the frequent hangs to a Firefox extension. I haven't identified the problematic one but when I turned off all of the Firefox extensions, the hangs mostly went away.

As for the SATA drive issue, a recent kernel update to kernel version 2.6.35-23-generic solves the problem so I can now access my SATA drive.

Peace...

[archolman]

Thank you very much for the tute, morgaes. And to the other contributors.
I wish I had been patient enough to read-up first, being an exemplar is interesting!

However, I now have a working system, & it is good! Thanks be to the forums, Linux Format Magazine, & the Open University!


The box (a P4) that I had the update games with, has been 'retired' until I can afford to get new RAM. One of the sticks died, & a LiveCD now takes an hour to load, & forever to respond to the keyboard/mouse. Ho-hum.

[fccluck]

From the release notes:


If you have already upgraded and find that the system reboots, hangs or drops you at a grub prompt when selecting Ubuntu (with or without error messages), then first try to replace the c:\wubildr file from the one in c:\ubuntu\winboot\wubildr (change 'drive' if necessary and backup c:\wubildr first as a precaution). This fix has been confirmed by many different people, as it appears that in many cases the upgrade is corrupting the wubildr file.

Otherwise another workaround is to boot a live CD, loop mount the wubi root.disk, edit the grub.cfg (gksu gedit /mountpoint/boot/grub/grub.cfg) and remove all lines above the first "menuentry".

If you get a read-only error on grub.cfg, then either use vi or nano, or before running gedit first run:
sudo chmod +w /mountpoint/boot/grub/grub.cfg
Note: if you install kernel updates, new kernels, remove kernels, run update-grub etc. you'll have to reapply the workaround as grub.cfg is regenerated automatically. It's easier to do this before you reboot (or you'll have to use the live CD again).

I did the editing grub.cfg thing, but what is the fix for the future? And what is it in those first set of lines that is preventing so many people from booting?

[bcbc]

I did the editing grub.cfg thing, but what is the fix for the future? And what is it in those first set of lines that is preventing so many people from booting?

There is no permanent fix that I am aware of. I'm not expecting one anytime soon either. From what I can figure out, the developer who is making these changes to grub (Colin Watson) is also responsible for wubi - because the main wubi developer (Agostino Russo) is not available anymore. And this grub developer doesn't have much time to investigate wubi. There also doesn't seem to be much oversight by Canonical in terms of them providing wubi and making sure that it's stable.

So, basically, your options are to backup data and reinstall Wubi and never update grub-pc or grub-common. Or to migrate the wubi to a partition as described here: http://ubuntuforums.org/showthread.php?t=1519354

Here's a quote from the #ubuntu-devel channel on IRC to explain the situation, referring to the bug that affects you (that hasn't seen any change since before the Maverick release):

[14:42] <cjwatson> wubi upgrades have never worked right before. it would have been nice to say that they worked this time, but I have a hard time considering it a blocker
[14:43] <cjwatson> (this is not to say I don't appreciate efforts to get them to boot ...)
[14:43] <cjwatson> er, to work
[14:43] <cjwatson> wubi really needs a maintainer who isn't me. Agostino has been mostly lacking in time
[14:44] <cjwatson> I'm only doing it by default

PS this maverick bug has been passed on to 10.04 installs now. They are breaking too since a grub update in the last week or so.

[lilmissdids]

Hello everyone!
I've been updating since 4.04 and have never had any problems - and I am sure I jinxed myself, because right before updating from 10.04 to 10.10 I thought how lucky I was that every update has always gone so smoothly.
For the past six years I've more or less been able to google myself through any difficulties, but I haven't come across anything helpful for this one. I don't know what exactly went wrong, but after the upgrade was done, it said that it had finished with errors. And many things aren't working correctly now (programs - skype, vlc etc as well as the x missing in the corners to close windows and my already sluggish laptop is even slower)
I know this is one of the problems. Does anyone know how to fix it??
Thank you so much for your time!!!

Loading new virtualbox-ose-3.2.8 DKMS files...
Building only for 2.6.35-23-generic
Building initial module for 2.6.35-23-generic

Error! Bad return status for module build on kernel: 2.6.35-23-generic (i686)
Consult the make.log in the build directory
/var/lib/dkms/virtualbox-ose/3.2.8/build/ for more information.
Traceback (most recent call last):
  File "/usr/share/apport/package-hooks/dkms.py", line 57, in <module>
    report.write(open(apport.fileutils.make_report_path(report), 'w'))
IOError: [Errno 2] No such file or directory: '/var/crash/virtualbox-ose-dkms.0.crash'
dpkg: error processing virtualbox-ose-dkms (--configure):
 subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing:
 virtualbox-ose-dkms
N: Ignoring file 'conkyhardcore-karmic.li' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Sub-process /usr/bin/dpkg returned an error code (1)

Make fie..

DKMS make.log for virtualbox-ose-3.2.8 for kernel 2.6.35-23-generic (i686)
Mon Nov 29 21:17:39 CET 2010
make: Entering directory `/usr/src/linux-headers-2.6.35-23-generic'
  LD      /var/lib/dkms/virtualbox-ose/3.2.8/build/built-in.o
  LD      /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/built-in.o
  CC [M]  /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.o
In file included from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/msr.h:17,
                 from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/processor.h:21,
                 from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/thread_info.h:22,
                 from include/linux/thread_info.h:56,
                 from include/linux/preempt.h:9,
                 from include/linux/spinlock.h:50,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/../SUPDrvInternal.h:99,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:33:
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/errno.h:1: error: include/asm-generic/errno.h: Input/output error
In file included from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/processor.h:21,
                 from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/thread_info.h:22,
                 from include/linux/thread_info.h:56,
                 from include/linux/preempt.h:9,
                 from include/linux/spinlock.h:50,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/../SUPDrvInternal.h:99,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:33:
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/msr.h: In function ‘native_read_msr_safe’:
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/msr.h:88: error: ‘EIO’ undeclared (first use in this function)
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/msr.h:88: error: (Each undeclared identifier is reported only once
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/msr.h:88: error: for each function it appears in.)
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/msr.h: In function ‘native_write_msr_safe’:
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/msr.h:111: error: ‘EIO’ undeclared (first use in this function)
In file included from include/linux/mmzone.h:664,
                 from include/linux/gfp.h:4,
                 from include/linux/slab.h:12,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/../SUPDrvInternal.h:100,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:33:
include/linux/memory_hotplug.h: In function ‘mhp_notimplemented’:
include/linux/memory_hotplug.h:184: error: ‘ENOSYS’ undeclared (first use in this function)
In file included from include/linux/module.h:13,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:71,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/kmod.h: In function ‘call_usermodehelper_fns’:
include/linux/kmod.h:98: error: ‘ENOMEM’ undeclared (first use in this function)
In file included from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:77,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/fs.h: At top level:
include/linux/fs.h:373: error: include/linux/path.h: Input/output error
In file included from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:77,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/fs.h:383: error: include/linux/capability.h: Input/output error
In file included from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:77,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/fs.h:925: error: field ‘f_path’ has incomplete type
In file included from include/linux/mm.h:40,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:78,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
/usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/pgtable.h:622: error: include/asm-generic/pgtable.h: Input/output error
In file included from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:78,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/mm.h: In function ‘do_mmap’:
include/linux/mm.h:1295: error: ‘EINVAL’ undeclared (first use in this function)
In file included from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/tlbflush.h:5,
                 from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/highmem.h:26,
                 from include/linux/highmem.h:43,
                 from include/linux/pagemap.h:10,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:79,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/sched.h: At top level:
include/linux/sched.h:93: error: include/linux/cred.h: Input/output error
In file included from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:79,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/pagemap.h: In function ‘mapping_set_error’:
include/linux/pagemap.h:31: error: ‘ENOSPC’ undeclared (first use in this function)
include/linux/pagemap.h: In function ‘fault_in_pages_writeable’:
include/linux/pagemap.h:398: error: ‘EFAULT’ undeclared (first use in this function)
include/linux/pagemap.h: In function ‘fault_in_pages_readable’:
include/linux/pagemap.h:421: error: ‘EFAULT’ undeclared (first use in this function)
In file included from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:96,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/pci.h: At top level:
include/linux/pci.h:58: error: include/linux/pci_ids.h: Input/output error
In file included from include/asm-generic/pci-dma-compat.h:7,
                 from /usr/src/linux-headers-2.6.35-23-generic/arch/x86/include/asm/pci.h:109,
                 from include/linux/pci.h:1222,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/r0drv/linux/the-linux-kernel.h:96,
                 from /var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:34:
include/linux/dma-mapping.h: In function ‘dma_set_coherent_mask’:
include/linux/dma-mapping.h:108: error: ‘EIO’ undeclared (first use in this function)
include/linux/dma-mapping.h: In function ‘dma_set_max_seg_size’:
include/linux/dma-mapping.h:127: error: ‘EIO’ undeclared (first use in this function)
include/linux/dma-mapping.h: In function ‘dma_set_seg_boundary’:
include/linux/dma-mapping.h:142: error: ‘EIO’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘vboxdrvLinuxUid’:
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:377: error: dereferencing pointer to incomplete type
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘vboxdrvLinuxGid’:
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:386: error: dereferencing pointer to incomplete type
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘vboxdrvLinuxEuid’:
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:395: error: dereferencing pointer to incomplete type
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘VBoxDrvLinuxInit’:
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:459: error: ‘EINVAL’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘VBoxDrvLinuxCreate’:
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:726: error: ‘EPERM’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘VBoxDrvLinuxIOCtlSlow’:
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:880: error: ‘EFAULT’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:885: error: ‘EINVAL’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:895: error: ‘E2BIG’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:906: error: ‘ENOMEM’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c: In function ‘VBoxDrvLinuxErr2LinuxErr’:
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1062: error: ‘EACCES’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1063: error: ‘EINVAL’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1064: error: ‘EILSEQ’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1065: error: ‘ENXIO’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1066: error: ‘EFAULT’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1067: error: ‘ENOLCK’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1068: error: ‘EEXIST’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1069: error: ‘EPERM’ undeclared (first use in this function)
/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.c:1070: error: ‘ENOSYS’ undeclared (first use in this function)
make[2]: *** [/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[1]: *** [/var/lib/dkms/virtualbox-ose/3.2.8/build/vboxdrv] Error 2
make: *** [_module_/var/lib/dkms/virtualbox-ose/3.2.8/build] Error 2
make: Leaving directory `/usr/src/linux-headers-2.6.35-23-generic'

[pierreu1]

In Maverick, I ran the following commands with sudo and without and I am a bit confused because no text file could be found! Noting happened after I ran the command! Where is the test file being generated? Am I missing something? Thank you.


If you in spite of this want to keep exactly the same packages in the new Ubuntu installation, there is an alternative to the online upgrade. Running the command

dpkg --get-selections > installed-software

gives a text file with all installed packages on the system. If you run this command on the old system, you will have the option of running

 dpkg --set-selections < installed-software

on the new system after a clean install and get the same selection of packages. Thanks to bcscomp for this suggestion.[/QUOTE]

.

[bcbc]

I did the editing grub.cfg thing, but what is the fix for the future? And what is it in those first set of lines that is preventing so many people from booting?

I found the permanent fix to the problem. For complete details see https://bugs.launchpad.net/wubi/+bug/653134

But here are the salient bits:

First back up /boot/grub
sudo cp -r /boot/grub /boot/grubbackup
Then delete all the stuff in /boot/grub that isn't supposed to be there (everything added after fresh wubi install)
cd /boot/grub
sudo rm *.mod
sudo rm *.img
sudo rm *.lst
sudo rm *.o
sudo rm *.pf2
sudo rm -rf locale
This leaves 2 files:
bcbc@ubuntu:/boot/grub$ ls
grub.cfg grubenv
Update the grub.cfg automatically:
sudo update-grub
FIXED!
Not done yet - prevent grub updates from breaking it again:
Go to Synatpic, select packages grub-pc and grub-common, click on Package, Lock Version

You have to lock grub-pc and grub-common still, until the developers figure out how to prevent the problem from reoccurring on grub updates. Ironic I suppose, because when they release a fix you won't get it (or need it).

EDIT:
This fix has been tested and confirmed on a 10.04.1 install, an install upgraded from 10.04.1 to 10.10, as well as a new 10.10 install (with grub-pc reinstalled to intentionally break it).

[Rubi1200]

Thanks yet again to bcbc for the tireless efforts to find solutions for Wubi installs

Quick question or two:

1. I assume this still needs to be done from the LiveCD if the install breaks?

2. If users employ the previous method of removing lines from grub.cfg (everything above the first menuentry) and then lock the version in Synaptic once back into Ubuntu will that also work or is the above method preferred?

[bcbc]

Thanks yet again to bcbc for the tireless efforts to find solutions for Wubi installs

Quick question or two:

1. I assume this still needs to be done from the LiveCD if the install breaks?

2. If users employ the previous method of removing lines from grub.cfg (everything above the first menuentry) and then lock the version in Synaptic once back into Ubuntu will that also work or is the above method preferred?

1. While you can delete the files from a live CD, you can't run 'sudo update-grub' on a wubi install without booting it (even chroot doesn't work). So they still need the workaround to boot the Wubi install and then after that make these changes.

2. No the previous method is just a quick fix that will break whenever you get a kernel update, or remove a kernel: this causes grub.cfg to be automatically regenerated and unless you take these extra measures, the grub.cfg will still cause problems.

Locking versions of grub-pc and grub-common isn't actually necessary with this new fix but it's a safeguard in case the grub developers release a new grub update without fixing the problem (I don't know how likely this is, but it's an unnecessary risk to take).

Locking grub-* is also what I recommend to users who decided just to reinstall as this also prevents the problem from happening in the first place (as we know there already is a grub update waiting to break every fresh wubi install)