Bug 154707

please attach /var/log/YaST2/*

/etc/grub.conf
/boot/grub/menu.lst
fdisk -l

The machine frooze a couple of time during install, so Yast2 logs might be a bit chaotic... (see bug #154709)
As it's well over 5M, I made it available for download at http://www.mkk.szie.hu/~czanik/allinone.tar.gz

I cleaned the MBR by dd if=/dev/zero of=/dev/sda, reinstalled 10.0 and now I have the same problem with 10.0 too. It boots fine, when started with an install CD and "boot from harddrive is choosen". But at least it runs stable...

Petr: Compress the logs using bzip2 (`bzip'-command or `tar bjvf y2logs.tar.bz2 /var/log/YaST' - this will store much more than gzip.

Are you sure the bootsector of that disk is OK? Have you tried using another disk?

I'm sure it's OK. I installed XP on it, and it boots fine from the disk, and if I write something to /dev/sda I can read it back without any problem.
Error checking the hard drive did not find any trouble.
I installed 10.0 again, and I have 'GRUB Hard Disk Error' again. 
Logs recompressed, now just 3.5M: http://www.mkk.szie.hu/~czanik/aia.tbz

Please always add files using the bugzilla attachment feature, this is more reliable and ensures the persistance of the availability of this data.

Please provide the information asked for by Martin in comment #1 and salvage the defective bootsector with `dd if=/dev/sda of=bootsector.bin bs=512 count=1' and also attach it here.

OK. Sorry, but my original logs were rejected by bugzilla, as oversized. I try it again.

Created attachment 71370 [details]
fdisk -l

Created attachment 71371 [details]
the boot sector

Created attachment 71372 [details]
grub.conf

Created attachment 71373 [details]
menu.lst

Created attachment 71374 [details]
YaST2 logs

This is a new install, not what I originally reported, but has exactly the same problem.

Thorsten: I suppose this is a GRUB problem? However if you suspect YaST, assign it back to us.

The working 10.0 configuration would have been interesting.

Peter, can you verify that the BIOS agrees with the 4425/255/63 geometry of the disk, and also add `fdisk -l -u` output to a matching `fdisk -l`?

I can't verify the BIOS, at least I could not find anything in the Adaptec SCSI BIOS.

czanik@linux:~> cat fdisk-l

Disk /dev/sda: 36.4 GB, 36401479680 bytes
255 heads, 63 sectors/track, 4425 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         637     5116671   a5  FreeBSD
/dev/sda2             638         768     1052257+  82  Linux swap / Solaris
/dev/sda3   *         769        1160     3148740   83  Linux
/dev/sda4            1161        4425    26226112+   f  W95 Ext'd (LBA)
/dev/sda5            1161        1813     5245191   83  Linux
/dev/sda6            1814        2466     5245191   83  Linux
/dev/sda7            2467        2597     1052226   82  Linux swap / Solaris
/dev/sda8            2598        2916     2562336   83  Linux
/dev/sda9            2917        2982      530113+  82  Linux swap / Solaris

czanik@linux:~> cat fdisk-lu

Disk /dev/sda: 36.4 GB, 36401479680 bytes
255 heads, 63 sectors/track, 4425 cylinders, total 71096640 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63    10233404     5116671   a5  FreeBSD
/dev/sda2        10233405    12337919     1052257+  82  Linux swap / Solaris
/dev/sda3   *    12337920    18635399     3148740   83  Linux
/dev/sda4        18635400    71087624    26226112+   f  W95 Ext'd (LBA)
/dev/sda5        18635463    29125844     5245191   83  Linux
/dev/sda6        29125908    39616289     5245191   83  Linux
/dev/sda7        39616353    41720804     1052226   82  Linux swap / Solaris
/dev/sda8        41720868    46845539     2562336   83  Linux
/dev/sda9        46845603    47905829      530113+  82  Linux swap / Solaris

I installed Lilo on a friends recommendation (which I have not used for ages), and the machine boots just fine.

FYI, I installed BETA8 on my IBM IntelliStation Mpro and it works fine.
But mine has a single IDE boot drive -- not an adaptec SCSI like yours.

I tested 3 different SCSI and SCSI RAID controllers, and they don't work with GRUB. Now I just leave the install CD in, 'boot from HDD' is default and find GRUB successfully, where normal boot does not work...

i have several simple pentium2/3/celeron systems upgraded lately to suse 10.1 from retail suse media. all systems have simple ide/atapi controller, no "fancy" stuff like sata, scsi or the like.

on one system i cant boot directly any more, only when i leave the suse 10.1 retail cd/dvd in the drive, and wait for the timeout, it then selects "boot from harddisk" (or similar) and then comes up with the grub loader from the installed/upgraded suse 10.1 from the harddisk.

we have a discussion ongoing in the following thread/subthread:
http://lists.suse.com/archive/suse-beta-e/2006-Jun/0058.html

thanks for any more hints. regards.

Closing NOREPSONSE, due to missing information. Please retest on openSUSE 11.0 and create a new bug report if the problem still persists.