Bugzilla – Bug 955962
SD card not properly partitioned/formatted
Last modified: 2018-04-13 15:02:55 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 Build Identifier: When using yast to partition an sd card, when it is at the partitioning stage for a fat partition, it will simply quit, whether in window or terminal mode, with no errors show. Reproducible: Always
Was the SD card partitioned in the end? Or did YaST crash earlier, before or during the partitioning? Please attach YaST logs, see https://en.opensuse.org/Bugs/YaST
Created attachment 656852 [details] y2
I found two format attempts in the YaST logs, both were successful: 2015-11-19 22:59:04 <1> compy(18398) [libstorage] SystemCmd.cc(execute):134 SystemCmd Executing: "/sbin/mkdosfs -F32 '/dev/sdc1'" 2015-11-19 22:59:05 <1> compy(18398) [libstorage] SystemCmd.cc(addLine):656 Adding Line 1 "mkfs.fat 3.0.26 (2014-03-07)" 2015-11-19 22:59:05 <1> compy(18398) [libstorage] SystemCmd.cc(getUntilEOF):622 pid:18675 added lines:1 stderr:false 2015-11-19 22:59:06 <1> compy(18398) [libstorage] SystemCmd.cc(doExecute):336 stopwatch 2.198643s for "/sbin/mkdosfs -F32 '/dev/sdc1'" 2015-11-19 22:59:06 <1> compy(18398) [libstorage] SystemCmd.cc(doExecute):356 system() Returns:0 2015-11-19 22:59:04 <1> compy(18398) [libstorage] SystemCmd.cc(execute):134 SystemCmd Executing: "/sbin/mkdosfs -F32 '/dev/sdc1'" 2015-11-19 22:59:05 <1> compy(18398) [libstorage] SystemCmd.cc(addLine):656 Adding Line 1 "mkfs.fat 3.0.26 (2014-03-07)" 2015-11-19 22:59:05 <1> compy(18398) [libstorage] SystemCmd.cc(getUntilEOF):622 pid:18675 added lines:1 stderr:false 2015-11-19 22:59:06 <1> compy(18398) [libstorage] SystemCmd.cc(doExecute):336 stopwatch 2.198643s for "/sbin/mkdosfs -F32 '/dev/sdc1'" 2015-11-19 22:59:06 <1> compy(18398) [libstorage] SystemCmd.cc(doExecute):356 system() Returns:0 As you can see in both cases formatting was quick (finished in about 2 seconds), but successful so no error was displayed. For me it looks OK, no bug actually.
Then why does it not give a job finished message? Is simply quitting expected behaviour for finishing a partition job?
Arvin - does partitioner provide some finish message when done with formatting? ( so we know it is improvement to show it or bug that something do not work )
No, the partitioner does not provide an annoying final message.
Reading the comments, looks like this is the expected behavior and there are no plans to change it by the developer. So, closing it again.
The usb stick I was partitioning doesn't mount after partitioning it with yast.
Plus, when yast is so unstable that it quits when trying to install software, or when resizing it, maybe a success/error message is a good thing when dealing with something as important as disk partitions. After all, even installing software with yast gives a success/error message, so why is this inconsistency expected behaviour?
Well, the usual Unix/Linux behavior is that if the requested operation succeeds the nothing is reported, it's expected that the request will usually succeed and thus do not annoy user with useless messages. Only errors are reported. That means they are easily visible (not hidden in a pile of success messages). The reason for the package installation summary is that some people want to continue with installing more packages. The other group of people wants to always quit and some prefer a summary dialog. For that reason I created a summary dialog where you can change the default behavior (install more packages, quit, or display the summary). Personally I do not like this solution much and I'd prefer quiet exit at the end by default (restart is pretty quick) and I would not like to expand this summary dialog beyond package management...
(In reply to ill lume from comment #8) > The usb stick I was partitioning doesn't mount after partitioning it with > yast. Could you add more details? The automount does not work? Or even manual mount does not work? Any error printed my "mount" command?
I think kde partition manager, gparted, and most other partion managers will tell you when it is successful or failed. That seems to be standard for gui programs. Could you add more details? It said something about special device not existing. The error stopped after I used gparted instead to partition it.
So finally it looks like there was indeed an error in the partitioning/formating, according to the reporter. Adding the bug to the YaST Team's Scrum queue, for it to be prioritized in relation to other tasks.
Please notice that depending on what desktop environment you are using, some media management applet might or might not automatically mount the SD card. For some operations it's also common that the SD card disappears for the kernel, so sometimes it's necessary to remove it from the reader and re-insert it. Did you try that? Was the non-mounting a one time event, or can it not be mounted any more at all? If it can't be mounted any more at all: Are there any errors in the kernel log? (check with "journalctl").
This might be something for the YaST community to pick up if anybody is willing to invest the time. Reassigning.
This is automated batch bugzilla cleanup. The openSUSE 42.1 changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or you can still observe it under openSUSE Leap 15.0, please feel free to reopen this bug against that version (see the "Version" component in the bug fields), or alternatively open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime