BTRFS error after Cloning disk with Clonezilla stable - 3.1.2-9

Friends,

I made a clone of my existing 250 ssd to 1tb ssd with Clonezilla stable - 3.1.2-9, I able to boot up normally, but my disk getting error BTRFS error (device sda1): bad tree block start, mirror 1 want 3313639833600 have 0 Tried scrub the drive getting following error ’ sudo btrfs scrub start -Bf /dev/sda1
[sudo] password for dev:
Starting scrub on devid 1
scrub done for 21552d5d-e026-4b4a-a2a8-ab97d6cbccde
Scrub started: Sun Mar 10 15:44:08 2024
Status: finished
Duration: 0:03:24
Total to scrub: 76.01GiB
Rate: 381.55MiB/s
Error summary: csum=64
Corrected: 0
Uncorrectable: 64
Unverified: 0
ERROR: there are uncorrectable errors’

smartctl --smart=on /dev/sda1
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.6.21-1-lts] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

Smartctl open device: /dev/sda1 failed: INQUIRY failed

Please guide to resolve it.

System:
  Kernel: 6.6.21-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=21552d5d-e026-4b4a-a2a8-ab97d6cbccde rw rootflags=subvol=@ quiet
    rd.udev.log_priority=3 vt.global_cursor_default=0
    resume=UUID=ac9e5d5d-f05f-49c9-b808-06d51f771ea8 loglevel=3 ibt=off
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0 with: albert,xfce4-panel
    tools: xfce4-screensaver avail: xautolock vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda
    base: Arch Linux
Machine:
  Type: Desktop System: Dell product: OptiPlex 7020 v: 01 serial: <superuser required> Chassis:
    type: 15 serial: <superuser required>
  Mobo: Dell model: 02YYK5 v: A01 serial: <superuser required> part-nu: OptiPlex 7020
    uuid: <superuser required> BIOS: Dell v: A04 date: 04/01/2015
