Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
It looks like you're trying to run fsck on a read/write filesystem. You might try booting into single-user mode, passing the kernel command-line “ro s” (ro for read-only, s for single-user). You should then be able to check the filesystem manually using fsck.
Failing that, you will need to boot from a rescue disk (so that the filesystem's completely unused) and run fsck from there.
Location: a magical place, on some remote place on the planet
Distribution: Mandrake 10.1 winxp pro, free bsd
Posts: 91
Original Poster
Rep:
a linux native file system is only read/write?
i get the same difficalty in single user mode
i got this problem just by shutting down, and booting into M$win2k
also for some reason after 10 or 15 trys i got somewhere i notice that they were in a users opera cache, i did the same exact thing each time too...
the odd thing is the last this happened in found them in the same spot, but did it on the first time. could this problem have something to do with opera it self
now i would like to know, is there a way i can evade this in the future
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.