Advertisement
Guest User

Untitled

a guest
Feb 25th, 2022
38
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. # mdadm configuration file
  2. #
  3. # mdadm will function properly without the use of a configuration file,
  4. # but this file is useful for keeping track of arrays and member disks.
  5. # In general, a mdadm.conf file is created, and updated, after arrays
  6. # are created. This is the opposite behavior of /etc/raidtab which is
  7. # created prior to array construction.
  8. #
  9. #
  10. # the config file takes two types of lines:
  11. #
  12. # DEVICE lines specify a list of devices of where to look for
  13. # potential member disks
  14. #
  15. # ARRAY lines specify information about how to identify arrays so
  16. # so that they can be activated
  17. #
  18.  
  19.  
  20. # You can have more than one device line and use wild cards. The first
  21. # example includes SCSI the first partition of SCSI disks /dev/sdb,
  22. # /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
  23. # line looks for array slices on IDE disks.
  24. #
  25. #DEVICE /dev/sd[bcdjkl]1
  26. #DEVICE /dev/hda1 /dev/hdb1
  27. #
  28. # The designation "partitions" will scan all partitions found in
  29. # /proc/partitions
  30. DEVICE partitions
  31.  
  32.  
  33. # ARRAY lines specify an array to assemble and a method of identification.
  34. # Arrays can currently be identified by using a UUID, superblock minor number,
  35. # or a listing of devices.
  36. #
  37. # super-minor is usually the minor number of the metadevice
  38. # UUID is the Universally Unique Identifier for the array
  39. # Each can be obtained using
  40. #
  41. # mdadm -D <md>
  42. #
  43. # To capture the UUIDs for all your RAID arrays to this file, run these:
  44. # to get a list of running arrays:
  45. # # mdadm -D --scan >>/etc/mdadm.conf
  46. # to get a list from superblocks:
  47. # # mdadm -E --scan >>/etc/mdadm.conf
  48. #
  49. #ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
  50. #ARRAY /dev/md1 super-minor=1
  51. #ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
  52. #
  53. # ARRAY lines can also specify a "spare-group" for each array. mdadm --monitor
  54. # will then move a spare between arrays in a spare-group if one array has a
  55. # failed drive but no spare
  56. #ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
  57. #ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
  58. #
  59.  
  60.  
  61. # When used in --follow (aka --monitor) mode, mdadm needs a
  62. # mail address and/or a program. To start mdadm's monitor mode, enable
  63. # mdadm.service in systemd.
  64. #
  65. # If the lines are not found, mdadm will exit quietly
  66. #MAILADDR root@mydomain.tld
  67. #PROGRAM /usr/sbin/handle-mdadm-events
  68. ARRAY /dev/md0 metadata=1.2 name=archiso:0 UUID=e15a4e74:8398b4ee:823dae0f:99bc73fc
  69. ARRAY /dev/md1 metadata=1.2 name=archiso:1 UUID=77d2dae2:f7a913cd:55ae6144:2e1a2d49
  70.  
Advertisement
RAW Paste Data Copied
Advertisement