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.
The problem is solved , but would like to know what is the cause the issue .
I use raid 5 , the volumn is unable to mount , when reboot it , the system will be hang it this volumn , tried the fsck command still not work , then I use the centos source disc and repair it in reseue mode .
Just would like to know what will be the reason of this issue , the partition table corruped ? system file lost ? hardware bad sector ? or other reason .
what error the centos source disc have fixed , it have overwrite the paritition table ?
besides , my system is safe now after such repairing ? is it good to re-install it or do the fully hardware diagnostic ?
I just would like to know what is the possible reason of the issue , to avoid it to be happen again .
There should be historical logs under /var/log/ directory. You should review them. Start with messages-<date>, look for the date when problem started to see if it gives you any hints of what happened?
Quote:
another question , after such repairing , the server is stable or not , is it better to re-install the OS again ?
Have you noticed any abnormalities or reviewed any logs that indicate any problems?
There should be historical logs under /var/log/ directory. You should review them. Start with messages-<date>, look for the date when problem started to see if it gives you any hints of what happened?
Have you noticed any abnormalities or reviewed any logs that indicate any problems?
Yes , I have read the logs in /var/logs/ but didn't find any relevant information about the server crashed.
is it a hardware ( bad sector , raid 5 )or software ( eg. partition ) issue ?
smartctl is good way to check hardware is healthy or not ?
Yes , I have read the logs in /var/logs/ but didn't find any relevant information about the server crashed.
is it a hardware ( bad sector , raid 5 )or software ( eg. partition ) issue ?
smartctl is good way to check hardware is healthy or not ?
smartctl will show you disk information, but disk information should be also in /var/log/messages. If hardware RAID, smartctl may be tricky. Lookup the vendor for hardware controler and check documentation?
If this is a physical server (not VM), and it has a BMC, you can install ipmitool to look at hardware logs (CPU; memory; sensor info etc).
For physical server with out BMC, there may be some info in BIOS logs?
For VM, may be review logs on hosts...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.