After rescue repair - disk mounted by id, mess in GRUB

Hi,
I find no short summary of my problem so please go thru this short story :wink:

My disk looks as follow:

sda
sda1 - Primary Part. (NTFS - WinXP)
sda2 - Primary Part. (Ext3 - “/”)
sda3 - Extended Part.
sda4 - Logical Part. (FAT32 - my files)
sda5 - logical Part. (FAT32 - my files)

Bootloaders were (at least I was thinking they were) as follow:
sda (standard code)
sda1 (Win XP Bootloader)
sda2 (GRUB Bootloader wit entries to Linux and Windows)

Boot flag was set to sda2 of course.

As you see I was able to simply re-install Windows without touching Linux. I did a Windows re-installation.
Of course this set the boot flag to disk sda1 and I was no able to boot my Linux.

So using a SUSE DVD I boot into a repair console and using fdsik just reverted the boot flag to sda2.

Reboot and … OK GRUB appeared but complained that can not find kernel.

At this point it’s probably worth to notice that my windows reinstall actually affected the SUSE somehow. A bit strange but maybe I was wrong and GRUB was not at sda2. Anyway I don’t need to track back what has happened, I need to fix it.

Then using the rescue DVD I’ve chosen Expert mode and selected the Bootloader repair. Only 2 default boot entries were created (SUSE and fails safe SUSE). After reboot OK the GRUB booted SUSE an I’ve get in to my OS but now the mess starts-up:

To add back my Windows to the bootloader menu I went o YaST > Bootloader and selected join with old GRUB entries. Looked OK, all the old entries came back.

Reboot and a disaster - could not boot anything. some strange erors, that disk entries are not OK or smth like that.
Using GRUB console I managed to boot SUSE.

What I have found is that now:

All disks in the Partitioning Manager are mounted not as sdaX but as a long strings disk-by-id or smth.

The same **** is in the bootloader entires.

Editing the bootloader entries and setting it to sdaX doesn’t make sense until I not fix mounting to be sdaX.
I can mount sda1,sda4 and sda5 back using sdaX instead of this disk-by-id. But the most important ROOT “/” sda2 I can’t. YaST says - Can not perform - files system in use, sorry.

Guys, can you help me to make it from scratch.

Mount disk by disk using sdaX format.
and after that erase all the GRUB containment and add all entries once again.

Thanks in Advance.
Marek

This may not be the reccomended method, but you could try to edit /boot/grub/menu.lst to suit your needs.
You could also try booting from a livecd and using chroot to get into the root directory and use yast from a console to modify the booting process.

GRUB menu has some stupid entries [hd0,2] and this mess-up, should I delete this?
Anyway I would prefer some semi-automatic way. To erase all and build it up once again from scratch.

But first have a look on fstab.etc.
The root partition “/” is mounted not as sda2 but using this disk id or smth. Due to that, when I’m trying to change bootloader entires under YaST it doesn’t see the sda2 disk. Only this long strings.

have a look fstab.etc:


/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part3 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part6 /mnt/sda6            vfat       user,users,gid=users,umask=0002,utf8=true 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
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part5 /mnt/sda5            vfat       ro,user,users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part1 /mnt/sda1            ntfs-3g    ro,user,users,gid=users,fmask=133,dmask=022,locale=pl_PL.UTF-8 0 0

The menu.lst looks now as follows:


# Modified by YaST2. Last modification on sob kwi 10 20:17:41 CEST 2010
default 0
timeout 8
gfxmenu (hd0,2)/boot/message
##YaST - activate


###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1
    root (hd0,2)
    kernel /boot/vmlinuz root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd


###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
    rootnoverify (hd0,0)
    chainloader +1


###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Tryb bezpieczny -- openSUSE 11.1
    root (hd0,2)
    kernel /boot/vmlinuz root=/dev/sda2 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1  x11failsafe
    initrd /boot/initrd


###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-xen
    root (hd0,2)
    kernel /boot/vmlinuz-xen root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd-xen


###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-2.6.27.45-0.1-xen
    root (hd0,2)
    kernel /boot/vmlinuz-2.6.27.45-0.1-xen root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd-2.6.27.45-0.1-xen


###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-2.6.27.45-0.1-default
    root (hd0,2)
    kernel /boot/vmlinuz-2.6.27.45-0.1-default root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd-2.6.27.45-0.1-default

Afterwards I think maybe the fault was using fdisk under Rescue Console without chrooting into my SUSE? So the disk was not seen as sda but this stupid ids?

