I have had my /home folder on a separate spinning disk for some time
now, but I now want to move it onto an ssd disk.

What is the best way to do this, clone it or just move it by the same
method used to move it before.

Thanks

On 3/9/2023 10:39 AM, Rob H wrote:
> I have had my /home folder on a separate spinning disk for some time now, but I now want to move it onto an ssd disk.
>
> What is the best way to do this, clone it or just move it by the same method used to move it before.
>
> Thanks

How about boot a LiveDVD, run gparted and "copy" the partition
in question to the SSD ?

You don't want the normal OS running that uses /home, to have
it open at the time, which is why a separate boot OS (LiveDVD)
might be better.

sudo apt install gparted # or similar

sudo gparted # I hope a copy can go to another spindle...

Is there some detail about a BLKID ?

Maybe the /etc/fstab makes a reference to /home
on your main OS drive. You want to verify that what
got done during the "copy", was reasonable. You don't
want to break something (and have home operations done
on the raw bare mount point :-) ).

Paul

On 09/03/2023 17:03, Paul wrote:
> On 3/9/2023 10:39 AM, Rob H wrote:
>> I have had my /home folder on a separate spinning disk for some time
>> now, but I now want to move it onto an ssd disk.
>>
>> What is the best way to do this, clone it or just move it by the same
>> method used to move it before.
>>
>> Thanks
>
> How about boot a LiveDVD, run gparted and "copy" the partition
> in question to the SSD ?
>
> You don't want the normal OS running that uses /home, to have
> it open at the time, which is why a separate boot OS (LiveDVD)
> might be better.
>
>    sudo apt install gparted       # or similar
>
>    sudo gparted                   # I hope a copy can go to another
> spindle...
>
> Is there some detail about a BLKID ?
>
> Maybe the /etc/fstab makes a reference to /home
> on your main OS drive. You want to verify that what
> got done during the "copy", was reasonable. You don't
> want to break something (and have home operations done
> on the raw bare mount point :-) ).
>
>   Paul
>
Thanks,and this is from my fstab file:

UUID=f24b367a-1f06-47f5-9ec9-b33c4c332478 / ext4
errors=remount-ro 0 1

# /boot/efi was on /dev/sda1 during installation

UUID=992E-E5B5 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw
0 0

UUID=77774aea-0430-4429-b301-a220157601a5 /home ext4 defaults
0 2

On 3/9/2023 1:47 PM, Rob H wrote:
> On 09/03/2023 17:03, Paul wrote:
>> On 3/9/2023 10:39 AM, Rob H wrote:
>>> I have had my /home folder on a separate spinning disk for some time now, but I now want to move it onto an ssd disk.
>>>
>>> What is the best way to do this, clone it or just move it by the same method used to move it before.
>>>
>>> Thanks
>>
>> How about boot a LiveDVD, run gparted and "copy" the partition
>> in question to the SSD ?
>>
>> You don't want the normal OS running that uses /home, to have
>> it open at the time, which is why a separate boot OS (LiveDVD)
>> might be better.
>>
>>     sudo apt install gparted       # or similar
>>
>>     sudo gparted                   # I hope a copy can go to another spindle...
>>
>> Is there some detail about a BLKID ?
>>
>> Maybe the /etc/fstab makes a reference to /home
>> on your main OS drive. You want to verify that what
>> got done during the "copy", was reasonable. You don't
>> want to break something (and have home operations done
>> on the raw bare mount point :-) ).
>>
>>    Paul
>>
> Thanks,and this is from my fstab file:
>
> UUID=f24b367a-1f06-47f5-9ec9-b33c4c332478 /               ext4 errors=remount-ro 0       1
>
> # /boot/efi was on /dev/sda1 during installation
>
> UUID=992E-E5B5  /boot/efi       vfat    umask=0077      0       1
> /swapfile                                 none            swap    sw          0       0
>
> UUID=77774aea-0430-4429-b301-a220157601a5 /home      ext4     defaults  0       2 <===
>

So your home entry has a UUID.

You would want to review the results of the cloning
and see if the UUID of the new item is correct.
And stop using the old spindle (disconnect), so
there won't be two items with the same UUID.

Alternately, you could change the UUID on the new SSD,
and also change the /etc/fstab (while you are running
from the LiveDVD).

Paul

On 3/9/23 07:39, Rob H wrote:
> I have had my /home folder on a separate spinning disk for some time
> now, but I now want to move it onto an ssd disk.
>
> What is the best way to do this, clone it or just move it by the same
> method used to move it before.

