Peter_APIIT wrote:
>
>
> I try it first.
>
>
I have solved the problem by issue this command fsck -y.
Thanks for your help.
--
View this message in context:
http://www.nabble.com/File-System-Corrupted-Due-to-didn%27t-Umount-cause-by-power-failure-tp16323986p16348397.html
Sent from the o
I try it first, then i come back here with a specific question and error
message.
--
View this message in context:
http://www.nabble.com/File-System-Corrupted-Due-to-didn%27t-Umount-cause-by-power-failure-tp16323986p16346589.html
Sent from the openbsd user - misc mailing list archive at Nabble
Hi,
I didn't get this right..
Have you got to the shell prompt after the crash?
If so, did you tried to run "fsck /dev/rwd0a"? Try it, it may show some
problems, or in the boot after the crash the system will show you what
partition have been compromised.
Just run the fsck /dev/rwd0X for all
Peter_APIIT wrote:
> Hello all expect openbsd user, i have encountered this incident before where
> previously i can solve it easily but not this time.
>
>
> My openbsd is running for 24 X 7 but my mother going off the power and i
> didn't know about that for few times. After that, file is not p
On Thu, Mar 27, 2008 at 03:31:45AM -0700, Peter_APIIT wrote:
> Hello all expect openbsd user, i have encountered this incident before where
> previously i can solve it easily but not this time.
>
>
> My openbsd is running for 24 X 7 but my mother going off the power and i
> didn't know about tha
5 matches
Mail list logo
