can 11.1 DVD Repair system not repair Kernel 2.6.27.48-0.3???

English Install/Boot/Login
1

I lost my previous mainboard Asus p4pe-x/te due to electric sparks during a thunderstorm.

I got a replacement :
Asus P4p800 deluxe
after installation win 98se works after driver upddate o.k

Opensuse 11.1 did not start.
I used the 11.1 instalation cd and did a systems repair.
According yast everything is ok. Except it detects an boot loader error.
(The configuration of the bootloader contains errors).
Repair: Comes up with Bootloder settings-Sction management:

Section name : SUSE LINUX
Section settings:
repair=1 resume=/dev/diskby-id/ata-ST33206720A_9QF79MNJ-part5 splash-silent showopts
Kernel image:
/boot/vmlinuz
innitial ramdisk;
/boot/initrd
Root device:
:76MNJ/part6
Vga Mode:
0x31a

and the repective failsafe option.

after o.k.
There comes:
The Bootloader was installed successful.

thereafter again it comes:
Bootloader error detected
“Repair”
The same bootloader Section management file comes up again.
after o.k
comes again:
The Bootloader was installed successfullt

after o.k.:
'Repairing bootloader… Repair was successful.

o.k.: reboots the System

On Reboot comes the Message Gnu Grub Ver 0.97
Minimal BASH-like line editing is supported …

Grub>
nothing eslse

I repeated this procedure Various times. Always with the same result/
I cleared even the first head of each harddrve, but no change.
With clonzilla sysrescue v. 3.1.0, I can access and mount every partition.

It looks like the 11.1 dvd Kernel can not recognize my system.
Or the pata_via modul is not working

System Kernel is 2.6.27.48-0.3

What puzzels me is that Yast Repair uses resume=/dev/diskby-id/ata
whilst the fstb uses /dev/disk/by-id/scsi-SATA

Need very urgent help and advice.

Can I use an 11.2 repair DVD or better upgrade to 11.3? Does anyone know it could work?

Thanks for your answers.

Willi

Here come some files:

/etc/fstab

/dev/disk/by-id/scsi-SATA_ST3120026A_5JS2MXTT-part4 /windows/C vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JS2MXTT-part6 /windows/D vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JS2MXTT-part7 /windows/E vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JS2MXTT-part8 /windows/F vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JS2MXTT-part9 /windows/G vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JS2MXTT-part10 /windows/H vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part14 /windows/I vfat users,gid=users,umask=0002,utf8=true 0 0

/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part15 /windows/J ntfs-3g force,users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8, 0 0

/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part6 /windows/K vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part7 /windows/L vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part8 /windows/M vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part9 /windows/N vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part10 /windows/O vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part11 /windows/P vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part12 /windows/Q vfat users,gid=users,umask=0002,utf8=true 0 0

/dev/disk/by-id/scsi-SATA_ST3200826A_4ND084LP-part6 /windows/M vfat users,gid=users,umask=0002,utf8=true 0 0

/dev/disk/by-id/scsi-SATA_ST3200826A_4ND084LP-part7 /windows/R ntfs-3g force,users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8, 0 0

/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part6 / ext3 defaults 1 1
/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part10 /data1 auto noauto,user 0 0
/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part11 /data1 auto noauto,user 0 0
/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part12 /data1 auto noauto,user 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JS2MXTT-part5 swap swap defaults 0 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part5 swap swap defaults 0 0
/dev/disk/by-id/scsi-SATA_ST3120026A_5JT3SJWL-part5 swap swap defaults 0 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part2 /boot ext3 defaults 1 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part7 /home ext3 defaults 1 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part8 /opt ext3 defaults 1 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part13 /tmp ext3 defaults 1 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part9 /usr ext3 defaults 1 0
/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part15 /windows/J ntfs-3g noauto,user 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
/dev/fd0 /media/floppy auto noauto,user,sync 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0

/etc/mtab
/dev/sdb6 / ext3 rw 0 0

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

debugfs /sys/kernel/debug debugfs rw 0 0

udev /dev tmpfs rw 0 0

devpts /dev/pts devpts rw,mode=0620,gid=5 0 0

securityfs /sys/kernel/security securityfs rw 0 0

none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0

/etc/grub.conf
setup --stage2=/boot/grub/stage2 --force-lba (hd0) (hd1,1)
quit

/etc/sysconfig/bootloader/
CYCLE_DETECTION=“no”
CYCLE_NEXT_ENTRY=“1”