How should we know what "the same method used to move it before" was?
Crystal ball or?

Am 09.03.2023 schrieb Paul <nospam@needed.invalid>:

> sudo gparted

Don't use it that way. Run it without sudo - you will be granted
permission via PolKit.

On 10/03/2023 06:15, stepore wrote:
> On 3/9/23 07:39, Rob H wrote:
>> I have had my /home folder on a separate spinning disk for some time
>> now, but I now want to move it onto an ssd disk.
>>
>> What is the best way to do this, clone it or just move it by the same
>> method used to move it before.
>
> How should we know what "the same method used to move it before" was?
> Crystal ball or?
>
Because I followed a guide on a Ubuntu site.

On 09/03/2023 22:50, Paul wrote:
> On 3/9/2023 1:47 PM, Rob H wrote:
>> On 09/03/2023 17:03, Paul wrote:
>>> On 3/9/2023 10:39 AM, Rob H wrote:
>>>> I have had my /home folder on a separate spinning disk for some time
>>>> now, but I now want to move it onto an ssd disk.
>>>>
>>>> What is the best way to do this, clone it or just move it by the
>>>> same method used to move it before.
>>>>
>>>> Thanks
>>>
>>> How about boot a LiveDVD, run gparted and "copy" the partition
>>> in question to the SSD ?
>>>
>>> You don't want the normal OS running that uses /home, to have
>>> it open at the time, which is why a separate boot OS (LiveDVD)
>>> might be better.
>>>
>>>     sudo apt install gparted       # or similar
>>>
>>>     sudo gparted                   # I hope a copy can go to another
>>> spindle...
>>>
>>> Is there some detail about a BLKID ?
>>>
>>> Maybe the /etc/fstab makes a reference to /home
>>> on your main OS drive. You want to verify that what
>>> got done during the "copy", was reasonable. You don't
>>> want to break something (and have home operations done
>>> on the raw bare mount point :-) ).
>>>
>>>    Paul
>>>
>> Thanks,and this is from my fstab file:
>>
>> UUID=f24b367a-1f06-47f5-9ec9-b33c4c332478 /               ext4
>> errors=remount-ro 0       1
>>
>> # /boot/efi was on /dev/sda1 during installation
>>
>> UUID=992E-E5B5  /boot/efi       vfat    umask=0077      0       1
>> /swapfile                                 none            swap    sw
>>          0       0
>>
>> UUID=77774aea-0430-4429-b301-a220157601a5 /home      ext4     defaults
>>  0       2   <===
>>
>
> So your home entry has a UUID.
>
> You would want to review the results of the cloning
> and see if the UUID of the new item is correct.
> And stop using the old spindle (disconnect), so
> there won't be two items with the same UUID.
>
> Alternately, you could change the UUID on the new SSD,
> and also change the /etc/fstab (while you are running
> from the LiveDVD).
>
>    Paul

these are the UUID's of the disks now. the new ssd is sda1:

rob@rob-Z97:~$ sudo blkid

/dev/sdb: LABEL="WDBlue" UUID="77774aea-0430-4429-b301-a220157601a5"
BLOCK_SIZE="4096" TYPE="ext4"

/dev/sdc5: UUID="f24b367a-1f06-47f5-9ec9-b33c4c332478" BLOCK_SIZE="4096"
TYPE="ext4" PARTUUID="f123373d-05"

/dev/sdc1: UUID="992E-E5B5" BLOCK_SIZE="512" TYPE="vfat"
PARTUUID="f123373d-01"

/dev/sda1: UUID="f41a8ea3-79d3-473d-bee1-45fc22caf353" BLOCK_SIZE="4096"
TYPE="ext4" PARTUUID="2ab0f1d4-01"

And this is my fstab file:

UUID=992E-E5B5 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw
0 0

UUID=77774aea-0430-4429-b301-a220157601a5 /home ext4 defaults
0 2

/dev/disk/by-id/ata-ATAPI_iHAS124_F_3524807_2D8021510791
/mnt/ata-ATAPI_iHAS124_F_3524807_2D8021510791 auto
nosuid,nodev,nofail,noauto,x-gvfs-show 0 0

