diff options
| author | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-10-24 07:17:17 +0000 |
|---|---|---|
| committer | madduck <madduck@3cfab66f-1918-0410-86b3-c06b76f9a464> | 2006-10-24 07:17:17 +0000 |
| commit | 73731ad40c861d37adb7fee3620923e01f4e0fed (patch) | |
| tree | 8a7cecf7bc3191bf2d3a9258536d43ca092bd994 /debian/FAQ | |
| parent | 6d5c823d1e4fbcd1b18aa89518d6d7f437c6ef4c (diff) | |
added dirty degraded to faq
Diffstat (limited to 'debian/FAQ')
| -rw-r--r-- | debian/FAQ | 9 |
1 files changed, 9 insertions, 0 deletions
@@ -332,6 +332,15 @@ Also see /usr/share/doc/mdadm/README.recipes.gz 0. http://marc.theaimsgroup.com/?l=linux-raid&m=116117813315590&w=2 +15. How can I start a dirty degraded array? +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + A degraded array (e.g. a RAID5 with only two disks) that has not been + properly stopped cannot be assembled just like that; mdadm will refuse and + complain about a "dirty degraded array". + + The solution is to force-assemble it, and then to start it. Please see + recipes 4 and 4b of /usr/share/doc/mdadm/README.recipes.gz . + -- martin f. krafft <madduck@debian.org> Wed, 18 Oct 2006 15:56:32 +0200 $Id$ |