>>>>> "Bish" == USM Bish <[EMAIL PROTECTED]> writes:
Bish> On Wed, Jun 05, 2002 at 01:27:18PM +0530, Ajay wrote:
>> Today my Debian Potato box crashed!!!
>>
>> Upon rebooting, it gave the expected error messages and dropped
>> me into a shell. I ran fsck on the partition, fixed the errors
>> and then rebooted the system. Again it gave the same messages,
>> viz., the partition was not umounted properly, etc., and then I
>> had to repeat the whole procedure, but to no avail. Obviously
>> the changes, corrections, etc., were not being saved.
>>
>> What should I have done in this situation? I'd used RH earlier
>> and I often used this procedure to solve the problem, but Deb's
>> different?
>>
>> This being a multi-boot system - both Deb and RH present - I
>> finally booted into RH and fsck'ed the Deb partition and
>> finally managed to solve the problem. But whats' the correct
>> procedure?
>>
>> Cordially
>>
>> Ajay Shankar
>>
Bish> ---end quoted text---
Bish> You cannot successfully do a fsck or e2fsck on a mounted
Bish> partition. You have actually done the correct thing. You
Bish> need to go through a rescue disk/ alternate OS (if
Bish> available, as in your case) and do a fsck on the unmounted
Bish> partition ... This is where single floppy distros like
Bish> tomsrtbt and alfa linux come handy.
Not necessarily. If I get dropped in a single-user shell due to fsck
failure I just:
mount -oremount,ro -n /
e2fsck -y /dev/<root disk device>
reboot
It's perfectly safe and valid to fsck a partition mounted read-only.
Regards,
-- Raju
--
Raju Mathur [EMAIL PROTECTED] http://kandalaya.org/
It is the mind that moves
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