LOADER_LOCATION=""
DEFAULT_NAME=""
DEFAULT_APPEND=" resume=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part5 splash=silent showopts"
DEFAULT_VGA=""
FAILSAFE_APPEND=""
FAILSAFE_VGA=""
XEN_KERNEL_APPEND=" resume=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part5 splash=silent showopts"
XEN_APPEND=""
XEN_VGA=""

/Boot/gub/device.map

(hd1) /dev/disk/by-id/ata-ST3320620A_9QF76MNJ
(hd0) /dev/disk/by-id/ata-ST3120026A_5JS2MXTT
(hd2) /dev/disk/by-id/ata-ST3120026A_5JT3SJWL

2

Man this is messed up
I’m crashing for the night, but i would seriously consider starting over.

3

You know that normally I suggest you reinstall your Operating System anytime you must replace a motherboard unless you got an identical replacement. I did try a motherboard replacement after I bricked one with a BIOS update and I found that Windows 7 did finally restart OK, but even so, there were odd things like being unable to use the built-in backup, until I finally did a full OS reinstall.

Now after I looked at your fstab file, it looks like you have went kind of partition crazy creating so many different mounts and separating all of the Linux folders as well. When I look at what grub does when it loads, it does not find your menu.lst file. Normally this would be located in /boot/grub which you show to be:

/dev/disk/by-id/scsi-SATA_ST3320620A_9QF76MNJ-part2 /boot ext3 defaults 1 0

in your fstab file. So you need to check for this file and recreate from your backups if needed. Since you say you got Windows XP running, how are you running it if your Grub menu is missing?

So, if it was me, I would do away with most of the seperate folders for Linux and just keep three with swap, / & /home. You could even leave /home unformatted and try a reinstall of openSUSE. Since you were using openSUSE 11.1, you might try loading openSUSE 11.2 which you can find here:

ftp://ftp.klid.dk/opensuse/distribution/11.2/iso/

Of course you can find openSUSE 11.3 online at any time. Try to find your menu.lst file in /boot/grub. Consider reducing the number of partitions for openSUSE and installing either version 11.2 or 11.3 and good luck with what ever you decide to do.

Thank You,

4

Hallo James,

I m using Suselinux since Version 6.3 and I never had to reinstall a linux.
My windows system is an old 98SE and it runs peerfect now on the Via controller. If I hook the harddrives to an Ich5 Intel, it does not recognize 2 partitions on drive 2 after the ext3 partitions.

I used pqmagic Bootloader before to start dos and win and the boot partiyion of linux. Now I deleted the mbr of the first disk and set the windows drive active.

However Linux 11.1 does not work with the via controller. because the pata_via kernel modul or the via 82cxxx are broken.

I found in the meantime that the grub menu.1st and menu.1st.old were ovewritten and contain only garbadge. I try now to move the harddrives to the ich5 controller and manually edit the menu.1st.

I hope this might help to start lniux on the ich5 controller. Thereafter I have to care about the Kernel problem becuse I must go back onto the Via.

Any other advise is appreciated.

Thank you

Willi

5

I am puzzeled
The fstab Yast created starts for the harddrives with

/dev/disk/by-id/scsi-SATA_ST3120026A,

however in lilo.conf yast wrote

/dev/disk/by-id/ata-ST3120026A

In my second system (11.2)

all fstab entries start with /dev/disk/by-id/ata-

Why and what is the difference???

can this be the cause why the system not starts ???

Thanks for any answer

Willi

6

Like Caf said, a true mess. Just one example: you have three partitions all mounted on /data1, that cannot be what you want. My 2 cents: backup everything and start from scratch, think about your partitioning.

7

Oh wonder

What the repair system automatic or manual could not do

The Clonzilla SysRescCD v.3.1.0 did.

The tool “Boot an existing on Disk 32bit Linux”

Did it.

With this tool I can boot my system. I checked the system works fine.

This system works with Kernel 2.6.35-std160-i386

Now my Questions:

Can I use Yast 11.1 in My system to configure a new bootloader? Because all the bootloader related items contain nothing or wrong entries due to the previous trys to repair with the 11.1 repair tools?

The file Grub.conf reads:
setup –stage2=/boot/grub/stage2 –force-lba (hd0) (hd1,5)
quit
Does the first (hd0) mean Grub is installed in the mbr of the 1st harddrive ??
because

File grub.conf.old reads:
setup –stage2=/boot/grub/stage2 –force-lba (hd1,5) (hd1,5)

