On 30/12/2021 21.59, Bob Rogers wrote:
From: Per Jessen <> Date: Thu, 30 Dec 2021 20:25:13 +0100
Carlos E. R. wrote:
. . .
>>> this is intentional. It also says "load module with >>> allow_unsupported=1 to enable read-write mode", but I don't know the >>> consequences of doing that. The laptop might explode or eat my >>> kittens. >>> >> >> Well, so do not. It is your decision. > > No documentation.
With or without documentation, your laptop might still explode or eat your kittens. But I agree, a list of which options are being enabled by "allow_unsupported=1" would be useful.
My guess is that the 15.3 kernel module just replaces the rw functionality with that message by default, and "allow_unsupported=1" just re-enables the original code. No new kitten-eating mode would have been implemented. ;-}
I still do not know if the option has to be given for this module only (and how, what config file), or is it global, option given on boot to kernel.
BTW, this is a good example of why I always do a fresh install in a new partition when upgrading, rather than "zypper dup"; it allows me to fall back on the existing installation if I have issues with the new one, or it takes me longer than I expect to configure and install my software and customizations. As the openSUSE sysadmin and fixit dude for almost 20 years at a company with a minimal hardware budget, I did many system upgrades on older hardware, including a number of Frankenstein models, and had to play it very safe. (Whether or not "zypper dup" actually applies in this case.)
I would still hit the same basic problem: the data partitions would be there, inaccessible. Yes, I can revert to the previous install, I have a full backup (both image and rsync files of the root partition, and rsync of the home partition). -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)