which mdx number is for real ?

helen314 · 06-27-2019, 07:58 PM

Since my original question got lost in other problems, I am re-posting this again.

Which command is telling me the real mdx number ?

None of these will "automount" on boot.
Only manual mount works.

Quote:

fdisk -l

Partition table entries are not in disk order.

Disk /dev/md0: 195.2 GiB, 209580982272 bytes, 409337856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disklabel type: dos
Disk identifier: 0x6a551d9f

Device Boot Start End Sectors Size Id Type
/dev/md0p1 2048 102402047 102400000 48.8G 83 Linux
/dev/md0p2 102402048 204802047 102400000 48.8G 83 Linux
/dev/md0p3 204802048 307202047 102400000 48.8G 83 Linux
/dev/md0p4 307202048 389122047 81920000 39.1G 83 Linux

Disk /dev/md127: 195.2 GiB, 209580982272 bytes, 409337856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 279969792 bytes
Disklabel type: gpt
Disk identifier: 14847C7F-025C-4AD2-9987-F3B55A4C3F04

Device Start End Sectors Size Type
/dev/md127p1 2048 81922047 81920000 39.1G Linux filesystem
/dev/md127p3 91897856 194297855 102400000 48.8G Linux filesystem
/dev/md127p5 194297856 296697855 102400000 48.8G Linux filesystem
/dev/md127p8 296697856 409335807 112637952 53.7G Linux filesystem

Disk /dev/md126: 195.2 GiB, 209580982272 bytes, 409337856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 279969792 bytes
Disklabel type: dos
Disk identifier: 0x6a551d9f

Device Boot Start End Sectors Size Id Type
/dev/md126p1 2048 102402047 102400000 48.8G 83 Linux
/dev/md126p2 102402048 204802047 102400000 48.8G 83 Linux
/dev/md126p3 204802048 307202047 102400000 48.8G 83 Linux
/dev/md126p4 307202048 409337855 102135808 48.7G 83 Linux

Disk /dev/md1: 195.2 GiB, 209580982272 bytes, 409337856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 4199546880 bytes
Disklabel type: gpt
Disk identifier: F64B9F7D-9E3C-42E7-8037-CACC998E8478

Device Start End Sectors Size Type
/dev/md1p1 2048 102402047 102400000 48.8G Linux filesystem
/dev/md1p2 102402048 215042047 112640000 53.7G Linux filesystem
/dev/md1p3 215042048 327682047 112640000 53.7G Linux filesystem
/dev/md1p4 327682048 409335807 81653760 39G Linux filesystem
z@z-desktop:~$ mdadm --examine --scan
z@z-desktop:~$ sudo mdadm --examine --scan
ARRAY /dev/md/0 metadata=1.2 UUID=5afe531e:3c41ecd9:7057ae6e:98985049 name=jim-desktop:0
spares=1
ARRAY /dev/md/1 metadata=1.2 UUID=2fcd6c3c:7536faa9:8eb26bcd:31243bf7 name=z-desktop:1
ARRAY /dev/md/2 metadata=1.2 UUID=3c054983:7f097201:ea7c71b7:63b6933d name=a-desktop:2
ARRAY /dev/md/3 metadata=1.2 UUID=92ea9b2e:5f6d6f5c:34b3efe6:42fb5617 name=a-desktop:3
z@z-desktop:~$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md1 : active raid5 sdd9[4] sde9[3] sde7[0]
204668928 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md126 : active (auto-read-only) raid5 sde5[1] sde11[3] sde4[0]
204668928 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md127 : active (auto-read-only) raid5 sdf14[3] sdf12[0] sdf13[1]
204668928 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md0 : active raid5 sde6[6](S) sdb6[3] sdb4[1] sda3[0]
204668928 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

unused devices: <none>
z@z-desktop:~$

OK, here is part of my original post.

Same problem - which " md number " is for real?
The mdadm.conf is missing 2 an 3 - I can fix that.
But what about md127 / md126 ?

Quote:

z@z-desktop:~$ sudo dpkg-reconfigure mdadm
[sudo] password for z:
update-initramfs: deferring update (trigger activated)
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-4.15.0-54-generic
Found initrd image: /boot/initrd.img-4.15.0-54-generic
Found linux image: /boot/vmlinuz-4.15.0-52-generic
Found initrd image: /boot/initrd.img-4.15.0-52-generic
Found linux image: /boot/vmlinuz-4.15.0-51-generic
Found initrd image: /boot/initrd.img-4.15.0-51-generic
File descriptor 3 (pipe:[81713]) leaked on lvs invocation. Parent PID 7465: /bin/sh
Found Ubuntu 16.04.6 LTS (16.04) on /dev/sda6
Found Ubuntu 16.04.6 LTS (16.04) on /dev/sdb2
Found Ubuntu 16.04.2 LTS (16.04) on /dev/sdb5
Found Ubuntu 16.04.6 LTS (16.04) on /dev/sdc4
Adding boot menu entry for EFI firmware configuration
done
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for initramfs-tools (0.122ubuntu8.14) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-54-generic
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915
W: mdadm: the array /dev/md/a-desktop:3 with UUID 92ea9b2e:5f6d6f5c:34b3efe6:42fb5617
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.
W: mdadm: the array /dev/md/a-desktop:2 with UUID 3c054983:7f097201:ea7c71b7:63b6933d
W: mdadm: is currently active, but it is not listed in mdadm.conf. if
W: mdadm: it is needed for boot, then YOUR SYSTEM IS NOW UNBOOTABLE!
W: mdadm: please inspect the output of /usr/share/mdadm/mkconf, compare
W: mdadm: it to /etc/mdadm/mdadm.conf, and make the necessary changes.
z@z-desktop:~$

frankbell · 06-27-2019, 08:11 PM

Do you mean md number?

I'm showing my ignorance, but I ask because a search of "mdx number" gives me "Miami-Dade Expressway," among other irrelevant results.

helen314 · 06-27-2019, 08:49 PM

Quote:

Originally Posted by frankbell

Do you mean md number?

I'm showing my ignorance, but I ask because a search of "mdx number" gives me "Miami-Dade Expressway," among other irrelevant results.

No problem.

The RAID "device arrays" in Linux are /dev/md0 - /dev/md127.
When you "build" the array YOU can select the number, but for some (to me ) unknown reasons the "system" can mess things up by numbering it "automatically?" "backwards " from md127 down.
I have several test arrays and they are numbered 0,1,2,3 or 0,1,126, 127 depending which command I use.
I had the original md0 working perfect.

Now it is a messed up and I need to get these numbers correct.

It looks as mixing UUID and label is also an issue - depending on command.

frankbell · 06-27-2019, 09:22 PM

I have no experience with RAID and can't help with your issue, but thank you teaching me something new to me.