On 3/10/2023 4:03 AM, Rob H wrote:
> On 09/03/2023 22:50, Paul wrote:
>> On 3/9/2023 1:47 PM, Rob H wrote:
>>> On 09/03/2023 17:03, Paul wrote:
>>>> On 3/9/2023 10:39 AM, Rob H wrote:
>>>>> I have had my /home folder on a separate spinning disk for some time now, but I now want to move it onto an ssd disk.
>>>>>
>>>>> What is the best way to do this, clone it or just move it by the same method used to move it before.
>>>>>
>>>>> Thanks
>>>>
>>>> How about boot a LiveDVD, run gparted and "copy" the partition
>>>> in question to the SSD ?
>>>>
>>>> You don't want the normal OS running that uses /home, to have
>>>> it open at the time, which is why a separate boot OS (LiveDVD)
>>>> might be better.
>>>>
>>>>     sudo apt install gparted       # or similar
>>>>
>>>>     sudo gparted                   # I hope a copy can go to another spindle...
>>>>
>>>> Is there some detail about a BLKID ?
>>>>
>>>> Maybe the /etc/fstab makes a reference to /home
>>>> on your main OS drive. You want to verify that what
>>>> got done during the "copy", was reasonable. You don't
>>>> want to break something (and have home operations done
>>>> on the raw bare mount point :-) ).
>>>>
>>>>    Paul
>>>>
>>> Thanks,and this is from my fstab file:
>>>
>>> UUID=f24b367a-1f06-47f5-9ec9-b33c4c332478 /               ext4 errors=remount-ro 0       1
>>>
>>> # /boot/efi was on /dev/sda1 during installation
>>>
>>> UUID=992E-E5B5  /boot/efi       vfat    umask=0077      0       1
>>> /swapfile                                 none            swap    sw          0       0
>>>
>>> UUID=77774aea-0430-4429-b301-a220157601a5 /home      ext4     defaults  0       2   <===
>>>
>>
>> So your home entry has a UUID.
>>
>> You would want to review the results of the cloning
>> and see if the UUID of the new item is correct.
>> And stop using the old spindle (disconnect), so
>> there won't be two items with the same UUID.
>>
>> Alternately, you could change the UUID on the new SSD,
>> and also change the /etc/fstab (while you are running
>> from the LiveDVD).
>>
>>     Paul
>
> these are the UUID's of the disks now. the new ssd is sda1:
>
> rob@rob-Z97:~$ sudo blkid
>
> /dev/sdb: LABEL="WDBlue" UUID="77774aea-0430-4429-b301-a220157601a5" BLOCK_SIZE="4096" TYPE="ext4"
>
> /dev/sdc5: UUID="f24b367a-1f06-47f5-9ec9-b33c4c332478" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f123373d-05"
>
> /dev/sdc1: UUID="992E-E5B5" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f123373d-01"
>
> /dev/sda1: UUID="f41a8ea3-79d3-473d-bee1-45fc22caf353" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2ab0f1d4-01"
>
> And this is my fstab file:
>
> UUID=992E-E5B5  /boot/efi       vfat    umask=0077      0       1
> /swapfile                                 none            swap    sw          0       0
>
> UUID=77774aea-0430-4429-b301-a220157601a5 /home      ext4     defaults  0       2
>
> /dev/disk/by-id/ata-ATAPI_iHAS124_F_3524807_2D8021510791 /mnt/ata-ATAPI_iHAS124_F_3524807_2D8021510791 auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0
>

So you do have something to fix then. The two identifiers are not currently the same value.

/dev/sda1: UUID="f41a8ea3-79d3-473d-bee1-45fc22caf353"

UUID=77774aea-0430-4429-b301-a220157601a5 /home ext4 defaults 0 2

The reason I can't jump to a conclusion, is I don't know if that home is being
used on any other OSes. When an identifier is "sprayed all over the place",
you have to think carefully about which fix is the least disruptive.

But at least you can see the values do not currently match.

The fstab could be handled this way. Comment out old one. Put new line below it.

# UUID=77774aea-0430-4429-b301-a220157601a5 /home ext4 defaults 0 2 <=== old line
UUID=f41a8ea3-79d3-473d-bee1-45fc22caf353 /home ext4 defaults 0 2 <=== new below it

And you could do that from your LiveDVD if you want.
You will need root to replace /etc/fstab at some point.

Paul

