I recently set up Bazzite on my friend's system after switching from Linux Mint due to some Nvidia driver issues. Although the hardware problems are not there anymore, the distro is now facing problems installing certain programs for software development that they had no problem installing in the previous distro. I think there are issues related to the immutability of the distro, though I am not sure since I am new to Linux too. Additionally, my friend is worried about higher storage consumption and slower performance in certain applications.

I realise the distro is primarily meant for gamers and my friend is not much of a gamer themselves, however they told me they appreciate its friendlier KDE interface so I wish to avoid switching from this distro again if possible. However I fear that they may encounter more errors in the future and that I may not be available to help them out whenever needed, so I am in a bit of a conundrum.

Thus I intend to ask here if it is possible to arrange something for easing development related tasks e.g. VM, distrobox etc. or whether it is easier to simply switch to some other compatible distro.

With regard to my previous post, I have run enough diagnosis and checks to determine it is primarily the SSD at fault for the malfunctioning of my homelab. It's recently bought so all of its parts are under warranty, plus the SSD is manufactured by the same brand.

What I am worried about is how the manufacturer is going to diagnose the homelab when it's running Linux. Since the manufacturer is a local brand, I am doubtful whether they have experience working on anything other than Windows, especially since the homelab came preinstalled with it. There could be a possibility that they could outright reject the product from repair. I've checked their warranty policy and does state that warranty will be void under "fault or failure resulting from software or user facilitated minor adjustments and settings", however I cannot say if switching OS comes under this or not.

I wanted to know your thoughts on how I should proceed with preparing the homelab for a warranty claim like this. Should I submit it with the Linux installation intact or replace it a fresh install of Windows just for this case? I've discussed this with one of my friends who is in favour of the latter, though I doubt this approach as well since they could question the fresh install itself.

In case this is needed to be said, getting this repaired under warranty is the only practical option I have. I don't have any spare SSD with me nor I have spare money to buy one and fix it myself. Also I have not tampered with the device in any other way, so I don't think they can reject the warranty claim for any other reason.

cross-posted from: https://sopuli.xyz/post/34381286

I've been having issues with my homelab ever since I set it up a few months ago. For some reason the server becomes unresponsive as if it is online. However when accessing its CLI, it seems to spew out this message in continuity.

I've tried entering commands directly into the CLI, but it shows an 'input/output' error instead. I cannot even get it to shutdown through the CLI so I have to manually pull the plug.

Here's another screenshot of the logs in the CLI a few moments just after the error occurred.

The issue does not even get fixed after I try switching it off and on. Sometimes the homelab gets stuck indefinitely in the startup loading screen, fails to detect the system partition between the GRUB stage, results in a Linux kernel crash or refuses to boot altogether. It is only mitigated when I leave the homelab switched off for 5 minutes or so.

The weird thing about it is that there is no way to predict when this error could come up. The server would work completely unhindered for a few weeks straight on some occasions, and break down just a few minutes after startup. It doesn't depend on what type of services I am hosting, all of which are lightweight in nature.

Additionally, once it does start working again there seems to be no record of the encountered error to be seen in the logs, apart from the number of unsafe shutdowns. This makes it difficult to debug or even document the matter coupled with the fact that its occurence is random in nature. I'be tried running several diagnostic tools including smartctl but I am unable to deduce anything useful out of it.

Some specs and info about the homelab is as follows:

• Build: Pre built Compact Mini PC
• CPU: Intel i7-14700
• RAM: 16GB
• Storage: 1TB SSD
• GPU: Integrated Intel HD Graphics 770
• Operating System: Ubuntu 24.04 LTS

I would really appreciate if you could point out the cause of this issue. This experience makes the server reliable which is why I don't feel comfortable hosting anything valuable or sensitive on it yet. I can provide you additional details or logs if required.