https://bugzilla.novell.com/show_bug.cgi?id=829436 https://bugzilla.novell.com/show_bug.cgi?id=829436#c0 Summary: systemd[1] dependency failed for /windows/G , grub2, no repair tools Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.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 Thread: systemd[1] dependency failed for /windows/G , grub2, no repair tools http://forums.opensuse.org/english/get-technical-help-here/install-boot-logi... Also: https://bugzilla.novell.com/show_bug.cgi?id=824861 alannsandiego Join Date May 2009 Location San Diego CA 92138 Posts 25 Default Re: systemd[1] dependency failed for /windows/G , grub2, no repair tools I noticed no one yet has a good solution to my original problem, except to get the developers to correct the problem ( 7/12/2013, This fix of the boot system is a complex fix and not to be done manually.

This is about asking the developers to build onto OpenSuse a GUI tool If you want to communicate with the developers, you need to open a bug in Bugzilla or a feature request in FATE. OK I see about this. Without an OpenSuse GUI repair tools and admin functions like saving all emails and personal settings, not everyone want to be a Linux expert, or do commands in text lines in Linux to use it. Without better support Linux remains unusable for productions system; it is just very pretty but not useful.)

so here it is again: 7/5/2013, Dear Forum, I have backup hardware the same as my desktop, but after a Restore on the backup hardware OpenSuse 12.3 will not boot: 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. =================================================== Even though the hardware is the same the device by ID is slightly different and so that method fails and the backup hardware will not start up completely. It boot too the emergency system even though all of OpenSuse is found and only non primary XP partitions are not found. The only reason that OpenSuse 12.3 boot at all is the start up script now ignores Dev/by id and now ignoring /Dev/by id method and booted /Dev/root must do the same thing for the XP C drive, but OpenSuse missed ignoring /Dev/by id method for my two other internal hard drives. Even if I replace my one of my failing drive OpenSuse 12.3 would fail to boot with the Dev/by id method; because the new drive will have a new ID and the only time OpenSuse repairs the boot method now is on an install; so any changes or do a restore to backup hardware and OpenSuse 12.3 can not be easily repair at present. Since there is no Live-CD with repair tools to fix the boot method like ================================================= BTW DO NOT USE THIS TOOL ON OPENSUSE, IT DOES NOT WORK FOR OPENSUSE. How about Novell fix this so that it works for OpenSuse? boot-repair: Simple GUI tool to Repair Grub2 Boot Loader | Handy Tutorial boot-repair-disk - Browse Files at SourceForge.net 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. ================================================================================= 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. ======================================================== OpenSuse 12.3 is a great op system if nothing breaks, but the lack of repair tools on a Live-CD is a great defect. Any suggestion for a non expert? a simple way to fix this problem? ========================================================== It does not matter who owns OpenSuse This is not a backup issue, the backup and restore work very well. This is about asking the developers to build onto OpenSuse a GUI tool like the one above and this comment This entails booting from a live/rescue DVD/CD and doing a chroot Might want to look at this thread https://forums.opensuse.org/english/...-not-boot.html

From a live-CD tool you have to use chroot to change the broken system, and of course if you read carefully, this boot does not need to fail at all same method use to find the /dev/root and c for XP can find all the drives with the same partition structure if the fix systemd[1]?

Yes, if you can expert you can use the emergency repair system to manual fix the broken system, But why not have a GUI repair tool for this and other repairs? As soon as I replace my week drive OpenSuse 12.3 will not boot because the boot process will not see the new drive with the /Dev/by ID method. Until you fix this I can not use OpenSuse. At the present time on on install do you fix the boot process and that is not good enough to use your system. User benefit: If you replace a hard drive on an OpenSuse system at present the system will fail boot because you have no process to fix the boot process by repair GUI. Also after a restore to almost identical hardware the system does not boot even after a restore because your boot process does not see the same partitions on drive with a different /Dev/by ID number There is a simple fix to this problem is to change the systemd[1] script to ignore /Dev/ by ID number and boot to /dev/root and ADD a method to SEE non root partitions as you have already done for /Dev/root and XP root or C: drive. 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.