Author Topic: SOLVED - After trying to fix something which wasn't broken......  (Read 1278 times)

Offline Maurice

  • Hero Member
  • *****
  • Posts: 1129
My machine was runnjng a bit slowly on memory intensive stuff like Google Earth so I opened it up and reset the memory cards and checked a few other connections. When I put it back together I found I couldn't get into my Pclos (updated). I could get into XP and Solusos but not Pclos.

I entered dmesg |tail from Solusos and got the following -

felix maurice # dmesg | tail
[  238.598673] Descriptor sense data with sense descriptors (in hex):
[  238.598676]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[  238.598689]         25 18 b0 00
[  238.598694] sd 3:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
[  238.598701] sd 3:0:0:0: [sda] CDB: Read(10): 28 00 25 18 af 30 00 00 f0 00
[  238.598718] end_request: I/O error, dev sda, sector 622374912
[  238.598729] JBD2: Failed to read block at offset 769
[  238.598737] ata4: EH complete
[  238.598748] JBD2: recovery failed
[  238.598752] EXT4-fs (sda3): error loading journal


Have I fried it? Can someone kindly make sense of this to me please?

Thank you
Maurice
« Last Edit: July 11, 2012, 06:24:05 AM by Maurice »
PcLinuxos 2012.02, Kde, dual booted with XP on custom built Desktop, Intel Core 2 Quad  cpu @ 2.4ghz, DG33FB mb, 4gb ram, Nvidia 8600 (512mb), Samsung (500gb) sata

"War does not determine who is right only who is left." Bertrand Russell

Offline bicol_willem

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2378
Re: After trying to fix something which wasn't broken......
« Reply #1 on: July 11, 2012, 05:38:33 AM »
I would first fire up my PMagic LiveCD and do a file system check. Then try again.

A remaster with Gparted on it could be used as well of course.
« Last Edit: July 11, 2012, 05:40:07 AM by bicol_willem »

Offline menotu

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 15304
  • ┌∩┐(◕_◕)┌∩┐
Re: After trying to fix something which wasn't broken......
« Reply #2 on: July 11, 2012, 05:43:55 AM »
Are both OS's on the same drive? If PCLinuxOS is on it's own drive maybe you've accidentally nudged a cable.

Have you checked the HDD cable(s) and tried reseating the ram modules?

And as a "just-in-case" you may want to boot the LiveCD and backup any important data/settings etc....
PCLinuxOS 32bit KDE 4.10.1; kernel-3.4.11-pclos1.bfs & 64bit 3.2.18bfs; NVidia GeForce 8400GS 1GB 310.19 driver

Sony Vaio SVE1513A4ESI Laptop, Intel Core i5, 2.6GHz, 6GB RAM, 750GB, 15.6" Intel HD Graphics 4000

Offline Maurice

  • Hero Member
  • *****
  • Posts: 1129
Re: After trying to fix something which wasn't broken......
« Reply #3 on: July 11, 2012, 05:54:44 AM »
I would first fire up my PMagic LiveCD and do a file system check. Then try again.

A remaster with Gparted on it could be used as well of course.


Are both OS's on the same drive? If PCLinuxOS is on it's own drive maybe you've accidentally nudged a cable.

Have you checked the HDD cable(s) and tried reseating the ram modules?

And as a "just-in-case" you may want to boot the LiveCD and backup any important data/settings etc....

Thanks for the replies. I don't have PMagic willem - I usually use Gparted and, of course, can't get at it. And no remaster. ::)

Yes menotu all are on the same drive, I reseated the four ram cards and double checked the HDD cables. I had only updated Pclos last week and have all the settings I need well backed up but thanks for the warning.
« Last Edit: July 11, 2012, 05:56:37 AM by Maurice »
PcLinuxos 2012.02, Kde, dual booted with XP on custom built Desktop, Intel Core 2 Quad  cpu @ 2.4ghz, DG33FB mb, 4gb ram, Nvidia 8600 (512mb), Samsung (500gb) sata

"War does not determine who is right only who is left." Bertrand Russell

Offline Just17

  • PCLinuxOS Tester
  • Super Villain
  • *******
  • Posts: 10654
  • MLUs Forever!
