@bcbc thanks a lot - everything worked perfectly.
@bcbc thanks a lot - everything worked perfectly.
Thanks for the quick reply. I've actually already tried that fix and it didn't work, it will probably work if I can figure out the correct dir. path, but I'm gonna need help for that. Keep in mind I'm new to linux. Here's the results I get. Thanks for the help
ubuntu@ubuntu:~$ sudo mkdir /media/win
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /media/win
ubuntu@ubuntu:~$ sudo mount -o loop /media/win/ubuntu/disks/root.disk /mnt
Killed
ubuntu@ubuntu:~$ sudo cp /mnt/boot/grub/grub.cfg /mnt/boot/grub/grub.cfg.copy
cp: cannot stat `/mnt/boot/grub/grub.cfg': No such file or directory
Here's the Boot Info Summary
Last edited by Ubuntered; January 21st, 2011 at 11:10 PM. Reason: wanted to add boot info summary
First backup the root.disk if possible.
Then try:
Then (if that doesn't give you errors),Code:sudo mkdir /media/win sudo mount /dev/sda1 /media/win sudo fsck /media/win/ubuntu/disks/root.disk
If that works - then continue with the rest of the instructions.Code:sudo mount -o loop /media/win/ubuntu/disks/root.disk /mnt
Actually I might run chkdsk on your Windows C: drive as well before running fsck.
Thanks, I'll give that a try, booting into window's now to run chkdsk on C:, I also have a backup of root.dsk just in case. I guess if all else fails I can always uninstall via wubi, then reinstall via wubi to fix boot problem and then replace my root.dsk with backup to get all my settings and programs back, I think that would work but I'm not sure. Thanks for your help, you guys are awesome!
Copying the root.disk back over will work. That's a convenient way to backup your Wubi install.
But backing it up after you are having problems won't help if the problem is on the root.disk itself. It's still a good idea to take a backup before attempting repairs e.g. running fsck
Alright, here's the results, looks like I might have some file corruption or something. Thanks again for all the help.
ubuntu@ubuntu:~$ sudo mkdir /media/win
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /media/win
ubuntu@ubuntu:~$ sudo fsck /media/win/ubuntu/disks/root.dsk
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext2: No such file or directory while trying to open /media/win/ubuntu/disks/root.dsk
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I'm not sure if this is relevant, but when I created the partitions, (which I did with a linux live cd - ubuntu 10.04) I chose a ext4 (or something similar, not exactly sure) file system for the linux partition, however I later used windows disk manager to alter the partition to ntfs so I could see it from windows explorer. So what I did was:
1. used live cd to format drive
2. used live cd to create 2 partitions (ext4?- for linux & ntfs for windows)
3. Installed windows
4. wanted to install linux via wubi but was unable to access from wubi installer, drive would not show up in install paths.
5. used windows disk manager to make partition visible to windows, which changed it to ntfs
6. from that point I was able to install linux on the partition and dual boot.
However I have had some boot issues, windows boots fine 100%, but linux has been hit and miss, but if I retried or chose the recovery option it would boot ok for awhile then it would act up again. I'm starting to think I might have screwed this up from the get-go. Thanks for all the help, if you think this is fixable, let me know, and I'll keep trying what ever you guys come up with. However if you think a fresh install with some changes to the partition is my best bet, I'm willing to do that also. Thanks again.
just to reiterate, I can not boot into linux at all now, above paragraph makes it sound like I can. Don't want to confuse anyone. thanks.
p.s. I need to head to town for a few hours but will be back later to check replies-suggestions.
Last edited by Ubuntered; January 22nd, 2011 at 01:18 AM. Reason: clarify
Doh! : \, dam, I actually double checked to make sure it was correct, and still missed it. Oh well, on the up side, I'm making progress.
Here's what I got:
ubuntu@ubuntu:~$ sudo mkdir /media/win
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /media/win
ubuntu@ubuntu:~$ sudo fsck /media/win/ubuntu/disks/root.disk
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
/media/win/ubuntu/disks/root.disk: recovering journal
Clearing orphaned inode 193332 (uid=0, gid=0, mode=0100644, size=9148600)
Clearing orphaned inode 18878 (uid=1000, gid=1000, mode=0100644, size=32768)
Clearing orphaned inode 18519 (uid=1000, gid=1000, mode=0100600, size=184)
Clearing orphaned inode 18844 (uid=1000, gid=1000, mode=0100644, size=32768)
Clearing orphaned inode 18820 (uid=1000, gid=1000, mode=0100644, size=0)
Illegal inode 1295509600 in orphaned inode list.
/media/win/ubuntu/disks/root.disk was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -764194
Fix<y>? yes
Free blocks count wrong for group #23 (15044, counted=15045).
Fix<y>? yes
Free blocks count wrong (1258729, counted=1258730).
Fix<y>? yes
Free inodes count wrong for group #2 (4681, counted=4682).
Fix<y>? yes
Free inodes count wrong (417496, counted=417497).
Fix<y>? yes
/media/win/ubuntu/disks/root.disk: ***** FILE SYSTEM WAS MODIFIED *****
/media/win/ubuntu/disks/root.disk: 207127/624624 files (0.2% non-contiguous), 1235734/2494464 blocks
ubuntu@ubuntu:~$
After this, I exited terminal, shutdown and rebooted to hard drive, selected my Ubuntu partition and bingity bango, hot dam, it booted perfectly, first try. I'm very impressed with this forum, and would like to offer a special thanks to user "bcbc" who's quick responses and good advice, fixed this problem for me. . With strong solid support like this, Linux is getting harder and harder to beat.
Bookmarks