|
LL update error
|
|
08-03-2018, 11:02 AM
Additional, when your are in the Live version do a heath check of your hard drive. Your present install may have become corrupted if the hard drive is starting to go. You can check by going to Menu=>Settings=>Disks. Then upper right corner left click to open a pull down menu. Click on SMART Data & Self-Test.
08-03-2018, 01:07 PM
Hi Charvie, DeepThought, kPanic. I have tested my HD. It is OK. My LL System Report tells me that the CPU is 32-bit, 64-bit.
So, I will follow your suggestions to try and install LL 4.0. I will be away for a few days, so it will take some time before I know the result. I want to thank you very much for your support and help. Ciao, Paul. 
08-03-2018, 01:13 PM
Exit status 139 is a memory fragmentation error. 239 is a net backup error caused by 139. Exit status 134 means the attempt to run was aborted because the application was killed for a seg-fault. Colect the files you want save on a USB and new install 4.0. Run a memory test first.
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
08-07-2018, 11:00 AM
Before trying LL 4.0 64-bit, I have tried to install LL 3.8 64-bit. That did not work at all. After trying the "safe mode" I got I/O errors for a number of sectors!
So, I went back to installing LL 3.8 32-bit. Halfway the installation, I got the message "Installation failed: /target/usr/lib/i386-linux-gnu/libpython3.5mso.1.0 This file did not match its source copy on the CD/DVD." I have tried to install various LL versions and even Lubuntu (from various different DVDś) and the message always was the same: Installation failed for the above-mentioned reason. The problem therefore must be found in the HD, I suppose. This is strange, since I had carried out a health test, which said the HD was OK. Ciao, Paul. 
08-07-2018, 11:22 AM
Def sounds like hardware issue. Run memtest. I would run more extensive tests on HDD. Big names like Seagate, Western Digital have there own diagnostic tools.
|
|
« Next Oldest | Next Newest »
|
![[Image: X5qGkCg.png]](http://imgur.com/X5qGkCg.png)
![[Image: 0op1GNe.png]](http://i.imgur.com/0op1GNe.png)
![[Image: LgJ2mtP.png]](http://i.imgur.com/LgJ2mtP.png)
![[Image: vLZcFUE.png]](https://imgur.com/vLZcFUE.png)
![[Image: lrUHro3.jpg]](http://i.imgur.com/lrUHro3.jpg)