I know the stage1, 1.5 and 2 s well as the menu.1st are on the (hd1,5)

Thank you for your help

Willi

8

I know now pritty well what wentt wrong.

Using the 11.1 DVD for repair does not work because the via kernelmodule is broken, and all my repair attempts worsened the problems.

The 3 data 1 mounts of part 10,11 and 12 of ST3320620A_9QF76MNJ are the result of an automatic repair and carry now an # in front.
Dont look at the non linux mounts. They are requied because I run an good old win98SE (This is very reliable and much faster than the XP on my second system) in dual boot and I want to have access under linux.

I transfered my systm back to the ich5 Controller and I can start with the Clonzylla"" tool. Now I just need a little help to get it under 11.1 running and kernel 2.6.27.48-0.3. (See my previous reply)

9

Solved Problem

After studying through various Grub manuals and pages I decides to set up a new Grub.
This worked, but whenever I wroth a new menu.lst, I still could not boot, because it was always overwritten by yast. Even when I used the Power Quest tool “wipetrkd.exe” to delete the entire 1st head of the drives.
After lot of web searches I was sure, Yast does not accept another grub installation, but its own.

I changed strategy.

The via_pata kernel bug was fixed, so my system running on kernel 2.6.27.48-0.3 should be up and running if I just could boot into.

I moved the boot partition into the /root/boot and deleted it.
I used an 11.2 DVD started the repair tool and repaired in expert tools only the bootloader with minimum sections. I got some error messages regarding initrd and setup (I have 3 Kernels installed, delft, pae and debug)

After reboot I could start my system in failsafe mode using Yast I added a chain loader and changed the grub settings to generic mbr.
When I rebooted grub-yast booted a wrong windows partition. I again deleted the first head of the primary master, used the 12.1 dvd again to create a new bootloader. It started thereafter in full mode. Using yast to configure a new bootloader worked. I now could boot all operating systems of my system.

However I expected trouble whenever there is another kernel update or I need to change anything in kernels or modules, because my menu.lst contained only 3 Suse items:

Modified by YaST2. Last modification on Tue Nov 2 07:49:11 GMT 2010

default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd1,5)/boot/message

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1
root (hd1,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 resume=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part5 splash=silent showopts vga=0x31a
initrd /boot/initrd

###Don’t change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (fd0)
chainloader +1

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.1
root (hd1,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
initrd /boot/initrd

I had enough of the cumbersome menu.lst editing, and used an much easier method.

I de-installed the Delft-Kernel and reinstalled it hereafter using Yast. After a reboot the proper entries were in the menu.lst. Next I started with the delft-kernel, de-installed the other kernels and reinstalled them again… This gave me the correct menu first.

Modified by YaST2. Last modification on Mi Nov 3 05:43:27 GMT 2010

default 2
timeout 8
##YaST - generic_mbr
gfxmenu (hd1,5)/boot/message

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.48-0.3 (default)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.48-0.3-default root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 resume=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part5 splash=silent showopts vga=0x31a
initrd /boot/initrd-2.6.27.48-0.3-default

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.1 - 2.6.27.48-0.3 (default)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.48-0.3-default root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
initrd /boot/initrd-2.6.27.48-0.3-default

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.48-0.3 (pae)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.48-0.3-pae root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 resume=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part5 splash=silent showopts vga=0x31a
initrd /boot/initrd-2.6.27.48-0.3-pae

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.1 - 2.6.27.48-0.3 (pae)
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.48-0.3-pae root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
initrd /boot/initrd-2.6.27.48-0.3-pae

###Don’t change this comment - YaST2 identifier: Original name: linux###
title Debug – openSUSE 11.1 - 2.6.27.48-0.3
root (hd1,5)
kernel /boot/vmlinuz-2.6.27.48-0.3-debug root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 resume=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part5 splash=silent showopts vga=0x31a
initrd /boot/initrd-2.6.27.48-0.3-debug

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1
root (hd1,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 resume=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part5 splash=silent showopts vga=0x31a
initrd /boot/initrd

###Don’t change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (fd0)
chainloader +1

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.1
root (hd1,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320620A_9QF76MNJ-part6 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a
initrd /boot/initrd

title win 98se
rootnoverify (hd0,3)
chainloader +1

title winthai
rootnoverify (hd0,2)
makeactive
chainloader +1

title dos
rootnoverify (hd0,0)
makeactive
chainloader +1

Now My system is o.k again and running like a clockwork.

Thank you all for your kind help and comments.

Willi

10

Nice
Thanks for the update