Grub error 22


Recommended Posts

Do a reading on the Wubi Guide, specially this section:

https://wiki.ubuntu.com/WubiGuide#How%20can%20I%20access%20my%20Wubi%20install%20and%20repair%20my%20install%20if%20it%20won't%20boot?

Also see this page: http://lubi.sourceforge.net/lvpm.html

If all of that fails you may want to recover your files from the Ubuntu install image and start a fresh install.

This issue may have been caused by an error on the Windows partition, you may want to check that before attempting another Ubuntu install. Check the partition for errors and, if possible, check the fragmentation too.

Do a reading on the Wubi Guide, specially this section:

https://wiki.ubuntu.com/WubiGuide#How%20can%20I%20access%20my%20Wubi%20install%20and%20repair%20my%20install%20if%20it%20won't%20boot?

Also see this page: http://lubi.sourceforge.net/lvpm.html

If all of that fails you may want to recover your files from the Ubuntu install image and start a fresh install.

This issue may have been caused by an error on the Windows partition, you may want to check that before attempting another Ubuntu install. Check the partition for errors and, if possible, check the fragmentation too.

thanks...but how do i access my Wubi install and repair it, if i don't have a Ubuntu CD (which i don't!)??? i simply downloaded the wubi installer from http://www.wubi-installer.org, and used it to install Ubuntu 8.10, instead of using a CD! so what then?

Looking forward to ur reply...

You can borrow a CD from someone, download it or order it online, it's free.

In alternative you can use something like cygwin which has the necessary tools to make the task of mounting your Wubi image under Windows.

Hey dude, don't blame me. I understand your frustration, and how it must be to not be able to access your files.

But don't blame the guy who is simply trying to help you... :)

You can borrow a CD from someone, download it or order it online, it's free.

In alternative you can use something like cygwin which has the necessary tools to make the task of mounting your Wubi image under Windows.

Hey dude, don't blame me. I understand your frustration, and how it must be to not be able to access your files.

But don't blame the guy who is simply trying to help you... :)

ok..cool! and i wasn't blaming u! i'm sorry if i gave u that impression...lol! :D and do u happen to happen to have the site to go to to download the ubuntu CD thing?

thanks for all ur help!!! i really appreciate it! :shiftyninja:

ok...so i burned a ubuntu desktop CD, and after booting with it, opened up a terminal, and ran the commands suggested in the section of the Wubi Guide u directed me to, Lechio, and got all the way up to the "sudo mount -o loop /win/ubuntu/disks/root.disk /vdisk" command but i got a message saying there was no such file or directory named /vdisk! :unsure: or something to that effect! any idea why the command didn't work?

Thanks, and looking forward to ur reply...

yes, lechio! but i've already ran that command u just gave! *confused* it was one of the first commands given in the Wubi guide! as for replacing "win/ubuntu/disks/root.disk"...i'm not sure what u mean!

additional information: it was the command right before the "sudo mount -o loop..." one!

You need to create the directory "/vdisk":

sudo mkdir /vdisk

Also you have to replace "/win/ubuntu/disks/root.disk" with the path where you have your windows partition mounted.

and as far as i know, that is the correct path...i've even gone to the root.disk location in Windows OS, and can verify that it exists! :unsure: please don't take that as an insult...just trying to make myself clear! yo!

i'll try to copy the exact terminal output for u, when i try running the sudo mount -o loop command for u, if that will help any!

not sure why it didn't work...

So you say you have your Windows partition mounted on the "/win/" directory?

If that's so:

sudo mkdir /vdisk
cd /win/ubuntu/disks/
sudo mount -o loop root.disk /vdisk

That is the complete process for mounting the image if you do have your Windows partition mounted on the "/win/" directory.

You understand how mounting a partition works right?

OK. You have a device (HDD), that device is divided into partitions. Those partitions contain your data. To be able to access this data you need to mount them.

Type "man mount" for a full explanation of the command.

Now run:

This gives you information about your partitions.

sudo fdisk -l

This gives you information about what is currently mounted.

df

