Upgrade Leap 42.1 -> 42.3 error "Cannot detect device mounted as root"

mse1 · January 13, 2018, 5:23pm

I try to upgrade Leap 42.1 to 42.3. In screen “Installation Settings” I get in item “Booting” the error message
“Cannot detect device mounted as root. Please check partitioning. Error: No proposal”

Any help appreciated.

hcvv · January 13, 2018, 5:47pm

First you should explain how you try to upgrade. There are several methods. And while we can guess what you did from your rather vague description, doing bug searching based on guesses is not a good idea.

gogalthorp · January 13, 2018, 5:48pm

Need more info. Encryption being used? LVM? Show fdisk -l and tell what partitions are which. Also how upgrading? I assume from a DVD or USB???

mse1 · January 13, 2018, 7:02pm

Installation by DVD, ISO downloaded from here:
http://download.opensuse.org/distribution/leap/42.3/iso/openSUSE-Leap-42.3-DVD-x86_64.iso
fstab of 42.1:


UUID=d3e17990-219e-4f27-9018-9c6af9db6e5f swap swap defaults 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 / btrfs defaults 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /boot/grub2/i386-pc btrfs subvol=boot/grub2/i386-pc 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /boot/grub2/x86_64-efi btrfs subvol=boot/grub2/x86_64-efi 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /opt btrfs subvol=opt 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /srv btrfs subvol=srv 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /tmp btrfs subvol=tmp 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /usr/local btrfs subvol=usr/local 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/crash btrfs subvol=var/crash 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/lib/libvirt/images btrfs subvol=var/lib/libvirt/images 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/lib/mailman btrfs subvol=var/lib/mailman 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/lib/mariadb btrfs subvol=var/lib/mariadb 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/lib/mysql btrfs subvol=var/lib/mysql 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/lib/named btrfs subvol=var/lib/named 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/lib/pgsql btrfs subvol=var/lib/pgsql 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/log btrfs subvol=var/log 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/opt btrfs subvol=var/opt 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/spool btrfs subvol=var/spool 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /var/tmp btrfs subvol=var/tmp 0 0
UUID=b1987f34-0b69-494c-9041-5d2fc12e9675 /.snapshots btrfs subvol=.snapshots 0 0
UUID=fe1bed3c-ecc7-4288-bbee-5ab7477a6ea1 /home                xfs        defaults              1 2

hcvv · January 13, 2018, 7:08pm

And what did you do? Installed new, Upgrade? Please inform us, we are not clairvoyant.

mse1 · January 13, 2018, 7:28pm

“Upgrade”, see the thread title.
Steps:
-Turn on the PC.

Press the button on the DVD-drive, the door opens.
Put the the DVD in the tray (do you need to know how I burned the ISO?).
Restart the PC by the power button.
The DVD drive closes.
There is a screen with a menu.
Select “Upgrade” by the arrow down key.
Press enter.
Linux boots.
The installation system will be loaded.
In the keyboard selection dialog select “German (Switzerland)”.
Accept the presented “System to upgrade” (IIRC d3e17990-219e-4f27-9018-9c6af9db6e5f Leap 42.1)
See the error described in the first post.

mse1 · January 13, 2018, 7:41pm

Sorry, copy paste error
"

Accept the presented “System to upgrade” (IIRC d3e17990-219e-4f27-9018-9c6af9db6e5f Leap 42.1)
"
should be
Accept the presented “System to upgrade” (IIRC b1987f34-0b69-494c-9041-5d2fc12e9675 Leap 42.1)

hcvv · January 13, 2018, 7:42pm

Fine, that is an extensive description. Many can now follow what you do (and maybe even try to recreate).

That you use the word “upgrade” in your first post, does not say much. People use that word also when they upgrade by switching to the repos of the new version and then doing

zypper dup

(and yes, dup for “distribution upgrade”).
And also when doing a fresh install over the older version (keeping /home and other application/user data). They will tel you that they upgraded from 42.2 to 42.3.

In any case we try to not take those things for granted as long as they are not explicit explained.

mse1 · January 13, 2018, 8:40pm


:~> sudo /usr/sbin/fdisk -l
root's password:

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x494e384d

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048    411647    409600   200M  7 HPFS/NTFS/exFAT
/dev/sda2          411648 205211647 204800000  97.7G  7 HPFS/NTFS/exFAT
/dev/sda3       924190720 976773167  52582448  25.1G 12 Compaq diagnostics
/dev/sda4       205211648 924190719 718979072 342.9G  f W95 Ext'd (LBA)
/dev/sda5       342855680 347052031   4196352     2G 82 Linux swap / Solaris
/dev/sda6       347054080 430944255  83890176    40G 83 Linux
/dev/sda7       430946304 924190719 493244416 235.2G 83 Linux
/dev/sda8       205213696 266653695  61440000  29.3G  7 HPFS/NTFS/exFAT
/dev/sda9       266655744 342855679  76199936  36.3G 83 Linux

Partition table entries are not in disk order.

hcvv · January 13, 2018, 9:12pm

And to see which UUID belongs to whih partition, one needs:

ls -l /dev/disk/by-uuid/

