Raid Array Gagal, Korupsi Kolam Panyimpenan NAS, sareng Rebuild Kasalametan¶

Nalika alat Network Attached Storage (NAS) di bumi atanapi usaha leutik (sapertos Synology DiskStation, QNAP Turbo NAS, TrueNAS, atanapi server Unraid) mimiti berbunyi bip sareng LED amber sareng ngalaporkeun "Kolam Panyimpenan Didegradasi" atanapi "Volume Crashed," klik-klik salajengna nu gaduhna biasana nangtukeun naha poto kulawarga irreplaceable atanapi permanén tiasa dirékam dina 20 atanapi henteu. ancur. Mangtaun-taun, pangguna parantos diajar yén nalika drive dina RAID 5 atanapi RAID 1 array janten beureum, anjeun ngan saukur narik drive anu maot, geser drive kosong anu énggal, teras klik "Perbaikan / Bangun deui."

Dina pools gudang-kapasitas tinggi modern diwangun ku 8 TB nepi ka 24 TB drive dibeuli ti bets manufaktur sarua, ** buta dimimitian hiji RAID rebuild di-tempat nyaeta # 1 ngabalukarkeun total, unrecoverable multi-drive Asép Sunandar Sunarya maot **. Ngawangun deui 4-drive 16 TB RAID 5 Asép Sunandar Sunarya unggal sésana drive sepuh maca 100 persén séktor na non-stop pikeun 24 ka 72 jam dina beban termal jeung mékanis maksimum. Nalika salah sahiji drive duduluran anu salamet pencét kasalahan maca anu teu tiasa dilereskeun (URE) atanapi ngalaman degradasi sirah satengahna ngawangun deui, RAID controller najong anu kadua drive kaluar tina kolam renang sareng ngadat sakabéh Asép Sunandar Sunarya. Salamet tina RAID, ZFS, atanapi Btrfs darurat peryogi ngareureuhkeun sadayana nyerat langsung, ngaudit S.M.A.R.T. telemétri dina sadaya drive anu masih aya, nyadangkeun polder kritis *saméméh * ngarampa topologi array, sareng ngagambar disk anggota anu didegradasi nganggo GNU ddrescue sateuacan nyobian ngawangun deui parity atanapi majelis metadata ngan ukur dibaca.

Laksanakeun ieu ayeuna¶