Post output of
fdisk -l

what you said in the first post does not match what is being reported in the second.

Hmmm - I don’t see your 2nd partition in your fstab at all.

Here’s some suggestions:

  • download and burn a SuperGrub CD. This is just a handy utility that can help restore your Grub mbr instead of using grub-install. Boot from the SuperGrub CD. This alone might resolve your issues - but if it doesn’t:
  • 2nd idea - check boot/grub/device.map. That should tell you what GRUB sees as your disk descriptions, by disk-id
  • Next, record the output of fdisk -l. This will tell you what your current partition id’s are.
  • Since we know that Grub refers to the 1st hdd as 0, when fdisk calls it 1 (eg. Grub hd0 = fdisk hd1, or sd1), you now know where grub is looking for stuff.
  • using a live cd, check, and edit if necessary, your fstab and menu.lst. You can replace any /disk/by-id/yada yada-part x with the appropriate (corresponding and correct) hdx or sdx notation. It won’t hurt anything to NOT use the disk-by-id.

Examples from my machine:

**device.map**
(hd1)	/dev/disk/by-id/ata-WDC_WD1600AAJB-00J3A0_WD-WCAV37419469
(fd0)	/dev/fd0
(hd0)	/dev/disk/by-id/ata-WDC_WD200BB-00DEA0_WD-WMAD22357848

# **fdisk -l**

Disk /dev/sda: 20.0 GB, 20020396032 bytes
255 heads, 63 sectors/track, 2434 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x89ca89ca

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        1129     9068661    7  HPFS/NTFS
/dev/sda2            1130        2434    10482412+  83  Linux

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00065272

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         411     3301326   82  Linux swap / Solaris
/dev/sdb2   *        1432        2434     8056597+  83  Linux
/dev/sdb3             412         672     2096482+  83  Linux
/dev/sdb4             673        1431     6096667+  83  Linux

Partition table entries are not in disk order

**fstab**
/dev/sdb1 swap                 swap       defaults              0 0
/dev/sdb2 /                    ext4       acl,user_xattr        1 1
/dev/sdb3 /var                 ext4       acl,user_xattr        1 1
/dev/disk/by-id/ata-WDC_WD200BB-00DEA0_WD-WMAD22357848-part2 /home                ext3       defaults              1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/sdb4 /home/hiero/looksee1 ext4       defaults              1 2

**menu.lst**
# Modified by YaST2. Last modification on Sun Apr  4 12:17:46 EDT 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

default 0
timeout 8
gfxmenu (hd1,1)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.2
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.31.12-0.2-default root=/dev/sdb2 resume=/dev/sdb1 splash=silent quiet showopts vga=0x31a
    initrd /boot/initrd-2.6.31.12-0.2-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.2
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.31.12-0.2-default root=/dev/sdb2 showopts 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.31.12-0.2-default

###Don't change this comment - YaST2 identifier: Original name: memtest86###
title Memory Test
    kernel (hd1,1)/boot/memtest.bin

###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-2.6.31.12-0.2-default
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.31.12-0.2-default root=/dev/sdb2 resume=/dev/sdb1 splash=silent quiet showopts vga=0x31a
    initrd /boot/initrd-2.6.31.12-0.2-default

###Don't change this comment - YaST2 identifier: Original name: other###
title Windows XP
    rootnoverify (hd0,0)
    chainloader +1

You will see that I am using the “sdx” convention in menu.lst, and partly in fstab. I edited menu.lst and fstab manually to replace the disk-id’s when I inserted a new hard drive to replace a failing drive. That way I just copied the partitions, booted a live cd, did a little editing, and I was up and running again.

This is my disk report


Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd391d391

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        4741    38082051    7  HPFS/NTFS
/dev/sda2   *        4742        6374    13117072+  83  Linux
/dev/sda3            6375       30401   192996877+   f  W95 Ext'd (LBA)
/dev/sda5            6375       18388    96502423+   b  W95 FAT32
/dev/sda6           18389       30401    96494391    b  W95 FAT32

Ouch nothing matches up.

Where is the second drive???

fdisk shows only one drive the tables indicate 2

oops sorry looking at the wrong post

Ok looking at the right set

you are trying to mount Part 3 (sda3) as root which is an extended partition as root should be part 2 (sda2)

You have no swap partition ! Not immediately fatal but could cause problems depending on how much memory you have

