Security concern with disk encryption in case of repair

While trying to migrate from a 1TB to a 2TB SSD; the cloning with clonezilla failed at 99% and the new SSD is not visible by any OS anymore.

As it’s brand new I was thinking to send it to repair, but what is the data cloned are still there and readable? Can a technician access the data from the bitcoin node? Worst, if it’s ending up as refurbished, can someone restore the data and get my bitcoin keys from it?

Ok, encrypted drives will do this but don’t panic. Most encrypted drives can’t be copied with clonezilla and have to do it the slow binary copy with Linux.

first make a boot usb with ubuntu 24.04LTS

shut down the computer, unplug the 2TB, then turn the computer back on, then shut it down again

then insert the drive, the ubuntu USB, turn it on, go to bios, you should see the drive, go to your boot override and boot the usb or exit out of bios and boot the Ubuntu usb, exit out of setup which will get you a desktop then open a terminal window (ctrl+alt+t)

find your drive by using the lsblk command. the nvme drive should be there as it will be labeled nvme0n2 or something like that.

lsbkl -a

now we have to set a root password for the live disk on 24.04Lts

passwd root

Now drop into a terminal TTY (ctrl +F2)

login as root and the password you just made

then after that, we binary clear the drive:

dd if=/dev/zero of=/dev/nvme0n2 bs=10M status=progress 

several hours later, we continue
After that, we can copy the drive.

find the 1TB drive

lsblk -a

Then copy it. I’ll use sda for an example which is the first SATA drive

dd if=/dev/sda of=/dev/nvme0n2 bs=1M status=progress

This takes forever, but it will be copied.

1 Like

Thanks for the detail support, I did boot on a USB Kubuntu (I had it on hand) but not sure why it’s necessary, I could do it directly from my main Kubuntu.

I did the command: lsblk -a (not lsbkl, you did a typo) but it’s not showing the new SSD drive. That’s why I think it’s fryed somehow. At least the LED of the SSD is ON when I plug it, but I don’t find anyway to see the drive again.

I ordered a new SSD, M2 with an M2 enclosure, I think it’s safer than these T7 thing from Samsung that are completely proprietary on the hardware.

My plan is to recover the node, close all channels, move all funds, then I will send this SSD for repair without the risk that someone access my keys.

Or do you think it’s over-paranoid and the disk should be safe to send for repair without any risk for leak of keys and sensible information?

I doubt anything happen to the M.2 module, I have had usb to m.2 enclosure go out w/o notice like that.

Its better to run M.2 drives on a m.2 slot on the motherboard or even in a card slot is even better.

I also had M.2 to usb work for a little while, then they crap out, but still work with other M.2 drives.

Sorry it was maybe not clear, the issue is with a Samsung T7 external USB-C SSD, the inside look like this: https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcSw2rM404QYAbhvbk7VYpyQVYIwJZqUAUp74g&usqp=CAU

So it’s impossible to mount it anywhere else. That’s why I think my only option is sending for repair.

I seeing people are having issues with this drive when I searched on the internet, and its associated with the connector on it only using one side/set of pins and burning up the cable. So I would try a different cable and rotate one connector side if it doesn’t work.

I tried the USB-C to USB-C cable, in all 8 possible positions (yes they are 8 with USB-C…) and the USB-C to USB-A in both way. Both cable works with the older Samsung T7 1TB that I have currently with my Umbrel install. I even try other cables laying around, on desktop and laptop computer, Linux Ubuntu, Clonezilla and Windows, the T7 2TB SSD is never seen.

I received another M2 Crucial 2TB SSD + ugreen M2 enclosure with aluminum casing ans thermal paste for heat dissipation. I will use your procedure to clone the old SSD to the new one.

Now the original question was never answered. What is the risk of accessing the bitcoin private keys and other sensible information from the Umbrel SSD for someone that get access to the SSD but without the Umbrel user password, nor the SD card?

very high risk. I would consider the wallet not usable anymore and transfer all of the coins out to a different wallet before sending it in. If its under a warranty.

OK thanks for the confirmation that’s I’m not paranoid. I will keep this faulty SSD on the side until I migrated my node entirely.

I now started your method to duplicate to the new SSD I just bought. I did the zero writing first but not sure it was truely necessary if there was not failed writing before like in my initial case. But anyway, it’s not as long as you mention, I’m 1/3 in after 10min. The real copy might take overnight however.

After the copy, what should I do to extend the new SSD to 2TB? or will it already have the full space available?