Corrupted SSD - what to check it with?

[FlailAway]

Ubuntu 16.04, i5, 256SSD, 6GB. I run BIT each night backing up to a 128GB SSD and let it shut the computer down when done. Been perfect for a looong time. This morning I came in and it was still running stuck at "Taking Snapshot" I looked at the backup-SSD and apart from backups it shows

last snapshot ... 5 items new snapshot ... 1 item

I thought I would just delete the "new snapshot" and run it again. When I tried to delete the "new snapshot," I get an error "trying to delete xxxx.pdf, no such file.

If I navigate to the "new snapshot" and follow through the contained folders, it shows the xxxx.pdf and I can open it OK.

What can I use to check this SSD? I tried using fsck but it returns "this appears to be a folder..." or something close to that.

I need help with this as I am way out of my depth here. :)

[glyndon]

What filesystem is on the SSD? If you can unmount it, try fsck again. e.g., fsck /dev/sdx1 or fsck -f /dev/sdx1 (if the first command says it's 'clean' and does nothing else) Let us know what it says.

In the above, substitute the proper letter and partition number for 'x1' (you can determine those using sudo parted -l which will list your disks and their partition tables.

[colinl]

If the data on the disc is important then before you do anything else make an image backup of it or at least copy off any critical data. Trying to recover may make it worse if the SSD is faulty or at the end of its life.

[FlailAway]

Thanks for the quick replies, much appreciated. The SSD is Veracrypt encrypted and them mounted so it appears in the "media" folder as "/medial/VCrypt2/", probably why fsck says it's a folder.

I actually have a mirror image of it a few days older, but thanks for mentioning. I tried to copy off the last backup (of 27 on the SSD) but it seems to think that every backup on there is the full complement of files and therefore tries to copy off 27 backups of 30GB each = 810GB, when in actual fact there is only 30GB of total files.

As mentioned, a little out of my depth at this level. :)

[glyndon]

I'm not familiar with Veracrypt. Some of those tools create an emulated filesystem that can be integrity-checked, either using a tool included with the crypto system, or a regular one, depending on how it emulates the filesystem. Check its manual for how to check the integrity of one of its volumes.

On Wed, Oct 24, 2018 at 2:56 PM FlailAway notifications@github.com wrote:

Thanks for the quick replies, much appreciated. The SSD is Veracrypt encrypted and them mounted so it appears in the "media" folder as "/medial/VCrypt2/", probably why fsck says it's a folder.

I actually have a mirror image of it a few days older, but thanks for mentioning. I tried to copy off the last backup (of 27 on the SSD) but it seems to think that every backup on there is the full complement of files and therefore tries to copy off 27 backups of 30GB each = 810GB, when in actual fact there is only 30GB of total files.

As mentioned, a little out of my depth at this level. :)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bit-team/backintime/issues/940#issuecomment-432785517, or mute the thread https://github.com/notifications/unsubscribe-auth/AH88XEN7h3lE0an7oJ8BdKiPc0u9Tug4ks5uoLf3gaJpZM4X4IH1 .

-- Gary Dobbins

[FlailAway]

OK, thanks for your suggestions.

[Germar]

First of all please dismount the volume in Veracrypt and create an image of the encrypted SSD so you won't loose data if something goes wrong

dd if=/dev/sdX1 of=/path/to/ssd_backup.img

where /dev/sdX1 is your SSD device. You always choose that device in Veracrypt when you click on Select Device

Then you need to mount the volume in Veracrypt and find out the device name of the decryted drive

mount | grep /media/VCrypt2

The device name is the first column. Something like /dev/mapper/veracrypt1. Now dismount the filesystem and check it with fsck

sudo umount /media/VCrypt2
sudo fsck /dev/mapper/veracrypt1

where /dev/mapper/veracrypt1 is the device name from above