Actually cygi, am I correct in thinking that before all this started you had another partition in front of the ext3 for linux at ‘/’? In other words your disk would have looked like this:

sda1,primary partition,windows xp installation or something else
sda2.primary partition,something else or windows xp installation
sda3,primary partition,linux ext3 mounted as ‘/’
sda4 extended partition
sda5,logical partition,fat32
sda6,logical partition,fat32

If so, did you then combine sda1 and sda2 into a new primary partition for the re-installed windows xp system? This would change the partition numbering and the devices with which they are associated. The inconsistencies between your fstab, menu.lst and ouput of fdisk -l seem to suggest this.

I think all you have to do is, under the Suse DVD edit the following directly:

  1. for /etc/fstab on sda change the lines:

/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part1 to /dev/sda1
/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part3 to /dev/sda2
/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part5 to /dev/sda5
/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part6 to /dev/sda6

  1. for /boot/grub/menu.lst on sda change all references from (hd0,2) (i.e. partition 3) to (hd0,1) (i.e. partition 2).

Then try rebooting. You may find that grub still complains because it thinks that the stage 1.5 stuff is still on partition 3 whereas it is now on partition 2. If so, grub can be re-installed. Let us know what happens.

Actually, no …

For 100% before re-install WinXP it was as it is in fdsik now.

In the ancient times I had something similar to what you describes:

sda1 primary winxp
sda2 extended
sda3 logical “/”
sda4 logical swap
sda5 logical other
sda6 logical other

But that was when I had SUSE 10.1. New 11.1 was not put on the old one. I first re-configured and erased disk to what we see today in the fdisk.

Could SUSE find somewhere this old geometry during automatic repair and create all this mess?

Can I operate in fstab names as /dev/sda1 or it always has to be disk/by-id? This disk/by-id propagates to for example YaST when I’m trying to set-up GRUB. In past I could choose location of the boot-loader using sdaX format, now it displays these long strings.

Actually I would prefer to re-insatll GRUB. Is it just go to YaST and un-install packages, add them back. Will it automatically detect both OS’es?
During SUSE installation it was done automatically without bothering me with Terminal set-up. Could it be same way now?

I know - but with my usage of PC is enough. At my previous PC SUSE 9 was running on 400MB RAM plus 2GB swap, so now 3 GB of RAM is an incredible amount for me ;p

You can use the old sdax syntax. You just need to be pointed to the right partition. The disk by Id is just a link to the device sdax anyway.

To reinstall grub boot from the install media and do a repair. You can just repair grub.

Some clarifying or confusing comments:

But that was when I had SUSE 10.1. New 11.1 was not put on the old one. I first re-configured and erased disk to what we see today in the fdisk.

Could SUSE find somewhere this old geometry during automatic repair and create all this mess?

I am not sure how the problems arose. Since you erased the disk I don’t think so but we have to manage the problem as it is now. Obviously my theory of how it happened is incorrect!

Can I operate in fstab names as /dev/sda1 or it always has to be disk/by-id? This disk/by-id propagates to for example YaST when I’m trying to set-up GRUB. In past I could choose location of the boot-loader using sdaX format, now it displays these long strings.

You can operate in either. Disk by id caters for the more general situation where you may have multiple disk controllers and you cannot determine the order in which the disks will be detected and device names assigned. Simple device names such as /dev/sda1 etc can be used when your hardware is fairly straightforward.

AN EXAMPLE
On most of my systems, I can use simple device names but on one particular system of mine which has:

1 sata disk
1 IDE pata disk
1 IDE pato cdrom
1 pata disk connected to a PCI IDE board

I cannot predict which order the drives will be detected. So the sata disk may be /dev/sda on one boot and /dev/sdc on the next etc. Here disk by id was the solution. In your case you can probably get away with simple device names. Yast will use ‘disk by id’ as a default to give you a guaranteed solution but you can change that if you wish. More on this below.

END OF EXAMPLE

Actually I would prefer to re-insatll GRUB. Is it just go to YaST and un-install packages, add them back. Will it automatically detect both OS’es?
During SUSE installation it was done automatically without bothering me with Terminal set-up. Could it be same way now?

The problem is that Yast and the bootloader definitions seem to have got themselves in a knot and I feel it would be best to change the details in the menu.lst and fstab files directly to make sure these are consistent with the current hardware (as shown in fdisk -l). When you have the system up and running, you can revert to Yast and manage further changes from there. At the moment, fstab and menu.lst refer to invalid partion numbers and Yast (using from fdisk?) cannot work out what to do. Further to that, fstab has disk by id entries and menu.lst has simple device name entries. Strictly speaking the two should be the same type. Hence I recommend you edit the fstab and menu.lst files as per my last post (unless someone else can think of a whizzo way of doing it automatically).

