<snip>
A little informed but still desperate to fsck (defrag?) the system. I am trying to leave the machine on as much as possible here and so far haven't been hit by a power outage....yet. When it does hit I am going to need to know howto use this fsck thing immediately.
So the questions remain: 1. How to get to the CLI from the rescue option when booting off the CD? 2. How can I get fsck to walk through my fstab file if the / partition isn't mounted? 3. What fsck -option would be the best to check and repair the fs's and also give me verbose output and a progress bar
Hylton -- The fscking desperate Little Helper
1. Boot to the DVD / cd #1
2. select rescue
3. If asked for your language select what is right for you.
4. Make sure that you load any/all modules for the FS that you use.
5. Continue to boot to the rescue system.
6. At the login prompt use root for the login.
7. fsck any filesystems needing repair.
Additional tasks that can be done from here
mount your / filesystem to /mnt i.e.: mount /dev/hda# /mnt (use the number
that is correct for your installation.
cd /mnt
chroot /mnt
mount any additional filesystem you need, i.e.: /boot if on a seperate
partition.
At this point you can add and remove packages using rpm manually even
kernel versions and sources required if you move your harddrive to another
MB using a different processor.
Run mkinitrd to create the boot environment.
-----------------
I require a special module to access the Ultra ATA 100 raid controller
which is -not- provided by SuSE (or any other linux supplier) because it
is not 100% opensource and I need to compile my own module which I can do
in the above rescue mode and then add the module to the /lib/modules tree
so I can boot using it.
Another command I have found to build the modules tree so that mkinitmd
will build the tree is:
depmod.old -a