I installed grub from CentOS, Debian 8, Devuan, Fedora

I tried run openSUSE after every grub installation in each distribution.

This is a confused mess to begin with. It won't help if you keep installing grub from different distros. Have you been closely examining and comparing the grub.cfg files from each distro every time you run grub-install? How can you keep track of what you're doing?

Pick one disto to be in charge of grub. Then see which ones you can boot from that menu. If any don't work, try starting them from grub command line. It might be that one or more installations is not where you think it is or not where grub thinks it is. https://www.linux.com/learn/how-rescue- … ub-2-Linux

So, whichever one ran grub-install last should be the one in charge of booting. And update-grub (or whatever command generates a new boot menu on that installation) should include an entry for each installation on that machine. Right now, which system is listed first, and will it boot?

If you can boot into devuan enough to run root commands, or if you can chroot into it, you might try the following. I can't tell if this is what you need for sure, but there's at least a small chance it will fix the problem with devuan.

apt-get remove live-tools
CRYPTSETUP=y update-initramfs -u (and maybe -k <kernel> if you want to be specific)

I tried run openSUSE after every grub installation in each distribution.

# apt-get remove live-tools
# CRYPTSETUP=y update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.16.0-5-amd64
cryptsetup: WARNING: failed to detect canonical device of /dev/sda14
cryptsetup: WARNING: could not determine root device from /etc/fstab
live-boot: core filesystems devices utils udev wget blockdev.

Devuan grub, it didn't solve anything.

If you can boot into devuan enough to run root commands, or if you can chroot into it, you might try the following. I can't tell if this is what you need for sure, but there's at least a small chance it will fix the problem with devuan.

apt-get remove live-tools
CRYPTSETUP=y update-initramfs -u (and maybe -k <kernel> if you want to be specific)

Did this installation ever work normally? Was it ok up until it complained about fsck, or did it complain on the first reboot into the new system?

Is this a uefi system, or legacy bios?
Are you using gpt or msdos partition table?
Please post the output of 'fdisk -l' and 'blkid'
Which installations will boot and which will not? Which one is in charge of grub?

Never. It complained on the first reboot into the new system.

Legacy bios.
Msdos partition table.

#fdisk -l

Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00......

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1  *          2048     718847     716800   350M  7 HPFS/NTFS/exFAT
/dev/sda2           718848  719351807  718632960 342,7G  7 HPFS/NTFS/exFAT
/dev/sda3        719351808 1953523711 1234171904 588,5G  5 Extended
/dev/sda5        719353856  719357951       4096     2M 83 Linux
/dev/sda6        719360000  721457151    2097152     1G 83 Linux
/dev/sda7        721459200  763406335   41947136    20G 83 Linux
/dev/sda8        763408384  779663359   16254976   7,8G 83 Linux
/dev/sda9        779665408  799199231   19533824   9,3G 83 Linux
/dev/sda10       799201280  803409919    4208640     2G 82 Linux swap / Solaris
/dev/sda11       803411968  887302143   83890176    40G 83 Linux
/dev/sda12       887304192  950212607   62908416    30G 83 Linux
/dev/sda13      1543329792 1662517247  119187456  56,9G 83 Linux
/dev/sda14      1021849600 1124188159  102338560  48,8G 83 Linux
/dev/sda15      1124190208 1179574271   55384064  26,4G 83 Linux
/dev/sda16      1662519296 1751398399   88879104  42,4G 83 Linux
/dev/sda17      1179576320 1300207615  120631296  57,5G 83 Linux
/dev/sda18      1300209664 1414524927  114315264  54,5G 83 Linux

Partition table entries are not in disk order.

# blkid
/dev/sda1: LABEL="System Reserved" UUID="D410F54A10F533D8" TYPE="ntfs" PARTUUID="00a68792-01"
/dev/sda2: UUID="7E80F79280F74F61" TYPE="ntfs" PARTUUID="00a68792-02"
/dev/sda5: LABEL="empty" UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-05"
/dev/sda6: UUID="........-....-....-....-............" TYPE="xfs" PARTUUID="00a68792-06"
/dev/sda7: UUID="........-....-....-....-............" TYPE="crypto_LUKS" PARTUUID="00a68792-07"
/dev/sda8: UUID="........-....-....-....-............" TYPE="crypto_LUKS" PARTUUID="00a68792-08"
/dev/sda9: UUID="........-....-....-....-............" TYPE="crypto_LUKS" PARTUUID="00a68792-09"
/dev/sda10: UUID="........-....-....-....-............" TYPE="swap" PARTUUID="00a68792-0a"
/dev/sda11: UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-0b"
/dev/sda12: UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-0c"
/dev/sda13: UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-0d"
/dev/sda14: LABEL="devuan" UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-0e"
/dev/sda15: UUID="........-....-....-....-............" TYPE="crypto_LUKS" PARTUUID="00a68792-0f"
/dev/sda16: UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-10"
/dev/sda17: LABEL="fedora" UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-11"
/dev/sda18: LABEL="debian" UUID="........-....-....-....-............" TYPE="ext4" PARTUUID="00a68792-12"

