[Bug 204745] New: OpenSUSE 10.2 alpha 4 fails to boot after installing on x86-64 with existing LVM patition setup
https://bugzilla.novell.com/show_bug.cgi?id=204745 Summary: OpenSUSE 10.2 alpha 4 fails to boot after installing on x86-64 with existing LVM patition setup Product: openSUSE 10.2 Version: Alpha 4 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Blocker Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: oded@geek.co.il QAContact: qa@suse.de On an AMD64 system with a pre-existing partition setup that employs LVM, I chose "Expert partitioning" and chose to use the current LVM setup on modified. This included: /dev/sda1 /boot (ext3) /dev/sda2 LVM PV /dev/mapper/root / (ext3) /dev/mapper/swap swap (ext3) /dev/mapper/home /home (ext3) The SUSE installer identified all the partition correctly and even detected the swap partition as swap. I had to help it with the mount point (which is reasonable) and then instructed it to format /boot, / and swap. After finishing the install without problems, the system rebooted but failed to start: there was a report about a missing root partition and waiting for the boot partition to appear. Above that there were several errors about evms_activate failing. The boot process then dropped me in a shell. I tried to run evms_activate by hand, but got a report about a missing libgcc_s.so.1 and evms_activate aborted. At this point the system is unusable. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 cthiel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |fehr@novell.com |screening@forge.provo.novell| |.com | ------- Comment #1 from cthiel@novell.com 2006-09-12 06:01 MST ------- Thomas, could you please look into this? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |oded@geek.co.il ------- Comment #2 from fehr@novell.com 2006-09-12 06:35 MST ------- Is the name of the VG really "mapper"? This might cause problems since there is already a subdirectory /dev/mapper used by device mapper. LVM will uses a subdirectory /dev/<vgname> with the name of the volume group. Please retry renaming the VG using the vgrename command. evms_activate has nothing to do with LVM, do not start it unless you know what you are doing. Please attach y2log files. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #3 from oded@geek.co.il 2006-09-12 06:55 MST ------- Sorry - the vg name is "system", I mistyped it above - it was available as /dev/mapper/system-<label>, and I mistyped it. I think the problem was that evms_activate wants libgcc_s.so.1, and that isn't installed on the initrd. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #4 from fehr@novell.com 2006-09-12 07:25 MST ------- As already said evms_activate is certainly not necessary to be called in initrd when you do and LVM based installation. Please attach full y2log file so that I can see what setup you have. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #5 from spam.lounge@gmail.com 2006-09-27 08:53 MST ------- Just wanted to let you guys know that this bug also cropped up in SUSE 10.1 after a series of updates I did yesterday. I opened a separate bug for 10.1: https://bugzilla.novell.com/show_bug.cgi?id=208417 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|oded@geek.co.il | Resolution| |FIXED ------- Comment #6 from fehr@novell.com 2006-10-19 05:47 MST ------- Problem should be fixed with updated mkinitrd. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 bdorner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #7 from bdorner@novell.com 2006-12-27 13:41 MST ------- This bug appears to be the same or very simular to the one I posted earlier today. Bug number 230876. It is happening in the latest code that I could find -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #8 from fehr@novell.com 2006-12-27 13:49 MST ------- Does not make much sense to open multiple bugs for the same problem. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 bdorner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #9 from bdorner@novell.com 2006-12-27 19:17 MST ------- yes I know. I found this bug only by accident. That is why I added my comments to this bug. Even though it is marked resolved I thought it might get the correct person looking at the bug I entered. I also thought it might help to have the information of both bugs to help resolve this. This is a nasty bug and appears to have distroyed 700 gB of my data and I can't even get rid of the lvm data that it sort of thinks is there. I currently have 700 GB of useless hard drive space. I am hoping that the data is still there but I am unable to read, mount, remove, delete or do anything else with the drives. so sorry for the duplicate but I did know this bug was there or I would have re opened it. Anyways, now that I have your attention. How do I fix this? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |bdorner@novell.com ------- Comment #10 from fehr@novell.com 2006-12-28 02:37 MST ------- I do not see much similarities between the other bug you opened an this one. The other bug was during update and involved a failed bootloader install, this one is during a new installation and involves a failing reboot since mkinitrd seems to mis-detecte a LVM setup as an EVMS setup. Neither bug contains y2log files, so with the currently available data, neither can be properly processed. If you are really unable to read any data from your drives, there is not much I can do to help since it is not possible to get any useful data about your setup. I am on vacation until 8th of January and cannot do much except bugzilla access until then. To provide the needed data to debug your problem there are two ways - try the update a second time and attach y2log files - boot a rescue system and execute the lvm commands "vgscan -vvv" and "vgchange -vvv -ay" and attach the output here. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #11 from bdorner@novell.com 2006-12-28 09:21 MST ------- Sorry I must have missed the reboot part of this bug. My other bug started with an update process. That was where it started to go wrong with the boot loader install. I started to play with the command-line LVM commands and was finally able to remove the physical and logical volumns. I then went into the install disks and choose to repair the drives. It found several problems with the partitions. Once those were fixed I was able to go into yast and recreate the LVM, formatting the drives. Of course this meant that I lost all of my data, but I have some backups and it is better to have some data loss but gain the use of my computer. It all appears to have come down to having a mixed SATA and IDE hard drive setup. Once I disconnected the SATA HD I was able to install, but by then the damage was done. Once it installed I was able to connect the SATA HD again and the do the steps above the computer now works. Thanks for the help. I'll put this same comment on the other bug -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #12 from fehr@novell.com 2006-12-28 09:33 MST ------- Cannot say much about the problem during bootloader installation of the other bug since I am not involved in bootloader setup. I do not really understand why you removed the LVM logical volumes via LVM command line tools (of course removal of a logical volume means loss if all data on that volume). If you can remove logical volumes, the volume group is necessarily consistent and you could simply have kept the logical volumes. I still do not see what this bug has to do with your problem (except that LVM is involved). So far I also do not see what might have caused your problem at all. I fear without either y2log files or debug output of the LVM commands there is no way to find out what actually happened. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #13 from bdorner@novell.com 2006-12-28 09:47 MST ------- Don't worry about it. I made a mistake associating it with this bug. I read through the first paragraph of the initial comment and missed the reboot part. The first paragraph of this bug was exactly what I experienced, but not the rest of it. I was in a hurry and mis-read the rest of the bug. As for the volume group, I was unable to do anything with it, until I removed the LV's and PV's via the command line tools. No matter what I did in yast with the partition or LVM tools I could not access the group nor partitions. It appears that whatever happened during the update process where the boot loader didn't install, that it messed up the partition tables on the hard drives ( specially those associated with the LVM). I only removed the LV's and PV's as a last resort. Believe me I didn't want to do that, but after 10 hours of trying to fix this I came to the conclusion that nothing else would work and I needed the computer. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #14 from fehr@novell.com 2006-12-28 09:56 MST ------- Strange, if you can remove the LVs you should also be able to mount them. Did you remove the LVs and PVs with lvm commands or did you simply remove the disk partitions with parted or fdisk? Do you have any log file of YaST2 or debug output of lvm tools. Without these it will be difficult if not impossible to track down what really caused your problems. Systems with mixed SATA and IDE disks are not too uncommon these days so I doubt this is a general problem with such as mixed setup. -- 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, or are watching someone who is.
From what I hear the combined SATA and IDE is still fairly common. But I run in a world where people build their own or modify their own computers. It might be
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #15 from bdorner@novell.com 2006-12-28 10:45 MST ------- I repaired the partitions, but that didn't seem to fix the lvm problems. I did not remove the partitions or do anything other then repair them. As for removal of anything I only removed the LV's and PV's for the LVM. that my world is different. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #16 from fehr@novell.com 2006-12-28 16:27 MST ------- What exactly did you do to "repair" the partitions? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 ------- Comment #17 from bdorner@novell.com 2006-12-29 10:50 MST ------- I ran the repair install option off of the installation cd. Then selected the repair partitions option. I don't remember the exact names of the options but that is basically what I did. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204745 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|bdorner@novell.com | Resolution| |FIXED ------- Comment #18 from fehr@novell.com 2006-12-29 13:41 MST ------- Ok, this explains he problem. This repair options searches for filesystem signatures on the disk and creates new partitions matching these signatures. Of course this destroy any LVM setup already on the disk. Closing this now. The the reason for reopening it was invalid anyway. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com