Bug 955062

Summary:	Tumbleweed Update (from 13.2) 64bit
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Forgotten User 1alVLDdb15 <forgotten_1alVLDdb15>
Component:	YaST2	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None	CC:	forgotten_1alVLDdb15, fvogt, jreidinger
Version:	Current	Flags:	lslezak: needinfo? (forgotten_1alVLDdb15)
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 13.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User 1alVLDdb15 2015-11-14 14:41:48 UTC

Today I updated 2 laptops from 13.2 64 bit (Samsung R60 Plus / Acer Travelmate) to Tumbleweed. 
I used DVD and rejected Net config during installation.

BOTH (!) machines provide the same error after update: They complain about a probable double entry in /etc/fstab  . (I checked out - there's no file sytem twice).
On the acer the machine doesn't stop probably because of that (watchdog is running :-(  ).

The Samsung provides additionally a boot problem:
When Installing there was an Install error. The machine takes a long time to boot  (I use LXDE) and 
the kernel configuration under yast2 ist not startable.
Here I am told to report this bug and send the log files.  
Internal Error Details: Unknown  udev device /dev/disk/by-id/wwn-0x50014ee2aed97914
Caller: /usr/share/YASt2/lib/bootloader/udev_mapping.rb:42:in `to_kernel_device´.
(I would be nice to copy that message- One has to type it -why?) 
Which log files are meannt?

I nearly forgot:
On the Acer there is a double double bootsector entry in GRUB2 of TW.. 
There's only a suse system on it. 
The samsung has a parallel Windows system behind the suse. This entry seems to be correct.

I hope the 3rd installation on my 32bit old nc4000 works better!

Comment 1 Forgotten User 1alVLDdb15 2015-11-14 14:45:59 UTC

Internal error. Please report a bug report with logs.                         │
│Details: Unknown udev device /dev/disk/by-id/wwn-0x50014ee2aed97914           │
│Caller:  /usr/share/YaST2/lib/bootloader/udev_mapping.rb:42:in `to_kernel_devi│


copied out of yast (not yast2)

Comment 2 Josef Reidinger 2015-11-19 15:15:33 UTC

wwn problem is handled in bug#949796

Comment 3 Forgotten User 1alVLDdb15 2015-11-19 18:24:03 UTC

see also bug 
https://bugzilla.suse.com/show_bug.cgi?id=902385 - they seem to be connected.

Comment 4 Ladislav Slezák 2015-11-20 16:09:30 UTC

Please, attach Yast logs to check the "double entry in /etc/fstab" issue.

Comment 5 Forgotten User 1alVLDdb15 2015-11-20 16:20:23 UTC

Please goto the Bug of Comment#3 - already available.

Comment 6 Ladislav Slezák 2015-11-20 17:12:57 UTC

I checked the logs, but I could not find anything related to any duplicate error. The logs are huge and it's hard to search if I do not know what exactly should I check...

Do you remember the exact error message? Or where did you see it, in which dialog? (A screenshot would be nice in this case, but that's not possible anymore...)

Comment 7 Forgotten User 1alVLDdb15 2015-11-20 19:16:26 UTC

THere's some message about systemd and the next line is with fstab.
"Maybe threre is a double entry in /etc/fstab" or very similar.
Threre ia a boot log file, I don't have in my head how it's called. 
(The log where all boot logs are stored).
Can you please tell me which file it is? 

Double boot entry in Grub is only the acer Laptop.

Comment 8 Josef Reidinger 2015-11-23 09:24:06 UTC

OK, in this case please provide also grub.cfg to check why there is double entries in grub. It should show which generator generate which entries. Then we will see where can be problem. Also please provide your /etc/fstab, as I have suspicious to be relevant to os-prober.

Comment 9 Fabian Vogt 2015-11-24 08:50:08 UTC

AFAICS only the fstab issue in the first message is remaining.

*** This bug has been marked as a duplicate of bug 948771 ***