[opensuse-support] YaST "boot loader" module error

newer
[opensuse-support] zypper search...

older
[opensuse-support] What happened...

Carlos E. R.

25 Jan 2019 25 Jan '19

13:19

Hi, I get a popup (paste fails, hand copy): Probing LUKS failed Unexpected situation found in the system. Click below to see more details (English only) Continue despite the error [continue][abort][details] Details gives another popup: command '/sbin/udevadm info '/dev/disk/by-uuid/39334baa-94...." failed: stderr: Unknown device, --name=, --path=, or absolute path in /dev/ or /sys expected. exit code: 4 Ideas? (I do have the save_y2logs output to report a bug) There is no /dev/disk/by-uuid/39334ba*, it corresponds to a disk that is not currently connected: cer@Telcontar:~> grep 39334ba /etc/crypttab cr_OldDatum /dev/disk/by-uuid/39334baa-941f-42ab-a0a4-7c20a427aff2 none noauto cer@Telcontar:~> cer@Telcontar:~> grep cr_OldDatum /etc/fstab /dev/mapper/cr_OldDatum /data/OldDatum xfs noauto,nofail,lazytime 1 5 cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Attachments:

signature.asc (application/pgp-signature — 195 bytes)

Show replies by date

Andrei Borzenkov

25 Jan 25 Jan

17:24

New subject: [opensuse-support] Re: YaST "boot loader" module error

25.01.2019 16:19, Carlos E. R. пишет:

...

Hi,

I get a popup (paste fails, hand copy):

Probing LUKS failed Unexpected situation found in the system. Click below to see more details (English only) Continue despite the error [continue][abort][details]

Details gives another popup:

command '/sbin/udevadm info '/dev/disk/by-uuid/39334baa-94...." failed:

Does the same command work if run from command line?

...

stderr: Unknown device, --name=, --path=, or absolute path in /dev/ or /sys expected.

exit code: 4

Ideas?

(I do have the save_y2logs output to report a bug)

There is no /dev/disk/by-uuid/39334ba*, it corresponds to a disk that is not currently connected:

So command failure is expected; open bug report against yast, I do not know what information it needs but probably it should be more permissive here.

...

cer@Telcontar:~> grep 39334ba /etc/crypttab cr_OldDatum /dev/disk/by-uuid/39334baa-941f-42ab-a0a4-7c20a427aff2 none noauto cer@Telcontar:~>

cer@Telcontar:~> grep cr_OldDatum /etc/fstab /dev/mapper/cr_OldDatum /data/OldDatum xfs noauto,nofail,lazytime 1 5 cer@Telcontar:~>

Carlos E. R.

28 Jan 28 Jan

11:55

New subject: [opensuse-support] Re: YaST "boot loader" module error

On 25/01/2019 18.24, Andrei Borzenkov wrote:

...

25.01.2019 16:19, Carlos E. R. пишет:

...
Hi,

...

...
There is no /dev/disk/by-uuid/39334ba*, it corresponds to a disk that is not currently connected:

So command failure is expected; open bug report against yast, I do not know what information it needs but probably it should be more permissive here.

Done. Bug 1123342. Unfortunately, I could not attach the yast logs that the yast people want: The file you are trying to attach is 18404 kilobytes (KB) in size. Attachments cannot be more than 10240 KB. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Freek de Kruijf

12:00

New subject: [opensuse-support] Re: YaST "boot loader" module error

Op maandag 28 januari 2019 12:55:51 CET schreef Carlos E. R.:

...

On 25/01/2019 18.24, Andrei Borzenkov wrote:

...
25.01.2019 16:19, Carlos E. R. пишет:

...
Hi,

...
There is no /dev/disk/by-uuid/39334ba*, it corresponds to a disk that is not currently connected: So command failure is expected; open bug report against yast, I do not know what information it needs but probably it should be more permissive here.

Done. Bug 1123342.

Unfortunately, I could not attach the yast logs that the yast people want:

