March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 477412] New: stunnel starting to many processes and state not correct in yast's Runlevel.
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=477412 Summary: stunnel starting to many processes and state not correct in yast's Runlevel. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i386 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: HatingSpam2009(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009011912 Firefox/3.0.6 Using the default suse rpm stunnel 4.25-1.1 when I start (or after rebooting since stunnel is enabled) the stunnel service in System Services (Runlevel) it starts 6 processes of stunnel: nobody 3636 0.0 0.0 5380 1988 ? Ss 14:00 0:00 /usr/sbin/stunnel nobody 3637 0.0 0.0 4612 800 ? S 14:00 0:00 /usr/sbin/stunnel nobody 3638 0.0 0.0 4612 444 ? S 14:00 0:00 /usr/sbin/stunnel nobody 3639 0.0 0.0 4612 444 ? S 14:00 0:00 /usr/sbin/stunnel nobody 3640 0.0 0.0 4612 444 ? S 14:00 0:00 /usr/sbin/stunnel nobody 3641 0.0 0.0 4612 444 ? S 14:00 0:00 /usr/sbin/stunnel Also, when I use the Runlevel "expert mode" it says under Running NO when cleary it is running, I can start it and it will say yes, close the window and open it again and it will say NO again Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 410118] New: stunnel does not start
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=410118 Summary: stunnel does not start Product: openSUSE 11.0 Version: Final Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: gassauer(a)kde.org QAContact: qa(a)suse.de Found By: --- stunnel-4.21-28.1 does not start and does not report any errors with debug level 7. I compiled stunnel 4.25 from sources, installed it in /usr/local, adapted /etc/init.d/stunnel to point to the new location and was up and running (except that the /etc/init.d/stunnel script does not handle the pid file correctly yet and hence reports wrong status and does not stop the daemon) using the same config file with stunnel-4.21-28.1 does not work either. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 480777] New: yast2 created fstab entries for crypt files should be processed diffrently then now. (new loop dev should not be used unless luksClose is called on already used).
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=480777 Summary: yast2 created fstab entries for crypt files should be processed diffrently then now. (new loop dev should not be used unless luksClose is called on already used). Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: 19972005(a)mail.ru QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 According to parts of the sample demonstration below: 1. After issuing 'mount' on the entry from fstab w/ fs-type 'crypt' and option 'loop' the password is asked from STDIN, then cryptsetup taints encrypted file, /dev/mapper/_dev_loop0 and /dev/loop0 . 2. Now doing umount on the mount point of 1). The logical referense between encrypted file, /dev/mapper/_dev_loop0 and /dev/loop0 is NOT cleared (and that is okay - umounting should not lead to luksClose on device, or we will be unable to do safe fsck for example). 3. Now again doing the mount on the same mount point. The mount asks for password. Due to 2) that is wrong - the device /dev/mapper/_dev_loop0 is still present and may be used w/o password. And if we enter correct password when mounting again - we will see that mount creates new reference encrypted file, /dev/mapper/_dev_loop1 and /dev/loop1. Obviousely this will lead soon to reaching limit of avaliable loop devices. --------------------------------------sample_session: fs:~ # grep loop /etc/fstab /backup/my_pvt_pix_and_video.cfs /backup/mnt/my_pvt_pix_and_video crypt loop,noauto,acl,user_xattr 0 0 /backup/my_pvt_files.cfs /backup/mnt/my_pvt_files crypt loop,noauto,acl,user_xattr 0 0 fs:~ # mount /backup/mnt/my_pvt_files Enter LUKS passphrase: key slot 0 unlocked. Command successful. fs:~ # ls /dev/mapper control _dev_loop0 vg_backup-backup vg_data-data vg_os-root vg_os-varlog vg_swap-swap fs:~ # losetup -va /dev/loop0: [fd03]:19 (/backup/my_pvt_files.cfs) fs:~ # umount /backup/mnt/my_pvt_files fs:~ # mount /backup/mnt/my_pvt_files Enter LUKS passphrase: [now pressing ^C - this was just to indicate that password is asked again] fs:~ # mount | grep /backup/mnt/my_pvt_files fs:~ # losetup -va /dev/loop0: [fd03]:19 (/backup/my_pvt_files.cfs) fs:~ # ls /dev/mapper control _dev_loop0 vg_backup-backup vg_data-data vg_os-root vg_os-varlog vg_swap-swap fs:~ # cryptsetup status _dev_loop0 /dev/mapper/_dev_loop0 is active: cipher: aes-cbc-essiv:sha256 keysize: 128 bits device: /dev/loop0 offset: 1032 sectors size: 1391608 sectors mode: read/write fs:~ # mount /dev/loop0 /backup/mnt/my_pvt_files mount: unknown filesystem type 'crypto_LUKS' fs:~ # mount /backup/mnt/my_pvt_files Enter LUKS passphrase: key slot 0 unlocked. Command successful. fs:~ # losetup -va /dev/loop0: [fd03]:19 (/backup/my_pvt_files.cfs) /dev/loop1: [fd03]:19 (/backup/my_pvt_files.cfs) fs:~ # cryptsetup status _dev_loop0 /dev/mapper/_dev_loop0 is active: cipher: aes-cbc-essiv:sha256 keysize: 128 bits device: /dev/loop0 offset: 1032 sectors size: 1391608 sectors mode: read/write fs:~ # cryptsetup status _dev_loop1 /dev/mapper/_dev_loop1 is active: cipher: aes-cbc-essiv:sha256 keysize: 128 bits device: /dev/loop1 offset: 1032 sectors size: 1391608 sectors mode: read/write fs:~ # umount /backup/mnt/my_pvt_files fs:~ # mount | grep /backup/mnt/my_pvt_files fs:~ # mount /dev/mapper/_dev_loop1 /backup/mnt/my_pvt_files fs:~ # ls /backup/mnt/my_pvt_files lost+found fs:~ # umount /backup/mnt/my_pvt_files fs:~ # Reproducible: Always Steps to Reproduce: 1. create crypt file w/ yast2 (or entry in fstab and related encrypted file like in session above) 2. mount the crypt file fstab entry by directory name from fstab - password prompt appear. 3. Do umount on the direcrtory above. 4. Do mount again on the same directory - the password prompt appear. Actual Results: mount Asks for password and creates new security associations enstead of using old ones (that are still okay) Expected Results: 1. mount shoud store at some place an association between /dev/mapper/_dev_loop0, crypted file and mount point from fstab to reuse /dev/mapper/_dev_loop0 when trying to mount the entry from fstab that already has active /dev/mapper/... device (this happens if umount is called w/ the dir or file as param). Also some service script should be responsible for LUKS mappings in /dev/mapper At least boot.crypto says 'unused' if /etc/crypttab and /etc/cryptotab are not used even when LUKS mapped devices are present in /dev/mapper. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 481877] New: mkinitrd: support split mount provided by kiwi
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481877 Summary: mkinitrd: support split mount provided by kiwi Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: agraf(a)novell.com ReportedBy: ms(a)novell.com QAContact: qa(a)suse.de CC: nat(a)novell.com Found By: --- The current mkinitrd does not support mounting a split image created by kiwi. The kiwi split system creates a rootfs.tar archive which contains: - files which are temporary read/write - links to the read-only files - links to the read-write files mounting the root filesystem extracts the rootfs.tar archive into a tmpfs and therefore allows the temporary files to be read/write as well as access to all files in the read-only and read-write partitions. Usually the read-only partition is a compressed filesystem like squashfs and the read-write filesystem is ext3 for details how kiwi mounts such a system you can take a look into KIWILinuxRC.sh function mountSystemCombined { ... } This is relatively kiwi specific but it would be great if mkinitrd could support mounting split systems Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 450221] New: DMRAID refuses to activate SATA RAID sets
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=450221 Summary: DMRAID refuses to activate SATA RAID sets Product: openSUSE 11.1 Version: RC 1 Platform: i686 OS/Version: Windows XP Status: NEW Severity: Blocker Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lasse.penttinen(a)gmail.com QAContact: qa(a)suse.de Found By: Community User DMRAID has been tested to work on this PC using: Ubuntu 8.10 (and many older versions), PCLinuxOS 2008 Mini. I have a NTFS fake RAID setup I want to mount in openSUSE. I have done this with a number of Linux distros with success, but fails in openSUSE 11.1. Note: DMRAID detects two sets of metadata as I have changed the controller at some point. This has never been a problem. linux-jm7t:/home/ljpp # dmraid -r /dev/sdg: "pdc" and "isw" formats discovered (using isw)! /dev/sdf: "pdc" and "isw" formats discovered (using isw)! /dev/sdg: isw, "isw_beicabedcj", GROUP, ok, 240121726 sectors, data@ 0 /dev/sdf: isw, "isw_beicabedcj", GROUP, ok, 240121726 sectors, data@ 0 linux-jm7t:/home/ljpp # dmraid -ay -f pdc RAID set "pdc_begabfcgj" was not activated linux-jm7t:/home/ljpp # dmraid -an /dev/sdg: "pdc" and "isw" formats discovered (using isw)! /dev/sdf: "pdc" and "isw" formats discovered (using isw)! RAID set "isw_beicabedcj_RAID" is not active linux-jm7t:/home/ljpp # dmraid -ay -f pdc RAID set "pdc_begabfcgj" was not activated linux-jm7t:/home/ljpp # ls /dev/mapper control linux-jm7t:/home/ljpp # modprobe dm-mirror linux-jm7t:/home/ljpp # dmraid -ay -f pdc RAID set "pdc_begabfcgj" was not activated If this is a widespread problem, then I would presume it might be a blocker? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 430906] New: dmraid installation does not work when LVM partition exists on disk
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=430906 Summary: dmraid installation does not work when LVM partition exists on disk Product: openSUSE 11.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Winfrid.Tschiedel(a)fujitsu-siemens.com QAContact: jsrain(a)novell.com Found By: Beta-Customer openSUSE 11.1 Beta1 sees 2 disks when a LVM resides on RAID1 - Please see allocation of disk under fedora 9 : df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 30995384 5699396 23721488 20% / /dev/mapper/ddf1_4c53492020202020808626820000000035e41e3000000a28p6 194442 13003 171400 8% /boot tmpfs 2031996 48 2031948 1% /dev/shm parted /dev/mapper/ddf1_4c53492020202020808626820000000035e41e3000000a28 GNU Parted 1.8.8 Using /dev/mapper/ddf1_4c53492020202020808626820000000035e41e3000000a28 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: Linux device-mapper (dm) Disk /dev/mapper/ddf1_4c53492020202020808626820000000035e41e3000000a28: 159GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 74.0MB 74.0MB primary ext3 boot 2 74.0MB 8669MB 8595MB primary linux-swap 3 8669MB 35.5GB 26.8GB primary ext3 4 35.5GB 159GB 123GB extended 5 35.5GB 67.8GB 32.3GB logical ext3 6 67.8GB 68.0GB 206MB logical ext3 7 68.0GB 159GB 91.0GB logical lvm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 22

