[opensuse] complete failure updating ?
Hello, I had a problem updating a server today. I would like to know if it's an install problem or a hardware problem... I have physical access to the server, but 20 km from my home, so not so easy. What I did was go there with a flash device holding openSUSE 13.1, boot it and ask for update. The original distro was 12.1, so I can't say it was obvious. At first glance all seemed to go pretty well. update (or may I say ugrade?) went on then the computer rebooted... and did reboot the flash device. removing the device got "no system". back to update menu, 1 package to update, got it, reboot without problem and then no more reboot problem. This computer was a gateway. no problem connecting to the net, the gateway worked (access to the net from an other computer). then zypper ref, zypper patch. no problem, patching zypper. again zypper patch an go to an hour long download. near the end of the download, zypper stopped "download.opensuse.org unreachable". No way to get it. go to an other xterm, no more network access. reboot the hole system (including the dsl box). Got the net for two minutes then nothing trying to launch yast/network, I got kernel hoops (black hex lines through the screen). retry, same things. memtest do not see problems after two minutes (I know it may be longer) So I gave up I back to home. so I wonder what is the problem. is it a hardware problem? the booting problem and the kernel bugs may be a symptom, or can this be only due to interrupted software download? without network, I can't update more. may be simply a failing ethernet device (could explain why the kernel problem is only with yast/network thanks for your help jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/21/2014 06:51 PM, jdd wrote:
zypper stopped "download.opensuse.org unreachable".
- perhaps "download.opensuse.org" went off-the-air for some hours? ............. regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 21/04/2014 19:27, ellanios82 a écrit :
On 04/21/2014 06:51 PM, jdd wrote:
zypper stopped "download.opensuse.org unreachable".
- perhaps "download.opensuse.org" went off-the-air for some hours?
may be, but I couldn't connect any where on the net :-( jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-21 17:51 (GMT+0200) jdd composed:
near the end of the download, zypper stopped "download.opensuse.org unreachable". No way to get it. go to an other xterm, no more network access.
reboot the hole system (including the dsl box). Got the net for two minutes then nothing ... so I wonder what is the problem. is it a hardware problem? the booting problem and the kernel bugs may be a symptom, or can this be only due to interrupted software download?
without network, I can't update more.
may be simply a failing ethernet device (could explain why the kernel problem is only with yast/network
These are symptoms I've often seen during updates for quite some time. It seems to have become a problem around either the time that "network management" seemed to become an assumed necessity, or the time systemd started taking over from sysvinit. It seems updates have devolved to often think it necessary to restart services the update process depends on during the update process instead of waiting at least until the downloading is finished. e.g., my NFS mounts for several months have been routinely disappearing during zypper dup or zypper up. When it has happened to me it has been common to find either resolv.conf has been fatally altered, or that the default route has disappeared. On occasion I've seen the assignment of an IP to the network device has disappeared, or that the network device name has been changed. So when network unreachable during updating happens I now: 1-examine resolv.conf for validity 2-examine output of route -n for validity 3-examine output of ifconfig -a for sanity and then proceed accordingly before answering zypper's question what it should do. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 21/04/2014 19:56, Felix Miata a écrit :
1-examine resolv.conf for validity
was ok, and the dns IP did not aswer to the ping neither
2-examine output of route -n for validity
did not test this one
3-examine output of ifconfig -a for sanity
seems ok but still, I couldn't use yast to reconfigure the network, due to kernel bugs :-( jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-21 19:59 (GMT+0200) jdd composed:
Le 21/04/2014 19:56, Felix Miata a écrit :
1-examine resolv.conf for validity
was ok, and the dns IP did not aswer to the ping neither
2-examine output of route -n for validity
did not test this one
Networking, including ping, is entirely dead if you need a gateway and don't have a valid one.
3-examine output of ifconfig -a for sanity
seems ok
but still, I couldn't use yast to reconfigure the network, due to kernel bugs :-(
YaST failure should be no impediment to enough network fixup to finish an update process. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 21/04/2014 20:12, Felix Miata a écrit :
Networking, including ping, is entirely dead if you need a gateway and don't have a valid one.
sure, but there I was on the gateway - not to say your remark is not valid
but still, I couldn't use yast to reconfigure the network, due to kernel bugs :-(
YaST failure should be no impediment to enough network fixup to finish an update process.
my guess is that the network hardware is failing, so the kernel problem only when accessing the device - but a broken module could also give such problem, but I need it to work :-( I should also try a live distro, if it works, the software is responsible. thanks jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 21/04/2014 20:12, Felix Miata a écrit :
YaST failure should be no impediment to enough network fixup to finish an update process.
finally, it's almost certainly a random hardware failure. even on live cd, I can connect only by chance - and it's not the netrwork card, removing it for a new one didn't fix the problem. so better trash the hardware :-( jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/21/2014 08:56 PM, Felix Miata wrote:
and then proceed accordingly before answering zypper's question what it should do.
- today, trying a TWeed zypper dup , i get : Retrieving: kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm ..........[done] Digest verification failed for kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm. Expected 53d874c8990c282ce7650de91fb45e53ec05b74f6aeea3d5c2743b9f2b762c15, found e67de9e3435efffb817ec7e40d44260ad7e01644d341a9e2e5eb693d76d9b6fa. Continue? [yes/no] (no): no Failed to provide Package kdebase4-runtime-branding-openSUSE-13.1-2.9. Do you want to retry retrieval? [Tumbleweed|http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/] Can't provide file './x86_64/kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm' from repository 'Tumbleweed' History: - kdebase4-runtime-branding-openSUSE-13.1-2.9.x86_64.rpm has wrong checksum ____________ - is "wrong checksum" cause for alarm? ............. regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
ellanios82 -
Felix Miata -
jdd