No software detected. Please ensure your system is configured correctly.
No software detected. Please ensure your system is configured correctly.
Hey everyone - I'm facing some trouble with Clonezilla while trying to restore my SSD. I've made a backup of my OS (Mint 18.3 saved on an HDD) so I can experiment with other non-Linux systems. Recently, I attempted a partition copy from the bigger HDD back to the SSD. The backup is stored there, but after rebooting it shows "error 1962: no operating system found. Press any key to reboot sequence." This happened after I installed Windows 10 on the SSD and wiped it in Gparted to a clean EX4 format, just like before. Normally Clonezilla requires the source drive to be no larger than the target, but it can't copy data from a bigger drive to a smaller one. To work around this, I manually shrink the partition in Gparted after copying to the HDD so it fits without issues. It's been smooth until I wiped Windows 10, which now triggers the same error. The odd thing is that when I try to reinstall from a DVD, it says Mint is already installed and offers an option to install it next to the current version. It lists it as installed but doesn't boot properly, leaving me confused. (I chose partitions because my personal data is on a separate NTFS partition.)
Was das BIOS oder UEFI von der Herkunft? Bei einer üblichen UEFI-Installation erstellt Mint eine etwa 500 MB große FAT-Partition, die im Verzeichnis /boot/efi gespeichert wird und die Einrichtung des Bootloaders enthält. Falls Sie diese Sicherung nicht ebenfalls mit der Wurzelpartition gespeichert haben, müssen Sie sie neu erstellen und GRUB erneut installieren. Ich habe das persönlich durch die Antwort von IBBoard in diesem Forum erfolgreich gemacht.
Check if the backup covered all partitions. sda1 contains swap space and boot partition, yes. The option appears in a dropdown but isn't labeled with an sd(number)(letter) identifier.
The issue with boot sectors lies in their strict size requirements and starting position on the disk. If Clonezilla altered these settings during copying, your BIOS might lack a valid boot sector and won't recognize any partitions as bootable. Begin with a live Linux environment and run a partition listing to verify the boot partition appears at the start, is correctly marked, and functions properly. If it's absent or improperly configured, you'll need to rebuild the boot partition. For Windows installations, consider using built-in repair utilities; otherwise, adhere to standard Linux installation instructions to fix the boot partition.
I'm still trying to figure out what just occurred. I performed a DBAN operation on the SSD, then transferred the saved partition back to it from the HDD. It wouldn't boot initially. I attempted to reinstall GRUB using a Live CD but had no success. Eventually, I reinstalled Linux Mint 18.3. After rebooting, a GRUB menu appeared requesting multiple versions of the distro. I selected the second option, and everything worked—my files were restored. Everything is now identical to the original setup. (???) I suspect there might be a misunderstanding, but I'm open to feedback if I'm mistaken. When I first cloned the system in Clonezilla, I selected partition to partition and chose sda1, not realizing sda2 contained the extended and swap partitions. I couldn't boot into Mint because I only had sda1, missing the swap and extended space. When I reinstalled Mint, I chose to wipe the disk and start fresh. It seems a new extended partition with swap was copied onto my original sda1, restoring everything. My old Linux boots, but I have a fresh Mint installation on another partition that isn't showing in Gparted.
It might happen because you wiped the SSD, which isn't ideal. To begin fresh, use cfdisk to remove partitions and then apply "sudo mkfs.ext4 /dev/yourHDD" followed by reinstalling your OS.
I'm really confused here. The last time I tried to clone a drive, I went straight for the drive itself, not just partitions. I have an option now to clone the bootloader—please do it next time with a GPT partition instead of MBR so I won't run into problems later. Anyway, keep learning from your mistakes.