1. ** PERNAH tarik kaluar sababaraha drive pikeun "reseat" aranjeunna bari NAS atawa server diaktipkeun, sarta PERNAH swap drive sabudeureun tanpa labél angka slot pasti maranéhanana. ** Sateuacan noel baki drive tunggal, cokot sharpie atawa labél maker jeung cirian luhureun fisik unggal drive kalawan jumlah bay na pasti (Bay 1 / sda, Bay 2 / sdb, Bay 3 / sdc). Sanajan Linux modern mdadm, LVM, sarta ZFS arrays nyimpen UUID superblocks on unggal disk, hardware razia Controllers (Dell PERC, HP Smart Array, Broadcom / LSI MegaRAID) mindeng meungkeut metadata konfigurasi kana fisik SAS / angka slot backplane SATA.
2. Ulah langsung klik "Perbaikan" atawa "Rebuild" dina RAID 5 / SHR-1 didegradasi Asép Sunandar Sunarya lamun teu boga cadangan éksternal up-to-date. Sedengkeun single-parity Asép Sunandar Sunarya (RAID 5, Synology SHR-1, atawa ZFS RAIDZ1) aya dina **Degraded Mode ** (1 drive maot, sésana drive ayeuna 0 persén file masih bisa dibaca online), ** 1 tina drive anjeun ayeuna masih bisa dibaca ayeuna ** ** 0. Colokkeun hard drive USB 3.0 éksternal langsung kana NAS sareng salin polder anu paling kritis sareng teu tiasa diganti tina kolam renang anu didegradasi * sateuacanna * anjeun matuh drive anu salamet kana uji setrés 48 jam anu brutal tina ngawangun deui parity.
3. ** PERNAH klik "Initialize Disk," "Jieun Kolam Anyar," "Hapus Konfigurasi," atanapi jalankeun fsck -y / btrfs check --repair dina Asép Sunandar Sunarya nabrak.** Lamun dua drive leupaskeun kaluar tina razia 5 Asép Sunandar Sunarya sakaligus (mindeng alatan hiji dip suplai kakuatan sakeudeung atawa SATA timeout tinimbang maot fisik leres), bakal NAS GUI nyirian Kolam Panyimpenan salaku "Cracked" sarta nawarkeun initialize atawa nyieun deui polumeu. Initializing nyerat superblocks seger jeung nol sakuliah stripes parity, ngancurkeun data recoverable. Nya kitu, lumpat btrfs check --repair dina volume Btrfs anu rusak kasohor di komunitas kernel Linux pikeun ngancurkeun tangkal extent saluareun recovery.
4. ** Eureun sadaya wadah Docker, Mesin Virtual, server média Plex, ngarékam kaméra panjagaan, sareng Scrubs RAID anu dijadwalkeun langsung. ** Unggal operasi nulis kana susunan anu didegradasi ningkatkeun résiko tina liang tulis parity atanapi ngadorong drive kadua marginal di tepi. Asup kana antarmuka wéb NAS atanapi terminal SSH sareng lirénkeun sadaya jasa latar tukang sareng tugas I/O tinggi.
5. Lamun aya drive dina NAS nu nyieun sora ngaklik, knocking, grinding, atawa screeching ritmis, mareuman NAS bersih ayeuna. A ngaklik atawa grinding drive ngalaman kacilakaan fisik maca / nulis sirah (tingali Gagalna hard drive sareng pamulihan data). Ninggalkeun éta berputar di jero kandang NAS bakal nyitak piring magnét janten lebu dina sababaraha menit.
6. ** Pariksa naha "gagal NAS" sabenerna ngan hiji motherboard NAS maot atanapi bata kakuatan éksternal.** Lamun Synology Anjeun, QNAP, atawa Asustor NAS ujug-ujug moal hurung dina sagala, atawa blinks kakuatan biru na LED endlessly (sapertos Intel Atom C2000 clock-sinyal bug kawentar), ** hard drive anjeun sarta data ampir pasti 100 persen rupa **. Anjeun tiasa migrasi drive-drive éta kana NAS anu ngagentos atanapi pasang aranjeunna ngan ukur dibaca dina PC desktop Ubuntu Linux nganggo port SATA standar.

flowchart TD
    A["NAS bip / RAID laporan Asép Sunandar Sunarya Degradasi atawa nabrak status"] --> B{"Naha aya drive anu nyababkeun ngaklik mékanis, ngagiling, atanapi sora kerok?"}
    B -->|"Sumuhun: kacilakaan sirah fisik"| C["Turunkeun NAS langsung, labél unggal drive nganggo Nomer Bay na, sareng cabut drive ngaklik"]
    B -->|"No: Operasi jempé"| D{"Naon status Kolam Panyimpenan?"}
    D -->|"DEGRADED (1 drive gagal, volume masih bisa dibaca)"| E["STOP sadayana Docker / VM / Surveillance nyerat sareng JANGAN klik Rebuild acan"]
    E --> F["Pariksa S.M.A.R.T. Atribut (ID 5, 187, 197, 198) dina sadaya drive SURVIVING"]
    F --> G["Colokkeun USB drive éksternal sareng salin file kritis tina kolam renang anu didegradasi"]
    G --> H{"Naha aya drive anu salamet nunjukkeun séktor anu goréng (ID 5 / 197> 0)?"}
    H -->|"Sumuhun: drive kadua gagal"| I["Turunkeun kakuatan sareng clone unggal drive nganggo GNU ddrescue sateuacan nyobian ngawangun deui"]
    H -->|"No: Salamet drive 100% cageur"| J["Selapkeun ngagantian CMR drive (pernah SMR) tur ngajalankeun parity Rebuild"]
    D -->|"CRASHED / OFFLINE (Sababaraha drive kaluar)"| K["Ulah Initialize atawa ngajalankeun fsck/btrfs --repair; pareum tur labél sagala drive bay"]
    C --> L["Klon sadaya drive anggota anu didegradasi kana drive séhat nganggo GNU ddrescue + mapfiles"]
    K --> L
    L --> M["Reassemble drive diklon dina mode Baca-Ngan via Linux Ubuntu mdadm / LVM, zpool import -o readonly = on, atawa UFS Explorer RAID"]

