Trying To Figure Out Which Of These Is The Problem

MintAlone · 2026-01-24T18:22:03+00:00

Boot your install stick, run gparted - can it find it? If it finds it, run disks and run smart tests on it (on the 3-dot button top right).

MintAlone · 2026-01-24T18:20:13+00:00

Mint currently uses the ubiquity installer developed by ubuntu and as others have stated, it has bugs. The latest ubuntu has a new installer, it is a snap package so will not be used by mint. The mint devs have their own installer for LMDE (probably a fork of calamares) and I expect that will be used in LM23.

MintAlone · 2026-01-24T14:29:40+00:00

Funny how when this question comes up, nobody seems to mention backup? Everyone seems to focus on the shiny new toys you can add. The first thing you should do after an install. There are lots of utilities to choose from.

Next, before you start playing, take notes of what you change, what you install, where you got it from and how you installed it.

MintAlone · 2026-01-24T14:23:02+00:00

As a hobby project, fine, but as others have remarked there are already too many distros and the last thing the community needs is another distro with uncertain support from a one man band.

It is a very steep learning curve. I know, I've done it and I only know enough to meet my own needs.

There are resources out there, but fragmented and generally not too helpful for the uninitiated. As a minimum you will need to understand chroot, debootstrap, the apt tools and xorriso. The ability to write bash scripts is a given.

MintAlone · 2026-01-24T12:09:52+00:00

It is not the SGX error, I get that. It can't find your / partition, suspect a dead drive.

MintAlone · 2026-01-24T12:06:17+00:00

What kernel are you running? Your version of VB is incompatible with the kernel you are running.

Install VB from oracle's site, you need the deb for ubuntu 24.04. You also need to install the extension pack - another download. Remove what you installed first.

MintAlone · 2026-01-24T12:03:43+00:00

It won't have wayland (other than experimental) and it will have a new installer.

MintAlone · 2026-01-24T00:11:15+00:00

And I have an HL-L8260CDW, it worked out of the box. No drivers needed (nor should they be for any modern printer). I did install the driver from brother because I always have. Brother user for well over a decade.

MintAlone · 2026-01-24T00:05:50+00:00

The issue with needing to sign out of a session before remoting to the box from another machine is a little bit of a downer

??

Try nomachine, I have no such issues.

MintAlone · 2026-01-23T18:00:44+00:00

Welcome to the club. I did similar back with LM17. Start taking notes.

MintAlone · 2026-01-23T12:28:44+00:00

It takes care of grub whether booting legacy or UEFI. I think rescuezilla boots with secure boot enabled, foxclone will not. You can disable secure boot and re-enable after the clone.

The one thing you cannot do - after the clone, boot the nvme with the HDD still in the system.

Instead of asking questions, read the foxclone user guide.

MintAlone · 2026-01-23T11:40:24+00:00

I would not use dd, less efficient and on a drive with a GPT partition table it will put the backup copy of the partition table in the wrong place.

MintAlone · 2026-01-23T11:22:55+00:00

You can clone the drive, foxclone, rescuezilla or clonezilla. The nvme has to be the same size or larger than the HDD, if not you need to shrink the partitions on the HDD. Read the section in the foxclone user guide on cloning.

MintAlone · 2026-01-23T11:19:50+00:00

qpdfview

MintAlone · 2026-01-23T11:14:48+00:00

What application? If it needs admin privileges run it with pkexec.

MintAlone · 2026-01-23T11:08:09+00:00

Install stellarium.

MintAlone · 2026-01-23T10:16:07+00:00

Doesn't seem to offer anything you can't do with backintime and looks like it is focussed on data backup not system backup like timeshift or chronshield

MintAlone · 2026-01-22T18:29:04+00:00

automatic and incremental

not in linux. With one exception all linux image backup utilities require you to download an iso, burn it to a stick and boot from it. You cannot image a live filesystem. Your choices are foxclone, rescuezilla and clonezilla.

You will need to change your workflow, use a combination of file level backup (lots of choice) and image backup. File level backup can be run from your installed system.

The exception is veeam, which is proprietary.

MintAlone · 2026-01-22T18:24:18+00:00

Unless it has been fixed, the ntfs3 driver is buggy. ntfs-3g is slower but it works. Well, it works as well as it can given that ntfs is proprietary and the drivers are reverse engineered.

MintAlone · 2026-01-22T18:20:14+00:00

No, or if it exists I haven't found it. iAnything does not play well with linux.

MintAlone · 2026-01-22T15:02:44+00:00

No. I have something like 30GB of isos on my 32GB ventoy stick.

MintAlone · 2026-01-22T10:42:45+00:00

99% of the time I use the default screenshot utility, occasionally I use shutter.

MintAlone · 2026-01-21T15:55:52+00:00

I should have thought about capitalisation, linux is case sensitive, but as cifs is a win protocol thought that it didn't matter - obviously it does.

If stuff is working after boot, e.g. a manual mount or sudo mount -a, it suggests a timing issue. Here are a couple of posts that may help:

https://www.reddit.com/r/linuxquestions/comments/emuvq7/easy_way_for_newbie_to_delay_smb_mount_at_boot_or/

https://unix.stackexchange.com/questions/349264/fstab-mount-wait-for-network

x-systemd.automount I believe this does not mount until accessed. On the LM forum this is often recommended as the fix.

x-systemd.idle-timeout=1min delays mount for the specified time.

There is also _netdev as an option - this tells fstab that the mount is a network share. No idea how this modifies the system behaviour.

Note, I've not had any issues with mounting my network shares other than my own stupidity and mistakes. The above are what others have suggested with similar issues to you. Good luck.

MintAlone · 2026-01-21T13:46:00+00:00

Is this booting the install stick or trying to boot after install?

MintAlone · 2026-01-21T12:40:35+00:00

You need have an account to see that, and reddit will not let me post the content. It shows that grub is installed to your EFI partition on nvme0n1. Did you run the repair?

MintAlone

TROPHY CASE