| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | * verbose log of [../] |
| | 4 | |
| | 5 | = mdadm -D /dev/md0 = |
| | 6 | * mitty@ubuntu-haa:~$ sudo mdadm -D /dev/md0 |
| | 7 | {{{ |
| | 8 | /dev/md0: |
| | 9 | Version : 00.90 |
| | 10 | Creation Time : Thu Mar 24 17:31:36 2011 |
| | 11 | Raid Level : raid1 |
| | 12 | Array Size : 2047936 (2000.27 MiB 2097.09 MB) |
| | 13 | Used Dev Size : 2047936 (2000.27 MiB 2097.09 MB) |
| | 14 | Raid Devices : 2 |
| | 15 | Total Devices : 2 |
| | 16 | Preferred Minor : 0 |
| | 17 | Persistence : Superblock is persistent |
| | 18 | |
| | 19 | Update Time : Thu Mar 24 17:31:47 2011 |
| | 20 | State : clean |
| | 21 | Active Devices : 2 |
| | 22 | Working Devices : 2 |
| | 23 | Failed Devices : 0 |
| | 24 | Spare Devices : 0 |
| | 25 | |
| | 26 | UUID : 32578407:6f33f50b:893cf340:745f5dce (local to host ubuntu-haa) |
| | 27 | Events : 0.34 |
| | 28 | |
| | 29 | Number Major Minor RaidDevice State |
| | 30 | 0 8 17 0 active sync /dev/sdb1 |
| | 31 | 1 8 33 1 active sync /dev/sdc1 |
| | 32 | }}} |
| | 33 | |
| | 34 | = dpkg-reconfigure mdadm = |
| | 35 | * see also wiki:TipAndDoc/RAID#dpkg-reconfiguremdadm |
| | 36 | |
| | 37 | * mitty@ubuntu-haa:~$ sudo dpkg-reconfigure mdadm |
| | 38 | {{{ |
| | 39 | ┌──────────────────────────┤ Configuring mdadm ├─ |
| | 40 | │ │ |
| | 41 | │ If the kernel supports it (versions greater than 2.6.14), mdadm can │ |
| | 42 | │ periodically check the redundancy of MD arrays (RAIDs). This may be a │ |
| | 43 | │ resource-intensive process, depending on the local setup, but it could │ |
| | 44 | │ help prevent rare cases of data loss. Note that this is a read-only │ |
| | 45 | │ check unless errors are found; if errors are found, mdadm will try to │ |
| | 46 | │ correct them, which may result in write access to the media. │ |
| | 47 | │ │ |
| | 48 | │ The default, if turned on, is to check on the first Sunday of every │ |
| | 49 | │ month at 01:06. │ |
| | 50 | │ │ |
| | 51 | │ Should mdadm run monthly redundancy checks of the MD arrays? │ |
| | 52 | │ │ |
| | 53 | │ [[<Yes>]] <No> │ |
| | 54 | │ │ |
| | 55 | └────────────────────────────────────── |
| | 56 | |
| | 57 | (snip) |
| | 58 | |
| | 59 | ┌──────────────────────────┤ Configuring mdadm ├─ |
| | 60 | │ │ |
| | 61 | │ The MD (RAID) monitor daemon sends email notifications in response to │ |
| | 62 | │ important MD events (such as a disk failure). │ |
| | 63 | │ │ |
| | 64 | │ Enabling this option is recommended. │ |
| | 65 | │ │ |
| | 66 | │ Do you want to start the MD monitoring daemon? │ |
| | 67 | │ │ |
| | 68 | │ [[<Yes>]] <No> │ |
| | 69 | │ │ |
| | 70 | └────────────────────────────────────── |
| | 71 | |
| | 72 | (snip) |
| | 73 | |
| | 74 | ┌─────────────────────────┤ Configuring mdadm ├── |
| | 75 | │ Please enter the email address of the user who should get the email │ |
| | 76 | │ notifications for important MD events. │ |
| | 77 | │ │ |
| | 78 | │ Recipient for email notifications: │ |
| | 79 | │ │ |
| | 80 | │ root_________________________________________________________________ │ |
| | 81 | │ │ |
| | 82 | │ <Ok> │ |
| | 83 | │ │ |
| | 84 | └─────────────────────────────────────── |
| | 85 | |
| | 86 | (snip) |
| | 87 | |
| | 88 | ┌───────────────────────────┤ Configuring mdadm ├ |
| | 89 | │ │ |
| | 90 | │ If your root filesystem is on a RAID, and a disk is missing at boot, it │ |
| | 91 | │ can either boot with the degraded array, or hold the system at a │ |
| | 92 | │ recovery shell. │ |
| | 93 | │ │ |
| | 94 | │ Running a system with a degraded RAID could result in permanent data │ |
| | 95 | │ loss if it suffers another hardware fault. │ |
| | 96 | │ │ |
| | 97 | │ If you do not have access to the server console to use the recovery │ |
| | 98 | │ shell, you might answer "yes" to enable the system to boot unattended. │ |
| | 99 | │ │ |
| | 100 | │ Do you want to boot your system if your RAID becomes degraded? │ |
| | 101 | │ │ |
| | 102 | │ [[<Yes>]] <No> │ |
| | 103 | │ │ |
| | 104 | └─────────────────────────────────────── |
| | 105 | }}} |
