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

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!