I currently have the following configuration:

  • 1 SSD of 128 GB containing Solus and Windows,
  • 1 HDD of 1 TB containing my personal documents.

I plan to replace my SSD, because it becomes difficult for me to manage the 2 operating systems, due to lack of space.
I would therefore need answers to some questions, thanking you in advance for enlightening me.

First of all, is it a good idea to clone the current SSD to the new one, and if so, which Linux application is recommended for this operation?
Or is it better to perform a new installation of each operating system?

Should I first install Windows before Solus (and if so, why?) or does it not matter? (for information, last time, I had first installed Solus before Windows)

Also, when installing Solus, should I place the swap on the SDD or rather on the HDD? (I had opted for the second choice, after reading a post on a forum on the web).

Looking forward to reading your feedback,
Thanks by advance.

    penny-farthing First of all, is it a good idea to clone the current SSD to the new one, and if so, which Linux application is recommended for this operation?

    It's been years since I've cloned anything, but I seem to remember the name CloneZilla. I do recall that the software I used was very straightforward and easy to use.

    penny-farthing Should I first install Windows before Solus (and if so, why?) or does it not matter?

    If you installed Windows last, I'm surprised it worked for you. I don't do dual boots (I prefer creating a virtual machine for the less important OS), but I remember seeing many forum posts complaining that Windows took over the entire dissk and the Linux distro need to be re-installeed afterwards. If you go that route, I'd install Windows first.

    penny-farthing Also, when installing Solus, should I place the swap on the SDD or rather on the HDD? (I had opted for the second choice, after reading a post on a forum on the web).

    I'd put it on the SSD. The difference in speed is significant, as you already know, and swapping large sections of memory slowly would be quite a distraction as you work with the computer. In fact, SSDs are so inexpensive these days, why not just get one more and clone the HDD to it?

      WetGeek

      Thanks for your feedback, it is always appreciated.

      Does the fact that you have not cloned anything for a long time mean that you prefer to reinstall the system?
      It is true that if cloning (when everything goes well) allows you to find your system in the same state as on the old hard drive, the advantage of re-installation gives you a clean and operational system (of course, you will have to reinstall the missing applications afterwards).

      I also note to favor the installation of Windows before Solus.
      However, it is true that by not having done the same, I have not encountered any particular problem with Windows. In addition, recently, to be able to give a little more space to Solus, I cut down on the Windows one with the help of GParted and it is going rather well so far.

      I know your position on the use of Windows in VirtualBox that I understand.
      However, on several occasions on Solus, I encountered cases where I simply couldn't remove the volume or eject an external hard disk, because it was occupied by the system. Rebooting to Windows enabled me to perform this operation successfully.

      Finally, I also intend to eventually acquire an SDD to replace the HDD, but my budget is limited, I must be patient...

        penny-farthing Does the fact that you have not cloned anything for a long time mean that you prefer to reinstall the system?

        Not necessarily. It's been so long that I no longer remember what caused me to do that. You're right about the main differences between a clone and a fresh install. The clone is a bytewise copy of the source, resulting in a destination that may have some or all the same problems the original did, but simply more unused space.

        There's something very satisfying about doing a fresh install of the system. That's been true for me, even when it was an accumulation of errors that made it necessary. I usually implement structural changes that would have been too much work to apply to a working system (like a larger swap paartition to allow hibernating) but are trivial when a new system is created. In my experience, there are always a few things I'd like to do differently when I reinstall a system.

        penny-farthing However, it is true that by not having done the same, I have not encountered any particular problem with Windows.

        Keep in mind that methods of dual-booting have changed a lot over the decades, as computer components and peripherals have evolved. It's entirely possible that it's no longer an issue with modern equipment and practices. Windows used to be a greedy beast.

        penny-farthing I know your position on the use of Windows in VirtualBox that I understand.

        Then please also understand that I'm not trying to make a convert of you. I made that comment only to explain why I'm not more conversant regarding modern dual booting. I simply prefer not to do it. For the most part, I have no need for Windows anymore, although nearly my whole career was spent creating enterprise Windows software. Even then, Windows was only on my computers at the office, and Linux only on my computers at home. And being retired, I no longer need the Windows computers.

        I still have one computer at home that runs Windows to stream content to my TV, but it's not because Windows is any better for that task. It's because Windows came on that machine when I bought it, and the only application I ever run on it is Vivaldi, which syncs with Vivaldi on all my Linux machines. It's not worth the time and trouble to chaange the OS. It ain't broke, so I ain't fixed it..

          WetGeek Keep in mind that methods of dual-booting have changed a lot over the decades, as computer components and peripherals have evolved. It's entirely possible that it's no longer an issue with modern equipment and practices. Windows used to be a greedy beast.

          It is still the same.
          If you install linux first windows will overwrite the boot manager.
          Ive tried that dozen times on client PCs in the last decade.

          Evenso i prefer cloning the discs.
          You just must replace the original drive after cloning, otherwise you`ll get a duplicate UUID.
          Clonezilla is a good tool for this.

            MikeK61 It is still the same.

            I'm curious how it worked for @penny-farthing then, but I'm not going to lose any sleep over it.

            And I finally remembered why I cloned disks such a long time ago. It was so I could install bigger disks into some computers without needing to reinstall the OS, all the applications, and duplicate all the data I'd accumulated. I suspect it was about the time that I replaced some 256 MB drives with bigger ones. It was before I had an NAS to handle data storage, so individual drives tended to get stuffed full and need to be replaced.

            I could clone a 256 MB disk to a 512 MB disk, and suddenly I had lots more room available, but all the original content was there, and the new disk actually booted just like the original. Then I could clean up the original disks and offer them to friends..

              As WetGeek noted, SSDs are cheap these days, so if you have a free connector, I recommend buying a second SSD and installing Solus and Windows on separate drives. In my opinion, even a SATA SSD is very fast as a boot drive, and 500 Gig SSDs go for about 25 bones last time I looked. Having a whole drive formatted with not-NTFS can also be useful. For example: Wine and Proton don't always function well (or at all) with programs on a drive formatted with NTFS.

                WetGeek

                penny-farthing I know your position on the use of Windows in VirtualBox that I understand.

                Then please also understand that I'm not trying to make a convert of you. I made that comment only to explain why I'm not more conversant regarding modern dual booting. I simply prefer not to do it.

                Don't be afraid.
                Your comments often have an educational character: you explain your point of view, based on your personal and professional experience, without seeking to influence your interlocutor and that is how I understood it.

                WetGeek

                I'm curious how it worked for @penny-farthing then, but I'm not going to lose any sleep over it.

                After installing Solus, I downloaded the Windows ISO image to a USB key using Rufus and installed it on the remaining space on my SSD. The installation went without any problem, as did the Windows management afterwards. I can't say anything more.

                Teggs

                Thank you for your comments.

                That said, I particularly want to install my personal documents on a specific SDD, because this allows them to be protected from a re-installation of Solus (even if of course, I should always plan a backup on an external hard disk).

                As for Windows, I use it more as a troubleshooter to handle certain situations (internet service provider requirements, personal incidents such as the one mentioned above, GPS updates).

                8 days later

                So I opted for a Windows installation, then Solus on the new SSD that I recently acquired, rather than a clone.

                It went well, but when I typed sudo eopkg check in terminal, it found me 3 errors:

                • one on the cups-browsed package
                  Vérification de l'intégrité de cups-browsed Cassé
                  Fichier manquant : usr/lib/systemd/system/cups-browsed.service
                  Fichier manquant : usr/lib/systemd/system/multi-user.target.wants/cups-browsed.service

                • another on the appamor package
                  Vérification de l'intégrité de apparmor Cassé
                  Fichier manquant : lib64/apparmor/apparmor.systemd
                  Fichier manquant : lib64/apparmor/profile-load
                  Fichier manquant : lib64/apparmor/rc.apparmor.functions

                • another finally on the linux-current package
                  Vérification de l'intégrité de linux-current Cassé
                  Fichier corrompu : lib64/modules/6.9.12-297.current/modules.builtin.alias.bin
                  Fichier corrompu : lib64/modules/6.9.12-297.current/modules.builtin.bin
                  Fichier corrompu : lib64/modules/6.9.12-297.current/modules.devname
                  Fichier corrompu : lib64/modules/6.9.12-297.current/modules.softdep

                I know that the last error was part of a problem that the Solus development team has not had time to fix yet.
                But the first 2 were not in anomaly before the change of SSD.

                Not knowing how to fix these issues, any help or advice is welcome.

                Waiting for your feedback,
                Thanks.

                I get the latter two, as well. No idea about the first one. I've been told that the apparmor and linux-current errors are false, and can be ignored. Perpahs that applies to the first one, too?

                I'm happy that your installation went well. Don't worry about those "errors" as long as everything is working okay.

                After installation, I typed the command bootctl status | grep "Secure Boot" which returned the following message:
                systemd-boot not installed in ESP. Secure Boot: enabled (user)

                I specify that when installing Solus on my new SSD, I mounted my EFI partition /dev/sdb5 on /boot with the flags boot, esp.

                On the /boot folder, there are currently 3 elements:

                • an EFI folder
                • a loader folder
                • a solus-enroll-me.cer file

                I found a post from 11/15/2022 on the Solus forum where @ReillyBrogan explained in particular that the boot partition is not supposed to be mounted normally:
                https://discuss.getsol.us/d/8981-systemd-boot-boot-parameters-not-updated/10

                Given the latest instructions provided in the Solus help to set up Secure Boot:
                https://help.getsol.us/docs/user/quick-start/installation/secure-boot#enabling-secure-boot-on-an-existing-install
                does this change anything in the way of configuring the boot partition? Do I need to correct things compared to what I did?

                I would like to point out that my configuration is working well so far, but fearing that a future update could disrupt its proper functioning, I prefer to contact somebody who are familiar with these issues.

                Thank you in advance for your feedback.