mse1 · January 13, 2018, 9:26pm


:~> ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jan 13 18:54 0D5527BB7E2AE37C -> ../../sda8
lrwxrwxrwx 1 root root  9 Jan 13 18:54 2017-07-19-16-46-54-00 -> ../../sr0
lrwxrwxrwx 1 root root 10 Jan 13 18:54 64829FE3829FB7CE -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 13 18:54 b1987f34-0b69-494c-9041-5d2fc12e9675 -> ../../sda6
lrwxrwxrwx 1 root root 10 Jan 13 18:54 B672ADA872AD6DB5 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 13 18:54 B8E6AC63E6AC241A -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 13 18:54 d3e17990-219e-4f27-9018-9c6af9db6e5f -> ../../sda5
lrwxrwxrwx 1 root root 10 Jan 13 18:54 fe1bed3c-ecc7-4288-bbee-5ab7477a6ea1 -> ../../sda7

hcvv · January 13, 2018, 9:49pm

The UUID used for mounting / is b1987f34-0b69-494c-9041-5d2fc12e9675. That belongs to sda6.

The error message says d3e17990-219e-4f27-9018-9c6af9db6e5f, which is sda5. In your fstab and in your fdisk -l this is Swap.

Oh no. In post #7, you say different.

arvidjaar · January 13, 2018, 10:08pm

You should really open bug report. Do not try to write down message - rather provide photo of screen with error.

mse1 · January 13, 2018, 10:20pm

In installed 42.1:


:~> ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jan 13 18:54 0D5527BB7E2AE37C -> ../../sda8
lrwxrwxrwx 1 root root  9 Jan 13 18:54 2017-07-19-16-46-54-00 -> ../../sr0
lrwxrwxrwx 1 root root 10 Jan 13 18:54 64829FE3829FB7CE -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 13 18:54 b1987f34-0b69-494c-9041-5d2fc12e9675 -> ../../sda6
lrwxrwxrwx 1 root root 10 Jan 13 18:54 B672ADA872AD6DB5 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 13 18:54 B8E6AC63E6AC241A -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 13 18:54 d3e17990-219e-4f27-9018-9c6af9db6e5f -> ../../sda5
lrwxrwxrwx 1 root root 10 Jan 13 18:54 fe1bed3c-ecc7-4288-bbee-5ab7477a6ea1 -> ../../sda7

In 42.3 installation environment booted from 42.3 installation DVD:


total 0
lrwxrwxrwx 1 root root 10 Jan 13 15:52 0D5527BB7E2AE37C -> ../../sda8
lrwxrwxrwx 1 root root  9 Jan 13 15:49 2017-07-19-16-46-54-00 -> ../../sr0
lrwxrwxrwx 1 root root 10 Jan 13 15:52 64829FE3829FB7CE -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 13 16:00 7B69-EBDA -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jan 13 15:52 b1987f34-0b69-494c-9041-5d2fc12e9675 -> ../../sda9
lrwxrwxrwx 1 root root 10 Jan 13 15:52 B672ADA872AD6DB5 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 13 15:52 B8E6AC63E6AC241A -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 13 15:52 d3e17990-219e-4f27-9018-9c6af9db6e5f -> ../../sda5
lrwxrwxrwx 1 root root 10 Jan 13 15:52 fe1bed3c-ecc7-4288-bbee-5ab7477a6ea1 -> ../../sda7

b1987f34-0b69-494c-9041-5d2fc12e9675 is /dev/sda6 in 42.1 and /dev/sda9 in 42.3 installation environment. Why? Maybe this is the problem?

hcvv · January 14, 2018, 12:00pm

Yes, very strange. What is the usage of sda9? also. can we check if it is detected in 42.2:

ls -l /dev/disk/by-* | grep sda9

mse1 · January 14, 2018, 12:20pm

“/dev/sda9” in 42.1 is a btrfs device for “/” which has been added recently, please see screenshot.
http://mseide-msegui.sourceforge.net/pics/partition.png

hcvv · January 14, 2018, 12:52pm

So you have two partitions used for the same purpose. Is sda9 in use for some system?

In any case, it seems that the installer sometimes detects sda6 as contains the / file system of the system you want to upgrade and sometimes thinks that sda9 contains it.

I assume you must admit that on inspection from outside it is difficult for a human being which partitions are in fact used for your current 42.2 and which partitions looks very much as belonging to the system, but isn’t. You created some fog I think.

Nevertheless, choosing the one during one phase of the installation and the other in another phase is not quite correct and maybe worth a bug report.

mse1 · January 14, 2018, 1:17pm

As written before it is a part of the btrfs cluster.

arvidjaar · January 14, 2018, 1:21pm

This is absolutely unclear. Your 42.1 already has root; what “device for “/”” means exactly? “/” of what? How it has been added? Which commands you used to “add” it?

Show output of “EVALUATE=scan blkid” from 42.1 and 42.3.

mse1 · January 14, 2018, 1:36pm

IIRC “btrfs device add /dev/sda9 /”

Show output of “EVALUATE=scan blkid” from 42.1 and 42.3.

What does this? I do not like to run commands as root I don’t understand…