[SOLVED] Need some help with clonezilla

My boot drive in my kde server machine MIGHT be the culprite of a occasional disk arm banging but not sure.
Here is my issue.
I boot to Live endeavour usb, clone disk to disk. Seems clonezilla must be built in, NICE
Shut down machine, disconnect old drive, move new drive to same sata port.<—
Boot, select the new drive as boot from the bios boot menu, but nothing happens.

Boot to live usb again, have a home/my name directory and a partimg directory.
With what I’ve read, things should be flat out cloned.

Do I need to fix the fstab file, rename a directory or something, etc?
Might be a few missing steps in the helps I’ve looked at idk
:Head explodes

I presume the partition on your new drive has a different UUID than the partition on the old drive, so yes, if you are using UUID to list the drives in fstab, it should be correct and match the drive you have plugged in.

In addition, if UUIDs change, then grub.cfg probably needs to be re-created.

Best way to do this from live usb?

> sudo grub-mkconfig -o /boot/grub/grub.cfg

edit -
uuids are same
tried from live usb

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

I get

/usr/bin/grub-prob: error: failed to get cononical path of ‘airootfs’

my disk is
sdb1 boot
sdb2 root
sdb3 swap
sdb4 home

so still stuck

1 Like

You would need to run the command in chroot.

I would reinstall the bootloader and regenerate grub.cfg.

Follow the instructions for your install mode UEFI or Legacy/MBR mode:

ok so I dont have btrfs or efi so I skip down to on the archroot page and do
sudo su
then
mount /dev/sdb1 /mnt
then
mount /dev/sdb1 /mnt/boot
it says /mnt/boot mnt does not exist
check
ls /home = liveuser

idk

idk what’s going on

From live session, could you post

sudo parted -l

?

[liveuser@eos-2020.05.08 ~]$ sudo parted -l
Model: ATA ST4000NC001-1FS1 (scsi)
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB ext4 Deadpool1

Model: ATA TOSHIBA MK6476GS (scsi)
Disk /dev/sdb: 640GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 525MB 524MB ext4
2 525MB 105GB 105GB ext4
3 105GB 109GB 3146MB linux-swap(v1)
4 109GB 640GB 532GB ext4