Re: After trying to fix something which wasn't broken......
« Reply #4 on: July 11, 2012, 05:59:14 AM »
Use a PCLOS LiveCD/LiveUSB and do a file system check on the PCLOS partitions.

man fsck

for info
MLUs rule the roost!

Linux XPS 3.4.38-pclos1.bfs  64 bit
Intel Core2 Quad CPU Q9450 @ 2.66GHz
4 GB RAM
MCP51 High Def Audio
GeForce GTX 550 Ti
PHILIPS  ‎DVD+-RW DVD8701
‎Logitech ‎BT Mini-Receiver
Afatech DTT

Offline djohnston

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6227
  • I don't do Windows
Re: After trying to fix something which wasn't broken......
« Reply #5 on: July 11, 2012, 06:00:16 AM »
Start with booting from a PCLinuxOS live CD. Run a filesystem check on sda3.

su root
umount -a
fsck -fy /dev/sda3


You will get an error that / is busy after issuing the umount -a command. That is normal.
Bare metal                           VBox
AMD Athlon 7750 Dual-Core    Single core
4GiB RAM                              1GiB RAM
nVidia GeForce FX 5200          64MB video
LXDE 32bit                            KDE 64bit

Registered Linux User #416378

Offline Maurice

  • Hero Member
  • *****
  • Posts: 1129
Re: After trying to fix something which wasn't broken......
« Reply #6 on: July 11, 2012, 06:05:04 AM »
Thanks DJ and Just18. Will do that.
PcLinuxos 2012.02, Kde, dual booted with XP on custom built Desktop, Intel Core 2 Quad  cpu @ 2.4ghz, DG33FB mb, 4gb ram, Nvidia 8600 (512mb), Samsung (500gb) sata

"War does not determine who is right only who is left." Bertrand Russell

Offline Maurice

  • Hero Member
  • *****
  • Posts: 1129
Re: After trying to fix something which wasn't broken......
« Reply #7 on: July 11, 2012, 06:23:24 AM »
Well, well, I never expected to get this fixed before I turned in for the night. ;D

I ought to know about fsck by now - I've used it before but didn't give it a thought.

Many thanks chaps, I really appreciate your quick and helpful replies.

Maurice
PcLinuxos 2012.02, Kde, dual booted with XP on custom built Desktop, Intel Core 2 Quad  cpu @ 2.4ghz, DG33FB mb, 4gb ram, Nvidia 8600 (512mb), Samsung (500gb) sata

"War does not determine who is right only who is left." Bertrand Russell

Offline djohnston

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6227
  • I don't do Windows
Re: SOLVED - After trying to fix something which wasn't broken......
« Reply #8 on: July 11, 2012, 06:32:15 AM »
Glad it was that simple, Maurice.
Bare metal                           VBox
AMD Athlon 7750 Dual-Core    Single core
4GiB RAM                              1GiB RAM
nVidia GeForce FX 5200          64MB video
LXDE 32bit                            KDE 64bit

Registered Linux User #416378

Offline Maurice

  • Hero Member
  • *****
  • Posts: 1129
Re: SOLVED - After trying to fix something which wasn't broken......
« Reply #9 on: July 11, 2012, 06:31:49 PM »
Glad it was that simple, Maurice.


Me too. Wish they were all that simple. ;D Still left with the problem of a sluggish Google Earth but I'll bring that up in another thread.
PcLinuxos 2012.02, Kde, dual booted with XP on custom built Desktop, Intel Core 2 Quad  cpu @ 2.4ghz, DG33FB mb, 4gb ram, Nvidia 8600 (512mb), Samsung (500gb) sata

"War does not determine who is right only who is left." Bertrand Russell

Offline Phil

  • Hero Member
  • *****
  • Posts: 740
Re: SOLVED - After trying to fix something which wasn't broken......
« Reply #10 on: July 12, 2012, 02:36:49 AM »
Hi Maurice,

"sluggish Google Earth "

Found these two complimentary items (see if they work for linux):


How To Fix Slow or Sluggish Google Earth Not Responding Windows 7


