|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 repair erroneously complains about "no valid root partition found" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Casual J. Programmer <casualprogrammer> |
| Component: | YaST2 | Assignee: | Jiří Suchomel <jsuchome> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aschnell, mvidner |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast2 logs
Screenshot of situation |
||
|
Description
Casual J. Programmer
2008-03-19 08:04:08 UTC
Created attachment 202848 [details]
yast2 logs
Created attachment 202849 [details]
Screenshot of situation
Happened to me too on Alpha 3. I thought that it would help to not run the module for the second time and instead start Expert - Reinstall Bootloader right away, but that only gave me an empty dialog (with lots of nils in the log), so I'll file a new bug. Hm. It might be caused by a wrong check if some device is already mounted. On the installed system (original report), root device is additionally mounted to /mnt. In the second run, yast2-repair tries to check if given partition is mounted using the call Storage::DeviceMounted (root_partition) - however, this call returns only one string (this time "/") although the device is mounted also at "/mnt" Arvin, is there any Storage:: call that returns all active mount points for given device? (I could probably check /etc/mtab, but I'd like to stick to usage of current API) Now there isn't but it should be possible to add on. Not trivial since internal map has to be changed to multimap. I will check and report back. *** Bug 372242 has been marked as a duplicate of this bug. *** Arvin, *ping* :) Sorry, currently to many bugs. Won't have time this week. So, I added a direct check agains /etc/mtab, hopefully this will work. yast2-repair-2.16.11 |