Update the software repositories and install Etcher using dnf package manager: $ sudo dnf update $ sudo dnf install balena-etcher-electron To add Etcher RPM repository on Fedora, RHEL and its clones like CentOS, AlmaLinux and RockyLinux, run: $ curl -1sLf '' | sudo -E bash To install Etcher on Solus, run: $ sudo eopkg it etcherĮtcher developers have also created repositories for Debian-based systems and RHEL-based systems. If you're using Arch Linux, you can install Etcher on Arch Linux using any AUR helper tools, for example Yay, like below: $ yay -S balena-etcherĮtcher is available in the default repositories of Solus. If you prefer to install Etcher using your Linux distribution's package manager, here is how to do it.Įtcher is available in AUR for Arch Linux and its variants. ![]() balenaEtcher-1.5.120-圆4.AppImage Install Etcher using Linux package managers Make it executable using command: $ chmod +x balenaEtcher-1.5.120-圆4.AppImage This will extract the Etcher zip file to Etcher AppImage format. $ unzip balena-etcher-electron-1.5.120-linux-圆4.zip ![]() Go to the location where you downloaded the Etcher zip file and unzip it. Since Etcher is an Electron application, installing Etcher is no big deal.ĭownload the latest Etcher edition from its website. Etcher is a cross-platform application that supports Linux, macOS and Microsoft Windows. No more accidental hard drive wiping! It can also directly flash Raspberry Pi devices that support USB device boot mode.Įtcher can able to write. It distinguishes the USB drives from the system partitions. The most important advantage of using Etcher is it will let you choose the correct flash drive and SD card and protects you from accidentally writing to your hard-drives. So you don't have to waste time writing images to corrupted drives or cards and wondering why your drive is not booting. ![]() It ensures every byte of data is correctly written to the intended drive. Etcher will validate the images written on the drive before finalizing the bootable drive. It can be used to enlarge or shrink an unmounted file system located on device. The resize2fs program will resize ext2, ext3, or ext4 file systems. The image will expand to any SD card on first boot using resize2fs just like on pi. You add what you need to the rootfs and then assemble a flashable image using that script. You can use Nvidia’s script called create-jetson-nano-sd-card.sh ( edit: this is now in the /tools/ folder and called jetson-disk-image-creator.sh) in the L4T install path to accomplish that. I need to get the zip compatible with balenaEtcher just like the JetPack original image. if we decided to go from 16GB to 32GB card it shouldn’t matter. The goal is to have image independent on the target SD card. I’d like to end up with a zip file, sized as the software contant rather than SD card size. The dd command is great for taking the image from the SD card. NOTE: You do not want to clone a mounted filesystem which might be written to during the clone. There isn’t much you can do about slow SD cards being slow. “dd” can be slow for production, but as mentioned the “bs” (block size) can speed things up somewhat. # Exit the mount area, else you cant unmount (umount): This would mount the clone for examination or editing: sudo mount -o loop clone_of_SD.img /mnt ![]() This would restore the image to the second SD card: sudo dd if=clone_of_SD.img of=/dev/mmcblk1 bs=512 (“bs” is block size, and isn’t critical, but can change how fast reads and writes go…512 is just the smallest block size of any disk, you could use a much larger value if it speeds things up) One could create a perfect bit-for-bit exact clone of the entire first SD via: sudo dd if=/dev/mmcblk0 of=clone_of_SD.img bs=512 SD cards tend to have a naming convention like “/dev/mmcblk0” (first SD) or “/dev/mmcblk1” (second SD), or “/dev/mmcblk0p1” (first partition of first SD). “lsblk -f” would give information about UUIDs and filesystem types of the whole list of detected block devices, “lslbk -f /dev/sda” would limit the response to the first SATA drive. “sda1” is the first partition of the first disk, “sda2” is the second partition of the first disk. …where “sda” is the first disk, “sdb” is the second disk, so on. If we were speaking of an ordinary SATA drive, then you would see entries from this: ls /dev/sd* The image can be loopback mounted and edited if desired (for example, a pure clone would have the same user accounts and passwords…perhaps you don’t want that…or if there was a network customization based on MAC address, then you’d need a new MAC address for each Jetson).Īs background, if you have a disk drive or other bulk storage device, then there will be a corresponding device special file for the disk (or SD card) as a whole, and for each partition. The “dd” tool can copy and restore exact images from one SD to another. If you are using Linux, then this is trivial.
0 Comments
|