Ngartos naha gagal ngawangun deui RAID: Perangkap "Sibling Drive Batch" sareng "SMR Drive".¶

Pikeun nyandak kaputusan anu aman nalika kaayaan darurat NAS, anjeun kedah ngartos dua perangkap fisik anu maéhan arrays RAID salami pamulihan:

Perangkap 1: Kagagalan Angkatan Berkorelasi sareng Kasalahan Bacaan anu Henteu Dilereskeun (URE)¶

Seuseueurna pamilik NAS mésér sadayana opat atanapi genep hard drive dina dinten anu sami ti pangecér anu sami. Drive-drive éta asalna tina jalur perakitan pabrik anu sami, ngabagi révisi firmware anu sami, spin dina lingkungan geter chassis anu sami, sareng ngumpulkeun jumlah jam kakuatan-on anu sami. * Nalika Drive 1 maot saatos 38,000 jam operasi, Drive 2, 3, sareng 4 ogé aya dina 38,000 jam dianggo. * Upami anjeun ngagentos drive énggal kana Bay 1 teras klik Rebuild dina RAID 5 Asép Sunandar Sunarya, NAS controller kedah maca ** unggal séktor tunggal ** dina Drive 2, 3, sareng 4 ka XOR-itung blok parity anu leungit pikeun Bay 1. * Lamun Drive 3 geus quietly harboring 14 unreadable bad sector (Current Pending Sectors, S.M.A.R.T. ID 197) dina hiji folder heubeul nu teu dibuka dina dua taun, prosés ngawangun deui bakal Slam sirah-mimiti kana eta sector bad dina Jam 19. Dina loba hardware kartu RAID jeung STL-detik Pamulihan NASrors tunggal (STL Errorsll) tunggal Reader jeung kernels NASror multi-kernel. ngabalukarkeun controller ** nyirian drive 3 salaku "Gagal / Faulted,"** leupaskeun drive kadua kaluar tina razia tunggal-parity Asép Sunandar Sunarya 5 sarta ngadat sakabéh volume.

Perangkap 2: Entong Selapkeun SMR (Rekaman Magnét Shingled) Drive kana RAID atanapi ZFS Array¶

Lamun meuli hard drive ngagantian darurat di toko éléktronik lokal pikeun ngawangun deui NAS Anjeun, ** pariksa yen drive ngagantian ngagunakeun CMR (Rekaman Magnét Konvensional), PERNAH SMR (Rekaman Magnetik Shingled) **. * Hard drive desktop anggaran (sapertos standar Western Digital Red non-Plus EFAX model ti 2 TB ka 6 TB, Seagate Barracuda Compute desktop drive, sarta loba mirah USB drive éksternal anu pamaké "shuck" kaluar tina kasus plastik) ngagunakeun ** Drive-Diurus SMR **, dimana lagu magnét tumpang tindih kawas shingles hateup. * Salila multi-terabyte RAID atanapi ZFS resilver nulis, cache média internal SMR drive pinuh pinuh dina 30 menit. Sakali cache pinuh, SMR drive lapak pikeun ** 10 nepi ka 30+ detik ** bari internal maca jeung nulis ulang sakabéh band shingled, atawa balik hiji ATA. IDNF (Sector ID Not Found) séép waktos. * Linux mdadm, Synology DSM, sareng khususna *ZFS (zed) ** nafsirkeun eta lapak SMR 20 detik salaku hard drive maot, ** najong drive ngagantian brand-anyar langsung kaluar tina Asép Sunandar Sunarya ** di tengah ngawann deui. Sok mésér **CMR S/Enterprise drive (sartos WD Red Plu / WD Red Pro, Seagate IronWolf / IronWolf Pro / Exos, atanapi Toshiba N300 / MG Enterprise).

