Problems using an externe SSD M2 for backups with encryption

Hi,

I want to use an external SSD (NVMe) for backups with rsync. I want the backup to be encrypted. This is causing more problems than I expected.

I tried it several times with different setups. I formated the ssd with the Yast2-Partitioner. I tried ext4, btrfs und xfs. No problems.

I started the backup process with rsync. Sometimes, the process stops after a few seconds with “broken pipe” and a read-only device. Sometimes it stops when I look into the filesystem with dolphin (dolphin freezes). With ext4 the backups process was very slow. It stops very often for a few moments. I have read that this could be a problem with the journal (commit).

Just now, I tried a backup with ext4 (without encryption), same problem. When I look into a directory everything freeze again. rsync stops (without exit).

When reconnecting the ssd to the computer I am not able to mount the ssd again:

Beim Zugriff auf „953,8 GiB Wechselmedium“ ist ein Fehler aufgetreten, die Meldung lautet: Ein nicht genauer angegebener Fehler ist aufgetreten: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

I tried a different usb-cabel. Maybe the external m.2-body is defect?

Thanks for all hints
Kay

I tried to create a backup with robocopy (Windows 10 in a VM (VMWare)), no problems. I’m not sure this is a hardware problem.

Maybe a problem with rsync? I use the following command:

rsync -avh --delete --info=progress2 /mnt/Daten/digikam /run/media/kay/Volume/                                                                                      

I doubt that very much. rsync is just an application program that in the end only does read and write commands for which it uses the kernel. I assume it must be something “below” it. Like kernel or hardware (as you already tried to attack o the hardware level).

How do you mount your external drive to /run/media/kay/Volume/?

On the same physical SSD?

Show the full output of dmesg after the problem happens. Upload to the https://paste.opensue.org/

Via KDE or Dolphin. It mounts the SSD automatically.

Yes.

I get the same error as above when I connect the ssd now with NTFS. No error messages in dmesg.

When I try to start the Yast2-Partitioner I get the following error messages:
https://paste.opensuse.org/pastes/4c6ca0add8d9

Now, I will format the disk with ext4 and try to reproduce the error with rsync.

You said “NVMe” and the log is full of USB errors. Are you sure you are working with the correct device?

So, here is the full log.

https://paste.opensuse.org/pastes/0757381cf960

rsync ended with

         39,74G  85%  835,48kB/s    2:09:11  rsync: [receiver] write failed on "/run/media/kay/ffcd48be-e0e8-418a-ba1e-0606990f2d2f/digikam/2008/09/21/DSCF0179.jpeg": Read-only file system (30)
rsync error: error in file IO (code 11) at receiver.c(381) [receiver=3.4.1]

rsync: [sender] write error: Broken pipe (32)

So, I’m not sure, what you mean. The SSD (m.2) is the original ssd from my notebook in an external usb-box. It is connected via USB-C.

I already ordered a new external usb-box. It will arrive on monday or tuesday.

The errors are the same.

Which you never mentioned before.

And when you used it with Windows - did you also use it in the external USB box?

Sorry, I wrote “external SSD”. Is there another way to connect other than USB? Yes, it is the same way. I only start VMWare and connect the SSD to the Windows-VM.

Try usb-storage instead of uas.

I tried to switch to usb-storage but the temporal solution doesn’t. When trying to remove the kernel module usb-storage I get the following error:

> sudo rmmod usb-storage                                               
rmmod: ERROR: Module usb_storage is in use by:rmmod: ERROR:  uasrmmod: ERROR:

Before trying the permanent solution I wait for the new external box.

It seems to have been a problem with this ugreen device. I ordered the same type again and had the same problems. With a different device (from a different manufacturer), I no longer have any problems.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.