The file you are trying to attach is 18404 kilobytes (KB) in size. Attachments cannot be more than 10240 KB.

Did you or is the file compressed? If not compress it and attach. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Carlos E. R.

12:08

New subject: [opensuse-support] Re: YaST "boot loader" module error

On 28/01/2019 13.00, Freek de Kruijf wrote:

...

Op maandag 28 januari 2019 12:55:51 CET schreef Carlos E. R.:

...
On 25/01/2019 18.24, Andrei Borzenkov wrote:

...
25.01.2019 16:19, Carlos E. R. пишет:

...
Hi,

...
There is no /dev/disk/by-uuid/39334ba*, it corresponds to a disk that is not currently connected: So command failure is expected; open bug report against yast, I do not know what information it needs but probably it should be more permissive here.

Done. Bug 1123342.

Unfortunately, I could not attach the yast logs that the yast people want:

The file you are trying to attach is 18404 kilobytes (KB) in size. Attachments cannot be more than 10240 KB.

Did you or is the file compressed? If not compress it and attach.

It is a tgz created by save_y2logs, not me. I might expand the archive and edit some log files, then make the archive again. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

Patrick Shanahan

12:59

New subject: [opensuse-support] Re: YaST "boot loader" module error

* Carlos E. R. [01-28-19 07:09]:

...

On 28/01/2019 13.00, Freek de Kruijf wrote:

...
Op maandag 28 januari 2019 12:55:51 CET schreef Carlos E. R.:

...
On 25/01/2019 18.24, Andrei Borzenkov wrote:

...
25.01.2019 16:19, Carlos E. R. пишет:

...
Hi,

...
There is no /dev/disk/by-uuid/39334ba*, it corresponds to a disk that is not currently connected: So command failure is expected; open bug report against yast, I do not know what information it needs but probably it should be more permissive here.

Done. Bug 1123342.

Unfortunately, I could not attach the yast logs that the yast people want:

The file you are trying to attach is 18404 kilobytes (KB) in size. Attachments cannot be more than 10240 KB.

Did you or is the file compressed? If not compress it and attach.

It is a tgz created by save_y2logs, not me.

I might expand the archive and edit some log files, then make the archive again.

or compress with a tighter algorithm. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Carlos E. R.

13:11

New subject: [opensuse-support] Re: YaST "boot loader" module error

On 28/01/2019 13.59, Patrick Shanahan wrote:

...

* Carlos E. R. [01-28-19 07:09]:

...
On 28/01/2019 13.00, Freek de Kruijf wrote:

...
Op maandag 28 januari 2019 12:55:51 CET schreef Carlos E. R.:

...
On 25/01/2019 18.24, Andrei Borzenkov wrote:

...
25.01.2019 16:19, Carlos E. R. пишет:

...
Hi,

...
There is no /dev/disk/by-uuid/39334ba*, it corresponds to a disk that is not currently connected: So command failure is expected; open bug report against yast, I do not know what information it needs but probably it should be more permissive here.

Done. Bug 1123342.

Unfortunately, I could not attach the yast logs that the yast people want:

The file you are trying to attach is 18404 kilobytes (KB) in size. Attachments cannot be more than 10240 KB.

Did you or is the file compressed? If not compress it and attach.

It is a tgz created by save_y2logs, not me.

I might expand the archive and edit some log files, then make the archive again.

or compress with a tighter algorithm.

It is whatever the script uses, written by the yast people. I can recompress, but I have seen that it takes much longer to decode on the other side. I used 7z format to store backups of some tool I use, and recently I needed to recover one: it took an hour or more to do so (78MB compressed). No kidding. And on mSATA. I'm using plain zip now. Anyway, I just edited some logs and removed older ones, and this time upload worked. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1921

Age (days ago)

1924

Last active (days ago)

List overview

Download

6 comments

4 participants

participants (4)

Andrei Borzenkov
Carlos E. R.
Freek de Kruijf
Patrick Shanahan