Matriks diagnostik: Tingkat RAID, kasabaran kasalahan, sareng aturan salamet¶

Triage step-by-step pikeun "Degraded" NAS Pool (1 drive gagal, data masih tiasa diaksés)¶

Upami NAS anjeun berbunyi bip sabab 1 drive dina RAID 1, RAID 5, SHR-1, RAID 6, atanapi kolam renang RAIDZ parantos gagal, tuturkeun urutan anu tepat ieu sateuacan ngagentos disk:

Lengkah 1: Audit S.M.A.R.T. atribut dina sadaya drive SURVIVING munggaran¶

Buka ** Manajer Panyimpenan -> HDD / SSD -> Inpormasi Kaséhatan -> S.M.A.R.T. Atribut ** (dina Synology / QNAP) atanapi ngajalankeun smartctl -a /dev/sdX via SSH on unggal ** cageur / online ** drive masih ditinggalkeun di kolam renang nu. Tingali RAW_VALUE kolom pikeun opat atribut kritis ieu: * ID 5 (Reallocated_Sector_Ct): Kudu ideally 0. Upami drive anu salamet ngagaduhan puluhan atanapi ratusan séktor anu dialokasikeun deui, permukaan platter atanapi sirahna aktip ngahinakeun. * ID 187 (Reported_Uncorrect): Kudu kitu 0. * ID 197 (Current_Pending_Sector): KRITIS. Sakur angka nu leuwih gede ti 0 hartina salamet drive * ayeuna boga séktor unreadable ngantosan ngabalukarkeun kacilakaan a * momen a RAID ngawangun deui nyobian maca aranjeunna. * ID 198 (Offline_Uncorrectable): Kudu kitu 0.

Aturan Kaputusan: * Upami sadaya drive anu salamet nunjukkeun 0 dina ID 5, 187, 197, jeung 198, anjeun tiasa aman nyadangkeun polder kritis anjeun ka USB drive éksternal lajeng lumangsungna kalawan GUI NAS normal ** Ngalereskeun / ngawangun deui ** ngagunakeun drive ngagantian CMR cageur. * Upami aya anu salamet drive dina hiji-parity RAID 5 / SHR-1 / RAIDZ1 pool nembongkeun Current_Pending_Sector > 0 atanapi escalating Reallocated_Sector_Ct, ULAH NGAJALANKEUN BANGUNAN. Nyalin sadaya data tina NAS anu didegradasi ka drive USB éksternal langsung bari polumeu masih dipasang; upami polumeu parantos berjuang, pareumkeun NAS sareng clone drive anggota anu gagal dina PC Linux nganggo GNU ddrescue kahiji.

Nyalametkeun léngkah-léngkah nalika RAID / NAS Jilid "Ngadat" (Sababaraha drive turun)¶

Kumaha upami anjeun hudang sareng RAID 5 4-bay anjeun nyarios ** "Panyimpen kolam renang 1: Kacilakaan" ** sabab ** Drive 2 ** gagal dina Salasa wengi sareng ** Drive 4 ** turun dina Rebo isuk?

** Naha sabagéan ageung "gagal 2-drive" saleresna tiasa pulih:** Kacuali bumi anjeun disambar kilat atanapi NAS diturunkeun kana tangga, dua hard drive mékanis ampir henteu kantos ngalaman kacilakaan sirah bencana dina detik anu sami. Sabalikna, naon anu saleresna kajantenan sacara berurutan: 1. Drive 2 ngembangkeun sababaraha séktor anu goréng sareng ditajong kaluar tina dinten-dinten atanapi jam-jaman sateuacana (ninggalkeun array dina modeu Degradasi dina Drive 1, 3, sareng 4). 2. Teras, Drive 4 mendakan *hiji séktor anu teu tiasa dibaca * (atanapi waktos SATA sakedap) nalika NAS ngajalankeun scrub latar. Kusabab Asép Sunandar Sunarya geus euweuh redundancy pikeun ngalereskeun nu bad sector tunggal on Drive 4, supir RAID ditajong Drive 4 kaluar teuing jeung ditandaan sakabéh kolam renang ** nabrak **.

