diff --git a/content/2.general/4.raid.md b/content/2.general/4.raid.md
new file mode 100644
index 0000000..a2fa8b4
--- /dev/null
+++ b/content/2.general/4.raid.md
@@ -0,0 +1,113 @@
+---
+navigation: true
+title: RAID
+main:
+ fluid: false
+---
+:ellipsis{left=0px width=40rem top=10rem blur=140px}
+# RAID
+
+_Redundant Array of Independent Disks_
+
+In computing, RAID (Redundant Array of Independent Disks) is a system that allows multiple hard drives to be combined to improve performance and/or reliability. It works by restructuring and distributing data blocks across the drives.
+
+Originally, RAID systems were hardware-based, meaning a dedicated controller (a specific chip) managed data distribution and RAID operations. Today, most RAID systems (or their equivalents) are software-based. In fact, many software technologies can create RAID-like systems with features not available in hardware RAID, such as automatic repair (data scrubbing), snapshots, and more.
+
+## Different Types of RAID
+
+There are several types of RAID, each offering its own pros and cons. In general, RAID impacts the following five factors:
+
+- Number of drives
+- Total storage capacity
+- Read speed
+- Write speed
+- Fault tolerance (resistance to hardware failure)
+
+::alert{type="warning"}
+:::list{type="warning"}
+ - RAID is not a backup system but a service continuity system! It only allows hot-swapping of drives without interrupting your server or restoring from backup. You still need an external backup system.
+::
+
+### No RAID
+---
+
+
+
+
+
Just your disks, without RAID. Data is stored disk by disk.
+
If you lose a disk, only its data is lost.
+
Total capacity is the sum of all disks.
+
+
+Use your disks without RAID when you're not afraid of data loss and can tolerate service interruptions between failure and backup restoration.
+
+### RAID 0
+---
+
+
+
+
+
OS sees 1 drive.
+
Data is striped across all disks.
+
If you lose one disk, you lose all data.
+
High read and write performance (multiplied by number of disks).
+
Total capacity is the sum of all disks.
+
Minimum of 2 disks required.
+
+
+Use RAID 0 when you prioritize performance and are not concerned about data loss. Ideal for temporary, high-speed storage (video editing, AI workloads, etc). Not suitable for long-term storage, as one failure means total data loss.
+
+### RAID 1
+---
+
+
+
+
+
OS sees 1 drive.
+
All disks contain identical data.
+
You can lose all but one disk.
+
Improved read speed (scales with number of disks).
+
Total capacity is equal to one disk (e.g., 2×10TB = 10TB).
+
Minimum of 2 disks required.
+
+
+Use RAID 1 for strong redundancy. Each disk contains all data, so performance remains unaffected during a failure. Once failed disks are replaced, data is quickly restored. However, usable storage is limited to one disk’s capacity, making it an expensive solution.
+
+::alert{type="success"}
+:::list{type="success"}
+- __Tip:__ You can combine RAID 1 with other RAID types to create mirrored arrays.
+:::
+::
+
+### RAID 5
+---
+
+
+
+
+- OS sees 1 drive.
+- Data is striped with parity blocks for redundancy.
+- You can lose 1 disk and recover data.
+- Improved read speed (scales with number of disks).
+- Total capacity is the sum of all disks minus one (e.g., 3×10TB = 20TB).
+- Minimum of 3 disks (4 recommended to reduce capacity loss).
+
+Use RAID 5 when you want reliable storage with 3 to 5 disks and minimal space loss. It tolerates one disk failure but may have degraded performance during recovery, which can take days.
+
+### RAID 6
+---
+
+
+
+
+- OS sees 1 drive.
+- Data is striped with dual parity blocks.
+- You can lose 2 disks and still recover data.
+- Improved read speed (scales with number of disks).
+- Total capacity is the sum of all disks minus two (e.g., 4×10TB = 20TB).
+- Minimum of 4 disks (6 recommended to minimize space loss).
+
+Use RAID 6 in similar situations as RAID 5, especially with 6 or more disks. More disks mean higher failure risk. RAID 6 offers peace of mind by tolerating two simultaneous failures.
+
+## Software RAID
+(coming soon)
\ No newline at end of file
diff --git a/public/img/global/no-raid.svg b/public/img/global/no-raid.svg
new file mode 100644
index 0000000..fa75b46
--- /dev/null
+++ b/public/img/global/no-raid.svg
@@ -0,0 +1,4 @@
+
+
+
\ No newline at end of file
diff --git a/public/img/global/raid0.svg b/public/img/global/raid0.svg
new file mode 100644
index 0000000..4621847
--- /dev/null
+++ b/public/img/global/raid0.svg
@@ -0,0 +1,4 @@
+
+
+
\ No newline at end of file
diff --git a/public/img/global/raid1.svg b/public/img/global/raid1.svg
new file mode 100644
index 0000000..0e48c0d
--- /dev/null
+++ b/public/img/global/raid1.svg
@@ -0,0 +1,4 @@
+
+
+
\ No newline at end of file
diff --git a/public/img/global/raid5.svg b/public/img/global/raid5.svg
new file mode 100644
index 0000000..0b6dbd2
--- /dev/null
+++ b/public/img/global/raid5.svg
@@ -0,0 +1,4 @@
+
+
+
\ No newline at end of file
diff --git a/public/img/global/raid6.svg b/public/img/global/raid6.svg
new file mode 100644
index 0000000..494014d
--- /dev/null
+++ b/public/img/global/raid6.svg
@@ -0,0 +1,4 @@
+
+
+
\ No newline at end of file
+ 
+ 
+ 
+
+