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.
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.
My UPS power went "bleep", my system shut down. Boot back up and start getting errors. Well, finally figure out my /var is jacked.
Why? power dip.
How? beats the heck out of me.
How to fix? not sure yet
so we booted to Knoppix
this is what my /var looked like.... ?--------- 29 root root 4096 Jan 31 2008 var
now it looks like this
?rwsrwsrwx 29 root root 4096 Jan 31 2008 var
so, chmod works
when I run file against /var, I get...
root@Knoppix:/mnt/sda2# file -s var
var: ERROR: invalid mode 06777
otherwise, file works against text files and other valid directories
lost+found has nothing e2fsck says all good
so does badblocks
I'm thinking if we can flip the bit back to say it's a directory, it may pull up the rest of it. otherwise, it just may be a painful reinstall.
Problem solved. back at the LUG last night, we ran e2fsck WITH THE -f option. NOW it finds an inode error (8-bit vs 16-bit) with it recognizing the file type descriptor of '?' as invalid. then we get stuff showing up in lost+found. took us a few more hours but we managed to get it up and running without reinstall. using the system now to post.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.