Dina skenario ieu, **Drive 4 boga freshest, up-to-the-menit razia acara counter (Events cacah) sarta 99,9999% cageur **, bari Girang 2 rada kaluar tina tanggal ("bulu").

Kumaha cageur Synology, QNAP, atanapi Linux anu nabrak mdadm Array aman dina PC Linux¶

Lengkah 1: Turunkeun NAS, labél unggal drive bay, sareng sambungkeun drive ka PC desktop anu ngajalankeun Ubuntu Linux Live USB¶

1. Pareuman NAS. Label unggal drive (Bay 1, Bay 2, Bay 3, Bay 4).
2. Sambungkeun drive kana palabuhan SATA motherboard (atanapi kartu HBA sapertos LSI 9211-8i / 9300-8i dina Modeu IT; ulah aya hub USB murah anu dipegatkeun dina beban) dina PC desktop anu di-boot kana Ubuntu Linux Live USB.
3. Buka terminal sareng mariksa perenah partisi sareng mdadm superblok sacara ketat dina modeu diagnostik baca wungkul:

# List all connected drives and partitions without mounting anything
lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE

# Inspect the Linux Software RAID (mdadm) superblock metadata on the data partitions
# Note: On Synology DSM, Partition 1 is Root OS, Partition 2 is Swap, and Partition 3 (or 5) is your User Data array (e.g., /dev/sda3, /dev/sdb3, /dev/sdc3, /dev/sdd3)
sudo mdadm --examine /dev/sd[a-d]3

Lengkah 2: Baca Events counter jeung Array State kaluaran ti mdadm --examine¶

Tingali raket kaluaran tina sudo mdadm --examine /dev/sd[a-d]3 pikeun tiap drive: * Anjeun bakal ningali garis sapertos: * /dev/sda3: Events : 48210, Array State : A.AA (A = aktip, . = leungit) * /dev/sdb3 (Drive 2, kaluar heula): Events : 47950, Array State : AAAA * /dev/sdc3: Events : 48210, Array State : A.AA * /dev/sdd3 (Drive 4, kaluar panungtungan): Events : 48209, Array State : A.AA * Perhatikeun naon Events counter ngabejaan Anjeun: Drives 1, 3, jeung 4 (sda3, sdc3, sdd3) aya dina 1 kajadian masing-masing (48210 vs 48209), sedengkeun Drive 2 (sdb3) murag kaluar loba saméméhna dina acara 47950. * ** Aturan kritis: ** Dina 4-drive RAID 5 Asép Sunandar Sunarya, anjeun ngan perlu ** 3 drive ** pikeun ngarekonstruksikeun 100 persén data. Anjeun WAJIB ngumpul susunan ngagunakeun 3 drive freshest (sda3, sdc3, jeung sdd3) jeung ninggalkeun drive basi (sdb3). Upami anjeun ngahaja maksa-ngumpul nganggo drive basi anu lami (sdb3), metadata sistem file ti dua dinten ka pengker bakal teu cocog sareng jalur data ayeuna dina drive anu sanés sareng ngaruksak polder anjeun.

Lengkah 3: Kloning drive naon waé kalayan séktor goréng nganggo GNU ddrescue kahiji¶

Saméméh assembling, clone drive nu anyar turun (/dev/sdd) (sarta ideally sakabeh anggota drive) ka drive ngagantian cageur ngagunakeun ddrescue (tingali Gagalna hard drive sareng pamulihan data keur pinuh ddrescue sintaksis):

# Clone the dropped drive (/dev/sdd) to a healthy new spare drive (/dev/sde) with a mapfile
sudo ddrescue -f -n /dev/sdd /dev/sde /root/drive4_clone.map
sudo ddrescue -d -f -r3 /dev/sdd /dev/sde /root/drive4_clone.map

