[Bug 1101979] New: openSUSE Tumbleweed network installer fails (snapshot 14-07-2018)
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979 Bug ID: 1101979 Summary: openSUSE Tumbleweed network installer fails (snapshot 14-07-2018) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: fmbernardo@live.com.pt QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 777536 --> http://bugzilla.opensuse.org/attachment.cgi?id=777536&action=edit Includes dmesg, hwinfo, /var/log/messages and y2logs.tgz. After accepting the terms of license and choosing the desired desktop, the network installer fails with the following messages. «Details: storage::Exception Caller: /mounts/mp_0001/usr/share/YaST2/lib/y2storage/storage_class_wrapper.rb:260:in`detect_content_info`» «Calling the Yast module 'inst_disk_proposal has failed. More information can be found near the end of the 'var/log/Yast2/y2log' file.» Relevant logs (including dmesg, hwinfo, /var/log/messages and y2logs.tgz) and screenshots are attached. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c1
--- Comment #1 from Filipe Bernardo
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c2
--- Comment #2 from Filipe Bernardo
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c3
--- Comment #3 from Filipe Bernardo
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c4
--- Comment #4 from Filipe Bernardo
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c5
--- Comment #5 from Filipe Bernardo
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c6
Filipe Bernardo
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c7
Richard Brown
2018-07-20 00:38:01 <3> install(4507) [libstorage] SystemCmd.cc:97 mount: /tmp/libstorage-Ipmikv/tmp-mount-YQuvvH: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
storage-inst/01-probed.yml suggests that sda2 is an ext4 partition of 16MiB in size, with an id: microsoft_reserved This sounds very confusing, why would an ext4 partition be so small and with an id that implies a relation to a windows installation? Can you provide any light onto this? What would you expect that 16MiB partition on your system to be? What filesystem would you expect it to already be? I'm asking to try and get more info to help the YaST team identifiy whether this bug is a problem with their detection (did it incorrectly identify the file_system for sda2?) or with insufficient handling of a very bizarre problem with your unusual/broken disk layout. Please reply to this question and choose the tickbox to clear the NEEDINFO request when you do Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c8
Filipe Bernardo
Logs show the following
2018-07-20 00:38:01 <3> install(4507) [libstorage] SystemCmd.cc:97 mount: /tmp/libstorage-Ipmikv/tmp-mount-YQuvvH: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
storage-inst/01-probed.yml suggests that sda2 is an ext4 partition of 16MiB in size, with an id: microsoft_reserved
This sounds very confusing, why would an ext4 partition be so small and with an id that implies a relation to a windows installation?
Can you provide any light onto this? What would you expect that 16MiB partition on your system to be? What filesystem would you expect it to already be?
I'm asking to try and get more info to help the YaST team identifiy whether this bug is a problem with their detection (did it incorrectly identify the file_system for sda2?) or with insufficient handling of a very bizarre problem with your unusual/broken disk layout.
Please reply to this question and choose the tickbox to clear the NEEDINFO request when you do
Thanks!
Thank you for reaching out. Yes that's correct, there's a ext4 formatted partition of 16 MiB in size and with id microsoft reserved partition. I confirm Yast did detect correctly the partition filesystem. And yes, it's odd that this partition is formatted as ext4. Today I successfully installed Tumbleweed on another laptop I had access to. I used the same network installer and the same USB pendrive. On this other laptop, the Microsoft reserved partition is formatted as NTFS rather than ext4. I will attach both disk partition layouts for comparison. If I recall correctly, this ext4 partition was created a year ago when I made a clean Windows install on this disk (instead of restoring from the OEM image). I remember Windows 10 complaining and requiring the existence of such a "Microsoft reserved partition" on the disk for successful installation, which after googling for a while, I proceeded to create. It's likely that I created this partition using GParted on a Live USB system and chose ext4 arbitrarily, since as far as I can remember, because the actual filesystem of this partition did not matter for Windows 10, just its existence of the disk. In the meantime, I did at least once successful Tumbleweed installation on this same disk with the same partition layout, and also of at least two other different Linux distributions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c9
--- Comment #9 from Filipe Bernardo
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979
http://bugzilla.opensuse.org/show_bug.cgi?id=1101979#c10
--- Comment #10 from Filipe Bernardo
participants (1)
-
bugzilla_noreply@novell.com