I already tried 11.1 but was not happy with it, so I went back to 10.3. This is a new SATA drive that I cloned from the previous IDE drive. I followed the Bugzilla thread and I have an updated kernel as suggested, but still have the problem. If 10.3 does not support SATA then why does it find /boot/grub/menu.lst and start grub only to tell me that it can’t find the very same drive?
Try 11.1 with KDE 3.59, if your complaint was with KDE.
I have a similar issue, but in reverse: I have a 160GB PATA with an 80GB SATA, and 10.3 won’t read the PATA. It installed everything onto the 80GB drive. I basically have 160 GB sitting there doing nothing.
I tried 11.1 and it handled both drives just fine. I deleted it, though, because I didn’t like KDE 4. I just haven’t had time to reinstall and select KDE 3.5, but I agree with the other poster, that should solve your problem.
I just realized that my previous post, where I mentioned that I have a 160 GB drive that’s just consuming power and taking up space, needed some eyeballs.
Too late to edit the post, so I attach them hereto forthwith:
Thanks smpoole7 and RickMura. My objection to 11.1 was not just KDE4. I have two sounds cards and I could only get one of them to work. I also didn’t care for several newer versions of applications provided. I have four computers in two countries and like to keep the same OS and software on all of them for maintenance reasons. Hopefully the next SUSE version will work better for me. If not I am likely to move to Ubuntu which impressed me.
Did you just do a kernel update? Or any other upgrades or system or configuration changes? Reply back, including an fdisk -lu report and also the contents of /etc/boot/grub.conf.
About the link SATA and openSuSE 10.3 problem Opensuse 10.3 Sata Problem - openSUSE Forums, I had an opposite problem. I had difficulties with sata on suse 10.2 after I bought a new computer, so I moved on to 10.3 and everything was fine.
Your sound card problem, though, could maybe rather be an alsa than a suse version issue. I remember having such a problem with my soundcard once. Maybe you could try an older alsa version, shouldn’t be much of a dependency hassle I think.
Kernel update - not for a while.
Upgrades - security patches. No configuration changes.
linux:/home/linux # fdisk -lu
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x000c77d7
Device Boot Start End Blocks Id System
/dev/sda1 63 4209029 2104483+ 82 Linux swap / Solaris
/dev/sda2 * 4209030 46154744 20972857+ 83 Linux
/dev/sda3 46154745 160826714 57335985 83 Linux
linux:/home/linux #
linux:/home/linux # mount /dev/sda2 /mnt
linux:/home/linux # cat /mnt/etc/boot/grub.conf
cat: /mnt/etc/boot/grub.conf: No such file or directory
Sorry about the /boot/grub/grub.conf error; yes, of course it is /etc/grub.conf. What is strange about that is it indicates that grub was installed in the sda2 boot sector, and given that sda2 has its boot flag set, that usually suggests that grub is not in the MBR. Having said that, the error message you got sounds like it’s coming from stage2, which would indicates that the code in the MBR is successfully finding stage2. So, let’s revisit a few points . . .
When precisely did this mis-behavior begin? There must have been something which changed something to induce the problem (hence the previous question about changes).
The grub error message you get, this happens exactly after selecting the default boot entry on the grub menu? And that is the exact error message?
Mount /dev/sda2 as you did, and post back this:
ls -l /mnt/boot
ls -l /mnt/boot/grub
Finally, let’s look at the MBR and the partition boot sector, too:
First of all, thank you very much for taking the time to help me.
History - Computer was running fine with an IDE drive. I wanted to try a SATA drive. Since the IDE drive was identified as /dev/sda (/boot on sda2) I used “dd” from a live CD to copy the entire IDE drive to the SATA drive. I then disconnected the IDE drive and tried booting from the SATA which was now /dev/sda. This failed of course since /boot/grub/menu.lst identified the old IDE drive BY DRIVE NAME AND ID. I edited the file so that the SATA drive was identified as /dev/sda2. I have done this on other grub menus. The grub default entry now reads…
The boot process starts normally. The grub menu displays. The default boot section starts. Then after some USB probing etc. it reports “Could not find /dev/sda2”.
Now on to your other questions…
linux:/home/linux # mount /dev/sda2 /mnt
linux:/home/linux # ls -l /mnt/boot
total 10220
-rw-r–r-- 1 root root 843681 Jan 14 02:36 System.map-2.6.22.19-0.2-default
-rw------- 1 root root 512 Oct 17 01:26 backup_mbr
lrwxrwxrwx 1 root root 1 Oct 17 01:23 boot → .
-rw-r–r-- 1 root root 80417 Jan 14 02:40 config-2.6.22.19-0.2-default
drwxr-xr-x 2 root root 4096 Feb 3 10:07 grub
lrwxrwxrwx 1 root root 28 Jan 24 16:10 initrd → initrd-2.6.22.19-0.2-default
-rw-r–r-- 1 root root 4615761 Jan 24 16:10 initrd-2.6.22.19-0.2-default
-rw-r–r-- 1 root root 103100 Sep 21 2007 memtest.bin
-rw-r–r-- 1 root root 389120 Dec 28 18:43 message
-rw-r–r-- 1 root root 100260 Jan 14 02:41 symsets-2.6.22.19-0.2-default.tar.gz
-rw-r–r-- 1 root root 400576 Jan 14 02:41 symtypes-2.6.22.19-0.2-default.gz
-rw-r–r-- 1 root root 116297 Jan 14 02:40 symvers-2.6.22.19-0.2-default.gz
-rwxr-xr-x 1 root root 2147432 Jan 14 02:40 vmlinux-2.6.22.19-0.2-default.gz
lrwxrwxrwx 1 root root 29 Jan 24 16:09 vmlinuz → vmlinuz-2.6.22.19-0.2-default
-rw-r–r-- 1 root root 1594380 Jan 14 02:36 vmlinuz-2.6.22.19-0.2-default
linux:/home/linux #