If you have a potentially (probably) dying SSD with BTRFS on it, would you rather:1.
-
If you have a potentially (probably) dying SSD with BTRFS on it, would you rather:
1. Try to copy out data first
2. Try to use BTRFS repair utilities first, and then try to copy dataFor reference this is from a used Thinkpad X390 which lately has been running extremely slowly and now not being able to boot properly (not reaching login screen). btrfs check found some errors (but FS was in use), UEFI diagnostic found no errors with the disk nor other hardware.
-
If you have a potentially (probably) dying SSD with BTRFS on it, would you rather:
1. Try to copy out data first
2. Try to use BTRFS repair utilities first, and then try to copy dataFor reference this is from a used Thinkpad X390 which lately has been running extremely slowly and now not being able to boot properly (not reaching login screen). btrfs check found some errors (but FS was in use), UEFI diagnostic found no errors with the disk nor other hardware.
@met Always make a copy first, if you care about the data. Make a copy of the entire disk with DD.
-
If you have a potentially (probably) dying SSD with BTRFS on it, would you rather:
1. Try to copy out data first
2. Try to use BTRFS repair utilities first, and then try to copy dataFor reference this is from a used Thinkpad X390 which lately has been running extremely slowly and now not being able to boot properly (not reaching login screen). btrfs check found some errors (but FS was in use), UEFI diagnostic found no errors with the disk nor other hardware.
Some further details: I was able to login to root using a TTY. It took several minutes to open the TTY and log in, and every command would freeze the computer for a while. Didn't notice anything disk related in dmesg. This is where I ran btrfs check mentioned in OP. Did not try to do startx or something as I assumed this was a disk related error.
Lenovo UEFI diagnostics for disk, memory, CPU and motherboard all passed without errors, although the disk test was very slow (>10 hours).
-
@met Always make a copy first, if you care about the data. Make a copy of the entire disk with DD.
@deshipu OK. Do you recommend some particular flags for dd? I've only ever used it to flash OS installers to USB sticks. Any reason to use dd over rsync?
-
@deshipu OK. Do you recommend some particular flags for dd? I've only ever used it to flash OS installers to USB sticks. Any reason to use dd over rsync?
@met Defaults should be fine. You use it the other way around than with the usb stick here, copy from the disk to a file. Then you can mount that file with a loop device, and do things to it like with normal disk. The reason to copy the entire disk instead of individual files is that then you can try various different recovery tools on it, and keep an unmodified backup, so even if some tool proves to be destructive, you can still go back and try something else. Obviously it takes time and space.
-
@met Defaults should be fine. You use it the other way around than with the usb stick here, copy from the disk to a file. Then you can mount that file with a loop device, and do things to it like with normal disk. The reason to copy the entire disk instead of individual files is that then you can try various different recovery tools on it, and keep an unmodified backup, so even if some tool proves to be destructive, you can still go back and try something else. Obviously it takes time and space.
@deshipu Makes sense. Thanks for the detailed advice!
-
undefined oblomov@sociale.network shared this topic
-
If you have a potentially (probably) dying SSD with BTRFS on it, would you rather:
1. Try to copy out data first
2. Try to use BTRFS repair utilities first, and then try to copy dataFor reference this is from a used Thinkpad X390 which lately has been running extremely slowly and now not being able to boot properly (not reaching login screen). btrfs check found some errors (but FS was in use), UEFI diagnostic found no errors with the disk nor other hardware.
@met 3. Make a bitwise image of the disk
-
@met 3. Make a bitwise image of the disk
@met (to work on for fixes, days extraction and anything similar)