[Bug 824861] New: boot fails because xp dependant drive not found
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c0 Summary: boot fails because xp dependant drive not found Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 32bit OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: root.aimcmp2@cox.net QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 6/13/2013 Dear Sirs, I have backup hardware, i.e. 2 computer with same hardware; none the less the drive ids are different slightly. These are Intel Core I7 CPU 870 @2.93GHz, 3 Western Digital VelociRaptor 1 300gb main drive and 2 150gb data drives. After restore of backup image from Main Desktop, backup hardware fails to boot on a dual boot system with Grub2 because it can not file "depentant drives" as the drive ids are slightly differnet even with the same drive model and size. Grub2 now finds Linux, where grub did not for a while, same reason; main drive id slightly different Desktop and backup hardware; and Grub2 find Xp, But Grub2 OR the boot system does not find "depentant drives" on the XP SP3 system and FAILS TO BOOT. WHY WOULD Linux not boot because of XP? Seems always should boot if finds Linux? Please advise. Even if I replace Grub2, system would still not start as your log clearly states: fail dependent drives and lanches emerency system and a mount -a fails to clear the problem. Reproducible: Always Steps to Reproduce: 1.6/13/2013 Dear Sirs, I have backup hardware, i.e. 2 computer with same hardware; none the less the drive ids are different slightly. These are Intel Core I7 CPU 870 @2.93GHz, 3 Western Digital VelociRaptor 1 300gb main drive and 2 150gb data drives. After restore of backup image from Main Desktop, backup hardware fails to boot on a dual boot system with Grub2 because it can not file "depentant drives" as the drive ids are slightly differnet even with the same drive model and size. Grub2 now finds Linux, where grub did not for a while, same reason; main drive id slightly different Desktop and backup hardware; and Grub2 find Xp, But Grub2 OR the boot system does not find "depentant drives" on the XP SP3 system and FAILS TO BOOT. WHY WOULD Linux not boot because of XP? Seems always should boot if finds Linux? Please advise. Even if I replace Grub2, system would still not start as your log clearly states: fail dependent drives and lanches emerency system and a mount -a fails to clear the problem. 2. 3. Actual Results: boot fails emeregcy login provided only Expected Results: dual boot -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c1 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |root.aimcmp2@cox.net --- Comment #1 from Jiri Srain <jsrain@suse.com> 2013-06-14 01:45:24 UTC --- Sorry, I don't understand what the problem is from your description. Where exactly does the boot process fail? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c2 Alan H Robinson Jr <root.aimcmp2@cox.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |root.aimcmp2@cox.net InfoProvider|root.aimcmp2@cox.net | --- Comment #2 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-18 08:52:19 UTC --- https://bugzilla.novell.com/show_bug.cgi?id=824861 14 June 2014, 11:30am pt U.S.A. Dear Sirs, I do not see any way to take the log files off the broken backup computer. Novell missing the fact the Backup Hardware never will be the same as the original system. I only reason the system boot at all is you now ignoring /dev/by id method and booted /dev/root Here is more description: last boot mesg: started show plymouth boot screen ---- boot log says this: systemd[1] dependency failed for /windows/G. ------------------------------------------- That is the best I can do for now. Let me know if that helps? Alan H Robinson Jr for www.aimcmp.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c3 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |root.aimcmp2@cox.net --- Comment #3 from Jiri Srain <jsrain@suse.com> 2013-06-19 01:20:16 UTC --- I think that for your use case, mounting by ID is not the right choice - if you want to easily move the system to another hardware. You have basically two options: - either change the device IDs in fstab manually after the move - use a different device naming scheme - e.g. by UUID od by label, or you can still use the old-fashioned device names, if you can assure that they will be stable (e.g. because having a single drive only). This can be changed in the YaST partitioner in running system as well as during installation. Mounting by-id is not the only option - it is only the default and different use-cases have different requirements. I hope I got your problem right. Please, tell me if I can help any more... -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c4 Alan H Robinson Jr <root.aimcmp2@cox.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|root.aimcmp2@cox.net | --- Comment #4 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-19 09:46:45 UTC --- 6/19/2013, Dear Support, It is incumbent on Novell to build an op system that is flexible and easy to use; It is too complex to do what you have suggested. I have tried changing from dev/id to /dev/sda6 and it just changed back. How about Novell fix this so that it works for OpenSuse? http://handytutorial.com/boot-repair-simple-gui-tool-to-repair-grub2-boot-lo... http://sourceforge.net/projects/boot-repair-cd/files/ Home How-To Ubuntu Linux Windows About Us Handy Tutorial boot-repair: Simple GUI tool to Repair Grub2 Boot Loader I tried this tool and it missing one routine "xxxx..." someone commented about it; the routine is not on the disk and so this tool is broken. ======================================================== And further, if you want people to use your op system then put back the system repair tools. ======================================================== Alan H Robinson Jr for www.aimcmp.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c5 --- Comment #5 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-20 13:09:06 UTC --- 6/20/2013, Dear Support, You are ignoring the fact that I have shown you that OpenSuse 12.3 will not start because of XP; at the very least OpenSuse should always start and not be dependent on XP. Also I have shown you that OpenSuse does find the OpenSuse's primary partition and XP's primary partition by ignoring the dev/by id method and boots with the fallback dev/root likely dev/sda6 or /dev/sdb6; why not have a fall back method for other than primary XP partitions? In all cases, OpenSuse 12.3 should start regardless of XP and you should have some method fixing the boot up during start-up or of repairing the Grub2 boot loader method from a GUI. I am hopeful you will refer this problem to development for a fix in the near future. Besides my specific problem, I have also suggest that you have on your install DVD a repair tool(s) like the Simple GUI tool to Repair Grub2 Boot Loader and other repair tools so that one can fix and repair and installation from the DVD. Looking forward to you working on these ideas. Alan H Robinson Jr for www.aimcmp.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c6 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |fcrozat@suse.com InfoProvider| |root.aimcmp2@cox.net --- Comment #6 from Jiri Srain <jsrain@suse.com> 2013-06-21 07:01:35 UTC --- This is not support - it is tool for tracking bugs in the software. If you need support, you should contact openSUSE forums. openSUSE fails to boot because it fails to mount one of partitions, which is referenced incorrectly (due to changed disk ID). Any heuristic, which tries to determine whether a filesystem is necessary or not, is only a heuristics and may fail. You may remove windows from your fstab if it is not needed (or stop mounting it on boot). Additionally, the bug does not seem to refer to GRUB or bootloader at all - it is about systemd mounting the partitions. About the repair tool: It is about having someone, who develops and (especially) maintains such tool. You are free to convince anyone in the openSUSE community to do so - or even do it yourself - and I'm pretty sure that if such tool works reliably, it will be added to the medium of the next release. However, openSUSE is a community project, and not a product owned by SUSE or Novell. Given that it is expected that mounting a partition will fail if the device identification in fstab changes, I don't really see what the bug to fix is. I also don't see why booting e.g. by device or by label fails for you. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c7 Alan H Robinson Jr <root.aimcmp2@cox.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|root.aimcmp2@cox.net | --- Comment #7 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-23 09:21:26 UTC --- 6/23/2013, Dear Support, I am going to remove OpenSuse 12.3 from my computer and find a better Linux distribution as the only time OpenSuse find my hard drives is when it is installed. Even an over install does not fix the boot process. You have no Live-CD with repair tools on it, and have not referred my development requests; so if anything goes wrong with your op system no way to fix it. It is too much trouble to support and use your version of Linux, as when I replace one of my drives that has gone defective your system will not find the new drive by Dev/id. Once installed your boot processes do not self heal as expected and if the Dev/id changes and you present NO tools to fix the boot process. In this case Linux self heals by ignoring Dev/by id and booting by device for Linux but Your OpenSuse 12.3 fails to start because it does not boot by device for other than the primary partition of XP, therefore your Linux fails to boot to int6 or GUI because of XP other than primary partitions only, which of course if absurd. This problem is much worse than a bug, it makes your software useless. Once installed you present no tools for fixing the boot structure; unlike Windows XP which is a much simpler op system, even it can find new drives on a restore. During boot, by Live-CD, or after boot you present no GUI tool to change or fix the boot process, or change it from Dev/by id, to by device, or by label; when changed in Grub2 (a Grub2 bug) this simply changes back to what you set it too on the install. The tool I presented might work if the missing procedure is installed in my installation before use; I will check this; also this tool is from a distribution with better supported clearly. You have not referred this flaw/bug in your op system to the development department or to systemd[1], systemd mounting the partitions development. Of course a op system that will not boot is not useful. OpenSuse 12.3 is clearly only useful if nothing goes wrong and nothing changes as you have no LIVE-CD with repair tools or any other repair GUI to fix you op system if anything goes wrong or changes; this is much worse than a bug; it makes your op system useless. Thanks for the information. I understand the problem much clear now; I am sorry you or Novell not able to improve this major flaw in your op system; much worse than a bug. Never mind then, if you unable to fix it or have someone help you. I fix it myself if I can; and I look for the Linux distribution that has the GUI repair tool where it came from. With out repair tools your distribution is not useful as it just breaks and can not be fixed. Alan H Robinson Jr for www.aimcmp.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c8 --- Comment #8 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-23 09:32:16 UTC --- The particular bug in Grub2 is that if you change from /Dev/by id to Dev/device this does not change the installation itself; it changes back. And further Grub2 does not present a list of /Dev/by id, or /Dev/device, or /Dev/by label to choose from so that one does not make an error in a long description. You are right that if your op system was not defective, buggy, it would self heal in the systemd[1], systemd mounting the partitions would self heal as it now does for all partitions exception non primary XP ones, it is a simple fix if you cared to fix your defective op system; it would be repetitive to fix it in Grub2 as well. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c9 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |root.aimcmp2@cox.net --- Comment #9 from Jiri Srain <jsrain@suse.com> 2013-06-25 03:00:43 UTC --- How does your report relate to GRUB2? Provided I understood correctly, the system halts in situation, when GRUB had loaded kernel, it had mounted the root filesystem and continues booting up to the point when it needs to mount the other filesystems, in particular the one with Windows. This has nothing to do with GRUB2 any more. Could you, please, elaborate on what is the bug in GRUB2 itself? Regarding repair tool: As I wrote above, bugzilla is a tool for handling bugs. You wrote yourself that lack of such tool is not only a bug. I really think that if you want to change this, you should go to the openSUSE mailing lists or forums. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c10 Alan H Robinson Jr <root.aimcmp2@cox.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|root.aimcmp2@cox.net | --- Comment #10 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-25 22:31:10 UTC --- The particular bug in Grub2 is that if you change from /Dev/by id to Dev/device this does not change the installation itself; it changes back. And further Grub2 does not present a list of /Dev/by id, or /Dev/device, or /Dev/by label to choose from so that one does not make an error in a long description. at stated above. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c11 --- Comment #11 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-25 22:37:55 UTC --- Thank you for helping me to understand what the problem is, as you have noted there are several ways to solve this problem; I am sorry if you bug reporting system is not able help with the fix; or refer for development. Can you explain why when I change in Grub2 from Dev/by id to /Dev/by device it changes back? How do I am a request for development to systemd[1], systemd mounting the partitions department? Can you give the specific forums I should use then? Any specific suggestion of how to get the problem solved? 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c12 --- Comment #12 from Jiri Srain <jsrain@suse.com> 2013-06-26 05:16:23 UTC --- @comment#10: Where exactly did you change it and where exactly it did not change? I don't understand. Can you refer to specific files or tools? Perhaps this will be more helpful... Also, remember that GRUB2 (or any bootloader) during the boot process does not care about the UNIX-like devices - it uses the BIOS naming scheme. @comment#11: I cannot explain it, since I don't understand what exactly you change and what did not change. For forums: Find the right one on http://forums.opensuse.org/forum.php, based on your topics. Mailing lists are available at http://lists.opensuse.org/; opensuse@opensuse.org (resp. alternatives for different languages) are targeted to user-to-user support. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c13 --- Comment #13 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-26 08:34:17 UTC --- 6/26/2013 Dear system bug persons, In as much as you have made a false assumption that the Dev/id never change and that your op system is useless if it does not start and/or find and mount all the filesystem the user wants; how do I suggest a change for the developers? Since you have a process already in place during the install process to find and mount file system; why not do so each time you fail to find what you looking for? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c14 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |root.aimcmp2@cox.net --- Comment #14 from Jiri Srain <jsrain@suse.com> 2013-06-27 06:03:07 UTC --- Can you have an example when device ID changes unless you replace the specific disk? Moving to different machine (or replacing a disk) is something, that does not happen on daily basis and changing the device identification manually is reasonable request. Note that old-fashioned device names (/dev/sda) can change on every boot and may only depend on the order the drivers get initialized. In fact, even forgotten USB stick can change that. You are free to choose the naming scheme in the installer. We believe that IDs are the most sane default. Regarding heuristics: That would be dangerous. Either specified disk is found, or mounting should fail. Imagine that you mount a different partition somewhere, where your software expects his cache and can remove any data... It is much safer to require user in such case to explicitly change the configuration. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c15 Alan H Robinson Jr <root.aimcmp2@cox.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|root.aimcmp2@cox.net | --- Comment #15 from Alan H Robinson Jr <root.aimcmp2@cox.net> 2013-06-27 14:14:29 UTC --- 6/27/2013, Dear bug support, Please close this case since you unwilling or unable to help. I will not use or recommend you op system to any one until you have more support for your op system and/or fixed this and any other serious defects. Your op system fails after a restore to backup hardware that is as similar to the original as possible. If you op system will not start after a restore it is not useful and can not be used for serious purposes or in a production system. As I have time I will see if I can make the tool I suggested work for your system, if not I will review for better Linux distribution going forward. Alan H Robinson, Jr. for www.aimcmp.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c16 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #16 from Jiri Srain <jsrain@suse.com> 2013-07-01 08:48:37 UTC --- OK, closing. Note, that above I tried to explain the reason for the decision to use device IDs, as well as suggested to use different naming scheme which fits you scenario. I also did not get from you sufficient information to resolve (where exactly - e.g. which bootloader config file - you changed the device and where - e.g. in which config file - it was not changed). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=824861 https://bugzilla.novell.com/show_bug.cgi?id=824861#c17 --- Comment #17 from Xiyuan Liu <xyliu@suse.com> 2014-01-10 08:18:29 UTC --- *** Bug 829436 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=829436 -- 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.
participants (1)
-
bugzilla_noreply＠novell.com