Copy and paste the output of those commands here.

ok...thanks, Lechio, for the explanation! i just got done running those commands u gave me, but the "cd /win/ubuntu/disks" one didn't work! i guess i was wrong about where the Windows partition was... MY BAD!!!

anyway, i'll be sure to copy and paste the terminal output of the commands above! ^

ok...so here's the terminal output for those two commands!

Output for “sudo fdisk -l”:

ubuntu@ubuntu:~$ sudo fdisk -l


Disk /dev/sda: 320.0 GB, 320072933376 bytes

255 heads, 63 sectors/track, 38913 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Disk identifier: 0x3c5a8d58


Device Boot Start End Blocks Id System

/dev/sda1 1 5 40131 de Dell Utility

/dev/sda2 6 1280 10240000 7 HPFS/NTFS

/dev/sda3 * 1280 38914 302290037+ 7 HPFS/NTFS

ubuntu@ubuntu:~$

Output for “df”:

ubuntu@ubuntu:~$ df

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 2027008 2380 2024628 1% /lib/modules/2.6.27-7-generic/volatile

tmpfs 2027008 2380 2024628 1% /lib/modules/2.6.27-7-generic/volatile

tmpfs 2027008 0 2027008 0% /lib/init/rw

varrun 2027008 88 2026920 1% /var/run

varlock 2027008 0 2027008 0% /var/lock

udev 2027008 2924 2024084 1% /dev

tmpfs 2027008 128 2026880 1% /dev/shm

rootfs 2027008 87236 1939772 5% /

/dev/scd0 715810 715810 0 100% /cdrom

/dev/loop0 691712 691712 0 100% /rofs

tmpfs 2027008 12 2026996 1% /tmp

Ok, you have 2 NTFS partitions, "/dev/sda2" and "/dev/sda3". Windows looks to be installed in "/dev/sda3".

So to mount that you can do it with the file browser or via the terminal:

sudo mkdir /mnt/tmpsda3
sudo mkdir /vdisk

sudo mount -t ntfs /dev/sda3 /mnt/tmpsda3
cd /mnt/tmpsda3/ubuntu/disks/

sudo mount -o loop root.disk /vdisk

Now browse with a file browser to the "/vdisk" directory. Your ubuntu image is located there with all your personal files in "/vdisk/home/yourUbuntuUserName"1. Backup those files some place where you wish to.

1.replace "yourUbuntuUserName" with your actual Ubuntu user name.

Ok, you have 2 NTFS partitions, "/dev/sda2" and "/dev/sda3". Windows looks to be installed in "/dev/sda3".

So to mount that you can do it with the file browser or via the terminal:

sudo mkdir /mnt/tmpsda3
sudo mkdir /vdisk

sudo mount -t ntfs /dev/sda3 /mnt/tmpsda3
cd /mnt/tmpsda3/ubuntu/disks/

sudo mount -o loop root.disk /vdisk

Now browse with a file browser to the "/vdisk" directory. Your ubuntu image is located there with all your personal files in "/vdisk/home/yourUbuntuUserName"1. Backup those files some place where you wish to.

1.replace "yourUbuntuUserName" with your actual Ubuntu user name.

ok...so ur commands worked all the way up until "cd /mnt/tmpsda3/ubuntu/disks/, at which command the terminal said "no such file or directory". after that, i changed it a little bit and tried first going into the "mnt" folder

cd /mnt

which worked ok, and then from there i went to "tmpsda3"

cd tmpsda3

