[Bug 1189003] New: Yast is unable to handle encrypted disk
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 Bug ID: 1189003 Summary: Yast is unable to handle encrypted disk Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs@suse.de Reporter: Ulrich.Windl@rz.uni-regensburg.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 851486 --> http://bugzilla.opensuse.org/attachment.cgi?id=851486&action=edit Screenshot showing problem and details When trying an update or installation, Yast detects an encrypted disk, asks for the password, and unlocks it, but then is unable to continue (see attachment). The device /dev/mapper/cr-auto-1 is there when Yast claims it is not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c1 --- Comment #1 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Created attachment 851487 --> http://bugzilla.opensuse.org/attachment.cgi?id=851487&action=edit Yast Logs -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c3 --- Comment #3 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Arvin Schnell from comment #2)
Please provide the output of 'blkid -c /dev/null' and 'blkid -c /dev/null /dev/sd[ab]' during the attempted installation. If possible also on the previous Leap 15.2 system (assuming you try to update from there).
The easy part (Leap 15.2): util-linux-2.33.1-lp152.5.6.1.x86_64: # blkid -c /dev/null /dev/sd[ab] /dev/sda: TYPE="isw_raid_member" /dev/sdb: TYPE="isw_raid_member" Now the interesting part (Leap 15.3 installation system): Script started on 2021-08-03 17:53:20-04:00 [TERM="linux" TTY="/dev/tty2" COLUMNS="240" LINES="75"] 0:install:/ # blkid -c /dev/null /dev/sda[ab] 0:install:/ # blkid --version blkid from util-linux 2.36.2 (libblkid 2.36.2, 12-Feb-2020) 0:install:/ # exit Script done on 2021-08-03 17:54:01-04:00 [COMMAND_EXIT_CODE="0"] So no output, but why? Using strace: execve("/sbin/blkid", ["blkid", "-c", "/dev/null", "/dev/sda[ab]"], 0x7ffdd50c7f58 /* 32 vars */) = 0 ... lstat("/dev", {st_mode=S_IFDIR|0755, st_size=6180, ...}) = 0 lstat("/dev/sda[ab]", 0x7ffd5becc5b0) = -1 ENOENT (No such file or directory) access("/dev/sda[ab]", F_OK) = -1 ENOENT (No such file or directory) ... +++ exited with 2 +++ That answers what happened: Script started on 2021-08-03 18:02:20-04:00 [TERM="linux" TTY="/dev/tty2" COLUMNS="240" LINES="75"] 0:install:/ # blkid -c /dev/null /dev/sda /dev/sdb /dev/sda: TYPE="isw_raid_member" /dev/sdb: TYPE="isw_raid_member" 0:install:/ # echo $? 0 0:install:/ # blkid /dev/sda /dev/sdb;echo $? /dev/sda: TYPE="isw_raid_member" /dev/sdb: TYPE="isw_raid_member" 0 0:install:/ # exit Script done on 2021-08-03 18:04:06-04:00 [COMMAND_EXIT_CODE="0"] So I think the shell in the installation system might be the problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c4 --- Comment #4 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Created attachment 851508 --> http://bugzilla.opensuse.org/attachment.cgi?id=851508&action=edit Description of UNIX Edition 7 (Shell filename completion) Sorry I could not resist: Edition 7 (that ran on a PDP-11/70) claimed that it would run with "96K bytes of core" while the shell could do filename completion (see text). 40 years later that seems impossible even when using multiple megabytes of RAM ;-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c6 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) | --- Comment #6 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Arvin Schnell from comment #5)
So blkid is able to detect the IMSM. The still open question is whether 'blkid -c /dev/null' reports infos about the disks or the partitions of /dev/sda and /dev/sdb (on Leap 15.2).
Unless you are talking about the Leap 52.2 installation system, I'd disagree: (In reply to Ulrich Windl from comment #3)
The easy part (Leap 15.2): util-linux-2.33.1-lp152.5.6.1.x86_64: # blkid -c /dev/null /dev/sd[ab] /dev/sda: TYPE="isw_raid_member" /dev/sdb: TYPE="isw_raid_member"
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c9 --- Comment #9 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Arvin Schnell from comment #8)
The question from comment #5 is still open: Does 'blkid -c /dev/null' (without providing any devices!) report infos about the disks or the partitions of /dev/sda and /dev/sdb (on Leap 15.2)?
Maybe re-read comment #3 (as indicated in comment #6), specifically the part "Leap 15.2". ;-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c11 --- Comment #11 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Arvin Schnell from comment #10)
Sorry, I do not understand what you are trying to tell me. I value it as NORESPONSE.
Well, you could have been more explicit: So it seems I forgot to leave out the disk names? I thought (as the other (two) disks are not involved (they are not encrypted)) they would play no role. Do you want to see the IDs of partitions, LVs, etc.? Or do you want to see the other two disks? Of course the decrypted disks in the running system are not named like /dev/mapper/cr-auto-1. If you'd share your thought a bit more verbosely, it would be easier for me to provide the information you need. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c12 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #12 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Created attachment 853688 --> http://bugzilla.opensuse.org/attachment.cgi?id=853688&action=edit Archive with screenshots documenting the failed upgrade attempt I retried the upgrade yesterday, and I came to the conclusion that YaST is telling nonsense: First it says /dev/mapper/cr-auto-1 is missing, but "dmsetup ls" lists it (console in the installation system at the moment when the error is being displayed). Next I verified that the device file is there and that the VG and LVs are there, while yast claims the VG "/dev/system" would be incomplete and PVs would be missing. I checked the PV and the VG without any issues, however (still in a console of the installation system). If I continue despite of the non-errors, no system is displayed for upgrading. As there was a refreshed installation system, I downloaded that and retried: The result is just the same. Remark: As it was decided that an auto-upgrade for the installation system (as available in SLES) is not necessary, it seems I'll have to wait for another three months before I can try again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c13 --- Comment #13 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Created attachment 853689 --> http://bugzilla.opensuse.org/attachment.cgi?id=853689&action=edit Installation system YaST log archive Here are the collected logs of the failed upgrade attempt. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c14 --- Comment #14 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Trying "openSUSE-Leap-15.3-2-DVD-x86_642" did not fix the problem, so I gave up (using the "zypper dup" method). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c15 --- Comment #15 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Created attachment 862845 --> http://bugzilla.opensuse.org/attachment.cgi?id=862845&action=edit Archived Yast logs from failed upgrade attempt Same problem for Leap 15.4; should I open a new bug? I guess it's simply not fixed. How sad! The hardware and disk layout is still the same. When Yast had reported a problem with the system VG, I escaped to a terminal: The VG is there, the LVs are all there, and vgck does not report any error. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c16 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|NORESPONSE |--- --- Comment #16 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Same problem, still not fixed! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189003 http://bugzilla.opensuse.org/show_bug.cgi?id=1189003#c19 --- Comment #19 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Arvin Schnell from comment #18)
(In reply to Ulrich Windl from comment #3)
0:install:/ # blkid -c /dev/null /dev/sda[ab]
Apparently a simple typo. Nothing more.
Agreed, I overlooked that, but still the problem is there. (In reply to Arvin Schnell from comment #17)
Seems to be the same problem as bug #1190969.
Maybe, but I only get "You are not authorized to access bug #1190969." -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com