Hi LCR,
Thanks for the help. I was being asked for my root password since
apparently my file system had errors. When I gave the password, I was given
a normal shell prompt. I did the fsck. It did not show any errors. then I
mounted the filesystem read write and I could run lilo and do everything
normally.
But the problem is my partition table sems to have changed after i added
the second disk. Previously my root partition and swap were hda7 & hda8. Now
they are hda6 & hda7 respectively. I could see this in /etc/fstab and
/etc/lilo.conf. I am also not able to mount any fat16 filesystems in my
disk. I think this happened because some changes were made in the cmos setup
when I added the second disk.
How can I now update these changes to linux , I mean at what all places
in linux does this change needs to be made like /etc/fstab, lilo etc. and
how can i do that? Thank you.
Prasad
> Quite possibly. Normal boot sequence goes like this (in part):
>
> 1. Root (/) gets mounted ro (readonly) so that a fsck (filesystem
> check and possible repairs) can be done (dangerous on a mounted
> and rw active filesystem).
>
> Then in the system initialization scripts:
> 2. Root gets the fsck
> 3. If successful, root gets remounted rw with a command similar
> to this:
> mount -n -o remount,rw /
> That can also be done by hand, without changing lilo or loadlin.
>
> 4. Else if the fsck fails, you are dropped into system
> maintenance mode, and the root password will be immediately
> demanded (unless the system initialization scripts are broken, as
> Red Hat's was back around version 4.2). If you are in this mode,
> type "runlevel" and you should see that the first number output
> is "1", aka "s", aka single user maintenance mode (the second
> number is the last runlevel, probably "N" (none). If this
> correct, manually fsck root:
>
> fsck -f /
>
> You'll likely get a lot of errors, since apparently the normal
> fsck in the boot scripts failed for some reason.
>
> 5. Then you can remount as above, and run lilo, etc. Mounting a
> filesystem with errors can lead to severe, unrecoverable,
> filesystem damage (eg, re-install, lose data). Usually
> filesystem errors are caused by improper shutdown, by newbie
> pushing the power or reset button, or more likely, power glitch
> (momentary power loss) or outage. We don't include crashes,
> because they are so rare (except I had some buggy hardware on one
> machine that would hose it).
>
> LCR
>
> --
> L. C. Robinson
> reply to no_spam+munged_lcr@onewest.net.invalid
>
> People buy MicroShaft for compatibility, but get incompatibility and
> instability instead. This is award winning "innovation". Find
> out how MS holds your data hostage with "The *Lens*"; see
> "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
>
>
>
> _______________________________________________
>
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com