YoperThis forum is for the discussion of Yoper Linux.
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It could be a lot of things rootkit, corrupt file .. my guess is that you have some messed up module loaded. Try and cat /proc/modules . Then I would try and back off drivers (one at a time) that get loaded at boot and see if you can run lsmod if you can't back off another and try again.
Hm... Seems like i had a badblocks... Tried to recover with reiserfsck and lost my system. Reinstalled and recovered stuff from backups. Feel totally lame now...
Did you have a recent crash? If not you may not want to trust that disk all that much. If you are having a hardware failure you could be in for more bad blocks! Note that bad blocks is not necessarily because of a bad disk .. I have seen bad power supplies cause problems like this.
No, man. No crashes, everything was nice and silent until it started to display strange things at startup ('wrong level found in node...'). I googled for answers and found something about what to do with reiserfsck. You know the rest... Now i want to understand what it was and what to do to avoid such situations in the future.
It is possible that you are having a hardware failure .. This can be quite difficult to debug, and you may need another box to test on.
Given the info you have provided its hard to tell whats going on. You may continue to run the system but I would not trust that disk. Periodically check dmesg for disk write errors?
I check it every time now... I have another hdd and thinking about reinstalling my system to, but it's kinda difficult now: it contains my 100 gig music collection, so i need to write it to CD's and create a database first... Strangest thing is now everything seems to be OK (i formatted a disk when reinstalled a system) so i even don't know what to think now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
