systemd[1] dependency failed for /windows/G , grub2, no repair tools

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?

This is so bad for me I am look if other op systems better supported?

Thanks.

Use partition labels. Note you can get into trouble with them too if you do not make absolutely sure all partitions have unique labels.

But the above problem can be fixed remaking the grub menu. 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/get-technical-help-here/install-boot-login/486023-cloned-opensuse-12-2-server-will-not-boot.html

On 07/06/2013 05:06 AM, alannsandiego wrote:
>
> Novell missing the fact the Backup Hardware never will be the same
> as the original system

two things:

  1. you assumed Novell still owns openSUSE and SUSE Linux Enterprise
    Linux…

  2. you assumed a backup from one machine could be used to restore an
    identical clone system on a different machine…

both assumptions are incorrect…

first, Novell was purchased by a holding company which removed it
from managing control of both SUSE Linux Enterprise Linux (suse.com)
and openSUSE…

second, as far as i know there is no single recommended, supported,
open source method of hands-off cloning a complete openSUSE system
(or any other Linux system) from one hardware set to another…though
there are several threads in this forum discussing how that might be
done–perhaps if you review those you will find a method which might
work for you (it certainly is more involved than a simple application
restoring a backup from one machine to another), see
https://www.google.com/search?q=site%3Aforums.opensuse.org+how-to+clone

as for the rest of your post: there is no sense in trying to ‘fix’ a
system which was born in such a broken way…it is hopeless. (well,
some here might like to try to help you ‘fix’ it, so stay tuned!)

by the way, what tool did you use to make the backup you are trying
to restore to different hardware? and, did it claim to be able to
restore the backed-up system to different hardware? if so then you
need to ask the maker of that backup/restore software for help.

for example, if you used Acronis Backup & Recovery 11.5 Server for
Linux
http://www.acronis.com/backup-recovery/smallbusiness.html#products-linux-server
and it did not work for you, i’m sure the seller will fix their
product or return the $895 you paid for the application…

> This is so bad for me I am look if other op systems better supported?

if you find a distro (or an open source back-up/restore application)
which fully supports a so simple clone scheme, please let us
know–perhaps the openSUSE developers would like to mimic it…


dd

On 2013-07-06 05:06, alannsandiego wrote:
>
> 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*_

Novell? What did Novell tell you and where, please? Do you have a link?

If you want my long answer, read DD answer instead, he saved me typing :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Knock on wood and I don’t know if it would address exactly the OP problem, I can highly recommend the following as a versatile backup solution that implements cloning(imaging)

g4u - Harddisk Image Cloning for PCs

The only thing that worries me is that it’s maintained (very well) by a single individual. I would be very unhappy if his app suffers if anything should happen to him.
I’ve used it to backup/restore both Linux and Windows systems (in support of major upgrades).
Big Plus for me is that it supports practically any type of direct attached and network storage using any protocol of your choice.

Perhaps what has made my life simpler is that I try to avoid all disk identification issues by using hardware RAID over software RAID and trying to install systems on single volumes (non-critical storage can be on another volume), this means that any OS is a single integrated “whole” so internal identifiers are typically consistent even when hardware changes.

It’s not surprising that tools supporting GRUB2 might be missing, GRUB2 is a “new technology” (if you can consider any FOSS project still new after about 3 years while openSUSE has been using for less than half that).

But, have you considered using the Install DVD as your repair disk instead of a LiveCD(repair option)? It’ll generally have all the base repos on disk and be configurable to download/install/run anything you might want that’s not on the disk.

TSU

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?

If you do not understand problem then please do not post here.

On Wed, 10 Jul 2013 22:46:04 +0000, alannsandiego wrote:

> 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.

> If you do not understand problem then please do not post here.

No, if someone doesn’t understand the problem they’re free to participate
as long as they stay on topic in the help forums. Asking clarifying
questions helps everyone, and insisting that only people who know what
you mean at the outset participate means that you’re not going to get a
lot of replies.

Just as a point of clarification. :slight_smile:

