I was trying to update an SLES SP1, it was never updated since 2010, (just a zypper update) and something went really bad and i really don’t know what it is.
Some packages may have broken during the update and I just can’t get access to root anymore (i keep receiving the message login incorrect) but i am using the right password and the GUI also does not load anymore (direct access).
I can get access my personal account but sudo does not work so i can’t do anything useful with my normal user access.
I tried to go to single-user mode to change root password but the problem persists, even the new root password does not work (direct access and ssh)
My boss just lost the original SLES SP1 DVD (in fact, he lost the WHOLE box of the server, so i don’t have access to any manual or anything) that came with the SGI rackable h2106-g7 (our server) so i can’t use the DVD to do a boot and an automatic repair. The problem gets worse when i just can’t find a SLES SP1 trial version for download and use it to try an automatic repair (i can find SP2,SP3 and SP4 here )
I don’t know if this is related to the problem but a couple days ago I have added the openSUSE oss Repo to the YAST to get packages like nano,gfortran and nco (netCDF stuff).
I really don’t know what to do. Please guys help me
I was trying to update an SLES SP1, it was never updated since 2010, (just a zypper update) and something went really bad and i really don’t know what it is.
Some packages may have broken during the update and I just can’t get access to root anymore (i keep receiving the message login incorrect) but i am using the right password and the GUI also does not load anymore (direct access).
I can get access my personal account but sudo does not work so i can’t do anything useful with my normal user access.
I tried to go to single-user mode to change root password but the problem persists, even the new root password does not work (direct access and ssh)
My boss just lost the original SLES SP1 DVD (in fact, he lost the WHOLE box of the server, so i don’t have access to any manual or anything) that came with the SGI rackable h2106-g7 (our server) so i can’t use the DVD to do a boot and an automatic repair. The problem gets worse when i just can’t find a SLES SP1 trial version for download and use it to try an automatic repair (i can find SP2,SP3 and SP4 here )
I don’t know if this is related to the problem but a couple days ago I have added the openSUSE oss Repo to the YAST to get packages like nano,gfortran and nco (netCDF stuff).
I really don’t know what to do. Please guys help me[/QUOTE]
On 04/09/2015 17:44, brunoborlini wrote:
[color=blue]
I was trying to update an SLES SP1, it was never updated since 2010,
(just a zypper update) and something went really bad and i really don’t
know what it is.
Some packages may have broken during the update and I just can’t get
access to root anymore (i keep receiving the message login incorrect)
but i am using the right password and the GUI also does not load anymore
(direct access).
I can get access my personal account but sudo does not work so i can’t
do anything useful with my normal user access.
I tried to go to single-user mode to change root password but the
problem persists, even the new root password does not work (direct
access and ssh)
My boss just lost the original SLES SP1 DVD (in fact, he lost the WHOLE
box of the server, so i don’t have access to any manual or anything)
that came with the SGI rackable h2106-g7 (our server) so i can’t use the
DVD to do a boot and an automatic repair. The problem gets worse when i
just can’t find a SLES SP1 trial version for download and use it to try
an automatic repair (i can find SP2,SP3 and SP4 ‘here’
(https://download.suse.com/index.jsp) )[/color]
By “SLES SP1” do you mean SLES11 SP1 or perhaps you’re referring to the
older SLES10 SP1 release? (“SP2,SP3 and SP4” can apply to both SLES11
and SLES10). Perhaps you could post the output from “cat /etc/*release”.
[color=blue]
I don’t know if this is related to the problem but a couple days ago I
have added the openSUSE oss Repo to the YAST to get packages like
nano,gfortran and nco (netCDF stuff).[/color]
That would depend on which openSUSE repo you added? If it offered a
limited number and/or specific set of packages then you might be okay
but if it was a general repo for a version of openSUSE then you will
likely have installed later versions of core packages from openSUSE
which were not intended for SLES.
[color=blue]
I really don’t know what to do. Please guys help me[/color]
Please post the output from “zypper lr -u” so we can see which repos you
have access to. After that we can advise a possible course of action.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
that’s a complete distribution repository - do you remember how much you installed from there? Probably more than just the compiler, but a (big) bunch of dependencies as well? Then your system would be in a pretty inconsistent state: You’ll have a mix of “SLES11SP1” and “openSUSE 11.4” installed.
Once you got access to the system again, you may be in for some big clean-up to do.
BTW, you might be able to start the system with a boot parameter of “init=/bin/bash”, which would skip any init processing, login etc. That would give you a chance for a first assessment, checking via rpm what packages from the opensuse repos made it into your system. Of course, booting into some recovery shell via installation media and then chroot’ing to the installed system would give you similar, if not better options.
that’s a complete distribution repository - do you remember how much you
installed from there? Probably more than just the compiler, but a (big)
bunch of dependencies as well? Then your system would be in a pretty
inconsistent state: You’ll have a mix of “SLES11SP1” and “openSUSE 11.4”
installed.[/color]
You can use “zypper se -ir ” (where is name or number of
openSUSE 11.4 repo - see output from “zypper lr -u”) to list packages
installed/updated from the openSUSE 11.4 repo.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
i have recovered root acess creating a local user and giving it sudo acess through the init=/bin/bash mode
but now i don’t I have to fix GUI
startx returns
Fatal server error:
could not open default font ‘fixed’
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at “/var/log/Xorg.0.log” for additional information.
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.
and zypper is returning segmentation fault for everything:
Example:
magma:~ # zypper update
Refreshing service ‘nu_novell_com’.
Segmentation fault
zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
Refreshing service ‘nu_novell_com’.
Segmentation fault
zypper se -ir opensuse11.4_repo give me this
[…]
No packages found.
have you run “zypper se -ir opensuse_repo2”, too? If you remember having installed packages from that repos (i.e. the desired compiler), the current result is strange.
Just for good measure, you might run “rpm -V all” to check all installed packages for broken files. (Please note that there will be several files reported as modified, without this indicating an error: Even the config files included in RPMs are checked against their state at installation time, but were modified later on during system setup.)
I still suspect a mix of SLES and OpenSUSE packages on your system, based on your prior description. But without RPM giving you proper feedback, it’ll be hard to find and fix.
Now that i have root access again any zypper variation (including “zypper se -ir…”)just give me a “Segmentation Fault”
Trying a simple zypper update with --verbose for increased verbosity and the answer is:
I think that you’re right, probably i have a mix of suse/openSuse packages in the system.
I believe that I have to fix the zypper first and then start the “cleaning”.
off-topic: Why i can’t edit the older posts of this topic?Just brand new posts can be edited?