Page 1 of 1

Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 1:01 pm
by SkOrPn
Well hello again,

A few days ago I decided to unretire my 5th gen Intel NUC5i7RYH and install MX-23. I put in a Samsung 970 Evo Plus NVMe SSD (250GB) to install MX to, and also installed a 1TB 870 EVO SATA SSD for files, etc. However after a few days of setting it up with all of the pertinent software and settings I discovered that I installed the system to the SATA drive. How in the heck I missed this I do not quite understand. However, I guess I could reinstall it and then format the sata drive. But I am curious if there is a faster better way? Like a perfect snapshot clone or something I could quickly use instead? Granted the sata drive is 1TB and the target drive is only 256gb. I have used Clonezilla many times, but isn't there something else that won't discriminate because of disk size? Something like MX Snapshot or something? Thanks for any tips etc.

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 1:50 pm
by Charlie Brown
Yep, MX Snapshot .. the free space won't be included in the iso, so it won't be a problem.

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 2:33 pm
by SkOrPn
Ok good then. Will the tool create a bootable iso for re-installation of mx with everything intact as it is now? Or something else? And if so, should I remove the sata drive just in case?

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 3:17 pm
by MXRobo
Yes, choose the Personal option, and MX-Snapshsot could be named MX-ISO-Maker - treat is as an iso because it is an iso.

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 5:32 pm
by SkOrPn
OK got it installed to the proper ssd. However after erasing and formatting the storage drive I can't get linux to use it. I can't make any Folders or anything. I can mount and unmount, but thats about the extent of it. I have tried multiple times both using gparted and the terminal. I partitioned as gpt and formatted as ext4. But thunar refuses to do anything with it, even after reboots. I am confused now.

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 6:02 pm
by towwire
You have a permission problem. If you right click and Properties/Permissions tab you will see that the owner is root.

If you want to change the permissions on your data files, you can do this:

Code: Select all

sudo chown -R $USER:$USER /top-level/path/to/files 

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 10:04 pm
by MXRobo

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Thu Sep 07, 2023 10:40 pm
by figueroa
If you have any mountpoints in /mnt/, they will not be included when you install the snapshot. Also, if you've changed the /etc/fstab, those changes may also not be included.

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Fri Sep 08, 2023 1:00 pm
by SkOrPn
Ok the link MXRobo supplied did the trick.

I used

Code: Select all

sudo chown -R rod:rod /media/rod/nameofpartition/.
And I was immediately given access to create and use folders. I sure hope that was correct. I was ready to pull the drive out of the machine. Thanks to everyone who replied.

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Fri Sep 08, 2023 1:05 pm
by Charlie Brown
SkOrPn wrote: Fri Sep 08, 2023 1:00 pmI sure hope that was correct.
Yep, it's ok.

The reason was: GParted gives the ownership to root by default.

Re: Installed to wrong drive. Can I fix/clone this easily to correct drive?

Posted: Fri Sep 08, 2023 1:17 pm
by MXRobo
Typed before I saw Charlie Brown's reply.
I'm not very good at this stuff so take all with a grain of salt, but did you use this for a partition or for a drive?
I ask for two reasons:
/media/rod/nameofpartition/
from your post,

and from my provided link which mentions both drive and partition in this quote:
which is especially useful for writes to the root of the drive/partition.

but does mentions only partition and not drive from there on.

I used the method in my provided link on a partition, not a drive.

So, I have not tried this on a drive.

But CB does know this stuff.