Agostino: I know for a fact that when I originally discovered "the problem", booting into Windows and then trying to boot back into the Wubi install made no difference. Files that read as corrupted in grub2 were still read as corrupted. As per your theory, it is true that if you look through the source to grub2's ntfs module, you won't find any code that references the USN journal. So one can only assume that grub2 ignores ntfs journaling altogether. However, I've been using Wubi for quite some time and have never run into the current problem before, and am fairly certain that grub NEVER had any code that checked the ntfs USN journal. So I'm not seeing the connection here.
But I have something stranger to report. I just did another fresh Wubi install, then performed a full update of all the new packages. So this is a default install with all current updates. And the system boots fine! There is no problem with grub2 that I can find, and I can successfully boot ALL kernels in my grub2 boot menu. I've even updated grub defaults and installed a custom kernel and initrd into /boot (which is in the root.disk). No problems. I'm at a loss to explain this. Were there any ubuntu or lupin updates in the past week that would have fixed the problem??? I'll continue trying to trigger the problem. -- Wubi/Karmic boot: kernel panic - not synching: VFS https://bugs.launchpad.net/bugs/477169 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