Ayeuna cabut panyambungna anu gagal /dev/sdd sareng nempatkeun éta aman dina rak supados anjeun damel sareng klon anu séhat (/dev/sde).

Lengkah 4: Pasang deui RAID array, grup volume LVM, sareng sistem file dina mode BACA-ONLY anu ketat¶

Dina Synology (SHR / RAID) sareng sistem QNAP, tumpukan panyimpen ngagaduhan dugi ka tilu lapisan: mdadm (RAID) -> LVM2 (Manajer Volume Logis) -> ext4 atawa Btrfs (Sistem File). Ieu mangrupikeun sekuen paréntah anu pasti pikeun dipasang sacara aman dina modeu baca-hijina dina Ubuntu:

# Install mdadm, lvm2, and btrfs-progs inside the Ubuntu Live environment
sudo apt update && sudo apt install -y mdadm lvm2 btrfs-progs

# Stop any partial auto-assembled md arrays first
sudo mdadm --stop --scan

# Assemble the 3 freshest RAID 5 partitions in READ-ONLY mode (using --force ONLY if the 3rd drive's event count is off by 1-2 events, on the cloned drive)
sudo mdadm --assemble --readonly --run /dev/md127 /dev/sda3 /dev/sdc3 /dev/sde3

# Check that /dev/md127 is now active (even in degraded [UU_U] read-only state)
cat /proc/mdstat

# Activate the LVM Volume Group in read-only mode
sudo vgchange -ay --readonly

# List the discovered Logical Volumes (look for /dev/vg1000/lv or /dev/vg1/volume_1)
sudo lvs

# Create a mount point and mount the Logical Volume strictly READ-ONLY (-o ro,noload for ext4 or -o ro,norecovery for Btrfs)
sudo mkdir -p /mnt/nas_rescue

# For ext4 volumes:
sudo mount -o ro,noload /dev/vg1000/lv /mnt/nas_rescue

# OR for Btrfs volumes (such as Synology Btrfs pools):
sudo mount -o ro,norecovery /dev/vg1000/lv /mnt/nas_rescue

sakali /mnt/nas_rescue mounts, sadaya polder dibagikeun NAS anjeun (photo, homes, video, documents) bakal muncul di jero /mnt/nas_rescue/ ku kituna anjeun tiasa nyalin aranjeunna langsung kana drive cadangan USB éksternal.

• ** Kumaha upami Synology NAS anjeun ngagaduhan "Synology Hybrid RAID (SHR)" kalayan ukuran drive campuran?** Synology SHR ngan saukur ngabagi drive anu langkung ageung kana sababaraha partisi (sda5, sda6) sarta nyiptakeun misah mdadm Asép Sunandar Sunarya dina unggal undakan partisi, teras gabungkeun éta md arrays babarengan di jero hiji LVM Volume Group (vg1000). Lumpat sudo mdadm --assemble --scan --readonly jeung sudo vgchange -ay otomatis ngahijikeun volume SHR multi-tier dina Ubuntu.
• ** Alternatif GUI Komérsial (Windows / macOS / Linux): ** Upami anjeun teu nyaman sareng paréntah terminal Linux atanapi gaduh kompleks QNAP kolam renang LVM anu disayogikeun ipis, ** UFS Explorer RAID Recovery ** atanapi ** ReclaiMe Free RAID Recovery ** tiasa mariksa sadaya drive NAS anu disambungkeun dina Windows atanapi Linux PC dina 100% modeu software anu dibaca wungkul, sareng ngadeteksi ukuranana puteran LVM sacara otomatis, sacara otomatis mareuman modeu puteran sareng LVM anjeun, sacara otomatis mareuman modeu puteran, LVM. polder kaluar tanpa ngarobah hiji sektor tunggal dina drive NAS.

ZFS (zpool) jeung paréntah nyalametkeun darurat Btrfs¶

