Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Red Hat Enterprise Linux Troubleshooting Guide

You're reading from   Red Hat Enterprise Linux Troubleshooting Guide Identify, capture and resolve common issues faced by Red Hat Enterprise Linux administrators using best practices and advanced troubleshooting techniques

Arrow left icon
Product type Paperback
Published in Oct 2015
Publisher
ISBN-13 9781785283550
Length 458 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Benjamin Cane Benjamin Cane
Author Profile Icon Benjamin Cane
Benjamin Cane
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Troubleshooting Best Practices FREE CHAPTER 2. Troubleshooting Commands and Sources of Useful Information 3. Troubleshooting a Web Application 4. Troubleshooting Performance Issues 5. Network Troubleshooting 6. Diagnosing and Correcting Firewall Issues 7. Filesystem Errors and Recovery 8. Hardware Troubleshooting 9. Using System Tools to Troubleshoot Applications 10. Understanding Linux User and Kernel Limits 11. Recovering from Common Failures 12. Root Cause Analysis of an Unexpected Reboot Index

What we have learned so far


From the troubleshooting steps that we have taken so far, we have collected quite a few key pieces of data. Let's walk through what we have learned and what we can infer from these findings:

  • On our system, we have two RAID devices.

    Using the mdadm command and the contents of /proc/mdstat, we were able to determine that this system has two RAID devices—/dev/md126 and /dev/md127.

  • Both RAID devices are a RAID 1 and missing a mirrored device.

    With the mdadm command and output of dmesg, we were able to identify that both RAID devices are set up as a RAID 1 device. On top of that, we were also able to see that both RAID devices were missing a disk; both the missing devices were partitions from the /dev/sdb hard disk.

  • Both /dev/sdb1 and /dev/sdb2 have mismatched event counts.

    With the mdadm command, we were able to inspect the superblock details of the /dev/sdb1 and /dev/sdb2 devices. During this, we were able to see that the event counts for those devices are not matching...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime