Resolved „Unbootable System Error“ after „update-initramfs“ (1and1)

[Dukemaster]

Hi friends and members of the amazing PLESK COMMUNITY,
yesterday I wanted to solve a plesk update problem (already fixed by Plesk) by making a manual update/upgrade in the best way, described by @UFHH01.
Great Plesk Onyx 7.017, Ubuntu 14.0.4 by Hoster 1and1
Everything worked fine with

apt-get clean

, followed by

apt-get update

.
Then I performed

aptitude upgrade

with a common error in systems by 1and1.

update-initramfs: Generating /boot/initrd.img-3.13.0-103-generic
W: mdadm: the array /dev/md1 with UUID dbbcb241:ac157198:3ec6073f:e8873211
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/md3 with UUID dbbcb241:ac157198:3ec6073f:e8873211
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.
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-103-generic /boot/vmlinuz-3.13.0-103-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-103-generic /boot/vmlinuz-3.13.0-103-generic
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-3.13.0-103-generic
Found kernel: /boot/vmlinuz-3.13.0-101-generic
Found kernel: /boot/vmlinuz-3.13.0-100-generic
Found kernel: /boot/memtest86+.bin
Merging changes into the new version
Updating /boot/grub/menu.lst ... done

After searching internet for hours I got the best information in this askubuntu article.
It has to do with the image and modified grub.lst by my provider 1and1. Seems a common issue.

First I want to help other Plesk user who have the same problem, mostly those who got Plesk with a linux distribution from 1and1.

My question now is simple for the experts, but not for me.
I already obtained

/dev/md1
UUID : dbbcb241:ac157198:3ec6073f:e8873211
/dev/md3
UUID : dbbcb241:ac157198:3ec6073f:e8873211

For security I changed the real UUID here in forum.
Please, could you tell me the commands how to replace them in /etc/mdadm/mdadm.conf.
A little instruction of needed commands would be helpful, also if it's necessary to do something else after replacing, like mount e.g. All commands until rebooting.
I had so much work last two weeks, reinitial server 8 times. I don't want to make everything again, only by my mistake choosing the option

do 3-way merge with both versions

in the selection menu according what to do with old and maintainers version of grub.lst during upgrade
Please help me to do the right.
Or is everything well because of:

Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-3.13.0-103-generic
Found kernel: /boot/vmlinuz-3.13.0-101-generic
Found kernel: /boot/vmlinuz-3.13.0-100-generic
Found kernel: /boot/memtest86+.bin
Merging changes into the new version
Updating /boot/grub/menu.lst ... done

Greets

 

[UFHH01]

Please, could you tell me the commands how to replace them in /etc/mdadm/mdadm.conf.

How you edit a linux configuration file, is totally up to yourself. You could use "vi", "vim", "nano", "pico"... it really depends on "what you like most", so pls. consider to use ALL of them once and decide by yourself, which one you would like to use in the future.


Actually, your hoster missed to configure the "mdadm.conf" correctly with his installation image, this is a "server hoster issue" and should be considered to be solved by them, not by you.
Anyway, to list the correct "UUID" for your corresponding arrays, you can use the command:

mdadm --misc --detail /dev/mdX​

... where "X" should be replaced with the correct number of your MD - array. To correct misconfigurations in your "mdadm.conf", you will now use the exact details from your output and replace it with the misconfigured ones, with the help of the editor of your choice.
Pls. check afterwards with "update-initramfs -u", if all is well configured! ( There is no warning/error - message in case of a correct configuration ).


For your "grub" - question:

Or is everything well because of:

Yes, all is fine here - no need to interact.

 

[Dukemaster]

Thanks for your help @UFHH01,
I prefer vi as editor but also be able to use nano.
I already did it today with the solution from askubuntu, the same like in your post:

Obtain the UUID for your array in question with the command: mdadm --misc --detail /dev/md1 and 3 (where X[1 and 3] is the array number) and edit /etc/mdadm/mdadm.conf and replace them with:

I got the UUID's.
/dev/md1
UUID : 8b29c735:8626b11e:1f51fb89:78ee93fe
/dev/md3
UUID : d6ada2f6:9ffb4352:1f51fb89:78ee93fe
9e691db1:f8fcc7d8:f56d9c11:1c202693

Would be great if you can help me with the right commands.
Lot of greets