fsck failure after not clean reset

[Nathan_S]

Having following issue:

/dev/sda1: '.' directory entry in directory inode 51318 is not Null terminated; run fsck manually.
(i.e., without -a or -p options)
/dev/sda1: Unexpected Inconsistency ; Run fsck manually
fsck died with exit status 4
Checking drive /dev/sda1: 73% (stage 2/5, 1968/11748

Error on Foxconn Motherboard, and also replacement Gigabyte EP43-DS3L Motherboard.

Current System:

Memory: DDR2 2GB RAM 667Mhz
MOBO: Gigabyte EP43-DS3L
VGA card:(had to, no VGA on MOBO) FORSA 8400GS, 256MB
CPU 1: Intel Pentium dual e2180 @ 2.00Ghz
CPU 2: Intel Pentium dual e2180 @ 2.00Ghz
HD : 40 GB 7200 rpm IDE
Swap: 2 GB RAM
Kernel: 2.6.24-16-Generic
Gnome: 2.22.2

how to fix problem ? Help

[Husse]

I have asked a hardware specialist what he thinks of your hardware - if it fits together or so.
What you should do is boot into recovery mode or if you can't boot the live CD and run fsck from the command line
NOTE under no circumstance should the disk be mounted
After a while you will be asked to repair - do that and hopefully no more problems
But as this seems to be a recurring problem
do not overclock, not only the CPU but also memory
Run a memory check
If the errors appeared on the same spot it could be a bad hard disk

[Nathan_S]

I have asked a hardware specialist what he thinks of your hardware - if it fits together or so.
What you should do is boot into recovery mode or if you can't boot the live CD and run fsck from the command line
NOTE under no circumstance should the disk be mounted
After a while you will be asked to repair - do that and hopefully no more problems
But as this seems to be a recurring problem
do not overclock, not only the CPU but also memory
Run a memory check
If the errors appeared on the same spot it could be a bad hard disk

Currently writing from a live CD.
How to do : 1) boot in recovery mode ?
2) run fsck from the live CD ?

Read in ubuntu forums to do: sudo e2fsck -C0 -p -f -v /dev/sda1
but got after running this command following error:

/dev/sda1:
'.' directory entry in directory inode 51318 is not NULL terminated

What does it mean ?

[Nathan_S]

ran command:

sudo fsck /dev/sda1
from live CD - I believe this is manual fsck.

result:
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 107551/501952 files (0.9% non-contiguous), 729843/2000084 blocks

what to do with this information? and what to do next ?

[Husse]

Hopefully it works now
fsck has worked on the file system. It is a powerful tool and I think it managed to repair the file system

directory entry in directory inode 51318 is not NULL terminated

means that the table that contains information on files and folders was damaged
A very techical paper on inodes here
http://people.debian.org/~adamm/doc/smm ... per-3.html
Check your lost + found folder - it may contain some leftover from the repair (an "orphaned" file or directory)

[Nathan_S]

Thanks, Succeeded entering the system, but wireless network, which worked previously, recognizes network but cannot access it - similar to situation I've noticed when trying dreamlinux.
Is it related to the fsck command ?
How can I change/Copy configurations to be like in Live CD, because there it works perfectly ?

[Husse]

Take a look in Lost+found - you need to be root for that
Perhaps something in wireless became a file fragment

[Nathan_S]

What should I be looking for in Lost+Found, and How can I restore It ?

[Nathan_S]

Crashed Again after System "went to Sleep", Had to make unclean restart and system noe can't even open Live CD - Open Solaris Worked, other debian/Ubuntu based systems failed (Ubuntu, gOS, EarOS). is it a kernel problem or compatibility problem with the intel D processors (I think it's 64 type) ?

[Husse]

Don't think it's the CPU
Have to read this again to give a verdict

[Husse]

Had to make unclean restart and system noe can't even open Live CD - Open Solaris Worked

Eh?
You mean that the live CD can't boot, which it obviously could before...
Can you boot the live CD if you disconnect the hard disk?
It could be a faulty disk
Be very careful to avoid static electricity....
If that does not make any difference I'm completely out of suggestions - this is not normal in any way. A logical error should not stop the live CD from booting which indicates hardware error

[Nathan_S]