You may have read that openSUSE can't boot. I installed grub from CentOS, Debian 8, Devuan, Fedora (run on this disk).

Is this a uefi system, or legacy bios?
Are you using gpt or msdos partition table?
Please post the output of 'fdisk -l' and 'blkid'
Which installations will boot and which will not? Which one is in charge of grub?

Aha! Did you notice that what was in the video looks completely different from what you saw during the installation? I recognize the warnings about using uuid or labels with encryption. That was the live installer. You can use uuids or labels with encrypted partition, but you have to do it manually after the install. The installer won't do it for you.

Are there any files in /etc/initramfs-tools/conf.d/ in the devuan installation? If so, what's there?

Is there more than one hard drive on the computer? If so, please say a little more about your setup.

Yes I did notice that, but unfortunately it's long time ago so it's hard to remember.

That is what I'm trying to.

/etc/initramfs-tools/conf.d   is empty.

One hard drive only.

Are there any files in /etc/initramfs-tools/conf.d/ in the devuan installation? If so, what's there?

Is there more than one hard drive on the computer? If so, please say a little more about your setup.

Here's a video showing the creation of an encrypted filesystem in the installer. In this case, I made a separate /boot partition so I could encrypt the root filesystem. But the procedure for creating the encrypted volume would be the same for /home. Take a look and see if you did something significantly different from this. It is confusing. The -4 in the filename is there because I had to do it four times before I got it right for the video.
http://distro.ibiblio.org/refracta/misc … rypt-4.ogv

You said above that you were able to fix it in one installation. What did you do on that one that you didn't do on the one that's still failing?

Did you try it like this?

fstab
/dev/sda14	/	ext4	defaults,noatime	0	1
/dev/mapper/home_fs	/home	ext4	defaults,noatime	0	2
/dev/sda10	swap	 swap	defaults	0	0

crypttab
home_fs		/dev/sda15		none		luks

Thank you for video. Did you use UUIDs and labels in your video ?

I've got this message from installer:

...
-->UUIDs in fstab won't work with encrypted filesystems and will not be used. Edit fstab manually after the installation.
-->Disk labels in fstab won't work with encrypted filesystems and will not be used. Edit fstab manually after the installation.
...

I created user's home directory after previous installation.

I tried this fstab and crypttab but user's home directory is not visible.

I'm not sure if it's related but something has happened during solving this:
https://dev1galaxy.org/viewtopic.php?id=1827

You said above that you were able to fix it in one installation. What did you do on that one that you didn't do on the one that's still failing?

Did you try it like this?

fstab
/dev/sda14	/	ext4	defaults,noatime	0	1
/dev/mapper/home_fs	/home	ext4	defaults,noatime	0	2
/dev/sda10	swap	 swap	defaults	0	0

crypttab
home_fs		/dev/sda15		none		luks

If you lost your home directory after editing files, you should restore those files to their previous working state. Exactly what edits did you do?

Previous state was created by installer:

fstab
/dev/sda14	/	ext4	defaults,noatime	0	1
/dev/sda15	/home	ext4	defaults,noatime	0	2
/dev/sda10	swap	swap	defaults	0	0

crypttab
home_fs		/dev/sda15		none		luks

But it causes boot error - see original post.

I tried these changes - see post #10

That doesn't make sense. If it was working before you commented those lines, it should work again when you uncomment them. Where is that volume already mounted or mapped?

Look at the output of

df -h
mount
ls -l /dev/mapper/

I've never been using both commented and uncommented lines at the same time. There is password prompt in infinite loop so I can't switch to command prompt.

Look at the output of

df -h
mount
ls -l /dev/mapper/

It makes sense that your /home is not visible after you comment out the lines for /home in fstab and cryupttab. That's not the right solution.

1. Boot a live CD/DVD/USB
2. As root, run:

cryptsetup luksOpen /dev/sda15 homefs
fsck /dev/mapper/homefs

3. When that's done, you can fix those two files:

mount /dev/mapper/homefs /mnt

Then edit fstab and crypttab to uncomment the lines you commented.
4. Finish

umount /mnt
cryptsetup luksClose homefs

5. Reboot into the installed system.

Thank you.
After uncommenting:

Cannot use device /dev/disk/by-uuid/33e...-...-...  which is in use (already mapped or mounted)

1. Boot a live CD/DVD/USB
2. As root, run:

cryptsetup luksOpen /dev/sda15 homefs
fsck /dev/mapper/homefs

3. When that's done, you can fix those two files:

mount /dev/mapper/homefs /mnt

Then edit fstab and crypttab to uncomment the lines you commented.
4. Finish

umount /mnt
cryptsetup luksClose homefs

5. Reboot into the installed system.