Lab 17.1 - device file can be unpredictable
I did the lab 17.1 to set up a RAID system on my Ubuntu 15.04
I did as mentioned in the lab/solution. Though I defined the RAID device file to be /dev/md0 it turns out that after reboot the device file got renamed to /dev/md127 without notice.
I figured this out because my Ubuntu booted into emergency mode. I had put /dev/md0 in the /etc/fstab file according to lab instruction, but the boot failed because the device file was finally named /dev/md127 for some reason.
Does anyone have an explanation for that?
I wonder why the RAID device file got renamed to /dev/md127 when I defined it to be /dev/md0.
The only thing that I did differently from the lab instructions was that I did not create a file /etc/mdadm.conf. Instead my system already had a file /etc/mdadm/mdadm.conf so I simply added the line that got returned by the commandmdadm --detail --scan
That line was (it is really one line, but the web page might display it in more than one line):ARRAY /dev/md0 metadata=1.2 name=elyasin-lcfs:0 UUID=4a491b9e:6590823a:c52acf39:8f9f5bb3
Comments
-
You may have missed the device name when inputting the mdadm -C
sudo -i
mdadm -C /dev/md0 -n 2 -l 1 /dev/vg/MD1 /dev/vg/MD20 -
No, I did not. I am very sure. I verified in my history the command I used.
I checked in my history withhistory | grep "sudo mdadm"
and it displayssudo mdadm --create /dev/md0 -l 1 -n2 /dev/sda2 /dev/sda3
.0 -
Now I booted my system and it went into root shell. The reason is that it could not find the
/dev/md127
mountpoint in from the/etc/fstab
file. I checked the device node and now all of the sudden the name is/dev/md0
.
I did not work with the RAID partitions since. I wonder how that could happen.0 -
I used VMs for my lab, if you used actual hard drives; maybe that makes a difference.0
-
I use a virtual machine too. I remember one difference now. I upgraded my Ubuntu to 15.04. Would it be reasonable to say it could be related to the update?0
-
Elyas wrote:I use a virtual machine too. I remember one difference now. I upgraded my Ubuntu to 15.04. Would it be reasonable to say it could be related to the update?
I wouldn't be able to confirm b/c I used CentOS7.0 -
I have also gone round and round with this exercise using Ubuntu 14.04 under VirtualBox. I have found the solution however. As the task is to create a raid under /dev/md0 (and not some other name) you will neeed to:
a) complete steps 1, 2 and 3 as described in the Lab text.
b) The command in step 4 is poorly constructed as it will lead to a permissions error while appending to /etc/mdadm.conf. One way is to first execute 'sudo -i', then the command as given, or 'sudo -- sh -c 'mdadm --detail --scan >> /etc/mdadm.conf'. The two dashes following sudo prevent sudo from interpreting the following text as a string of options, sh calls a shell and -c says execute everything between ' ' as a command. Weird, but it works.
c) And here is the important part: edit /etc/mdadm.conf, removing the NAME=... parameter. It should now look something like:
ARRAY /dev/md0 metadata=1.2 UUID=123456:789abc:cba987:fedcba
d) reboot and cat /proc/mdstat. You should get something like that shown in step 5, with the array name indicating md0.
It seems from a search that the most reasonable place for mdadm.conf is under
/etc/mdadm/mdadm.conf, but
/etc/mdadm.conf works as well.
0 -
Hi,
There is some few differences between distros; it's normal that something that works on one kind of distro won't on another, or at least will need to be modified.
I'm glad that you found a solution.
Luis.0 -
I have started redoing some of these exercises on a clean Ubuntu 14.04.5 server, and see that my comment above about removing the NAME= parameter from /etc/mdadm/mdadm.conf is insufficient in itself to prevent the automatic renaming of the array to /dev/md127. I did find however, that after editing mdadm.conf as above and adding the proper fstab entry, you must also run:
sudo update-initramfs -u
to force a read of mdadm.conf. Things then work well for auto-mounting raid device /dev/md0 on the next boot.
From what I can discover, this may only be an issue on the later Ubuntu servers.
Sam
0 -
Hi Sam,
I see that you tried this on Ubuntu 14 and 15. Have you tried on Ubuntu 16 LTS?
Thanks,
Luis.
0
Categories
- All Categories
- 216 LFX Mentorship
- 216 LFX Mentorship: Linux Kernel
- 783 Linux Foundation IT Professional Programs
- 352 Cloud Engineer IT Professional Program
- 174 Advanced Cloud Engineer IT Professional Program
- 80 DevOps Engineer IT Professional Program
- 146 Cloud Native Developer IT Professional Program
- 136 Express Training Courses
- 136 Express Courses - Discussion Forum
- 6.1K Training Courses
- 44 LFC110 Class Forum - Discontinued
- 70 LFC131 Class Forum
- 42 LFD102 Class Forum
- 226 LFD103 Class Forum
- 18 LFD110 Class Forum
- 36 LFD121 Class Forum
- 18 LFD133 Class Forum
- 7 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 4 LFD210 Class Forum
- 5 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 692 LFD259 Class Forum
- 111 LFD272 Class Forum
- 4 LFD272-JP クラス フォーラム
- 12 LFD273 Class Forum
- 135 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 2 LFS116 Class Forum
- 4 LFS118 Class Forum
- 4 LFS142 Class Forum
- 5 LFS144 Class Forum
- 4 LFS145 Class Forum
- 2 LFS146 Class Forum
- 3 LFS147 Class Forum
- LFS148 Class Forum
- 15 LFS151 Class Forum
- 2 LFS157 Class Forum
- 23 LFS158 Class Forum
- 6 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 31 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム
- 18 LFS203 Class Forum
- 127 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 52 LFS241 Class Forum
- 48 LFS242 Class Forum
- 38 LFS243 Class Forum
- 15 LFS244 Class Forum
- 2 LFS245 Class Forum
- LFS246 Class Forum
- 48 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 150 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 7 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 118 LFS260 Class Forum
- 159 LFS261 Class Forum
- 42 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 21 LFS268 Class Forum
- 30 LFS269 Class Forum
- 202 LFS272 Class Forum
- 2 LFS272-JP クラス フォーラム
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 9 LFW111 Class Forum
- 259 LFW211 Class Forum
- 181 LFW212 Class Forum
- 13 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 795 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 102 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 757 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 148 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 353 Ubuntu
- 468 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 93 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 61 Mobile Computing
- 18 Android
- 31 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 370 Off Topic
- 114 Introductions
- 173 Small Talk
- 22 Study Material
- 796 Programming and Development
- 302 Kernel Development
- 476 Software Development
- 1.8K Software
- 236 Applications
- 183 Command Line
- 3 Compiling/Installing
- 987 Games
- 317 Installation
- 93 All In Program
- 93 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)