Skill This
AI Skill Report Card

Fixing Linux System Malfunctions

B+78·May 17, 2026·Source: Web

Linux System Malfunction Fixing

Quick Start15 / 15
Bash
# Emergency diagnostic commands
sudo journalctl -p 3 -xb  # Check critical errors since boot
dmesg | tail -20          # Recent kernel messages
systemctl --failed        # Failed services
df -h && free -h          # Disk/memory usage
Recommendation▾
Streamline the workflow section - the triage checklist and diagnostic steps overlap significantly and could be consolidated
Workflow13 / 15

System Triage:

  • Check system responsiveness (SSH, local terminal)
  • Identify symptoms (boot failure, service down, performance)
  • Gather initial logs and metrics
  • Determine severity and impact

Diagnostic Steps:

  1. Check system resources

    Bash
    top -bn1 | head -20
iostat 1 3
lsof | wc -l  # File descriptor usage

  2. Examine logs systematically

    Bash
    journalctl -f &  # Follow live logs
tail -f /var/log/syslog /var/log/messages

  3. Service and process analysis

    Bash
    systemctl status service-name
ps aux --sort=-%cpu | head -10
netstat -tulpn  # Network services

  4. Hardware/kernel checks

    Bash
    dmesg -T | grep -i error
smartctl -a /dev/sda  # Disk health
sensors  # Temperature monitoring

Resolution Process:

  • Isolate root cause
  • Apply targeted fix
  • Verify resolution
  • Document for prevention
Recommendation▾
Make examples more concrete by showing actual error outputs and their specific fixes rather than just command sequences
Examples15 / 20

Example 1: Service Won't Start Input: systemctl start nginx fails

Bash
systemctl status nginx -l
journalctl -u nginx --since "10 minutes ago"
nginx -t  # Test configuration
# Fix config error, then restart

Example 2: System Slowdown Input: System extremely slow, users complaining

Bash
iotop -ao  # Find I/O bottlenecks
ps aux --sort=-%mem | head -10
# Kill runaway process: kill -9 PID

Example 3: Boot Failure Input: System won't boot past GRUB

Bash
# From rescue mode:
fsck /dev/sda1
mount /dev/sda1 /mnt
chroot /mnt
grub-install /dev/sda
update-grub
Recommendation▾
Reduce verbosity in the best practices section - some points are obvious to experienced users and could be cut or condensed
Best Practices
  • Log everything: Keep detailed records of symptoms, diagnostics, and fixes
  • Non-destructive first: Always try safe commands before potentially harmful ones
  • Backup before major changes: cp /etc/config /etc/config.backup.$(date +%s)
  • Single change principle: Make one change at a time, test, then proceed
  • Monitor after fixes: Verify stability with watch commands

Priority order:

  1. Data integrity
  2. Service restoration
  3. Performance optimization
  4. Root cause elimination
Common Pitfalls
  • Don't restart blindly - Gather diagnostics first, restarts destroy evidence
  • Avoid mass service restarts - Fix specific problems, not symptoms
  • Don't ignore hardware - Check dmesg and hardware logs early
  • Never rm -rf in panic - Corrupted files can often be recovered
  • Don't edit configs without backup - Always backup before changes
  • Avoid kill -9 on system processes - Use proper shutdown sequences

Red flags requiring caution:

  • Filesystem corruption warnings
  • Hardware error messages
  • Memory allocation failures
  • Kernel panics in logs
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
15/15
Workflow
13/15
Examples
15/20
Completeness
18/20
Format
15/15
Conciseness
12/15
Save to My Skills