Yesterday my pc started crashing and it was caused by trying to run a game, where it crashed trying to verify the game files and then my pc bluescreened and wouldn't boot. I was able to boot off my secondsry hard drive however the issue still persisted and my pc would bluescreen randomly. I have finally setup rescuezilla and now my progress bar stops at 0.26% and will not progress past "restoring parition 2" I made sure to check the box to ignore any errors and now it wont even progress. What can I do????? I am very stressed with work and life and i have no clue what im doing.
Cloning my main ssd drive to a new m.2 i just purchased solely because of this issue.
Rescuezilla's ability to clone more deeply-damaged disks is limited.
It's largely designed for backups to have been made when the disk was healthy to restore to.
There is a tool that is much more suitable to cloning deeply-damaged disks. It's called ddrescue. It's installed in Rescuezilla environment but it's not yet integrated into Rescuezilla graphical user interface.
It's a very very powerful and dangerous command that can easily blow away the wrong disk with a typo.
First close Rescuezilla, open GParted and identify the source and desitination drive names. Eg, /dev/sda and /dev/nvme0n1
Then open a terminal and run:
ddrescue --force /dev/sdX /dev/nvmeYnZ
(replacing X, Y anx Z)
It will make a perfect clone of your source disk onto your destination regardless of damage.
But it won't resize any partitions to best utilize your new disk (you'll need to do that with eg, GParted) after.
Then remove your source disk and boot from destination disk and see what happens. Worth running a filesystem check too (from Rescuezilla's environment) on your destination.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have done this and now the terminal is doing the same thing. I did see this error within gparted and think it may be the reason why? If this is whats causing it how can i fix this to try again? Side note, i assume if i do this and have any actual corrupted data i will lose it correct? that will suck but id rather have stuff missing than gone forever.
I recommend closing GParted once you have verified the partition names.
While the clone with ddrescue is ongoing the information GParted shows you is invalid and may interfere with the ddrescue clone.
i recommend not accepting any fixes GParted recommends on the source disk. Once the DDrescue clone completes you have a destination disk thats completely separate that you can file system check etc
If there is an internal error on your drive you can open a new Terminal and run dmesg -Tw before starting the clone. This will show you the damaged blocks as they are accessed.
Also ensure the disks have adequate fan cooling during the clone since to 1000s of gigabytes they can overheat and pause access to protect themselves.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the disk shown in gparted in my location disk, my source drive does not show this message which makes me think its not able to write to it. the terminal hasnt moved progress wise and the remaining time just keeps going up and is now at 108 days. this is only ~400 gigs of storage being moved to a new 1tb ssd.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
also nothing has told me to acceppt and fixes on gparted. this error was just here. Could it have because i formatted the drive before attempting this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
then it wll continue progress amd not restart the copy when you specify the same log file again.
but it generally should automatically skip and retry bad sectors without intervention so your source disk may be bad.
will analyze more after work
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2025-05-29
Thank you for all help. Trying this still has it saying 107 days, i know cloning an entire drive will take a while but this seems overkill... going to shut off for time being if i see no improvement.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yesterday my pc started crashing and it was caused by trying to run a game, where it crashed trying to verify the game files and then my pc bluescreened and wouldn't boot. I was able to boot off my secondsry hard drive however the issue still persisted and my pc would bluescreen randomly. I have finally setup rescuezilla and now my progress bar stops at 0.26% and will not progress past "restoring parition 2" I made sure to check the box to ignore any errors and now it wont even progress. What can I do????? I am very stressed with work and life and i have no clue what im doing.
Cloning my main ssd drive to a new m.2 i just purchased solely because of this issue.
Rescuezilla's ability to clone more deeply-damaged disks is limited.
It's largely designed for backups to have been made when the disk was healthy to restore to.
There is a tool that is much more suitable to cloning deeply-damaged disks. It's called
ddrescue. It's installed in Rescuezilla environment but it's not yet integrated into Rescuezilla graphical user interface.It's a very very powerful and dangerous command that can easily blow away the wrong disk with a typo.
First close Rescuezilla, open GParted and identify the source and desitination drive names. Eg,
/dev/sdaand/dev/nvme0n1Then open a terminal and run:
ddrescue --force /dev/sdX /dev/nvmeYnZ(replacing X, Y anx Z)
It will make a perfect clone of your source disk onto your destination regardless of damage.
But it won't resize any partitions to best utilize your new disk (you'll need to do that with eg, GParted) after.
Then remove your source disk and boot from destination disk and see what happens. Worth running a filesystem check too (from Rescuezilla's environment) on your destination.
I have done this and now the terminal is doing the same thing. I did see this error within gparted and think it may be the reason why? If this is whats causing it how can i fix this to try again? Side note, i assume if i do this and have any actual corrupted data i will lose it correct? that will suck but id rather have stuff missing than gone forever.
I recommend closing GParted once you have verified the partition names.
While the clone with ddrescue is ongoing the information GParted shows you is invalid and may interfere with the ddrescue clone.
i recommend not accepting any fixes GParted recommends on the source disk. Once the DDrescue clone completes you have a destination disk thats completely separate that you can file system check etc
If there is an internal error on your drive you can open a new Terminal and run
dmesg -Twbefore starting the clone. This will show you the damaged blocks as they are accessed.Also ensure the disks have adequate fan cooling during the clone since to 1000s of gigabytes they can overheat and pause access to protect themselves.
the disk shown in gparted in my location disk, my source drive does not show this message which makes me think its not able to write to it. the terminal hasnt moved progress wise and the remaining time just keeps going up and is now at 108 days. this is only ~400 gigs of storage being moved to a new 1tb ssd.
also nothing has told me to acceppt and fixes on gparted. this error was just here. Could it have because i formatted the drive before attempting this?
worth ctrl-c quitting the copy and trying again
oh one thing i should have mentioned is if you specify a log file
ddrescue --force /dev/sdX /dev/nvmeYnZ mylogfile.txtthen it wll continue progress amd not restart the copy when you specify the same log file again.
but it generally should automatically skip and retry bad sectors without intervention so your source disk may be bad.
will analyze more after work
Thank you for all help. Trying this still has it saying 107 days, i know cloning an entire drive will take a while but this seems overkill... going to shut off for time being if i see no improvement.
Should take no longer than a few hours, possibly even less.
Shut it off is fine. We cam tweak ddrescue options to skip over bad areas, dmesg.may give more information.
appreciate the help, looking forward to any ideas you may have
Any update on this?