CPU:
  Info: model: Intel Core i3-4160 bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 3592 min/max: 800/3600 scaling: driver: intel_cpufreq governor: performance
    cores: 1: 3592 2: 3592 3: 3592 4: 3592 bogomips: 28746
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel 4th Generation Core Processor Family Integrated Graphics vendor: Dell
    driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: HDMI-A-1
    empty: DP-1, DP-2, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:041e class-ID: 0300
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 compositor: xfwm4 v: 4.18.0
    driver: X: loaded: modesetting alternate: fbdev,intel,vesa dri: crocus gpu: i915 display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Lenovo LEN L27i-28 serial: <filter> built: 2020
    res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
    ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: Vulkan v: 1.3.279 layers: 5 device: 0 type: integrated-gpu name: Intel HD Graphics 4400
    (HSW GT2) driver: mesa intel v: 24.0.2-arch1.2 device-ID: 8086:041e surfaces: xcb,xlib
    device: 1 type: cpu name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
    v: 24.0.2-arch1.2 (LLVM 17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Dell 8 driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  API: ALSA v: k6.6.21-1-lts status: kernel-api tools: N/A
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I217-LM vendor: Dell driver: e1000e v: kernel port: f080 bus-ID: 00:19.0
    chip-ID: 8086:153a class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: br-ea45ab4dcfe7 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IF-ID-3: vboxnet0 state: down mac: <filter>
  IF-ID-4: vethcb30345 state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-5: virbr0 state: down mac: <filter>
  Info: services: httpd, NetworkManager, smbd, sshd, systemd-timesyncd, wpa_supplicant
Drives:
  Local Storage: total: 4.55 TiB used: 1.09 TiB (23.9%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1 size: 931.51 GiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 043
    scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5425 serial: <filter>
    fw-rev: 0001 scheme: GPT
  SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
  ID-1: / raw-size: 920.29 GiB size: 920.29 GiB (100.00%) used: 74.58 GiB (8.1%) fs: btrfs
    block-size: 4096 B dev: /dev/sda1 maj-min: 8:1
  ID-2: /home raw-size: 920.29 GiB size: 920.29 GiB (100.00%) used: 74.58 GiB (8.1%) fs: btrfs
    block-size: 4096 B dev: /dev/sda1 maj-min: 8:1
  ID-3: /var/log raw-size: 920.29 GiB size: 920.29 GiB (100.00%) used: 74.58 GiB (8.1%) fs: btrfs
    block-size: 4096 B dev: /dev/sda1 maj-min: 8:1
  ID-4: /var/tmp raw-size: 920.29 GiB size: 920.29 GiB (100.00%) used: 74.58 GiB (8.1%) fs: btrfs
    block-size: 4096 B dev: /dev/sda1 maj-min: 8:1
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.53 GiB used: 1.11 GiB (7.1%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 11.22 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
    maj-min: 8:2
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.53 GiB used: 7.5 GiB (48.3%)
  Processes: 302 Power: uptime: 9h 10m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6.19 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 255 default: graphical tool: systemctl
  Packages: 2091 pm: pacman pkgs: 2037 libs: 499 tools: octopi,pamac,paru,yay pm: flatpak
    pkgs: 54 Compilers: clang: 17.0.6 gcc: 13.2.1 Client: shell wrapper v: 5.2.26-release
    inxi: 3.3.33
Garuda (2.6.23-1):
  System install date:     2024-03-07
  Last full system update: 2024-03-10 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio
  Windows dual boot:       <superuser required>
  Failed units:            systemd-vconsole-setup.service 

I have no idea how to fix the existing 1tb clone without fumbling around and wasting your time, but I’d consider using a different method to clone the 250mb drive.
This sounds promising:
GitHub - mwilck/btrfs-clone: A tool for copying a btrfs file system with all its subvolumes to another btrfs file system

2 Likes

Maybe you could try a

sudo btrfs check --repair /dev/sda1

:warning: Be warned: the --repair flag is considered a “dangerous” option. It may successfully repair your filesystem, or it may fail and destroy your filesystem in the process. In your case, your filesystem is somewhat unusable anyway but you should be aware the --repair flag can make it worse.

But if this happens only to the cloned drive, you could try, from a chroot, I think the drive should be unmounted.

3 Likes

it is showing errors

sudo btrfs check --force --repair /dev/sda1
[sudo] password for dev:      
enabling repair mode
Opening filesystem to check...
WARNING: filesystem mounted, continuing because of --force
Checking filesystem on /dev/sda1
UUID: 21552d5d-e026-4b4a-a2a8-ab97d6cbccde
[1/7] checking root items
Fixed 0 roots.
[2/7] checking extents
checksum verify failed on 3313399070720 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313399070720 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313399070720 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3313399070720, bytenr mismatch, want=3313399070720, have=0
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space tree
[4/7] checking fs roots
checksum verify failed on 3313399070720 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313399070720 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313399070720 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3313399070720, bytenr mismatch, want=3313399070720, have=0
checksum verify failed on 3198709530624 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3198709530624 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3198709530624 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3198709530624, bytenr mismatch, want=3198709530624, have=0
checksum verify failed on 3198726275072 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3198726275072 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3198726275072 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3198726275072, bytenr mismatch, want=3198726275072, have=0
checksum verify failed on 3313639833600 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313639833600 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313639833600 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3313639833600, bytenr mismatch, want=3313639833600, have=0
checksum verify failed on 3279650832384 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3279650832384 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3279650832384 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3279650832384, bytenr mismatch, want=3279650832384, have=0
checksum verify failed on 3279260811264 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3279260811264 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3279260811264 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3279260811264, bytenr mismatch, want=3279260811264, have=0
checksum verify failed on 3313419206656 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313419206656 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313419206656 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3313419206656, bytenr mismatch, want=3313419206656, have=0
checksum verify failed on 3313431953408 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313431953408 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 3313431953408 wanted 0x00000000 found 0xb6bde3e4
bad tree block 3313431953408, bytenr mismatch, want=3313431953408, have=0
ERROR: errors found in fs roots
found 89904168960 bytes used, error(s) found
total csum bytes: 60071692
total tree bytes: 2072903680
total fs tree bytes: 1858289664
total extent tree bytes: 119373824
btree space waste bytes: 396586597
file data blocks allocated: 151352283136
 referenced 85196378112

I don’t think it will try to repair if sda1 is mounted.

2 Likes

same result with Garuda live disk

I think it is fair to say this is very bad. You could have a corrupted filesystem (bad) or a faulty drive (worse). I would not waste your time trying to salvage this cloning effort, I would reformat the disk and start over.

You could give Clonezilla another shot in case there was just some issue with the cloning process , or try a different tool like @meanruse suggested (that btrfs-clone tool looks pretty neat actually :eyes:).

If you reformat the disk and get a bad filesystem again, I would start looking into what kind of warranty the drive has and get in touch with the vendor.

1 Like

I have reformatted 2nd SSD 1 TB Disk is fine, I am again trying Clonezill then if fail I ll try for @meanruse 's btrfs-clone

Parted Details

GParted 1.6.0

configuration --enable-libparted-dmraid --enable-online-resize

libparted 3.6

========================================

|Device:|/dev/sda|
| --- | --- |
|Model:|ATA CT1000MX500SSD1|
|Serial:|2204E602AF4E|
|Sector size:|512|
|Total sectors:|1953525168|
||
|Heads:|255|
|Sectors/track:|2|
|Cylinders:|3830441|
||
|Partition table:|msdos|
||

|Partition|Type|Start|End|Flags|Partition Name|File System|Label|Mount Point|
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
|/dev/sda1|Primary|2048|1953523711|||btrfs|||

========================================

|Device:|/dev/sdb|
| --- | --- |
|Model:|ATA KINGSTON SA400S3|
|Serial:|50026B778234A630|
|Sector size:|512|
|Total sectors:|468860015|
||
|Heads:|255|
|Sectors/track:|2|
|Cylinders:|919333|
||
|Partition table:|msdos|
||

|Partition|Type|Start|End|Flags|Partition Name|File System|Label|Mount Point|
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
|/dev/sdb1|Primary|2048|450402085|boot||btrfs||/, /home, /root, /run/BtrfsAssistant/21552d5d-e026-4b4a-a2a8-ab97d6cbccde, /srv, /var/cache, /var/log, /var/tmp|
|/dev/sdb2|Primary|450402086|468857024|swap||linux-swap|swap||

========================================

Check and repair file system (btrfs) on /dev/sda1** 00:00:01 ( SUCCESS )
calibrate /dev/sda1 00:00:01 ( SUCCESS )
<i>path: /dev/sda1 (partition)
start: 2048
end: 1953523711
size: 1953521664 (931.51 GiB)</i>

check file system on /dev/sda1 for errors and (if possible) fix them 00:00:00 ( SUCCESS )
***btrfs check '/dev/sda1'*** 00:00:00 ( SUCCESS )
<i>Opening filesystem to check...
Checking filesystem on /dev/sda1
UUID: efcf8c40-765b-44fb-99fa-ea78d16e0982
found 147456 bytes used, no error found
total csum bytes: 0
total tree bytes: 147456
total fs tree bytes: 32768
total extent tree bytes: 16384
btree space waste bytes: 140455
file data blocks allocated: 0
referenced 0</i>

<i>[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)</i>

grow file system to fill the partition 00:00:00 ( SUCCESS )
***mkdir -v /tmp/gparted-gS3ymp*** 00:00:00 ( SUCCESS )
Created directory /tmp/gparted-gS3ymp

***mount -v -t btrfs '/dev/sda1' '/tmp/gparted-gS3ymp'*** 00:00:00 ( SUCCESS )
<i>mount: /dev/sda1 mounted on /tmp/gparted-gS3ymp.</i>

***btrfs filesystem resize 1:max '/tmp/gparted-gS3ymp'*** 00:00:00 ( SUCCESS )
<i>Resize device id 1 (/dev/sda1) from 931.51GiB to max</i>

***umount -v '/tmp/gparted-gS3ymp'*** 00:00:00 ( SUCCESS )
<i>umount: /tmp/gparted-gS3ymp unmounted</i>

***rmdir -v /tmp/gparted-gS3ymp*** 00:00:00 ( SUCCESS )
Removed directory /tmp/gparted-gS3ymp


Please :slight_smile:

  • Format terminal output (including your garuda-inxi) as a code block by clicking the preformatted text button (</>) , or put three tildes (~) above and below the text
1 Like

how to post html document

I have deleted all snapshot on source disk then clone via Clonezilla then it works without error, One thing i found that source disk has some smart error, Garuda should provide migration tools so we could do it easily.

1 Like

That was likely the cause of errors then. Keep using the 1tb, when you’re sure that one is good wipe and reformat the 250mb (I hope that will mark defective sectors not to be used again) and use it only for not important things (e.g. downloads, moving files from one computer to another, not any personal documents nor backups).
Sorry to say it’s probably giving up the ghost, the good news is that you likely saved your stuff just in time.
hard drive - How to quickly format a HDD with bad sectors (in linux)? - Super User

1 Like

how to post html document?

You post the html syntax.

Mark the text,
Ctrl + C
and then insert here with
Ctrl + V
Looks like this :arrow_down:

GParted Details

GParted 1.6.0

configuration --enable-libparted-dmraid --enable-online-resize

libparted 3.6

========================================

|Device:|/dev/sda|
| --- | --- |
|Model:|ATA CT1000MX500SSD1|
|Serial:|2204E602AF4E|
|Sector size:|512|
|Total sectors:|1953525168|
||
|Heads:|255|
|Sectors/track:|2|
|Cylinders:|3830441|
||
|Partition table:|msdos|
||

|Partition|Type|Start|End|Flags|Partition Name|File System|Label|Mount Point|
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
|/dev/sda1|Primary|2048|1953523711|||btrfs|||

========================================

|Device:|/dev/sdb|
| --- | --- |
|Model:|ATA KINGSTON SA400S3|
|Serial:|50026B778234A630|
|Sector size:|512|
|Total sectors:|468860015|
||
|Heads:|255|
|Sectors/track:|2|
|Cylinders:|919333|
||
|Partition table:|msdos|
||

|Partition|Type|Start|End|Flags|Partition Name|File System|Label|Mount Point|
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
|/dev/sdb1|Primary|2048|450402085|boot||btrfs||/, /home, /root, /run/BtrfsAssistant/21552d5d-e026-4b4a-a2a8-ab97d6cbccde, /srv, /var/cache, /var/log, /var/tmp|
|/dev/sdb2|Primary|450402086|468857024|swap||linux-swap|swap||

========================================

Check and repair file system (btrfs) on /dev/sda1** 00:00:01 ( SUCCESS )
calibrate /dev/sda1 00:00:01 ( SUCCESS )
<i>path: /dev/sda1 (partition)
start: 2048
end: 1953523711
size: 1953521664 (931.51 GiB)</i>

check file system on /dev/sda1 for errors and (if possible) fix them 00:00:00 ( SUCCESS )
***btrfs check '/dev/sda1'*** 00:00:00 ( SUCCESS )
<i>Opening filesystem to check...
Checking filesystem on /dev/sda1
UUID: efcf8c40-765b-44fb-99fa-ea78d16e0982
found 147456 bytes used, no error found
total csum bytes: 0
total tree bytes: 147456
total fs tree bytes: 32768
total extent tree bytes: 16384
btree space waste bytes: 140455
file data blocks allocated: 0
referenced 0</i>

<i>[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)</i>

grow file system to fill the partition 00:00:00 ( SUCCESS )
***mkdir -v /tmp/gparted-gS3ymp*** 00:00:00 ( SUCCESS )
Created directory /tmp/gparted-gS3ymp

***mount -v -t btrfs '/dev/sda1' '/tmp/gparted-gS3ymp'*** 00:00:00 ( SUCCESS )
<i>mount: /dev/sda1 mounted on /tmp/gparted-gS3ymp.</i>

***btrfs filesystem resize 1:max '/tmp/gparted-gS3ymp'*** 00:00:00 ( SUCCESS )
<i>Resize device id 1 (/dev/sda1) from 931.51GiB to max</i>

***umount -v '/tmp/gparted-gS3ymp'*** 00:00:00 ( SUCCESS )
<i>umount: /tmp/gparted-gS3ymp unmounted</i>

***rmdir -v /tmp/gparted-gS3ymp*** 00:00:00 ( SUCCESS )
Removed directory /tmp/gparted-gS3ymp
1 Like

I noticed before, when pasting text that looks like a table (TAB characters) it gets converted into a markdown table (and then html) by the forum software.
Sometimes helpful and sometimes annoying.
For instance (fish syntax):

pacman -Ss linux-zen |sed -E 'N;s/\n +/\t/' |column -tL -s\t -o\t
extra/linux-zen 6.7.9.zen1-1 [installed] The Linux ZEN kernel and modules
extra/linux-zen-docs 6.7.9.zen1-1 Documentation for the Linux ZEN kernel
extra/linux-zen-headers 6.7.9.zen1-1 [installed] Headers and scripts for building modules for the Linux ZEN kernel
|extra/linux-zen 6.7.9.zen1-1 [installed]        |The Linux ZEN kernel and modules|
|---|---|
|extra/linux-zen-docs 6.7.9.zen1-1               |Documentation for the Linux ZEN kernel|
|extra/linux-zen-headers 6.7.9.zen1-1 [installed]|Headers and scripts for building modules for the Linux ZEN kernel|

No html involved, just a table with tabs.

2 Likes

yes i am using Fish shell

not the problem, that is just an example to show what happens when pasting text that contains TAB characters, I think that was the reason for the strange formatting.
I specified it’s fish syntax because POSIX shells like bash would use $'\t' for a TAB.


Beware one thing if/when you wipe the old drive: if it’s close to end of life, that may well be its last breath. I think it’s better than it failing unexpectedly, but I just remembered I should warn about the chance.

Thanks for the concern, I ll remain watchful. Another thing I came to know after cloning my 1 tb SDD 27gb left un-formatted when i am trying resize the disk the system not getting boot UUID error

I forgot details, but to resize sda1 the swap would have to be moved to the end of the disk first, leaving the unallocated space in between (next to sda1 to the right that is).

Yes, resizing may change some UUID, in case the fix is easy but this is where I don’t know for sure… and I don’t want to give bad advice.
If no one else responds I’ll look at it tomorrow, now I’m tired and my brain does not work.

Screenshot_2024-03-12_09-19-21
Screenshot_2024-03-12_09-19-07
Screenshot_2024-03-12_09-18-16

I have tried to move SWAP partition i am getting above error then finally i have created new swap portion and delete older one, how to use un allocated space i have tried but failed with error UUID then i have to start over restoration process using clonezilla.

A few months ago, I cloned Garuda under a live system
From a 500GB HDD to a 500GB SSD. With the help of DD.
sudo dd if=/dev/sdx of=/dev/sdy bs=64K conv=noerror,sync status=progress
(HDD detached, SSD attached, and gpt partition table created on it.)