("cd /tmpsda3" or "cd /tmpsda3/" didn't work!)...the only error came when trying to 'cd' into /ubuntu/disks/, at which command i got the same error! it appears that there is nothing in "tmpsda3" because after obtaining that output, i put in:

ls

and it didn't show anything in it! :unsure:

looking forward to ur reply...

Coolname007

Edited by Coolname007

Haven't you made the directory "/mnt/tmpsda3"? Browse with a file browser to "/mnt" and see what directories are there.

"/mnt/tmpsda3" is just an example, you can use any other directory, use even the home directory if you want. Make a directory like "/home/ubuntu/tmpsda3" and mount the partition there.

Haven't you made the directory "/mnt/tmpsda3"?
yes! i typed in the command "sudo mkdir /mnt/tmpsda3", and it worked...i would not have been able to get in it otherwise! :D

additionally, r u absolutely sure that sda3 and not sda2 is the one where Windows is located? not dissing u, or anything, just wondering! yo! :blink:

OK... In the Gome menu > places, you see your partition. Click on it and it will automount somewhere in /media. Use the previously referred "df" command to know where it was mounted. Then just use that directory instead of "/mnt/tmpsda3".

additionally, r u absolutely sure that sda3 and not sda2 is the one where Windows is located? not dissing u, or anything, just wondering! yo!

No I am not sure, I've said it looked like it was installed there, because it is the active partition from where the system boots.

It's up to you to know where you have your windows installation, I don't read minds.

OK... In the Gome menu > places, you see your partition. Click on it and it will automount somewhere in /media. Use the previously referred "df" command to know where it was mounted. Then just use that directory instead of "/mnt/tmpsda3".

ok...thanks! i'll try that, and let u know if it works! thanks for all ur help! :D

No I am not sure, I've said it looked like it was installed there, because it is the active partition from where the system boots.

It's up to you to know where you have your windows installation, I don't read minds.

ok...no offense! i was just checking! yo! i'll try what u suggested, and then get back to u!

well...i finally completed the mounting process!!! i figured out what i was doing wrong...i tried the original commands from the Wubi Guide again, this time changing the "sda1" to "sda3, and it WORKED!!!! turns out that the Windows OS was in the /win directory, after all, in sda3! i should of thought of that before! my issue (wait...i mean issues!) now is copying my Home folder in Ubuntu into my Windows OS! it keeps saying that permission to "read" the folder is not allowed, and so wont let me copy it! i also tried booting into Ubuntu again (this is the second issue! :shifty:), hoping that it would work, since i ran the filesystem check with "sudo fsck /win/ubuntu/disks/root.disk" and it said that it had recovered a "journal", whatever that means...and so i was hoping that it would work! but...it DIDN'T!!! i still get the same crc error, which i can't figure out!

and so i need help with these two issues!

Thanks, and looking forward to ur reply... :(

Here's the complete output of the commands that i ran, and the results that i obtained:

ubuntu@ubuntu:~$ df

Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 2027008 2380 2024628 1% /lib/modules/2.6.27-7-generic/volatile

tmpfs 2027008 2380 2024628 1% /lib/modules/2.6.27-7-generic/volatile

tmpfs 2027008 0 2027008 0% /lib/init/rw

varrun 2027008 88 2026920 1% /var/run

varlock 2027008 0 2027008 0% /var/lock

udev 2027008 2924 2024084 1% /dev

tmpfs 2027008 104 2026904 1% /dev/shm

rootfs 2027008 87232 1939776 5% /

/dev/scd0 715810 715810 0 100% /cdrom

/dev/loop0 691712 691712 0 100% /rofs

tmpfs 2027008 12 2026996 1% /tmp

/dev/sda3 302290036 95022316 207267720 32% /media/OS

ubuntu@ubuntu:~$ sudo mkdir /win

ubuntu@ubuntu:~$ sudo mount /dev/sda3 /win

ubuntu@ubuntu:~$ sudo mkdir /vdisk

ubuntu@ubuntu:~$ sudo mount -o loop /win/ubuntu/disks/root.disk /vdisk

ubuntu@ubuntu:~$ /vdisk

bash: /vdisk: is a directory

ubuntu@ubuntu:~$ sudo fsck /win/ubuntu/disks/root.disk

fsck 1.41.3 (12-Oct-2008)

e2fsck 1.41.3 (12-Oct-2008)

/win/ubuntu/disks/root.disk: recovering journal

/win/ubuntu/disks/root.disk: clean, 124039/855120 files, 784497/3417968 blocks

ubuntu@ubuntu:~$

turns out that the Windows OS was in the /win directory

It was in the "/win" directory because you've mounted it there ("sudo mount /dev/sda3 /win"), don't just copy>paste the commands without understanding what you are doing.

First recover the files located in your home directory, don't copy the entire directory, just your important documents you wish to save. If you don't have permission to read those files, copy them with the sudo command or as root.

After all your files have been backed up, you may go and try to fix your install.

It was in the "/win" directory because you've mounted it there ("sudo mount /dev/sda3 /win"), don't just copy>paste the commands without understanding what you are doing.

First recover the files located in your home directory, don't copy the entire directory, just your important documents you wish to save. If you don't have permission to read those files, copy them with the sudo command or as root.

After all your files have been backed up, you may go and try to fix your install.

ahh...NOW i get it!!! that makes sense! ok...so how do i copy them with the sudo command or as root? and more importantly, how do i try to fix my install? do u have any suggestions for that?

Thanks in advance! :D

so how do i copy them with the sudo command or as root?

I've just reproduced this with an Ubuntu live CD and it allows me to browse to the user home directory, read and copy the files with the ubuntu default permissions...

If it doesn't allow you to read the files you could always run the file browser as root, by running the command:

gksu nautilus

Alternatively you can use terminal to copy your files by using the "cp" command. Do "man cp" to get more details on how the command works.

and more importantly, how do i try to fix my install? do u have any suggestions for that?

I cannot give you more details on how to fix your Wubi install than those that are available in the pages that I've referenced to you before. This issue never happened to me, so I wouldn't know how to go about fixing it. Maybe try to fscheck the other image "usr.disk", checking the boot options from grub, reinstalling grub. Just guesses here...

If I were you I would, after recovering my files, uninstall Wubi from Windows and make a fresh Ubuntu install using the Ubuntu CD.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Would you please fix your graphics. They are outdated and don't fit the article.
    • The Light of Life? We actually do glow till our Death, study finds by Sayan Sen Image by Rafael Rendon via Pexels A study by researchers at the University of Calgary has found that living organisms produce an extremely faint light known as ultraweak photon emission, and that this glow appears to drop significantly after death. The research was published in the Journal of Physical Chemistry in April 2025 and quickly drew widespread attention, leading to more than 200 news stories about the findings. Ultraweak photon emission (or UPE), sometimes called biophoton emission, refers to tiny amounts of light released by living cells as a result of normal biological activity. A photon is the basic particle of light, and researchers say every living system examined so far, including plants and animals, has been found to emit these photons. The glow is far too faint to be seen by the human eye. “I suppose it has a little to do with people being reminded of auras,” says Dr. Christoph Simon, PhD, one of the authors of the study and a professor in the Department of Physics and Astronomy in the Faculty of Science. “It is a fact that living beings glow. It’s a very weak glow, but it’s there and visible with very sensitive cameras.” According to the study, the light involved is extremely weak, ranging from 10 to 1,000 photons per square centimetre per second across a spectral range of 200 to 1,000 nanometres. For comparison, a nanometre is one-billionth of a metre and is commonly used to measure wavelengths of light. Detecting emissions at such low levels requires highly specialized equipment. To study the phenomenon, researchers used electron-multiplying charge-coupled device (EMCCD) and charge-coupled device (CCD) cameras. These imaging systems are designed to detect extremely small amounts of light, including individual photons, while minimizing background noise. The technology allowed researchers to capture signals that would otherwise be impossible to observe. The team worked with the Human Health Therapeutics Research Centre at the National Research Council of Canada (NRC) in Ottawa to examine photon emissions in mice. Researchers took two-hour exposure images of the animals before and after death and compared the results. “We saw that the level of light that they emit – this biophoton glow – is distinctly different between living and dead animals,” says Dr. Daniel Oblak, PhD, an associate professor in Physics and Astronomy and the corresponding author of the study. The images showed a clear decrease in photon emissions after death across the entire body of each mouse. According to the researchers, this provided direct evidence that living and dead tissue produce different levels of ultraweak photon emission. “It’s a very small amount and it’s, of course, very tricky to detect,” Oblak says. The study grew out of discussions between Simon, whose research interests include quantum biology, and Oblak, whose work focuses on detecting light for quantum communication experiments. Quantum biology is a field that explores whether processes described by quantum physics, which studies matter and energy at very small scales, may also play a role in living systems. “Since I work as a quantum physicist on light detection for quantum communication, I thought that experimentally we have a lot of the tools to be able to detect the light,” Oblak explains. The researchers also investigated UPE in plants and found that the light changed in response to stress. When plants were exposed to higher temperatures or physically injured, their photon emissions increased. Chemical treatments also affected the glow. Among the substances tested, the local anesthetic benzocaine produced the strongest emission response when applied to injured plant tissue. These findings suggest that ultraweak photon emission is closely linked to biochemical and metabolic activity inside living organisms. Metabolism refers to the chemical reactions that allow cells and organisms to stay alive and function. Because these reactions change when an organism experiences stress, injury or disease, researchers believe UPE may provide a way to monitor those changes. The researchers stress that the glow is a physical and biological phenomenon, not a metaphysical one. Oblak says more research is needed to understand exactly how the light is produced and what information it may reveal about the condition of living tissue. “We must understand what that is to figure out what’s happening,” he says. “If we can understand how that relates to certain influences on the body – stress, diseases – then that could be used as a diagnostic tool.” The researchers believe the technique could eventually help scientists study health and disease without invasive procedures. Because UPE can be measured without adding dyes, markers or labels, it may offer a way to monitor whether tissue is healthy, damaged or alive. In plants, it could help researchers better understand how organisms respond to injury, heat and other forms of stress. While the work is still in its early stages, the study demonstrates that ultraweak photon emission imaging can provide a non-invasive and label-free way to observe biological activity. Researchers say the approach could become a useful tool for studying vitality, stress responses and other important processes in both animals and plants. Source: University of Calgary, ACS publication This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Damn, I loved this show back in the day.  
    • Rufus 4.15.2393 Beta 2 by Razvan Serea Rufus is a small utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc. Despite its small size, Rufus provides everything you need! Oh, and Rufus is fast. For instance it's about twice as fast as UNetbootin, Universal USB Installer or Windows 7 USB download tool, on the creation of a Windows 7 USB installation drive from an ISO (with honorable mention to WiNToBootic for managing to keep up). It is also marginally faster on the creation of Linux bootable USBs from ISOs. A non-exhaustive list of Rufus supported ISOs is available here. It can be especially useful for cases where: you need to create USB installation media from bootable ISOs (Windows, Linux, UEFI, etc.) you need to work on a system that doesn't have an OS installed you need to flash a BIOS or other firmware from DOS you want to run a low-level utility Rufus 4.15.2393 Beta 2 changelog: Add RISC-V 64 support to UEFI:NTFS Improve the guards for using the "silent" option Improve the ability to cancel during write retries Improve progress reporting for compressed image extraction Fix unrestricted XML entity expansion and integer overflow in ezxml parser (courtesy of @esadowski4) [GHSA-55r2-34wg-8mv9] Fix "silent" Windows installation failing at 75% in most cases [#2960] Fix a crash during boot when using UEFI:NTFS on Snapdragon X based ARM64 platforms [#2934] Fix the first WUE option always being checked by default [#2965] Fix an infinite loop when using Windows ISOs that contain multiple WIMs Fix "Enable runtime UEFI media validation" checkbox not always being properly enabled Other WUE improvements/fixes for OneDrive removal and username validation (with thanks to @christian8641) [#2984, #2991] Download: Rufus 4.15 Beta 2 | 1.9 MB (Open Source) Links: Rufus Home Page | Project Page @GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Year In
      hhgygy earned a badge
      One Year In
    • One Month Later
      AMV earned a badge
      One Month Later
    • Week One Done
      AMV earned a badge
      Week One Done
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      515
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      83
    4. 4
      Steven P.
      74
    5. 5
      Michael Scrip
      72
  • Tell a friend

    Love Neowin? Tell a friend!