Difference between revisions of "Bootable Linux USB stick"
|Line 169:||Line 169:|
==== Low-level formatting of (micro)SD cards ====
==== Low-level formatting of (micro)SD cards ====
In a SD slot, <code>blkdiscard /dev/
In a SD slot, <code>blkdiscard /dev/</code> initializes the card.
==== Low-level formatting of other USB sticks ====
==== Low-level formatting of other USB sticks ====
Revision as of 14:44, 25 January 2018
We regularly and successfully use USB sticks for courses where participants bring their own notebooks. The big benefit is that students learn Linux, and realize that they can easily use the hardware they already own. Current notebook hardware is by far fast enough for data processing, structure solution and coot visualization. What we found:
- the sticks should be fast USB3 (very good results with SANdisk Extreme 32GB or bigger; physically small sticks like Kingston DataTraveler look nicer but are slow). The computers do not have to be recent, nor do they have to have USB3 ports. USB2 ports support up to 30MB/s, but only USB3 sticks deliver this! With a bit of tuning (below) the stick feels as fast as a local harddisk.
- we use Fedora (FC23 and higher) because its hardware support is very good. We always use the 64bit distro.
- The stick can be booted on MacBooks as well (press the
altkey at the boot sound); their hardware works well with Fedora. For Windows clients (press F11 or F12 or sometimes F9 or F10 for the boot menu; if that does not work press F2 or DEL for the BIOS menu and change the boot order), one has to make sure that "fast boot" (or "fast startup") is disabled (or Shift is pressed while shutting Windows down), and sometimes
powercfg -H off(as Administrator in a console window) is additionally required; otherwise the USB stick may not boot. Occasionally we find a computer that does not boot from the stick because the BIOS screen can not be reached (due to unknown BIOS password; happens with machines belonging to institutions which administer them centrally) or some such, but 19 out of 20 work as they should.
- if the WiFi does not work out-of-the-box on MacBook Pro, connect temporarily to the Internet by other means (ethernet cable, WiFi via USB key, tether to your phone via Bluetooth), become root, and install the latest kernel and tools with
dnf install -y akmods kernel kernel-devel broadcom-wl --best --allowerasing. After installing, reboot into the new kernel.
- we just install CCP4 and whatever else we need (XDS, Phenix, Chimera, ..), and then dd or ddrescue (on a machine with USB3 ports) an image of that stick to all other sticks.
- any number of bells and whistles could be added to this, like clients sending their hostnames to a server after booting, and accepting updates by rsync.
To make students familiar with the sticks and how to boot them, one needs 30+ minutes and a few tutors.
Some more details
- we always create a few-GB FAT32 partition because that makes file exchange with Windows and Macs very simple. The FAT32 partition should be the first partition on the stick; 2GB is enough for us. Then comes a biosboot partition (1MB; required for booting bios system from a GPT disk), an efi partition (e.g. 250MB; required for UEFI/EFI boot on PC's/MAC's) and the Linux partition, with 13.9GB, so that the sum of the four partitions is slightly below 16GB. The third partition is then a 16.1GB /data partition. This scheme has the advantage that the image of the stick can just as well be copied (with dd or better ddrescue) to a 16GB stick; the /data partition then does not fit and cannot be used on that stick, but the operating system will then work on the small stick just as well. This requires that the /data partition is not fsck'ed automatically from /etc/fstab (0 in the 6th field).
- it is a good idea to give easy root access to the one user you create because certainly some packages will have to be installed or updated when the stick is in use
- it is a good idea to save an image of the stick whenever you made a successful change; otherwise you might need to start from scratch if you mess something up.
- (if the installation not already does it for you) you should label the partitions and use the labels for mounting the partitions in /etc/fstab, alternatively use UUID's; don't use /dev/sda1 or the like because depending on the hardware it is booted on, after booting the stick, and depending on the actual hardware, the stick may be /dev/sdb or /dev/sdc or ... !
How to create a bootabled GPT-partitioned USB-stick with Fedora
This will create a USB stick capable to
- EFI boot on Macs
- UEFI boot on PCs
- BIOS boot on newer hardware (legacy boot / CSM enabled in BIOS)
- BIOS boot on medium aged hardware
- not boot on really old BIOS hardware which doesn't support booting from GPT (see below)
GPT partition the stick using
The example shows a 32 GB Sandisk Extreme:
Part 1: +1G VFAT (0700) (Windows needs it to be the first partition) Part 2: +1M BIOSBOOT (ef02) Part 3: +250M EFI (ef00) Part 4: +13500M / (0083) Part 5: +15000M /mnt/data (0083)
For performance, make sure that the big partitions are aligned to 8192-sector boundaries; gdisk default is 2048-sector boundaries - the default can be adjusted. If you use the above sizes and the + sign for specifying them, this happens to work out automatically.
install Fedora on an UEFI machine (UEFI enabled ; LegacyBoot / CSM disabled)
Note: in the following, whenever you see the X in sdX, you must fill in the appropriate drive letter (e.g. a or b or c or d or ...).
sdX3: efi /boot/efi sdX4: ext4 / sdX5: ext4 /mnt/data
Not much to say about the installation of programs (CCP4 ?, Phenix ?, XDS ?, ...?). You should also install the
- hfsplus-tools RPM to access Mac harddisks,
- fuse-exfat RPM to access exFAT SD cards,
- binutils RPM to get the "strings" and other useful GNU commands,
- atop, a better top; lbzip2, a parallel bzip2; xxdiff, a diff GUI; nedit, editor
- tcsh RPM to allow installation of CCP4.
dnf -y install tcsh xterm tk qt-x11 xxdiff atop nedit lbzip2 hfsplus-tools binutils
adjust the USB-stick for UEFI/EFI boot (before reboot from chroot environment)
chroot to the installed system:
install Fedora updates:
dnf -y update # Fedora's dnf is successor to yum
configure grub2 for (U)EFI systems:
- disable auto recognition of other installed Operating systems (specific to current computer), and
- update grub2-efi.cfg
echo 'GRUB_DISABLE_OS_PROBER=”true”' >> /etc/default/grub grub2-mkconfig -o /etc/grub2-efi.cfg
(last step automatically puts UUID's to recognise the boot device in grub2-efi.cfg ; default after fresh Fedora installation is the device name which might be different on another computer)
Performance tuning (not strictly required):
We use ext4 filesystems and
data=writeback,nobarrier in /etc/fstab. To be able to set these options also on the / filesystem, we use tune2fs to set both as default mount options on a Linux machine where the stick (dev/sdX) is just plugged in (i.e. not booted from):
tune2fs -o journal_data_writeback,nobarrier /dev/sdX4 tune2fs -o journal_data_writeback,nobarrier /dev/sdX5
create & label vfat filesystem:
mkfs.vfat /dev/sdX1 dosfslabel /dev/sdX1 VFAT
shutdown or reboot:
exit systemctl poweroff (or reboot for testing)
Install grub2 for BIOS boot (from chroot environment)
boot Fedora Live DVD on a BIOS machine and chroot to the stick:
mount /dev/sdX4 /mnt mount -o bind /dev /mnt/dev mount -t proc /proc /mnt/proc mount -t sysfs /sys /mnt/sys chroot /mnt
install grub2 for BIOS boot and configure it:
rm /boot/grub2/grubenv grub2-install /dev/sdX grub2-mkconfig -o /etc/grub2.cfg
(on UEFI systems /boot/grub2/grubenv is a symlink to /boot/efi/EFI/fedora/grubenv (from package grub2-efi.rpm). The symlink has to be removed before grub2-install can finish successfully, it automatically creates a new file /boot/grub2/grubenv (as in package grub2.rpm)
check /etc/grub2.cfg and if needed, change at all positions: “linuxefi” to “linux16”, and “intrdefi” to “intrd16”
generating images and copies of the stick
Save a compressed disk image - we use the parallel gzip program called pigz:
pigz -c < /dev/sdX > usbstick.img.gz
(time: ~180 secs speed: ~175MB/s, size of image: 1.8 GB) write compressed image back to a stick:
unpigz -c < usbstick.img.gz > /dev/sdX
(speed: ~ 98MB/s)
For creation/maintainance a bunch of sticks, a multiple port USB-HUB is a very usefull tool. E.g. the Raid Sonic Icy Box IB-AC6113 accepts 12 Sandisk Extreme sticks at once (port 7 has to stay empty due to spatial restrictions) and all 12 stick are recognized by the OS (CentOS7).
Cheap USB sticks can hold a lot of data, but when it comes to writing small files (which happens when used as the operating system disk), they are either slow from the beginning, or their write performance quickly degrades as soon as free space becomes low for the first time. We have been using CrystalDiskMark (Windows) for characterizing USB media: as a rule of thumb, the "Random write 4k blocks" disciplines should result in at least 1 MB/s, and for sequential writes the numbers should be >50 MB/s. However, CrystalDiskMark does not capture the effect of degrading write performance, which can only be mitigated by TRIMming the media - a feature that few USB sticks support (see below).
The following is about performance and durability of the USB media. If you don't know what TRIM is and how it relates to flash media, read this.
types of USB media
The suitability of the media makes a notable difference, in particular when the operating system or CCP4 is upgraded, or when e.g. a new Phenix version is installed.
- very good: USB sticks that support TRIM. The ones known to us are the Sandisk Extreme USB sticks bought before 2017 (e.g. SDCZ80-032G 32GB for ~22€ or SDCZ80-064G 64GB for ~40€; unfortunately, these are no longer available, at least not at reasonable prices). These sticks are very fast (CrystalDiskMark scores >10MB/s for random 4K writes). The successor are the differently-named current (2018) Sandisk Extreme Pro USB sticks, but only 128 and 256 GB models exist, and they are expensive. There exist also fast and big, but costly Mushkin USB sticks which support TRIM. USB sticks which support TRIM also usually support S.M.A.R.T., which is useful for detecting problems.
- good: we have verified that a USB3 adapter with (micro)SD card (separate items) is suitable. USB3 adapters are cheap (around 5€ at Amazon, like https://www.amazon.de/EX1-Kartenleser-Micro-Karte-Adapter/dp/B06XX3T219; cheaper at Ebay). microSD cards usually come with a SD adapter, and can be TRIMmed (but only in a SD slot; see below!). microSD cards ideally should be in the Class 1 (A1) application performance class since this is what is defined as requirement for use as extended operating system disk in Android smartphones. 64GB A1 microSD cards cost around 25€. In practice, slightly cheaper non-A1 microSD cards also seem to work well, but may be slower and may require more often TRIMming. The price/performance ratio of the microSD/USB3 combination is very good.
- acceptable: USB sticks that do not support TRIM but are fast and high quality, e.g. Sandisk Extreme Go or Sandisk Ultra bought 2017 and later. However, their write performance may degrade with time (or rather, with the number of writes to a partition), and not much can be done about that.
- inacceptable: tiny sticks like Sandisk Ultra Fit become hot, degrade fast and are unreliable. Cheap sticks are usually just too slow.
The drawback of the "good" solution above is: from time to time (e.g. once every week), a knowledgeable person may want to
- remove the microSD card from the USB3 adapter
- insert it into the SD adapter, and that into a SD slot - it is usually auto-mounted by the operating system
- run the
fstrim -v /mount/pointcommand (this takes a few seconds)
- unmount the card, and revert steps 2. and 1.
This naturally begs the question whether it wouldn't be much smarter to not use an USB adapter for microSD cards, but rather just use the SD adapter in a SD slot right away. That would have advantages - the SD card vanishes in most SD slots which is better than an USB stick sticking out,
fstrim works, and possibly the SD controller is faster than the USB3 controller (depending on the notebook model). However, we tried to boot a microSD card in a SD lot and found that it doesn't boot, whereas it does boot in an USB adapter. Thus, setup of a microSD card for booting in SD slot needs to be investigated.
TRIMming informs the firmware about blocks of the filesystem that do not contain file data. This is available for USB sticks for which
hdparm -I /dev/sdX returns "Data Set Management TRIM supported".
wiper.sh script (part of the
hdparm source distribution) TRIMs ext3/ext4/xfs filesystems, but does not reproducibly seem to work for our preferred SanDisk Extreme 32GB stick if the filesystem is mounted. This is probably due to the fact that this stick has a limitation of max 65536 blocks in one TRIM command (https://sourceforge.net/p/hdparm/bugs/63/). Since
wiper.sh also works for unmounted filesystems, and the mapping of unused space is then obtained with a different tool, one should try with an unmounted filesystem as well - this worked for us in all cases tried so far (tested with this script).
All other methods, like the
fstrim command and the
discard mount option do not work for USB sticks, because the usb-storage kernel module does not pass the ATA TRIM command through the USB bridge and controller to the device. The same goes for
These support TRIM when in a SD slot, but not when inserted in a USB adapter. When in a SD slot, the
lsblk -D command reveals that the card can be TRIMmed, and
fstrim -v /dev/mmcXXXXX works.
fill empty space of a partition with “zeroes”
This could be done after updating the software or data on the USB media, and before saving and compressing an image of it.
USB sticks that support “Deterministic read data after TRIM” according to
hdparm -I /dev/sdX, and microSD cards (which have zeroes in free space after
fstrim in a SD slot) should be TRIMmed because this does not wear out the storage cells.
Other media: as root
dd if=/dev/zero of=/mountpoint_of_partition/delete.me bs=10M # this will stop when filesystem is full rm /mountpoint_of_partition/delete.me
However, this stresses the flash cells; they sustain only a limited number of write cycles.
initializing the media
Low-level formatting restores the write performance, and removes any sensitive information (e.g. passwords) - important for workshops.
Low-level formatting of "very good" USB sticks
hdparm's (ENHANCED) SECURITY ERASE initializes the whole stick in a few seconds, and restores it to an almost factory-fresh condition, including zeroing the device. This works on all sticks where
hdparm -I /dev/sdX reports "supported: enhanced erase" but if used wrongly (e.g. on the wrong device, or with the wrong options, or ...) it may brick your device, or delete valuable data! So use at your own risk:
- check if
hdparm -I /dev/sdXreports "supported: enhanced erase" and "not frozen" (to unfreeze a frozen diks, suspend your system with
pm-suspendand wake it up again)
- set disk password, and erase it (which unsets the password):
hdparm --user-master u --security-set-pass Eins /dev/sdX hdparm --user-master u --security-erase-enhanced Eins /dev/sdX
If you tried with --security-erase-enhanced, but the disk does not support it, then an error will occur and the disk will still be locked after the failed command, and you will not be able to write anything to it! If this happens, you can unlock it with
hdparm --user-master u --security-unlock Eins /dev/sdX
Low-level formatting of (micro)SD cards
In a SD slot,
blkdiscard /dev/mmcblk0pX initializes the card.
Low-level formatting of other USB sticks
One may try to write zeroes on the whole stick
dd if=/dev/zero of=/dev/sdX bs=8192k
hoping that the firmware will understand this as a request for low-level formatting. This seems to work with some sticks, but takes a long time and may stress the flash cells.