Thanks Husse, I found out it was hardware problem - Because I did not construct the system last time, the technician did a bad job. I changed memory slots, and bios changes and succeeded in booting it up till Log-in page. current problem is probably with my nvidia card, which is the only available VGA I/O in my system. New problem is the system inability to start desktop screen, to allow me to run ENVY, or install nvidia restricted drivers. Can you show me threads regarding nvidia install guide on start-up ? Maybe change xorg ?
There are also error messages that I don't have time to read because they are flashing to quickly. But one thing I succeded reading is something about the greeter application ??? Is it related to the nvidia driver ?

[Husse]

Yes an error in the greeter can be related to graphics Its the GDM screen where you log in (I can't remember if X starts before or after this...)
Start in Recovery mode and try the new X configuration tool
If that does not help start in Recovery mode and log in to - I think it's called - a maintenance shell
For this you need to have a root password - if you don't boot the live CD
Go to /etc/X11/xorg.conf (the one on your hard drive ) and in Section Device change driver to vesa or add vesa, because there may not be a line with the driver
It should look something like this

Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
EndSection

Comment out any options
Hopefully you can start and see the desktop now - if not there are more problems
(use EnvyNG to reinstall the driver - first remove then install)

[Nathan_S]

Probably do not have xorg.conf file, and can not enter into Live CD Desktop. again black screen with mouse arrow, like in system.

should I try creating a new default xorg file with this command:

sudo dpkg-reconfigure -phigh xserver-xorg

or Should I copy a xorg.conf file into system, If better to copy, from where?

[Husse]

Seems to me that you should go over your hardware - there may be more than one faulty component
First when you have done a thorough check you go on with software.

[Nathan_S]

It might be, I already got a new sata HD (Not installed yet), Memory was not checked yet.
Probably something in the bios settings is wrong, but I can not find anywhere an easy way to configure it to Linux Requirements.
could not find reference on the gigabyte P43 motherboards with Linux.
Could not find anything on bios updates.

Any clues ?

[Husse]

Well with your errors and two motherboards (and two CPUs ?) I would check/swap
Hard disk
Memory
PSU
All ribbon cables
Other cables
Of these perhaps the PSU is the most interesting
Can you tell me the brand/model and check what it is supposed to deliver - amperes at different volts - and it's age
I now strongly suspect PSU or hard disk

[Nathan_S]

Hi Husse - Changed Graphic card to Old ATI Radeon (GV-RX60P128D) - instead of the Nvidia 8400gs - Worked like a charm, can view desktop, also was recognized by system. Current problem:

1) Skipped HD Check so it still might be with errors, Old HD, had it for few years, connected it to an EverCool HDAC unit.

2) Network card still not working - Edimax Wireless Lan PCI Adapter - recognizes network, can't connect into it - What to look for in Lost+Found and how to use it ? Maybe necessary to reconfigure Network card - How ? It previously worked automatically, so do not have knowledge what to do.
Please show me how to make it work after fsck ?

3) Regarding PSU, it came with case - 2-3months OLD - 500W from L&C
+12V - 18A - Peak output 216W

+5V - 50A
+3.3V - 28A
Peak output - Total 230W

[Husse]

Holy crap
The video card.....
Some nvidia cards (like my 6600GT PCIe) can't use the open "nv" driver - you have to use vesa and then install the closed nvidia driver "nvidia"
You don't look for anything special in lost and found. That's the folder where the fsck app puts any "broken files" it finds - like the files in Windows named something.001 002 003 and so on
So you may not find anything there or a lot
Depending on what you find you may come to the conclusion that a reinstall is the thing to do or you might try to repair
I must admit that I have never had anything there so I don't know what to expect. It's really rare to get that kind of error in Linux - and Windows using ntfs as a journaling file system is used, which can recover in most cases

[Nathan_S]

Thanks for your input, it was most helpful.

Regarding VGA card, it's somewhat strange because "Mint" with same card on a via mm3500 motherboard worked perfectly, do you suspect that the chipset on the GA-EP43-DS3L has bad compatibility with Linux ? Is there something that can be done regarding better support of Gigabyte motherboards for Linux ?
I understand you did not find anything new regarding the Network situation, Do you suggest to reinstall, after full backup of data (Files, Bookmarks, List of addon's etc...) ?