Platform NAS modern (TrueNAS SCALE/CORE, Proxmox, Ubuntu Server, Unraid, and Synology Btrfs volumes) beuki ngagunakeun sistem file copy-on-write (CoW) tinimbang warisan. ext4. Lamun hiji ** ZFS zpool** atawa ** Btrfs kolam renang ** nampik Gunung atawa ngabalukarkeun panik kernel on boot sanggeus hiji outage kakuatan atawa drive gagalna, ** ningkatna normal bakal gagal sabab OS nyoba replay ruksakna nulis transaksi **. Anjeun kedah nganggo parameter rollback transaksi anu dibaca wungkul.

1. ZFS (zpool) Pamulihan Darurat (TrueNAS / Proxmox / Linux ZFS)¶

Mun hiji kolam renang ZFS nyatakeun FAULTED, UNAVAIL, atawa ngadat server (kernel panik) sakedapan anjeun nyoba ngimpor eta sanggeus leungitna kakuatan najis:

# 1. Inspect all visible ZFS pools on the connected disks without importing them
sudo zpool import

# 2. ALWAYS attempt a Read-Only Import first (prevents ZFS from writing to disks or replaying the ZIL/SLOG)
sudo zpool import -f -o readonly=on -R /mnt/zfs_rescue <pool_name>

# 3. What if a normal import causes a kernel panic or says 'damaged pool metadata'?
# Use -F (Rollback/Recovery Mode) with -n (Dry Run ONLY) to see if ZFS can rewind the last few seconds of corrupted Transaction Groups (TXGs):
sudo zpool import -F -n <pool_name>

# 4. Combine Read-Only + Safe Transaction Group Rewind (-F -o readonly=on) so no disk sectors are altered while you copy your data off:
sudo zpool import -f -F -o readonly=on -R /mnt/zfs_rescue <pool_name>

# 5. For heavily damaged pools where Space Map allocation tables are corrupt, disable space map loading prior to read-only import:
echo 1 | sudo tee /sys/module/zfs/parameters/zfs_recover
sudo zpool import -f -F -o readonly=on -R /mnt/zfs_rescue <pool_name>

Sakali dipasang di handap /mnt/zfs_rescue, nyalin set data anjeun kaluar ngagunakeun rsync atawa zfs send sateuacan kantos nyobian ngimpor kolam renang baca-tulis.

2. Pamulihan Darurat Btrfs (Synology Btrfs / Unraid Cache Pool / Linux Btrfs)¶

Sabalikna, cobian pasang atanapi nimba volume Btrfs dina urutan progresif anu ketat, tina pangsaeutikna invasif dugi ka scan anu paling jero:

# Stage 1: Mount Read-Only without replaying the corrupted Journal Log Tree (fixes 80% of power-loss Btrfs mount failures)
sudo mount -t btrfs -o ro,norecovery /dev/sdX1 /mnt/btrfs_rescue
# (Note: on newer Linux kernels 5.11+, use: -o ro,rescue=nologreplay)

# Stage 2: Mount Read-Only using the backup Root Tree + ignoring bad checksums (for multi-drive or bit-rot corruption)
sudo mount -t btrfs -o ro,rescue=all /dev/sdX1 /mnt/btrfs_rescue
# (On older kernels: sudo mount -t btrfs -o ro,usebackuproot,nologreplay,degraded /dev/sdX1 /mnt/btrfs_rescue)

# Stage 3: If the volume still refuses to mount in the kernel, extract files directly in userspace without mounting using 'btrfs restore'
# First, list available backup tree roots:
sudo btrfs-find-root /dev/sdX1

# Then run 'btrfs restore' (strictly read-only userspace extractor) to dump all files to an external healthy drive:
sudo btrfs restore -v -i -m -S /dev/sdX1 /mnt/external_usb_backup/

Hardware RAID Controller Darurat: "Konfigurasi Asing" sareng Kartu RAID Paéh¶

Server perusahaan (Dell PowerEdge kalayan kartu PERC, HPE ProLiant sareng Smart Array, Lenovo ThinkSystem, atanapi stasiun kerja sareng pangendali Broadcom / LSI MegaRAID) nganggo kartu RAID hardware sareng NVRAM onboard sareng cache batré / supercapacitor (BBU / CacheVault).

