Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- content:serverbasics [2024/04/20 13:02] – [UMask- Approach] Daniel
+++ content:serverbasics [2024/10/26 12:35] (aktuell) – [Recover faulty Disc] Daniel
@@ Zeile 60: / Zeile 60: @@
 You than install your Linux Bootmanager / EFIBOOT to that md- Device. If its not found in the beginning of the installation, scan for raid- devices or just create it while installing with the line above.
+=== Recover faulty Disc ===
+If some Raid- Disc becomes faulty, it will show up like this (its for raid5, but raid1 will look alkie):
+<code>
+obel1x:~ # mdadm -D /dev/md126
+/dev/md126:
+          Version : 1.0
+    Creation Time : Fri Apr 10 11:44:19 2020
+       Raid Level : raid5
+       Array Size : 1460286976 (1392.64 GiB 1495.33 GB)
+    Used Dev Size : 730143488 (696.32 GiB 747.67 GB)
+     Raid Devices : 3
+    Total Devices : 2
+      Persistence : Superblock is persistent
+    Intent Bitmap : Internal
+      Update Time : Sat Oct 26 14:26:37 2024
+            State : clean, degraded
+   Active Devices : 2
+  Working Devices : 2
+   Failed Devices : 0
+    Spare Devices : 0
+           Layout : left-symmetric
+       Chunk Size : 128K
+Consistency Policy : bitmap
+             Name : any:slowstorage
+             UUID : 6542dc7c:a8f93b36:15f90ca1:54d03417
+           Events : 285411
+   Number   Major   Minor   RaidDevice State
+       8        5        0      active sync   /dev/sda5
+       8       21        1      active sync   /dev/sdb5
+      -       0        0        2      removed
+</code>
+Maybe instead of removed you can see some entry like faulty instead of removed - this is, when the array had just failed.
+To add a new device, you need an empty partiotion with at least the expected size (here 696 GB would be enough):
+<code>
+obel1x:~ # fdisk -l /dev/sdc
+Disk /dev/sdc: 698.64 GiB, 750156374016 bytes, 1465149168 sectors
+Disk model: WDC WD7500AAVS-0
+Units: sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 512 bytes
+I/O size (minimum/optimal): 512 bytes / 512 bytes
+Disklabel type: gpt
+Disk identifier: 699DC7F4-D344-4447-8C5B-1F98E017A12B
+Device     Start        End    Sectors   Size Type
+/dev/sdc1   2048 1465149134 1465147087 698.6G Linux RAID
+</code>
+That Partition should have the Type Linx Raid. If you don't have that, create it with partition- tool of kde or what you want.
+Now you can simply add the device to the raid and it will begin to work:
+<code>
+obel1x:~ # mdadm /dev/md126 --add /dev/sdc1
+mdadm: re-added /dev/sdc1
+obel1x:~ # mdadm -D /dev/md126
+/dev/md126:
+          Version : 1.0
+    Creation Time : Fri Apr 10 11:44:19 2020
+       Raid Level : raid5
+       Array Size : 1460286976 (1392.64 GiB 1495.33 GB)
+    Used Dev Size : 730143488 (696.32 GiB 747.67 GB)
+     Raid Devices : 3
+    Total Devices : 3
+      Persistence : Superblock is persistent
+    Intent Bitmap : Internal
+      Update Time : Sat Oct 26 14:34:57 2024
+            State : clean, degraded, recovering
+   Active Devices : 2
+  Working Devices : 3
+   Failed Devices : 0
+    Spare Devices : 1
+           Layout : left-symmetric
+       Chunk Size : 128K
+Consistency Policy : bitmap
+   Rebuild Status : 1% complete
+             Name : any:slowstorage
+             UUID : 6542dc7c:a8f93b36:15f90ca1:54d03417
+           Events : 285497
+   Number   Major   Minor   RaidDevice State
+       8        5        0      active sync   /dev/sda5
+       8       21        1      active sync   /dev/sdb5
+       8       33        2      spare rebuilding   /dev/sdc1
+</code>