Open Internet Explorer, select Tools->Internet Options
Click on the Connections Tab
Click on the Lan Settings button
Uncheck the Automattically detect settings check box
Click the Ok button
Restart Google Earth

This fixed all of the slowness issues I had with Google Earth 6.1.0.5001

Offline Maurice

  • Hero Member
  • *****
  • Posts: 1129
Re: SOLVED - After trying to fix something which wasn't broken......
« Reply #11 on: July 12, 2012, 03:56:04 AM »
Hi Maurice,

"sluggish Google Earth "

Found these two complimentary items (see if they work for linux):

Open Internet Explorer, select Tools->Internet Options
Click on the Connections Tab
Click on the Lan Settings button
Uncheck the Automattically detect settings check box
Click the Ok button
Restart Google Earth

This fixed all of the slowness issues I had with Google Earth 6.1.0.5001

Thanks Phil. I don't have I Explorer. However I solved the problem by going to Tools/Options in GE itself and speeding up some of the settings there, many of which are set at low defaults. There was also the facility there for clearing the memory cache and the disk cache. It then worked as it should, all the sluggishness gone.

It seemed a bit too easy though and, from my searching, I found that it is a very common problem on all platforms, but I hope that the improvement I got is permanent.
PcLinuxos 2012.02, Kde, dual booted with XP on custom built Desktop, Intel Core 2 Quad  cpu @ 2.4ghz, DG33FB mb, 4gb ram, Nvidia 8600 (512mb), Samsung (500gb) sata

"War does not determine who is right only who is left." Bertrand Russell

Offline Maurice

  • Hero Member
  • *****
  • Posts: 1129
Re: SOLVED - After trying to fix something which wasn't broken......
« Reply #12 on: July 13, 2012, 12:59:20 AM »
But   ::) ::)-- on starting GE again it was back to its sluggishness.

So, back to searching and I finally found the answer and it's simple - just disable Desktop Effects. The effect is immediate and the speed makes it usable once more.

After doing this I have opened Earth five times and it works each time.

I hope this helps others who are having the same problem.
PcLinuxos 2012.02, Kde, dual booted with XP on custom built Desktop, Intel Core 2 Quad  cpu @ 2.4ghz, DG33FB mb, 4gb ram, Nvidia 8600 (512mb), Samsung (500gb) sata

"War does not determine who is right only who is left." Bertrand Russell

Offline aguila

  • Hero Member
  • *****
  • Posts: 1210
  • soaring high = no Windows here :-D
Re: SOLVED - After trying to fix something which wasn't broken......
« Reply #13 on: July 13, 2012, 02:28:00 AM »
IIRC, there's a widget to toggle desktop effects. Maybe a nice addition - turn off when starting GE, turn on when finished.

Dunno if they can can be turned off on the command line, in that case you could even turn them off via the command when hitting the GE icon.

Just an idea though.
All that is is good. PCLinuxOS is.

Thinkpad X61 Tablet, Core2Duo 1.66 MHz, 4 GB Ram, Intel onboard Graphics, Plextor PX-256M3 256 GB SSD; Thinkpad R61i, Core2Duo 1.66 MHz, 2 GB Ram, Intel onboard graphics, 120 GB HDD

Online Bald Brick

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6380
  • I'm going South
Re: SOLVED - After trying to fix something which wasn't broken......
« Reply #14 on: July 13, 2012, 02:59:09 AM »
IIRC, there's a widget to toggle desktop effects. Maybe a nice addition - turn off when starting GE, turn on when finished.

Dunno if they can can be turned off on the command line, in that case you could even turn them off via the command when hitting the GE icon.

Just an idea though.


From System Settings in KDE 4.8.3:



« Last Edit: July 13, 2012, 04:37:42 AM by Bald Brick »
Feed the trolls!
They need it!

AMD Athlon 7450 Dual-Core Processor, 7.80 GiB RAM, Nvidia GeForce GT 120/PCIe/SSE2, OpenGL/ES-version: 3.3 0 NVIDIA 295.40, SBx00 Azalia (Intel HDA) soundcard, ‎Logitech B500 webcam, SAA7146 DVB card, HDDs: Seagate 250824AS, Western Digital WD10EAVS-00D