Quote:
|
How can you tell which one is causeing the problem
|
I saw this line in /etc/fstab
Quote:
|
/dev/evms/hda1/boot / reiserfsck acl,user_xattr 1 2
|
1.) /dev/hda1 is your /boot partition - where the kernel and the bootloader is and I know that this is not needed for the system to function properly - it is normally not even mounted
2.) the normal boot procedure was interrupted because there was something wrong with your / (root) partition - see the error message...it is the / (slash) at the end of the message
Because of the interruption, you are placed in a single user system (to be able to correct the error) which is usually called runlevel 1
After you remounted the
/ partition
rw and got no error you should be able to issue something like:
and your system should continue to boot normally
3 is in most linux systems the default-runlevel
You can check this with this command:
this will list the contents of this file
- it contains the description how
init (the very first process started after boot) is supposed to bring up your system
Look for a line like this:
Code:
# Default runlevel.
id:3:initdefault:
the 3 in there is what I used in the above command to really bring up your system
Even if this works - there is still the issue: why does fsck fail everytime?!
Can knoppix see the raid-setup you have
I'm really not familiar with raid - never used it -in fact I don't even know for sure if it is raid or LVM or what exactly the difference is...
- but if knoppix sees it - you can use knoppix to check it
HINT
you might want to change the subject of the thread ( I think editing the subject of the first post does the trick ) to something like:
CHANGED:fsck fails on raid setup OES LINUX 9
to catch the attention of people who really know about this - the current title is not very precise - it was, sort of, but not anymore.
I got it fixed!