1. Impor Konfigurasi Asing vs Konfigurasi Hapus (KRITIS)¶

Nalika drive momentarily megatkeun sambungan atawa anjeun mindahkeun drive kana chassis server ngagantian, Dell PERC atanapi LSI MegaRAID mios layar boot ngareureuhkeun sarta dibewarakeun: ** "Konfigurasi Asing (s) kapanggih dina adaptor."** * ** Sok pilih Import Foreign Configuration (atawa Preview Foreign Configuration -> Import).** The "Asing" tag saukur hartina razia controller ningali metadata razia valid aya ditulis dina hard drive sorangan (nu ** Data Disk Format / DDF ** atawa séktor konfigurasi LSI di tungtung drive) nu béda ti kaayaan NVRAM kartu ayeuna. Impor maca tata letak array langsung tina drive sareng mawa disk virtual anjeun deui online tanpa kaleungitan bait tunggal. * ** PERNAH milih Clear Foreign Configuration atawa Initialize Virtual Disk.** Ngabersihan atawa initializing wipes metadata arrays atawa nol drive. * ** Pangecualian Perhatosan: ** Lamun hiji drive turun kaluar tilu minggu ka tukang, Anjeun terus nulis data anyar ka Asép Sunandar Sunarya didegradasi salila tilu minggu, lajeng Anjeun nyolok eta heubeul 3-minggu-bulu drive tunggal deui, ** NOT ngimpor konfigurasi asing ti drive bulukan tunggal ** leuwih luhureun drive aktip cageur anjeun; tibatan, ngaganti atawa clone drive bulukan.

2. Kumaha lamun Hardware RAID Card sorangan maot?¶

Upami motherboard server anjeun atanapi kartu pengontrol RAID hardware PCIe ngalaman kagagalan éléktronik sareng moal boot: * Anjeun teu kedah mésér révisi motherboard anu sami, sareng data anjeun masih utuh dina drive. * Mésér panggantian RAID controller tina ** kulawarga chipset controller sarua ** (Contona, LSI wae / Broadcom MegaRAID SAS 2108/2208/3108 atanapi Dell PERC H710 / H730 / kartu H740 bisa maca metadata DDF tina kartu PERC heubeul). * Pasang kartu RAID ngagantian kana PC anu tiasa dianggo, sambungkeun drive anu dilabélan anjeun dina urutan bay aslina, boot kana BIOS controller (Ctrl+R atawa Ctrl+H atawa menu UEFI HII), tur pilih Impor Konfigurasi Asing. Controller bakal maca perenah RAID tina drive sareng langsung dipasang volume anjeun.

Patarosan anu sering ditaroskeun¶

Panungtun patali¶

• Gagalna hard drive sareng pamulihan data
• Ngahapus file teu kahaja, drive formatna, sareng pamulihan poto
• Nyadangkeun komputer: strategi 3-2-1 sareng pamulihan musibah
• Gagal boot sistem Linux sareng perbaikan GRUB
• Tanggapan darurat ransomware sareng malware
• Nomer darurat global

Sumber dipariksa¶

• Organisasi Kernel Linux (Internasional): Linux RAID (mdadm) Wiki (raid.wiki.kernel.org), Recovering a Failed Software RAID, and Btrfs Kernel Documentation (btrfs.readthedocs.io asup btrfs rescue jeung btrfs restore).
• OpenZFS Documentation Project (International): zpool import Read-Only and Transaction Group Rollback (-F -o readonly=on) Administration Reference.
• Synology Inc. (Taiwan/International): Official Synology Knowledge Base Article KB-1079 (How can I use a PC to recover data when my Synology NAS malfunctions using Ubuntu mdadm jeung lvm2).
• GNU Project / Free Software Foundation (International): GNU ddrescue Manual for Non-Destructive Block-Level Imaging of Degraded RAID Member Drives.
• National Institute of Standards and Technology (NIST) (United States): Special Publication 800-86 and Storage Reliability Guidance on RAID Rebuild Exposure Windows and Uncorrectable Read Error (URE) Probabilities.