On 10/03/2023 12:36, Paul wrote:
> On 3/10/2023 4:03 AM, Rob H wrote:
>> On 09/03/2023 22:50, Paul wrote:
>>> On 3/9/2023 1:47 PM, Rob H wrote:
>>>> On 09/03/2023 17:03, Paul wrote:
>>>>> On 3/9/2023 10:39 AM, Rob H wrote:
>>>>>> I have had my /home folder on a separate spinning disk for some
>>>>>> time now, but I now want to move it onto an ssd disk.
>>>>>>
>>>>>> What is the best way to do this, clone it or just move it by the
>>>>>> same method used to move it before.
>>>>>>
>>>>>> Thanks
>>>>>
>>>>> How about boot a LiveDVD, run gparted and "copy" the partition
>>>>> in question to the SSD ?
>>>>>
>>>>> You don't want the normal OS running that uses /home, to have
>>>>> it open at the time, which is why a separate boot OS (LiveDVD)
>>>>> might be better.
>>>>>
>>>>>     sudo apt install gparted       # or similar
>>>>>
>>>>>     sudo gparted                   # I hope a copy can go to
>>>>> another spindle...
>>>>>
>>>>> Is there some detail about a BLKID ?
>>>>>
>>>>> Maybe the /etc/fstab makes a reference to /home
>>>>> on your main OS drive. You want to verify that what
>>>>> got done during the "copy", was reasonable. You don't
>>>>> want to break something (and have home operations done
>>>>> on the raw bare mount point :-) ).
>>>>>
>>>>>    Paul
>>>>>
>>>> Thanks,and this is from my fstab file:
>>>>
>>>> UUID=f24b367a-1f06-47f5-9ec9-b33c4c332478 /               ext4
>>>> errors=remount-ro 0       1
>>>>
>>>> # /boot/efi was on /dev/sda1 during installation
>>>>
>>>> UUID=992E-E5B5  /boot/efi       vfat    umask=0077      0       1
>>>> /swapfile                                 none            swap    sw
>>>>          0       0
>>>>
>>>> UUID=77774aea-0430-4429-b301-a220157601a5 /home      ext4
>>>> defaults  0       2   <===
>>>>
>>>
>>> So your home entry has a UUID.
>>>
>>> You would want to review the results of the cloning
>>> and see if the UUID of the new item is correct.
>>> And stop using the old spindle (disconnect), so
>>> there won't be two items with the same UUID.
>>>
>>> Alternately, you could change the UUID on the new SSD,
>>> and also change the /etc/fstab (while you are running
>>> from the LiveDVD).
>>>
>>>     Paul
>>
>> these are the UUID's of the disks now. the new ssd is sda1:
>>
>> rob@rob-Z97:~$ sudo blkid
>>
>> /dev/sdb: LABEL="WDBlue" UUID="77774aea-0430-4429-b301-a220157601a5"
>> BLOCK_SIZE="4096" TYPE="ext4"
>>
>> /dev/sdc5: UUID="f24b367a-1f06-47f5-9ec9-b33c4c332478"
>> BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f123373d-05"
>>
>> /dev/sdc1: UUID="992E-E5B5" BLOCK_SIZE="512" TYPE="vfat"
>> PARTUUID="f123373d-01"
>>
>> /dev/sda1: UUID="f41a8ea3-79d3-473d-bee1-45fc22caf353"
>> BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2ab0f1d4-01"
>>
>> And this is my fstab file:
>>
>> UUID=992E-E5B5  /boot/efi       vfat    umask=0077      0       1
>> /swapfile                                 none            swap    sw
>>          0       0
>>
>> UUID=77774aea-0430-4429-b301-a220157601a5 /home      ext4     defaults
>>  0       2
>>
>> /dev/disk/by-id/ata-ATAPI_iHAS124_F_3524807_2D8021510791
>> /mnt/ata-ATAPI_iHAS124_F_3524807_2D8021510791 auto
>> nosuid,nodev,nofail,noauto,x-gvfs-show 0 0
>>
>
> So you do have something to fix then. The two identifiers are not
> currently the same value.
>
> /dev/sda1: UUID="f41a8ea3-79d3-473d-bee1-45fc22caf353"
>
>            UUID=77774aea-0430-4429-b301-a220157601a5 /home
> ext4     defaults  0       2
>
> The reason I can't jump to a conclusion, is I don't know if that home is
> being
> used on any other OSes. When an identifier is "sprayed all over the place",
> you have to think carefully about which fix is the least disruptive.
>
> But at least you can see the values do not currently match.
>
> The fstab could be handled this way. Comment out old one. Put new line
> below it.
>
> # UUID=77774aea-0430-4429-b301-a220157601a5 /home      ext4
> defaults  0       2    <=== old line
> UUID=f41a8ea3-79d3-473d-bee1-45fc22caf353 /home      ext4     defaults
> 0       2      <=== new below it
>
> And you could do that from your LiveDVD if you want.
> You will need root to replace /etc/fstab at some point.
>
>    Paul