Before you edit, make sure you take a copy of fstab and menu.lst in case for some reason you make a mistake and make the situation worse.

Then, after editing, try and re-boot the system and tell us what happens when grub loads or tries to. I suspect it will complain about not finding stage 1.5/2 but I could be wrong. If that happens then repair grub. I have never used the repair facility on the DVD (gogalthorp can help you there) but if it is along the lines as given in the Howto All About Grub - openSUSE then I would think you need to open an su command prompt under the DVD, run grub then enter the commands:

find /boot/grub/menu.lst #should return (hd0,1)
root (hd0,1)
setup (hd0,1) #installs grub in the boot sector on the second partition whereas (hd0) = mbr
quit

then reboot.

ABOUT USING YAST TO MANAGE PARTITIONS

Unfortunately all my suse linux systems are either 11.0 or 11.2 (and I cannot remember the exact gui for the partitioner in 11.1). In both of those if you edit a partition entry amd click on the ‘Fstab Options’ button you can then bullet the desired ‘Mount in /etc/fstab by:’ option - ‘Device name’, ‘Device ID’ etc.

Hope that helps you.

I decided to set-up things manually.

So first the /etc/fstab:


/dev/sda1                                 ext3       acl,user_xattr        1 1
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
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

Win partition and others can wait.
Performed a REBOOT.

Then I uninstalled the following packages:

  • gfxboot
  • gfxboot-branding-OpenSUSE
  • grub
  • bootcycle
  • splashing

I also deleted (have a backup copy) folder /boot/grub

Then I installed all the removed packages back.

After that was time for the manual set-up of the GRUB:

have a look:
device.map

(hd0)   /dev/sda

menu.lst


# Modified by YaST2. Last modification on czw kwi 15 21:38:09 CEST 2010
default 0
timeout 8
gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1
    root (hd0,1)
    kernel /boot/vmlinuz root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
    rootnoverify (hd0,0)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Tryb bezpieczny -- openSUSE 11.1
    root (hd0,1)
    kernel /boot/vmlinuz root=/dev/sda2 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1  x11failsafe
    initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-xen
    root (hd0,1)
    kernel /boot/vmlinuz-xen root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd-xen

###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-2.6.27.45-0.1-xen
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.27.45-0.1-xen root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd-2.6.27.45-0.1-xen

###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-2.6.27.45-0.1-default
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.27.45-0.1-default root=/dev/sda2 splash=silent showopts
    initrd /boot/initrd-2.6.27.45-0.1-default

These files I did not change but you can have a look:
/etc/sysconfig/bootloader


## Path:        System/Bootloader
## Description: Bootloader configuration
## Type:        list(grub,lilo,none)
## Default:     grub
#
# Type of bootloader in use.
# For making the change effect run bootloader configuration tool
# and configure newly selected bootloader
#
#
LOADER_TYPE="grub"


## Path:        System/Bootloader
## Description: Bootloader configuration
## Type:        list(floppy,mbr,root,boot,custom,none)
## Default:     mbr
#
# Location of boot loader.
# For making the change effect run bootloader configuration tool
#
#
LOADER_LOCATION=""
DEFAULT_NAME="openSUSE 11.1"
DEFAULT_APPEND="splash=silent showopts"
DEFAULT_VGA=""
FAILSAFE_APPEND="showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1  x11failsafe"
FAILSAFE_VGA=""
XEN_KERNEL_APPEND="splash=silent showopts"
XEN_APPEND=""
XEN_VGA=""
## Path:        System/Bootloader
## Description: Bootloader configuration
## Type:        yesno
## Default:     no
#
# Should the boot cycle detection be used to
# avoid unconditional reboot cycles of not
# supervised system.
#
CYCLE_DETECTION="no"

## Type:        integer(0:)
## Default:     1
#
# The number of the entry in grub's menu.lst
# which should be used on the next reboot cycle.
# Note that the first entry has the number 0.
#
CYCLE_NEXT_ENTRY="1"

/etc/grub.conf


setup --stage2=/boot/grub/stage2 --force-lba (hd0,1) (hd0,1)
quit