Jim

Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 2013-07-07 01:16, tsu2 wrote:
> But, have you considered using the Install DVD as your repair disk
> instead of a LiveCD(repair option)? It’ll generally have all the base
> repos on disk and be configurable to download/install/run anything you
> might want that’s not on the disk.

12.3 has a dedicated rescue system, a whole CD, with XFCE :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

My apologies if you believe that my post was not on topic,

As Carlos highlighted from my post
AFAIK the rescue option from the DVD likely should have automatically fixed your fstab problem.
(No Desktop involved, it “just works” by itself).

TSU

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.

On 2013-07-12 19:36, alannsandiego wrote:

> 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.

That’s just your opinion, as many use it on production environments.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

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?

On 07/13/2013 07:26 PM, alannsandiego wrote:
> But why not have a GUI repair tool for this and other repairs?

so, the developers do NOT come to these forums looking for work to
do…if you want to request a new feature do that at
https://features.opensuse.org/

we here are just users LIKE YOU! we can’t do the work you want and
can make anyone else do it. get it?

STOP your asking here for development work and do it in the CORRECT
place…as you have been told before!!!


dd

On 2013-07-13 19:26, alannsandiego wrote:
>
> I_noticed_no_one_yet_has_a_good_solution_to_my_original_problem,_except_to_get_the_developers_to_correct_the_problem

For one, I have difficulty reading you, there are so many underscores on
your text, and you mix text from others and yourself, in a manner that I
have no idea what is yours and what is not.

However, I gather that you request developers to answer you.
WHO YOU SAY? We are just users of openSUSE, not the developers. The
developers that make the distro do not read the forum.

Do you get that clear?

I will not read the rest of your post, I get a headache.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

https://features.opensuse.org/315964

I am hoping for a fix.

I have to replace a none root hard drive and when I do so,
OpenSuse will be unusable until the next revision and at the present time
the boot process is fix only during the install.

On 2013-07-14 22:56, alannsandiego wrote:
>
> https://features.opensuse.org/315964
>
> I am hoping for a fix.
>
> I have to replace a none root hard drive and when I do so,
> OpenSuse will be unusable until the next revision and at the present
> time
> the boot process is fix only during the install.

Sigh…

You have to improve your writing skills if you want anybody to read that
and vote.

Sorry.

Can somebody be kind enough and translate what he wants, please?


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Yes. When you are using mount by ID (which normally includes HDD serial number) and replace HDD, system will fail to mount filesystems because at least /etc/fstab refers to old device ID (old serial number). I had even worse experience - apparently under some conditions YaST2 will put device ID in grub_installdevice as well, so re-installation of boot loader fails as well.

I’m not sure what can be done here though except not using device ID at all. There is no way system can tell that new device is replacement for the old device (if it were possible, we would not need the whole “device by ID” in the first place).

On 2013-07-15 04:46, arvidjaar wrote:
>
> robin_listas;2571888 Wrote:
>>
>> Can somebody be kind enough and translate what he wants, please?
>>
>
> Yes. When you are using mount by ID (which normally includes HDD serial
> number) and replace HDD, system will fail to mount filesystems because
> at least /etc/fstab refers to old device ID (old serial number). I had
> even worse experience - apparently under some conditions YaST2 will put
> device ID in grub_installdevice as well, so re-installation of boot
> loader fails as well.

True.

> I’m not sure what can be done here though except not using device ID at
> all. There is no way system can tell that new device is replacement for
> the old device (if it were possible, we would not need the whole “device
> by ID” in the first place).

Right, I use Labels instead. I can clone a system straight, but on the
other hand, I can not clone a disk and work with the original and the
destination mounted simultaneously (a situation I had recently).

Each “disk/by-…” has its uses and disadvantages, each one should use
what he prefers.

But still, I do not understand what alannsandiego wants the developers
to do. An automated rescue system, perhaps? A GUI for rescue?

openSUSE did have a GUI rescue system, but it had big bugs (big
cockroaches, not mosquitoes), so much that it was discontinued because
no one wanted to offer himself to maintain it.

Is that what he wants? :-?

It would be nice having such a software, but it is not going to happen,
no matter how many want it. Someone has to volunteer to create it.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)