Thanks Paul.
I booted a liveUSB with Mint 21.1, then copied /home from the spinning
disc to the ssd.
I shut my system down and thought that if I disconnected the spinning
disc, /home would be picked up on the ssd when booting up. But no, it
didn't.
Anyway, I booted as normal after reconnecting the spinning disc, and
then added the new UUID line to my fstab file, as well as commenting out
the spinning disc UUID.
I rebooted and Mint came back as tho' nothing had changed.

thanks again

Paul <nospam@needed.invalid> writes:
>
> You don't want the normal OS running that uses /home, to have
> it open at the time, which is why a separate boot OS (LiveDVD)
> might be better.
>
FWIW, I always have several root partitions on my boot disk. There is
the root partition of my 'everyday system', and a root partition of a
'rescue' partition which does the same job as having a Live disk but
also can immediately take over as the 'everyday system' if a disaster
happens to strike. The 'rescue' partition runs the same distro version
as the 'everyday' partition.

As for that third root partition, that's the 'experimental' root where
I try out different operating systems or different distros without
interfering with my two 'everyday' systems.

Regards,

Jack
--
They call me 007 at work:
0 Motivation
0 Skills
7 Smoke Breaks

On 3/10/23 00:58, Rob H wrote:
> On 10/03/2023 06:15, stepore wrote:
>> On 3/9/23 07:39, Rob H wrote:
>>> I have had my /home folder on a separate spinning disk for some time
>>> now, but I now want to move it onto an ssd disk.
>>>
>>> What is the best way to do this, clone it or just move it by the same
>>> method used to move it before.
>>
>> How should we know what "the same method used to move it before" was?
>> Crystal ball or?
>>
> Because I followed a guide on a Ubuntu site.
>

And once more, how should we know what guide that was or what you did
before? I mean. omg.

On 11/03/2023 07:22, stepore wrote:
> On 3/10/23 00:58, Rob H wrote:
>> On 10/03/2023 06:15, stepore wrote:
>>> On 3/9/23 07:39, Rob H wrote:
>>>> I have had my /home folder on a separate spinning disk for some time
>>>> now, but I now want to move it onto an ssd disk.
>>>>
>>>> What is the best way to do this, clone it or just move it by the same
>>>> method used to move it before.
>>>
>>> How should we know what "the same method used to move it before" was?
>>> Crystal ball or?
>>>
>> Because I followed a guide on a Ubuntu site.
>>
>
> And once more, how should we know what guide that was or what you did
> before? I mean. omg.

Why do you want to know something I did about 3 years ago and is
immaterial to me now

On 3/11/23 00:22, Rob H wrote:
>
> Why do you want to know something I did about 3 years ago and is
> immaterial to me now

Immaterial? WT hell.

You literally ask:
>>>>> What is the best way to do this, clone it or just move it by the same
>>>>> method used to move it before.

"the same method used to move it before"! How the hell should we know
what you did to move it before. We need this information in order to
know what is the best way. As you're asking "what is best". Maybe what
you did before was the best way! What is this, some kind of inside joke
i'm missing? Is this not clear to you? How can anyone give you advice on
what's best if we don't actually know what you did before?

It's like asking, hey what's your advice on best linux laptop. This new
dell XPS or that other model I was using before, but don't actually tell
anyone what that old model you were using before.

On 12/03/2023 05:41, stepore wrote:
> On 3/11/23 00:22, Rob H wrote:
>>
>> Why do you want to know something I did about 3 years ago and is
>> immaterial to me now
>
> Immaterial? WT hell.
>
> You literally ask:
> >>>>> What is the best way to do this, clone it or just move it by the
> same
> >>>>> method used to move it before.
>
> "the same method used to move it before"! How the hell should we know
> what you did to move it before. We need this information in order to
> know what is the best way. As you're asking "what is best". Maybe what
> you did before was the best way! What is this, some kind of inside joke
> i'm missing? Is this not clear to you? How can anyone give you advice on
> what's best if we don't actually know what you did before?
>
> It's like asking, hey what's your advice on best linux laptop. This new
> dell XPS or that other model I was using before, but don't actually tell
> anyone what that old model you were using before.

You are a bit late anyways now because I did what I wanted 2 days ago now