[Bug 481875] New: mkinitrd: support overlay mount (aufs,unionfs)
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481875 Summary: mkinitrd: support overlay mount (aufs,unionfs) Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: agraf(a)novell.com ReportedBy: ms(a)novell.com QAContact: qa(a)suse.de CC: nat(a)novell.com Found By: --- the current mkinitrd does not support overlay root mount via aufs or unionfs. If the root filesystem is compressed (squashfs) it would be great to mount that root filesystem with an overlay mount to support writes on the filesystem. - if no other than the partition with the compressed filesystem is available the mount should use a tmpfs. In any other case the available write partition should be used fore reference how kiwi mounts that system take a look into KIWILinuxRC.sh function mountSystemUnified { ... } would be great if you can implement that Thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 480747] New: Nagios Control Script Incorrectly Extracts Values from the Nagios Configuration File
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=480747 Summary: Nagios Control Script Incorrectly Extracts Values from the Nagios Configuration File Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marc(a)mccoombe.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 During system shutdown, I noticed two error messages (one from chmod and another from chown) when the Nagios service was being stopped. The same problem also happens when the service is being started, or restarted (see Actual Results). It appears that the get_var function in the /etc/init.d/nagios script does not remove the trailing carriage return (\r) from the lines it extracts from the /etc/nagios/nagios.cfg file. Note: Nagios still appears to run without issue. Reproducible: Always Steps to Reproduce: Run /etc/init.d/nagios restart as root user. Actual Results: Shutting down nagios Warning: nagios killedchmod: cannot access `/etc/nagios/resource.cfg\r': No such file or directory chown: invalid user: `nagios\r:nagcmd' done Starting nagios - Error: looks like nagios is still running with PID 11338 - trying to kill previous nagios processchmod: cannot access `/etc/nagios/resource.cfg\r': No such file or directory chown: invalid user: `nagios\r:nagcmd' done Expected Results: Shutting down nagios done Starting nagios done Workaround - Modify the get_var function in the /etc/init.d/nagios script as follows (i.e., change the sed command to also strip-out the carriage return character): # grab a config option function get_var() { if [ -n "$2" ]; then set -- `grep ^$1 $2 | sed 's@=@ @ ; s@\r@@'` else set -- `grep ^$1 $NAGIOS_CFG | sed 's@=@ @ ; s@\r@@'` fi shift # remove first ARG => search-string echo $* } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 481861] New: openSUSE BuildService - KDE:Community broken
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=481861 Summary: openSUSE BuildService - KDE:Community broken Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: mhoppe(a)novell.com QAContact: qa(a)suse.de Found By: IS&T I was unable to find any contact address for this .... I get this error for some days now: zypper lu (...) File 'repomd.xml' from repository 'openSUSE BuildService - KDE:Community' is unsigned, continue? [yes/NO]: n Retrieving repository 'openSUSE BuildService - KDE:Community' metadata [error] Repository 'openSUSE BuildService - KDE:Community' is invalid. Signature verification failed for repomd.xml Please check if the URIs defined for this repository are pointing to a valid repository. Warning: Disabling repository 'openSUSE BuildService - KDE:Community' because of the above error. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 469256] New: Differing entries in /etc/fstab and menu.lst (grub) for mounting by "Device Name"
by bugzilla_noreply＠novell.com 04 Mar '09

04 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=469256 Summary: Differing entries in /etc/fstab and menu.lst (grub) for mounting by "Device Name" Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: PC OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jaylinux52(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 I had a problem in installing openSUSE 11.1 in a PC with Windows XP already installed on HD 1. The HD's are as follows: HD 1: 250 GB IDE (PATA) (has C:/ of Windows) HD 2: 500 GB SATA (has ext3 partitions for Linux install) HD 3: 500 GB SATA (One FAT32 & two NTFS partitions) Details of the partition setup are in the attached files and in the text below (between <=====> lines for sake of clarity). In my opinion, what happened was that the openSUSE 11.1 install process/installer mixed up the naming in the system files (menu.lst, /etc/fstab). This may have been because, during the install process, I chose to mount the partitions in all 3 HD's by 'Device Name' instead of the (default) 'Device Id' (as I am more familiar with device names than Device Id's which can be long & complicated to remember. Win XP was already installed on C:/ partn. (/dev/sda1 to openSUSE 11.1 Linux) of 250 GB IDE HD. Then, I tried to install openSUSE 11.1 onto the 2nd HD, 500 GB SATA (/dev/sdb/ to Linux; / (root partition) on /dev/sdb3/, /boot on /dev/sdb2/ ... both on the 2nd HD (SATA). The openSUSE 11.1 install itself went ok. I went with the default option to install grub on the MBR (all the other options in grub were unchecked). The system re-booted with the grub menu listing openSUSE 11.1 & Windows XP properly. Am able to boot into Win XP. But when I try to boot into the newly installed openSUSE 11.1, after a series of messages in console view, the system stops saying that it could not detect/load /dev/sdb3/ (the root (/) partition in Linux) & then it just hangs there at $ prompt, & I have to reboot the system. The exact Error Message (in console/cmd-prompt view) is given below. ============================================================================== ...... (console text messages) Invoking Userspace resume from /dev/sdb1 resume: libcrypt version: 1.4.1 Trying Manual resume from disksdb1 Want me to fall back to /dev/sdb3 (Y/N) <Y> Waiting for device /dev/sdb3 to appear ......... not found -- exiting to /bin/sh $ < (I have to Ctrl-Alt-Del to re-start the PC) > ============================================================================== OLD CONFIG FILES are as follows: fdisk -l Results: Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xe393e393 Device Boot Start End Blocks Id System /dev/hda1 * 1 4255 34178256 7 HPFS/NTFS /dev/hda2 4256 30401 210017745 f W95 Ext'd (LBA) /dev/hda5 4256 10942 53713296 7 HPFS/NTFS /dev/hda6 10943 17629 53713296 7 HPFS/NTFS /dev/hda7 17630 24316 53713296 7 HPFS/NTFS /dev/hda8 24317 30401 48877731 7 HPFS/NTFS Disk /dev/sda: 500.1 GB, 500106780160 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x1154698e Device Boot Start End Blocks Id System /dev/sda1 1 262 2104483+ 82 Linux swap / Solaris /dev/sda2 4283 60801 453988867+ f W95 Ext'd (LBA) /dev/sda3 * 263 1897 13133137+ 83 Linux /dev/sda4 1898 4282 19157512+ 83 Linux /dev/sda5 4283 30550 210997678+ 7 HPFS/NTFS /dev/sda6 30551 37854 58669348+ 83 Linux /dev/sda7 37855 60801 184321746 b W95 FAT32 Partition table entries are not in disk order Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0d7a0d7a Device Boot Start End Blocks Id System /dev/sdb1 * 1 6375 51207156 c W95 FAT32 (LBA) /dev/sdb2 6376 60801 437176845 f W95 Ext'd (LBA) /dev/sdb5 6376 31872 204804621 7 HPFS/NTFS /dev/sdb6 31873 60801 232372161 7 HPFS/NTFS ============================================================================== menu.lst (/etc/grub/menu.lst) # Modified by YaST2. Last modification on Sun Jan 25 06:55:06 UTC 2009 default 0 timeout 25 gfxmenu (hd1,2)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.1 - 2.6.27.7-9 root (hd1,2) kernel /boot/vmlinuz-2.6.27.7-9-pae root=/dev/sdb3 resume=/dev/sdb1 splash=silent showopts vga=0x31a initrd /boot/initrd-2.6.27.7-9-pae ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.1 - 2.6.27.7-9 root (hd1,2) kernel /boot/vmlinuz-2.6.27.7-9-pae root=/dev/sdb3 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.7-9-pae ###Don't change this comment - YaST2 identifier: Original name: windows 1### title windows 1 rootnoverify (hd0,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: windows 2### title windows 2 map (hd2) (hd0) map (hd0) (hd2) rootnoverify (hd2,0) makeactive chainloader +1 ============================================================================== fstab (/etc/fstab) /dev/sdb1 swap swap defaults 0 0 /dev/sdb3 / ext3 acl,user_xattr 1 1 /dev/sda1 /Windows/C ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/sda5 /Windows/E ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/sda6 /Windows/F ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/sda7 /Windows/G ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/sda8 /Windows/H ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/sdb4 /home ext3 user,acl 1 2 /dev/sdb6 /tmp ext3 user,acl 1 2 /dev/sdb5 /windows/I ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/sdb7 /windows/J vfat user,users,gid=users,umask=0002,utf8=true 0 0 /dev/sdc1 /windows/L vfat user,users,gid=users,umask=0002,utf8=true 0 0 /dev/sdc5 /windows/M ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/sdc6 /windows/N ntfs-3g user,users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 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 ============================================================================== Reproducible: Always Steps to Reproduce: 1. During installation. 2. For partitioning, chose to mount by 'Device Name', instead of the default mount by 'Device Id'. 3. Actual Results: Could not boot into openSUSE 11. The Error Message details are as given above. Had to manually edit the /etc/fstab, and menu.lst files to ensure similar naming convention. After this manual editng, the system (openSUSE 11.1) booted properly. If relevant, grub was installed on MBR and GRUB aws used as the main bootloader. It could successfully boot into Windows XP. It could boot into openSUSE 11.1 only after the manual edit of the files as given above & in attachment. Expected Results: Should have booted into openSUSE 11.1 normally, since after install it gave an 'Install Successful & Re-booting' message. You can reach me at jaylinux(a)aol.in if you need further information /clarifications. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3