@@ -224,16 +224,6 @@ on the SD card is not edited after a clone to the SD card, see
224
224
examples 4 and 5.
225
225
226
226
#### 4) Creating a USB bootable disk for other than a USB enabled Pi3
227
- + Warning Note: I have to consider this example experimental because
228
- after doing it on a Pi using device names, /dev/sda1 was not mounted
229
- on /boot after the boot completed but syslog said it did mount.
230
- And after booting a "mount /boot" command worked so the fstab was right.
231
- So far I don't know where the problem is.
232
- In any case, if you do this example, check /boot after
233
- the USB boot to make sure it was mounted. This should not affect
234
- example 5 which works, but don't do example 5 until you are sure the
235
- USB boot has /dev/sda1 mounted on /boot.
236
-
237
227
rpi-clone can be used to create a SD card to USB boot setup and preserve
238
228
that setup when cloning from a USB boot back to the SD card slot.
239
229
With the SD card booted and a target USB disk plugged in and assuming
@@ -278,6 +268,11 @@ again, its cmdline.boot can be moved back to cmdline.txt.
278
268
+ If -l is not used, rpi-clone will not replace the currently booted SD card
279
269
cmdline.txt and it will need to be edited by hand for the USB boot to work.
280
270
271
+ + Also a caution note if fstab uses device names: check your
272
+ /boot to be sure it is mounted with /dev/sda1 after booting to USB.
273
+ I have a Pi where this fails even though syslog says it mounted.
274
+ Just be sure to check when you first do this and before you try example 5.
275
+
281
276
Now when the Pi is booted from SD card to USB and the SD card is no longer
282
277
in use, the SD card slot is available for cloning to.
283
278
0 commit comments