Suse 10.1 won't start

[goude]

Hello everyone,

I was wondering if anyone encountered the same problem with me and found a solution.
There was a power cut in my building and my machine was on at that time and working fine.
However after the power cut Suse boots up but it doesn't get to the graphical interface where you can type the username and password.

The error I get on the Ctrl+Alt+F2 screen is the following:

starting powersaved: /usr/sbin/powersaved: error while loading shared libraries: libobject-2.0.so.0: cannot open shared object file: No such file or directory.

startingproc: exit status of parent of usr/sbin/powersaved:127 FAILED


starting service kdm/opt/kde3/bin/kdm: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory FAILED


Can anybody please give me some sugestions?

Thank you!!!

[gogalthorp]

Looks like from here that your Hard drive was scrambled. The best tool I know to fix hard drives is spinrite. This is not a free program though. You might find a utility on your hard drive manufactures site.

GRC*|*SpinRite 5.0 to 6.0**

[goude]

Thank you for your reply gogalthorp,

I had a look at spinrite and I am thinking to buy it but before I do I want to ask you:
Are you sure that is going to fix this problem?
Is the errors I get caused by the sudden power cut?
How do you know that my disk is scrambled?
Windows boots up with no problems, is suse that causes problems.

Sorry for bombing you with all these questions.

Thank you!!

[gogalthorp]

Thank you for your reply gogalthorp,

I had a look at spinrite and I am thinking to buy it but before I do I want to ask you:
Are you sure that is going to fix this problem?
Is the errors I get caused by the sudden power cut?
How do you know that my disk is scrambled?
Windows boots up with no problems, is suse that causes problems.

Sorry for bombing you with all these questions.

Thank you!!

1) no why to be absolutely sure it will fix the problem but if anything can spinrite will.
2) power los can alway mess a hard drive even in Windoz
3) well it sounds like it. The loss of directories is a big clue. Scrambled is not very precise. What is most likely is that you have some bad sectors caused by the power loss, they did not get written correctly.
4) the problem is most likely isolated to the partition that was in use at the time. It has nothing to do with Suse it could happen in Windows also.

In most cases power loss will be recovered from with out a problem but if data is being written then it can cause bad sectors these are not necessarily broken but the stored check sums will not agree with the actually data and the data may be corrupt. If the sector is bad Spinrite will fix it if possible.

An other option is to reinstall. the default install of Suse makes separate root and home partitions. So if you reinstall set the root to be reformatted and mounted as / and set the home partition to not be reformatted and mounted as /home. This will preserve your personal data and settings.

The only way to avoid this in any OS is a backup power supply.



This is why it is good to have a battery backup.

[goude]

Thank you gogalthorp!!!!