Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I had 2 hard drives fail this morning on a RedHat 7.2 server. (Yes, I know, ancient.) The users are froathing at the mouth about this old thing.
I've replaced one of he drives, managed to run fsck on / and everything else, repaired about a million files, corrected a ton of inodes, etc. I got into the sh prompt and restored an old version of the passwd file. I think I've cleared up most stuff... BUT, when I try to boot it gets all the way to 'Starting opcagt:' and fails hardcore. The error "Assertion failure in journal_forget_Rsmp_726ff55a() at transaction.c:1227: "!jh->b_commited_data"
Is there any way to recover from this? If I can just get the system up and semi-functional I can do a restore from tape.
Do you happen to use OpenView in your environment? I've seen that opcagt thing in conjunction with OV before. If so, you can just remove the startup statements for it, and it should continue to boot.
Another alternative is to build a new system, with an up-to-date distro, and do the file restore to it, solving two problems (having not only an old system, but a dead one too).
Thank you!! I removed the openview from startup and it booted the rest of the way. Now here's hoping the system is functional for a restore to kick off!
Thank you!! I removed the openview from startup and it booted the rest of the way. Now here's hoping the system is functional for a restore to kick off!
You're very welcome...glad it helped. What do you use to back up? If you're using Tivoli, you should be able to just do a bare load of the client, then modify the dsm.opt and .sys files, giving the new system the same name as the old. The client should just fire up, and let you restore. I don't know about other network-based backup solutions, but it should be about the same thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.