SUSE 10.3 Not Rebooting After Power Cut.

[sparcnz]

HI All,

I have just recently had a power cut and as a result I am now not able to boot my SUSE 10.3 OS up.
It goes through the boot-up screen or lines and then gets to where it is asking for my password. If I do this it goes to the prompt.
I did have this problem once before and I was able to recover from it by entering a command which cleaned or fixed the 1Tb 2nd drive.
I believe that in the power cut the drive may of gotten a little corrupted.

I can't remember what the command line code was, I should of written it down.
But why would this happen? I went to Linux to run a Broadcast software package (Rivendell) as I was told Windows would be worst.
I need to get this back working as quickly as I can.

Please any help would be grateful, I need as much guidance as I can.

Regards

Kevin.

[whych]

Check the error messages you get when you boot, it should give you a clue about which disk has problems.

Login as normal at the terminal and type:
su
Enter the root password
now type
fdisk -l (lowercase L)
Check the output and note the output designagation for the 1 TB drive
(something like /dev/sdx)

Now type fsck /dev/sdx to fix the errors.

To get a full explanation of fsck, type
fsck --h

[onederer]

To probably fix your corrupted hard drive, open a terminal, and type "fsck /dev/(your device number). You may have to use an external 'live' OS to do this. Run the OS, and mount the bad hard drive /dev/your hard drive number into /mnt/bad_drive. Then open a terminal, and run fsck /mnt/bad_drive. It will tell you what it found bad, and will ask you permission to fix it. Just type "yes" to all the permissions that it asks you. When it is finished, reboot, remove the CD, and let it reboot the "formerly" bad Linux.
If it was a correctable problem on your hard drive, then Linux should boot up normally.

If this happens frequently, then it's time to look for another replacement hard drive.
If you can't reload Linux, then the hard drive went to heaven. Time for a new one.

[dE_logics]

Are you using ext*? I always preffer reiserfs, once I used ext3 to realize it's realibility is crap... I think it's even worst than ntfs.

Another problem might be a bad HDD... HDD QA is too bad now a days, and Seagate and WD are worst of the lot; so I would suggest a SMART analisys. Notice WD and Seagate turn off SMART by default to ensure they wont get replacements if (again) their HDD adds problems. So turn it on and do a badblocks on it. Ensure there are no pending sectors to be remapped in the SMART data.

Hitachi is good on the other hand.

[Rubberman]

Generally, Linux file systems are pretty resilient to power failures, though it may take some time for fsck to do its work, depending upon how big and how many drivers were effected, as well as which file system is installed on the drives. Journaling file systems such as ext3, ext4, reiser, etc. will generally recover much more rapidly than non-journaling systems like ext2. In any case, invest in a UPS so you can shut the system down gracefully if there is a power failure of more than a few minutes. That has saved my bacon on numerous occasions.

[martinfromdublin]

Insert your 10.3 installtion CD/DVD & boot from it, select 'Installation' & you should find an option to attempt a repair of the installed system. Let that do it's thing & see if you can boot your system when the repair finishes.