Groups | Search | Server Info | Login | Register

Groups > uk.comp.os.linux > #23726

Re: Here we go again

Show all headers | View raw

On Tue, 09 Sep 2025 22:02:52 +0100
"Vincent Coen" <VBCoen@gmail.com> wrote:

trimmed for brevity.

>  >>
>  >> Using Fstrim has to be via sudo e.g., sudo fstrim -av and here I
>  >> get :  sudo fstrim -av [sudo] password for mbse: /home: 5.4 GiB
>  >> (5775577088 bytes) trimmed on /dev/nvme0n1p4 /: 950.7 MiB
>  >> (996900864 bytes) trimmed on /dev/nvme0n1p2  Note that every time
>  >> you reboot or restart running fstrim will produce size around the
>  >> total capacity and this is normal but say a few minutes after
>  >> rerunning it  will give a more sensible number e.g.,
>  >>  sudo fstrim -av
>  >> /home: 319.8 MiB (335319040 bytes) trimmed on /dev/nvme0n1p4
>  >> /: 0 B (0 bytes) trimmed on /dev/nvme0n1p2
>  >>
>  >> I you try running fstrim before shutting down for a drive swap but
>  >> leave the system running for say 30 minutes before shutting down
>  >> for a swap out and no, it just gives some time for the controller
>  >> to clear out lost clusters etc.
>  >>
>  >> I am assuming here that your laptop has minimal extra drive
>  >> capacity / Sata connections ? so what to do, if you have data
>  >> files on the boot drive then removing the 2nd drive (assuming it
>  >> is not needed when booting) and using new drive in place before
>  >> copying over all such data having partitioning / format the new
>  >> drive first (as root / sudo) AND knowing that you have fdisk or
>  >> similar to do so. Also install rsync as it is quicker than using
>  >> cp as multi copies are run at same time.
>  >>
>  >> Firstly install Linux on new drive as as m.2 slot one with no
>  >> other drive present and install if not already fstrim, rsync &
>  >> fdisk and any other packages you might need. Reboot and run
>  >> update service then shutdown, reinstall old drive as slot two and
>  >> do the above processes, i.e., copying over and folders from slot
>  >> 2 to boot drive / partition as needed.  Reboot - to confirm it
>  >> still works.  Remove m.2 slot 2, replacing with old 2nd drive and
>  >> boot up. Now depending size of slot 1 and your needs copy over
>  >> any folders from slot 2 to boot drive to any / all partitions you
>  >> have created when first installing ---- Bye the bye, set up the
>  >> partitions MANUALLY if possible creating any extra partitions AND
>  >> formatting them (EXT 4 etc and create labels for them) as well as
>  >> the one for booting the system - personally I use a max size of
>  >> 50 GB for the boot partitions and I do have more than one on a
>  >> drive so I can test a new version and/or install an other distro
>  >> if I wish to experiment creating 40 - 50 GB partitions for them
>  >> as a guess but but not below 20 GB,  but you might want to use a
>  >> different size depending on total capacity and your needs.
>  >> Another option to moving m.2 units about is to get a adaptor that
>  >> will take a m.2 drive that can be mounted as a usb drive and no
>  >> never looked but assume they are around at a reasonable price.
>  >> This option, will be slower in operation as USB is less than 5%
>  >> speed of a M.2 drive. [ Here an m.2 runs at 6,000 Mb persec and
>  >> USB 4-500 Mb if you are lucky - yes they actually operate well
>  >> below specification speeds.  Look you cannot go wrong PROVIDING
>  >> you NEVER overwrite the original drives and only use them to copy
>  >> FROM.  OK, you might make mistakes and have to redo it all but it
>  >> is only time and your original data is safe BUT, BUT only do this
>  >> process when you are wide awake :(    Vincent  
> 
>  > Vince,  
> 
>  > I know and appreciate your sincerity, but the last paragraph reeks
>  > of "What can possibly go wrong?" to me!  
> 
>  > Unless you can GUARANTEE full success, I am headed in the "Use
>  > what's there" direction. And it's the cheapest.  
> 
>  > Cheers
>  > --
>  > Davey.  
> 
> Here the trick is to only open these systems you are copying FROM as
> Read Only - the entire partition. via MOUNT i.e., sudo mount -r ....
> 
> 
> 
> Vincent
> 
> 

Yes, but that needs the process of switching drives around etc etc to
work as intended, plus buying adaptors and a drive that I may never
need again. And even if it does go as described, it won't let me copy
working applications to the new partitions, will it? Only files will be
transferable, I can't just transfer stuff and then suddenly have a
working Libre Office all ready to go, complete with all of my previous
setup and preferences. And I can see an advantage in setting each
application up again from scratch, as the upgrade to ver. 22.04 was,
not a disaster, but certainly not the smooth installation as it was on
the Desktop. It is possible that there was some confusion between the
two SSDs. when doing the upgrade, as discussed earlier. Reinstalling
the OS onto a blank SSD would prevent that, and would be similar
to the original layout when ver. 18.04 was first installed, and it
worked fine. 22.04 did not.

The more I think about it, the more I am coming down on the restart
plan, with no new items involved:
Remove the M2SSD, wipe the primary drive (SATA SSD) and install a clean
setup of ver. 22.04. Install required applications. When all is
operating as it should, then re-install the M2SSD.
The only files that I will lose are the TB Local Folders since the
last backup, and they can be recreated, thanks to gmail keeping all
messages.

I appreciate what you say, and ma grateful for the thoughts, but TO ME
my way has more advantages than disadvantages, and is simpler to
implement.

-- 
Davey.

Back to uk.comp.os.linux | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Here we go again Davey <davey@example.invalid> - 2025-09-02 11:03 +0100
  Re: Here we go again Davey <davey@example.invalid> - 2025-09-03 08:57 +0100
    Re: Here we go again Daniel James <daniel@me.invalid> - 2025-09-03 16:49 +0100
      Re: Here we go again Theo <theom+news@chiark.greenend.org.uk> - 2025-09-03 17:21 +0100
        Re: Here we go again Davey <davey@example.invalid> - 2025-09-03 17:48 +0100
          Re: Here we go again Theo <theom+news@chiark.greenend.org.uk> - 2025-09-03 18:20 +0100
            Re: Here we go again Davey <davey@example.invalid> - 2025-09-03 20:10 +0100
            Re: Here we go again Davey <davey@example.invalid> - 2025-09-03 20:50 +0100
            Re: Here we go again Davey <davey@example.invalid> - 2025-09-04 11:35 +0100
              Re: Here we go again Daniel James <daniel@me.invalid> - 2025-09-04 17:30 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-04 19:52 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-05 23:49 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-08 11:50 +0100
                Re: Here we go again "Vincent Coen" <VBCoen@gmail.com> - 2025-09-08 16:11 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-08 17:28 +0100
                TRIM (Was: Here we go again) Daniel James <daniel@me.invalid> - 2025-09-15 16:00 +0100
                Re: TRIM (Was: Here we go again) Davey <davey@example.invalid> - 2025-09-15 17:30 +0100
                Re: TRIM Richard Kettlewell <invalid@invalid.invalid> - 2025-09-17 08:43 +0100
                Re: TRIM Daniel James <daniel@me.invalid> - 2025-09-17 10:30 +0100
                Re: TRIM Davey <davey@example.invalid> - 2025-09-17 11:05 +0100
                Re: TRIM Daniel James <daniel@me.invalid> - 2025-09-17 15:12 +0100
                Re: TRIM Davey <davey@example.invalid> - 2025-09-17 15:54 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-09 09:04 +0100
                Re: Here we go again "Vincent Coen" <VBCoen@gmail.com> - 2025-09-09 12:19 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-09 18:03 +0100
                Re: Here we go again "Vincent Coen" <VBCoen@gmail.com> - 2025-09-09 22:02 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-10 00:14 +0100
                Re: Here we go again -Update Davey <davey@example.invalid> - 2025-09-11 17:12 +0100
                Re: Here we go again -Update Davey <davey@example.invalid> - 2025-09-21 16:10 +0100
                Re: Here we go again -Update "Vincent Coen" <VBCoen@gmail.com> - 2025-09-22 01:41 +0100
                Re: Here we go again -Update Davey <davey@example.invalid> - 2025-09-22 09:29 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-10 12:43 +0100
                Re: Here we go again Theo <theom+news@chiark.greenend.org.uk> - 2025-09-08 21:33 +0100
              Re: Here we go again Daniel James <daniel@me.invalid> - 2025-09-04 20:07 +0100
                Re: Here we go again Davey <davey@example.invalid> - 2025-09-05 02:47 +0100
          Re: Here we go again Gordon <Gordon@leaf.net.nz> - 2025-09-03 23:46 +0000
            Re: Here we go again Davey <davey@example.invalid> - 2025-09-04 09:36 +0100
        Re: Here we go again Gordon <Gordon@leaf.net.nz> - 2025-09-03 23:31 +0000

csiph-web