Topic: How do you fsck system?

[Dennis]

I tryed aasking other ways but appartently its all in how you ask. I have SME 5.1.2 on my server. runs great ..but on boot up hangs at finding module dependencies. Thanks to Ken who gave me the info on how to control c past that point. I am able to get up and running. My server is an AMD 1.3gz 512 ram 20 gig hard drive. and has been running flawlessly for over a year now. My email has been on occasion been un accessable over the internet. So I did a reboot. it was then I had the lockup at the finding module dependencies point. When I control c it gives at 7s. and finishes boot sequence. I need to know how to fsck to find wher my problem is...please

[ldkeen]

Dennis,
I'm far from an expert in this field but I'll offer a bit of advice as you seem as though you're getting ready to pull your hair out with this one. I really don't think that you have a problem with your Hard disk but if you really want to check it:
After starting the machine and when the Mitel splash screens appears hit Ctrl + x then tab twice to show a list of the available kernels (should be something like Mitel-SME and possibly Mitel-SME-SMP) Start the system in single user mode with:
#<kernel_name> single
On completion of booting you will be presented with a command prompt in single user mode. If you dont know what partition needs repairing you will have to list your partitions using fdisk:
<screenshot>
[root@guru root]# fdisk /dev/sda

The number of cylinders for this disk is set to 8942.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p (TO PRINT THE PARTITION TABLE)

Disk /dev/sda: 255 heads, 63 sectors, 8942 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sda1   *         1        13    104391   83  Linux
/dev/sda2            14        46    265072+  82  Linux swap
/dev/sda3            47      8942  71457120   83  Linux

Command (m for help):
<finish screenshot>
You can safely type q now to exit without making any changes. In my case I would need to run fsck on /dev/sda1 and /dev/sda3. YMMV
You can use e2fsck as you only have an ext2 filesystem. You will probably need to use something like the following: (If in doubt man e2fsck)
#e2fsck -pyc /dev/hda1
The -pyc tells e2fsck to automatically repair the filesystem, assume an answer of yes to all questions and check for bad clusters. And possibly:
#e2fsck -pyc /dev/hda6
Having said all that I think you're problem MAY be related to a network adapter that could be failing. The system is trying to load a module for a device that is failing?? Have a look in your /etc/modules.conf. Make sure that you dont have any custom templates in /etc/e-smith/templates-custom/etc/modules.conf that maybe aren't applicable anymore. Try rebuilding modules.conf with:
#/sbin/e-smith/expand-template /etc/modules.conf. I recall someone saying that if you run kudzu from the command prompt it will redetect all your hardware - you could maybe try that. Try removing the PCI devices one at a time and see if that stops the system from hanging. Try also:
#dmesg |more
and see if you can't pinpoint what device is causing the system to hang, also check /var/log/messages. And if all this seems like too much hard work you could try the recommended plan of action which is to UPGRADE to SME 6.0 final which may also fix the problem. HTH
Regards Lloyd

[RavenIV]

first:
fsck checks your filesystem FileSystemChecK.
it will not find any dependencies.
nevertheless it is a good idea to check the filesystem time to time.
for any help type "man fsck" or "man 5 fsck"

second:
it is not recommended to run a 5.1.x-SME.
it has many security-holes, that have been repaired in 5.6 or 6.x.

my hint:
update your machine to 5.6 or 6.x and you're fine.

cheers