How to switch over from SD-card to USB-attached device (USB thumbstick, USB enclosed SSD or HDD, etc.) to have more durable storage option.
-
Connect USB device to your RPI
-
Make sure USB device visible by the system
sudo fdisk -l sudo lsblk
Usually
mmcblk0
is your SD-card, andsda
,sdb
,sdX
are attached USB devices, in my case it wassda
. Make sure there is no sensitive data stored on the target USB device. If it's new USB device there should be no partitions reported byfdisk
for it. You may want to clean target device usingsudo sfdisk --delete /dev/sda
(be very careful, it will delete everything on your target device) -
Install
rpi-clone
git clone https://github.com/billw2/rpi-clone.git cd rpi-clone sudo cp rpi-clone rpi-clone-setup /usr/local/sbin sudo rpi-clone-setup -t $(hostname -s) sudo rpi-clone -s
-
Clone SD-card to USB device
sudo rpi-clone sda # replace sda here with your device name
This may take some time depending on how much data you have, storage performance, running applications, clients connected, etc. During the process few questions will be asked, read carefully and answer. On the last step where it's asked to examine mounted clone run another connection to RPI, keep existing intact.
If you've accidentally skipped it just remount it manually:
sudo mount /dev/sda6 /mnt/clone/boot
.sudo mount /dev/sda7 /mnt/clone
-
Identify partitions
Target device will have the same partitions layout as in source device. We need to find out
boot
and last partition ids.sudo lsblk -o name,mountpoint,size,partuuid /dev/sda6 # clone of mmcblk0p6 mounted as /boot sudo lsblk -o name,mountpoint,size,partuuid /dev/sda7 # clone of mmcblk0p7 mounted as / or root
Write down
PARTUUID
column, in my case these were3b4344a4-06
forboot
and3b4344a4-07
for root partition respectively -
Change
cmdline.txt
To be able to boot from the target device we have to change
cmdline.txt
file:- change
root=/dev/mmcblk0p7
toroot=PARTUUID=3b4344a4-07
which is the root partition id - append at the end of the line
rootdelay=5
option to wait while attached device is initialized at boot time
Complete example:
console=serial0,115200 console=tty1 root=PARTUUID=3b4344a4-07 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait rootdelay=5
If you'll try to boot without this change you'll get endless
Waiting for root
message.Note: there is one interesting caveat, if you'd like to use LABEL or UUID instead of PARTUUID you must create initramfs/initrd file, hence additional step will be required. Do not use PARTUUID with initrd.
If you're going to use PARTUUID then you don't need this step (I repeat, skip it and follow the next step).
- make sure
root=
set to something likeroot=LABEL=USB-ROOT
cd /mnt/clone/boot/
- generate initrd file with
mkinitramfs -o initrd.sda
- append
initramfs initrd.sda followkernel
afterrootdelay=5
Complete example:
console=serial0,115200 console=tty1 root=LABEL=USB-ROOT rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait rootdelay=5 initramfs initrd.sda followkernel
- change
-
Change
fstab
After the boot process has been completed we would need to mount correct partitions.
Open
/mnt/clone/etc/fstab
and do the following:- change device
/dev/mmcblk0p6
toPARTUUID=3b4344a4-06
(remember to use your own id) - change device
/dev/mmcblk0p7
toPARTUUID=3b4344a4-07
(remember to use your own id)
Complete example:
proc /proc proc defaults 0 0 PARTUUID=3b4344a4-06 /boot vfat defaults 0 2 PARTUUID=3b4344a4-07 / ext4 defaults,noatime 0 1
- change device
-
Unmount
Now return back to the initial terminal where we've left
rpi-clone
process open and hit enter to unmount all partitions. Make sure you don't have the second terminal open somewhere at the mounted paths. -
Test
Shutdown RPI with
sudo shutdown -h now
, disconnect PSU, unplug SD card, plug PSU in, verify
A couple of notes on the above:
Make sure you have your boot order set correctly BEFORE you start the steps listed. This can be done with raspi-config utility, though that doesn't show what your current boot order settings are. You'll want to set your boot order to be USB-MSD first, followed by SD-CARD as a backup. I ended up using a utility called rpi-eeprom-mgr, to both update the bootloader to the latest stable version and to confirm the desired boot order. The utility is discussed here, and can be downloaded from there too:
https://forums.raspberrypi.com/viewtopic.php?t=283347
After updating the BOOTLOADER EEPROM, you should get a display like this in rpi-eeprom-mgr:
And if you've successfully changed your boot order, you can confirm that in rpi-eeprom-mgr:
Reboots are required after each one of these changes, and also after the:
in Step #2 above, if your USB Flash drive has been previously partitioned.
The
cmdline.txt
referenced in Step #6 is somewhat ambiguous, as there are two such files after running rpi-clone. I modified the one under /mnt/clone/boot, as this is the file that will be used when booting from the new USB drive. I did not need to modify anything under /mnt/clone/etc/fstab as the PARTUUID entries were already correct.Everything seems to be working fine, after completing this process. I do get a brief error message on the console now:
This does not appear to be an issue, and the only solutions I've found involve flashing the USB drive from scratch and re-loading everything -- which I'd very much prefer not to do.
For reference, I'm using an RPi4 8GB board with the Raspberry Pi OS (64-bit) -- originally the Lite version, but updated later with Desktop. USB 3.1 flash drive is a 256GB Samsung Fit Plus.