Installation in Multidrive Environment

Hello,

I do have a question or rather a comment. I have been trying to install openSUSE LEAP 42.1 with a friend, on a multidrive and multiOS environment. There exist several harddisks and several different OS.

During installation, even with expert partitioner, the installer wanted to override the settings, messing around with the other OS’s disks and partitions. Now, since I plan on using Leap mainly for business clients, who might use multi drives and OS, this is of great importance. Now, I am running it fine on a single HDD System, with several partitions but without any other OS and it works like a charm and install was very and straight forward.

I wonder, if this was an user issue, as of we simply did not see the appropriate option, or if this is maybe an issue with LEAP and how it handles multiple drives. After the installation, there was another issue. Using the sofware manager, there was a diskspace warning for an sda partition, though it had sufficient diskspace available but was part of another OS. I finally fount out, that a label with whitespaces New OS later caused the false alert. Changing the label to NEW_OS_LATER alongside with the mount point, did fix the error. However, bow there is another issue:

If we start package manager from within YaST Control Center it works fine and no errors. Same goes for the terminal version of YaST. However, if we click on add / remove software in the Xface System Settings Window, the package manager starts up, loads the files but then terminates with the error message:

Package not found on media %F

The error shows exclusively when attempting to open Software Management from the Xfce System Settings. From Console and from within YaST it works fine. While this is surely a work around, I am curious about this as well and about a possible fix.

Please let me know what you think as well as any ideas you might have.

Cheers,

Ben

Hi
In the partition section, select expert partitioner and the hit the rescan disk button to leave everything alone, then go up and select the disks and create partitons on disks as required. You would also on the final summary page review the bootloader installation to ensure you configure as required.

If a UEFI install, then you could create additional esp’s on individual disk’s, but probably have to do some foo with efibootmgr after the install. Else use one esp and just ensure it’s probably bigger than the default of 260MB.

By default, the install medium is left enabled, just disable it and all should be fine.

Can you elaborate on the “messing around with other OS’es …” part?

Sure. In this case we have been installing it on its own dedicated hard-drive. On the machine exist several other Linux Distros, each having its own dedicated hard-drive as well.
During install, we set up the dedicated HDD for openSUSE, give it all the partitions needed (both of us, who did the install, are IT professionals with our own IT business, getting people on Linux on a frequent base). After accepting the changes, and clicking on continue, etc. the installer kept changing the set partitions, insisting and creating the swap drive on a different HDD; used by another Linux Distro. It took quite some time to have it accept the desired setting without making changes.

On the other hand, I run it on a single boot system and as the sole OS and I had no problems at all during the installation. In fact - as I said - it was very smooth and easy. So I suppose, that maybe the issue is with the multiple HDDs and OS on the machine. Maybe openSUSE does not handle such a setup well or we just missed something during the install, in order to solve it.

As for the other issue: The DVD is disabled as the repo but the error of “Package not found on media %F” persists. The error occurred after changing the label of a different HDD, to remove white spaces. The HDD changed is not part of the openSUSE installation nor used by it. Also, as I said, if we attempt to run the package manager from YaST, it works fine. No error and it does work as intended. However, if we open xfce Settings, there is also an option to Install / Remove Software. Clicking on it does open the YaST Package manager, it loads all the repos and information and just when it is about done, said error appears and it closes. Using “yast” in the command line, does start the console version of YaST, also without any issues.

So there are two things I am curious about:

  1. Is there a way to make the install easier on a multi boot environment (or is there something I missed during the install)
  2. How to I get rid of that error in Software Manager and why is it there the first place. Given that both Links open the same program, I am baffled as for why from within YaST it works but from the Xfce System Settings it does not.

We have been disabling and reenabling the repos, inserted the install medium, updated the repos, updated all software installed, made a zypper dup and reviewed the settings to no avail. As I said, we had planned to use openSUSE as preffered OS for our customers (right now we are working a lot with Debian and Ubuntu but openSUSE has several advantages over that).

With complex installs you must take control using expert mode. Any installer can not read you mind you need to tell it exactly what you want. I have always found that when given my setup wishes it does it.

The other problem we need more detail to understand it.

As I mentioned, We DID use expert mode. I always use expert mode to install and to set partitions as I want.

All information about the other issue is in the two posts. There was not much information to get. I try to start Software Manager from the Xfce Settings menu: Error I start it from within YaST and it works. All I know is that the issue started after changing the label of an unrelated HDD, that used white spaces.

On Mon 01 Aug 2016 01:36:02 PM CDT, bbuske wrote:

As I mentioned, We DID use expert mode. I always use expert mode to
install and to set partitions as I want.

All information about the other issue is in the two posts. There was not
much information to get. I try to start Software Manager from the Xfce
Settings menu: Error I start it from within YaST and it works. All I
know is that the issue started after changing the label of an unrelated
HDD, that used white spaces.

Hi
I wonder if it’s an issue with the xfce menu entry (aka desktop file)
and maybe tied to xdg-su or similar.

Maybe you could identify the specific launcher xfce uses for YaST2, it
should be /usr/share/applications/yast2-packager.desktop?

If you open a terminal and run;


xdg-su -c "/sbin/yast2 sw_single %F"

Does it launch properly?


Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.27-27-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

Well, not really a multi-drive environment comment here, but a multi-boot enviro on an enterprise system running win10pro/server 2k12. I installed Leap 42.1 on this(well, the boss’))I don’t think he’s ready for SUNN/SPARC) ASUS/AMD rig and it was freakin’ fantastic.:slight_smile: Not only did it install first time, even all the codecs came in for basic multimedia playback for the boss. Some one’s doing their job and the boss who HATES all computers anyway just loves it, and I gotta admit I like it, too. No problems with the enterprise corporate stuff and and I can’t wait to get my new Wild dog Pro System 76 rig online with Leap. Windoze is out of there for good. kinda like saying goodbye to BASIC, although my buds over at NASA still uses it for multimillion mile comms and data telemtery. See you guys later when I have a hair puller popup again.rotfl!

J.Williams
Fernandina Fl.
Htos A/V Data systems

Hello, sorry fpr the late reply, but I did not have a chance to get on that machine before. It is not mine, but a friend’s one. Here is the output of the command: xdg-su -c “/sbin/yast2 sw_single %F” (gnomesu:2761): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn’t be used anymore. It will be removed in a future version. (gnomesu:2761): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn’t be used anymore. It will be removed in a future version. (gnomesu:2761): Gtk-WARNING **: gtk_window_set_titlebar() called on a realized window Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. YaST got signal 11 at file /usr/share/YaST2/modules/Popup.rb:961 sender PID: 0 /sbin/yast2: line 440: 2790 Segmentation fault $ybindir/y2base $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS Any ideas?

Sorry for the late reply and I have just noticed the mess, the prior post has been.

xdg-su -c “/sbin/yast2 sw_single %F”

(gnomesu:2761): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn’t be used anymore. It will be removed in a future version.
(gnomesu:2761): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn’t be used anymore. It will be removed in a future version. (gnomesu:2761): Gtk-WARNING **: gtk_window_set_titlebar() called on a realized window Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
YaST got signal 11 at file /usr/share/YaST2/modules/Popup.rb:961 sender PID: 0 /sbin/yast2: line 440: 2790 Segmentation fault $ybindir/y2base $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS

Any ideas?

Use code tags to stop the editor here from formatting the text. (# in tool bar)

Thanks for the note… I shall try that next time. Can’t edit that post.