and the fdisk -l as you know already gives:


Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd391d391

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        4741    38082051    7  HPFS/NTFS
/dev/sda2   *        4742        6374    13117072+  83  Linux
/dev/sda3            6375       30401   192996877+   f  W95 Ext'd (LBA)
/dev/sda5            6375       18388    96502423+   b  W95 FAT32
/dev/sda6           18389       30401    96494391    b  W95 FAT32

In general it works now.
I have a GRUB gfx menu.
I can boot either Windows or Linux.

Except 1 stupid thing. In YaST2 disk partitioner disks are in a big mess and not as defined in the fstab! Crazzy.

The sda1 is mounted in /ext3 folder ;). sda5 as /media/STORE and the best one sda6 as “/”
This is of course as YaST2 is thinking, GNOME sees disks as they are in fstab.

See this: http://img707.imageshack.us/img707/7226/yast2.png
Sorry is in Polish but the columns are:
Device
Size
F
Type
Partition Type
Disk Label
Mounting Point - this is the crazy section!
Mounted according to or smth ;p

Still in YaST2 bootloader if I edit entires they disk are called:
/dev/disk/by-id/ata-Hitachi_HTS542525K9SA00_080423BB3F00WDJ6PBWF-part2 not sda2, but you saw the menu.lst is OK now.

From where SUSE gets these data I have no clue but this is not funny anymore.

Hope to repair it, not as always reinstall the whole linux, due to the leakage of my knowledge :confused:

BTW: Thx guys for the whole support so far. It’s good to be not alone :slight_smile:

Marek ‘cygi’

I think it would have been advantageous to have followed my/our recommendations more closely. It looks as though you have made a mistake in editing /etc/fstab. The line in that which says:

/dev/sda1 ext3 acl,user_xattr 1 1

I think is wrong. It does not contain a mount point and your linux root/boot partition is actually on sda2 (the second partition) and not sda1 (the first partition) as indicated. Thus it should read:

/dev/sda2 / ext3 acl,user_xattr 1 1

Note that partition p (e.g. 2) on the first hard drive would be device /dev/sdap (e.g. /dev/sda2) whereas for the grub and its menu items it is (hd0,{p - 1}) (e.g. (hdo,1). That may have confused you.

The system booted though its first stages OK because all the information is contained in the grub menu details (which are correct I think).

However, when the system then tries to use fstab, it would find it in error and may just ignore it. Normally when fstab is incorrect, you are presented with a black console screen in order for you to make changes to fstab through an editor, after which you have to re-boot. This did not happen I take it?

Yast would also find fstab in error so may just ignore it and would rely on system calls akin to ‘fdisk -l’ to obtain the partition information and then give you the defaults (disk by id) for setting up those.

Try correcting fstab and see what happens. Read what I said before about changing the mount methods in Yast from disk by id to simple device names.

Try again and let us know. You are almost there I think.

shame on me! What a mistake :
Will try after work today,
Cheers.

chnaged to sda2, reboot and still the same. with 1 small change. sda1 is mounted properly.

Seems like YaST2 has this buffered somewhere.
How to clear such a cache …

No Yast is not cached some place.

Exactly what ie wrong with what Yast is reporting?

It might help to see the output of

mount

Exactly what ie wrong with what Yast is reporting?

Well gogalthorp if you look at cygi’s Yast screen shot and ignore the sda1 erroneous mount (which has now been corrected apparently), you have both sda2 and sda6 mounted at ‘/’.

I am a truly puzzled penguin!

I notice that for suse 11.2 and 11.0 (I have no 11.1 system) the dependencies for yast2-storage include ‘parted’. So I am wondering if yast gets its information by calling that. In addition to the output of ‘mount’, maybe we could also look at the output of ‘parted -l’ to see if that shows any inconsistencies.

A change finally! :slight_smile:
After second reboot it is now OK in YaST as well.

I think the case is closed then.
Thank all of you for the support!

This anyway does not explain what has happen to my disk after WinXp reinstall.
the fact that rescue repair messed-up things I can imagine and in a way make sense but why the hell, simple WinXP reinstall upset my GRUB so I was forced to use a rescue repair - no clue.

But that is only a history now.
Have a nice weekend.

Most do not have this problem. Installing Windows after Linux is always a problem but most do not have a partitioning scheme like yours. I suspect you simply chose a incorrect option when repairing, but admit I don’t know what it was. Any time you mess with partitions and booting you have a chance of messing up if you are not certain of what you are doing with any OS.