Model: ATA Hitachi HDS72101 (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 17.4kB 1000GB 1000GB ext4

Model: ATA SAMSUNG HD204UI (scsi)
Disk /dev/sdd: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 2000GB 2000GB ext4

Model: ATA WDC WD2002FYPS-1 (scsi)
Disk /dev/sde: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 2000GB 2000GB primary ext4

Model: ATA WDC WD2002FYPS-1 (scsi)
Disk /dev/sdf: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 20.5kB 2000GB 2000GB ext4 Deadpool2

Model: SanDisk Cruzer (scsi)
Disk /dev/sdm: 4000MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
2 84.0kB 67.2MB 67.1MB primary fat16 esp

Model: ATA ST4000NC001-1FS1 (scsi)
Disk /dev/sdg: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB ext4 Stormbreaker

[liveuser@eos-2020.05.08 ~]$

A bit confusing your disk setup.
You have a disk with GUID partition table (GPT).
Normally you would need to have an EFI System Partition (ESP) for booting in UEFI mode.
ESP can be placed anywhere in the disk.

However, it is possible to boot in Legacy/MBR mode on a GPT disk but then you would need a partition with no filesystem and flagged as bios_grub (see here)
I am not seeing any such partition on your disk :thinking:

My suggestion is, if your system supports UEFI boot mode, then create a EFI System Partition and use that as the location of the bootloader.

That is a little beyond me atm.
What is frustrating me is,
I installed EOS to a drive,
cloned EOS to another drive,
uuids are the same,
EOS should boot…
I did not have UEFI as an option when installing,
don’t think hardware supports it.
Other than maybe change boot drive option,
this is supposed to be simple and I don’t get why it’s not.

For me the only thing I can think of is to try the same thing but with a clonezilla live usb,
could this be the issue? Thoughts?

Perhaps some additional info could shed a little more light on the issue.

Connect your original disk with EnOS. Boot it up and post the output of the following commands:

test -d /sys/firmware/efi && echo UEFI || echo BIOS

lsblk -fs

sudo parted -l

cat /etc/fstab

Copy the output from terminal, paste it in your reply, highlight it and press Ctrl-E to format.

Hopefully this will give forum members some more idea on your set up leading to a solution.

$ test -d /sys/firmware/efi && echo UEFI || echo BIOS
BIOS
$ lsblk -fs
NAME FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                         0   100% /var/lib/snapd/snap/core/13308
loop1
     squash 4.0                                                         0   100% /var/lib/snapd/snap/core/13425
loop2
     squash 4.0                                                         0   100% /var/lib/snapd/snap/core18/2409
loop3
     squash 4.0                                                         0   100% /var/lib/snapd/snap/core18/2538
loop4
     squash 4.0                                                         0   100% /var/lib/snapd/snap/core20/1581
loop5
     squash 4.0                                                         0   100% /var/lib/snapd/snap/core20/1587
loop6
     squash 4.0                                                         0   100% /var/lib/snapd/snap/ngrok/50
loop7
     squash 4.0                                                         0   100% /var/lib/snapd/snap/ngrok/53
sda1 ext4   1.0   Deadpool1  8ccbf74d-318e-4770-9193-b8d4014797cb      2T    38% /run/media/major/Deadpool1
??sda
                                                                                 
sdb1 ext4   1.0   boot       58299366-4c3a-444b-92e0-fef7cb71ed1a  323.3M    26% /boot
??sdb
                                                                                 
sdb2 ext4   1.0   root       7a72f96e-f38b-4991-b8ee-1d8954823bd7   56.5G    36% /
??sdb
                                                                                 
sdb3 swap   1                19426e66-b2ac-476b-b08b-4e97b4cdcdef                [SWAP]
??sdb
                                                                                 
sdb4 ext4   1.0   home       c25629d3-f90d-4eda-8caa-22e6f47ce79b  261.8G    22% /home
??sdb
                                                                                 
sdc1 ext4   1.0   InfinityGem
                             8f01ab83-0666-44b3-b5b9-7baec4071460  387.5G    53% /run/media/major/InfinityGem
??sdc
                                                                                 
sdd1 ext4   1.0   Cosmic_Cube
                             dd8e0dd8-aee2-452e-9b3d-ba373a6c11ed    1.3T    21% /run/media/major/Cosmic_Cube
??sdd
                                                                                 
sde1 ext4   1.0   Asteroid_M 2769cac4-9616-41f8-a84c-286aba9ece7c    1.6T     8% /run/media/major/Asteroid_M
??sde
                                                                                 
sdf1 ext4   1.0   Deadpool2  b472f25d-0805-474a-ad5c-8e2c139b2795    1.1T    33% /run/media/major/Deadpool2
??sdf
                                                                                 
sdg1 ext4   1.0   Stormbreaker
                             55d147d6-f2ff-473c-b156-8371f7c3f584    1.7T    47% /run/media/major/Stormbreaker
??sdg
                                                                                 
sdh                                                                              
sdi                                                                              
sdj                                                                              
sdk                                                                              
sdl                                                                        
      
$ sudo parted -l
[sudo] password for major: 
Model: ATA ST4000NC001-1FS1 (scsi)
Disk /dev/sda: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name       Flags
 1      1049kB  4001GB  4001GB  ext4         Deadpool1


Model: ATA TOSHIBA MQ01ABD0 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name  Flags
 1      1049kB  525MB  524MB   ext4
 2      525MB   105GB  105GB   ext4
 3      105GB   109GB  3146MB  linux-swap(v1)
 4      109GB   500GB  392GB   ext4


Model: ATA Hitachi HDS72101 (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      17.4kB  1000GB  1000GB  ext4


Model: ATA SAMSUNG HD204UI (scsi)
Disk /dev/sdd: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2000GB  2000GB  ext4


Model: ATA WDC WD2002FYPS-1 (scsi)
Disk /dev/sde: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  2000GB  2000GB  primary  ext4


Model: ATA WDC WD2002FYPS-1 (scsi)
Disk /dev/sdf: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name       Flags
 1      20.5kB  2000GB  2000GB  ext4         Deadpool2


Model: ATA ST4000NC001-1FS1 (scsi)
Disk /dev/sdg: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name          Flags
 1      1049kB  4001GB  4001GB  ext4         Stormbreaker


$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=58299366-4c3a-444b-92e0-fef7cb71ed1a /boot          ext4    defaults,noatime 0 2
UUID=7a72f96e-f38b-4991-b8ee-1d8954823bd7 /              ext4    defaults,noatime 0 1
UUID=c25629d3-f90d-4eda-8caa-22e6f47ce79b /home          ext4    defaults,noatime 0 2
UUID=19426e66-b2ac-476b-b08b-4e97b4cdcdef none swap defaults 0 0
UUID=8ccbf74d-318e-4770-9193-b8d4014797cb /run/media/major/Deadpool1 ext4 defaults,rw,relatime,data=ordered 0 0
UUID=b472f25d-0805-474a-ad5c-8e2c139b2795 /run/media/major/Deadpool2 ext4 defaults,rw,relatime,data=ordered 0 0
UUID=2769cac4-9616-41f8-a84c-286aba9ece7c /run/media/major/Asteroid_M ext4 defaults,rw,relatime,data=ordered 0 0
UUID=8f01ab83-0666-44b3-b5b9-7baec4071460 /run/media/major/InfinityGem ext4 defaults,rw,relatime,data=ordered 0 0
UUID=dd8e0dd8-aee2-452e-9b3d-ba373a6c11ed /run/media/major/Cosmic_Cube ext4 `Preformatted text`defaults,rw,relatime,data=ordered 0 0
UUID=55d147d6-f2ff-473c-b156-8371f7c3f584 /run/media/major/Stormbreaker ext4 defaults,rw,relatime,data=ordered 0 0`Preformatted text`

OK, marking solved.

Turns out trying actual Clonezilla Live usb made a difference like I was wondering.
Instead of the builtin version of clonezilla on live Endeavour USB
Made Clonezilla Live ISO USB, cloned disk to disk, power off swith drive places, boot flawless as far as I can tell.

Thankyou @pebcak and anyone else who helped.

1 Like

You got it sorted out! That’s great to hear!
Enjoy your EnOS in its new home!
:enos_flag:

Marking a post as solved is different here.
There is no need to change the post title. You select the post that solved the issue, click the 3 dotted lines and click on the solution button. It will help the forum software for users searching similar issue in the future.

1 Like

I used to do that, but someone made a comment when I marked my own post as solution.

that is better than what you have done now, it serves no purpose and doesn’t close the thread. If you mark a solution, the forum automatically closing the thread and the thread shows up in search results both here and on other web engines.

In our forum you mark the post that solves the issue as the solution, and in most cases that isn’t your own post.

2 Likes

Were you trying to run clonezilla before from the installed disk?

Edit: Oh i see you ran it from the EndeaourOS live usb installed on it i assume?

Yes it was on the live Endeveour USB, and thats the other part to this if someone uses the built in version to clone a boot drive in my case this could cause a perplexing glitch.

Having said that, my ISO, according to file date was made 5-7-20
So an older iso, so idk if that could be a thing or not, just adding the info.
According to package list clonezilla 3.35.2-2

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.