Hi,

During updating Solus today (113 packages, 1,62 GiB), my system displayed an alert message telling me "Low hard disk space". Fortunately, I was able to finish this update and rebooted my computer without any problem.

This is due to originally, I planned 42 Go to install Solus Budgie and it had to be enough at this time. I must specify that my computer has 2 hard drives: 1 SSD (128 Go) to manage operating systems and 1 HDD (1 To) to manage personal data. But over time, it turned out to be insufficient and during today's update, my Solus partition went from 6.9 Go to 1.2 Go to finish more than 5 Go.

On this SDD coexist Solus and Windows managed in dual-boot.
(I specify that Windows is installed on my computer, because my internet service provider requires it to help me remotely in the event of a problem).
So I had the idea of take 10 Go from Windows to assign them to Solus and I successfully carried out this operation with the GParted application used on a USB key containing the ISO image of Solus 4.5 (it was not easy, because the partition containing the data in Windows was not contiguous with Solus).

However, when checking if Windows was operational (after pressing F12 when I start the PC), I noticed a line indicating "Solus Linux Bootloader - Drive not present".
What's more, Windows tells me "Option not available" in the defrag tool for the SSD, which wasn't the case before.
After research in the Solus help center, I found and typed this terminal command:
sudo clr-boot-manager update
thinking that this could resolve this anomaly.
In fact, this has generated a new entry of the same type in the BIOS:
https://0.0g.gg/?23bd5dd7e46b254c#4DQtn3wc1aLJzAPVx37dbJ9WirAjoGi4GqJhiLWxthdw

What can I do else?
Any help would be appreciated, thank you in advance.

  • Patrice

    I thought about your analysis and here's what I did to fix this problem.

    I simply deleted the Windows partitions and reinstalled Windows 10 and now here's the result:

    The defragmentation on Windows is working again and the partition dedicated to Solus now has more space (51.77 Go instead of 42 Go before).

    Thanks for helping me find the solution.
    Cheers!

    To complete this post:

    • GParted before my changes:

    • GParted after my changes:

    I noticed something: the letter of the devices changes randomly, whether in GParted or in Disks (for example, sda becomes sdb and vice versa), is this normal?

    Salut @penny-farthing ,
    I don't know if you can still access your OS (Solus or Windows). I would first try to access it
    using https://www.supergrubdisk.org/ on a USB key, and see if there are things you can do once
    in the OS.
    If unable to sort out your problem, I would recommand to save your data and re install your both systems properly.
    I know it sounds extreme as a solution but everytime I had these types of issues, it was a mess to correct.
    I hope someone will be able to help you more with that.
    Bonne chance.

      Patrice

      Thanks for your feedback.

      To answer to your question, yes, I manage to access both Solus and Windows, it's just that I noticed this line:
      "Solus Linux Bootloader - Drive not present"
      at PC startup after pressing F12, which I hadn't seen before.

      I specify that the dual-boot is not managed by Grub on my computer.

        6 days later

        Patrice

        I thought about your analysis and here's what I did to fix this problem.

        I simply deleted the Windows partitions and reinstalled Windows 10 and now here's the result:

        The defragmentation on Windows is working again and the partition dedicated to Solus now has more space (51.77 Go instead of 42 Go before).

        Thanks for helping me find the solution.
        Cheers!