I made a mistake while cloning a windows partition. I fought that mess for a while and in the process overwrote grub after failing to unplug the wrong drive. The end result is that I have a working Windows installation (that I use once month) but I can’t start openSUSE (11.2 RC2 via zypper dup).
My partitions should look like this (except actually /by-id/blah)
/dev/sda1 /
/dev/sda2 swap
There are 3 other partitions here but they aren’t being used.
/dev/sdb1 /home
/dev/sdb2 /windows/C
I went to use my 11.1 disk to reinstall grub but received the error “No valid root partition found”
I subsequently attempted “Verify Installed…” but received the same error.
Not knowing whether this was a limitation of the 11.1 install/repair disk, I attempted to use Super Grub Disk to boot the system. It also failed saying that the files were invalid or corrupted.
I would love to avoid a full reinstall but I am at a loss as to how to determine whether the problem is with grub or with a messed up kernel or something I haven’t even considered. If more detail is need I will get it.
Try booting off a live cd like Knoppix, openSUSE Live CD, whatever.
Log into this forum so you can post the results straight away form commands below. Mount sda1 into the live cd with these commands (su to root first):
mkdir /mnt/sda1
mount /dev/sda1 /mnt/sda1
Then post here the results of these commands(but su to become root first):
ls -l /mnt/sda1
ls -l /mnt/sda1/boot
ls -l /mnt/sda1/boot/grub
df -Th
That should tell us a lot more
PS “su to root” means to open a terminal window and enter the command su. That gives superuser permissions to the command that follow.
I will run the requested commands shortly and add another reply. Things have become a bit more interesting.
Since my first post I booted off a Knoppix cd and basically did just what you asked. All appeared to be in order though. I played with menu.lst and was then greeted by grub Error 15: File not found. I thought I should try and poke at the problem through chroot and after 15 minutes of scratching my head realized that knoppix is 32bit but my install is 64…
I returned to the 11.1 dvd to use the “Rescue System” option so I would have a 64bit environment.
mount /dev/sda1 /mnt
ls -l /mnt
-rwxr-xr-x 1 root root 0 Jan 1 1980 ??(
-rwxr-xr-x 1 root root 1605635 Nov 28 1907 ??.???
-rwxr-xr-x 1 root root 0 Jan 1 1980 ??(
-rwxr-xr-x 1 root root 1605635 Nov 28 1907 ??.???
-rwxr-xr-x 1 root root 0 Jan 1 1980 ??(
-rwxr-xr-x 1 root root 1605635 Nov 28 1907 ??.???
drwxr-xr-x 2 root root 16384 Jan 1 1970 .
drwxr-xr-x 19 root root 400 Nov 12 00:21 ..
-rwxr-xr-x 1 root root 0 Jan 1 1980 ??(
-rwxr-xr-x 1 root root 1605635 Nov 28 1907 ??.???
knoppix showed me what I expected. I’ve just finish running fsck.ext3 looking for badblocks and I am running fsck.ext3 -f right now.
Again, I’ll boot back into knoppix and give you the output of the commands as soon as it’s done. Or you might know what those question marks mean – they are very difficult to search for – because I don’t know if they mean corruption or what.
I think it’s almost fixed. While still looking for answers I was reading up on grub and found the geometry command. I had attempted to use the grub command line before and it refused to display so I just double checked my devices.map file to make sure I had everything set right. Next boot cycle I figured I would try again now that I had something concrete to try. This time I was able to use grub>. During the boot grub has decided to reverse the drives from their order in devices.map. I don’t know if I caused this by some other troubleshooting attempt or if it is related to a (what I considered unrelated) problem my BIOS has with detecting hard drives on warm boots. Whatever the source. Just switching (hd0) and (hd1) in menu.lst solved the problem.
I still don’t know why the install disk “Rescue System” mounted the ext3 file system with all of those question marks but the file system checks out clean. I would guess that is why Recovery found no valid root partitions and why none of the other recovery options I chose worked. (No I did not use the Automatic recovery option. I chose the options I thought were apropos.)
Now I just have to figure out why cold boot works fine but warm boots leave me with no processor and no hard drives even though this has never been a problem in the past.
Unless someone thinks that problem is related to the grub problem, I’m going to consider this solved. Thanks for the help even though it seems this was mostly at user error problem. :shame: