I can't boot up the pc after i restored (for test) the backup just created. Hardisk has 4 partition:
/dev/sdb1
/dev/sdb2 ext2
/dev/sdb4 jfs
/dev/sdb3 swap
It looks like the restore OS has kernel issue for your hardware or something related to Linux kernel. Did you restore the image to different hardware? If so, maybe you have to upgrade the kernel. You can try to boot into the so-called safe mode with boot parameters like "noapic acpi=off.." to upgrade the system.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I backed it up > shutdown the pc > restored it for test. With the disk unformatted, restoring the backup made me the ability to mount it but gave me errors about a sort of "stale" (or sthale i don't remember) filesystem. So i decided to erase the disk and retry to restore the backup. After that the partition is not mountable because is corrupted.
The JFS partition is corrupted /dev/sdb4 even if i try to mount in different way ("too many inodes bad superblock" and other error like this when try to fsck.jfs), seems that the backup stage or restore stage in clonezilla has a problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes the PC it's all ok. Now i don't care about that backup because i'm doing a new fresh install of gentoo linux.
However, even in the actual new scheme partition (ext4 instead of jfs) errors occours. I try doing backup with acronis true image boot cd 2014 and it complains about incorrect closed filesystem and can proceed only in raw mode.
Then, conscious of this error message i re-run clonezilla but this way i forced to check filesystem consistency in expert mode; so the fsck stage finds and fix some errors on the ext4 partition maybe due to incorrect unmounting\shutdown gentoo. Each shutdown on gentoo brings to these errors.
Maybe is a problem in how gentoo handle the shutdown process.
The old JFS partition may has the same problem and it was backed up in an inconsistent way without repair the filesystem before the backup. I do not have time to retry again but should be this problem!!
However, problem solved with forced filesystem check mark in clonezilla during the backup stage. The restore stage works as well.
You can mark as SOLVED, or you can suggest to make default option to check filesystem consistency before use partclone.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
https://forums.gentoo.org/viewtopic-t-1078560.html?sid=04e457193af450b559935643de1b8e1b
I can't boot up the pc after i restored (for test) the backup just created. Hardisk has 4 partition:
/dev/sdb1
/dev/sdb2 ext2
/dev/sdb4 jfs
/dev/sdb3 swap
This is the log "clonezilla-img" that is saved into the destination folder:
https://paste2.org/mtUve196
This is the kernel panic error:
Kernel panic - not syncing: Requested init /bin/bb failed (error -116).
CPU: 0 PID: 1 Comm: swapper Not tainted 4.12.12-gentoo #1
Hardware name: /761-686B(KG7), BIOS 6.00 PG 03/06/2003
Call Trace:
dump_stack+016/0x1a
panic+0x81/0x19f
? rest_init+0x60/0x60
kernel_init+0x8b/0xf0
ret_from_fork+0x19/0x24
Kernel Offset: 0x6200000 from 0xc1000000 (relocation range: 0xc0000000-0xf7ffdfff
---[ end Kernel panic - not syncing: Requested init /bin/bb failed (error -116).
random: crng init done
It looks like the restore OS has kernel issue for your hardware or something related to Linux kernel. Did you restore the image to different hardware? If so, maybe you have to upgrade the kernel. You can try to boot into the so-called safe mode with boot parameters like "noapic acpi=off.." to upgrade the system.
Steven
No. Same machine!
I backed it up > shutdown the pc > restored it for test. With the disk unformatted, restoring the backup made me the ability to mount it but gave me errors about a sort of "stale" (or sthale i don't remember) filesystem. So i decided to erase the disk and retry to restore the backup. After that the partition is not mountable because is corrupted.
The JFS partition is corrupted /dev/sdb4 even if i try to mount in different way ("too many inodes bad superblock" and other error like this when try to fsck.jfs), seems that the backup stage or restore stage in clonezilla has a problem.
Maybe it's a hardware issue? Did you try to do a memtest for that machine?
Steven
Yes the PC it's all ok. Now i don't care about that backup because i'm doing a new fresh install of gentoo linux.
However, even in the actual new scheme partition (ext4 instead of jfs) errors occours. I try doing backup with acronis true image boot cd 2014 and it complains about incorrect closed filesystem and can proceed only in raw mode.
Then, conscious of this error message i re-run clonezilla but this way i forced to check filesystem consistency in expert mode; so the fsck stage finds and fix some errors on the ext4 partition maybe due to incorrect unmounting\shutdown gentoo. Each shutdown on gentoo brings to these errors.
Maybe is a problem in how gentoo handle the shutdown process.
The old JFS partition may has the same problem and it was backed up in an inconsistent way without repair the filesystem before the backup. I do not have time to retry again but should be this problem!!
However, problem solved with forced filesystem check mark in clonezilla during the backup stage. The restore stage works as well.
You can mark as SOLVED, or you can suggest to make default option to check filesystem consistency before use partclone.
Thanks for your feedback. We hesitate to enable fsck by default because it will change the source file system, and we have to be careful about that.
Steven