USB Flash Drive – How to Recover Data from a Crashed Drive

I was just going to comment with this, but ran out of room...

USB flash drives are very poor for random access read and write unless you specifically purchase a USB flash drive for speed. You'd know if you had a 'fast' USB thumb drive since you probably would have paid two or three times more for it. This versus this. 70MB/s & 39MB/s versus 155MB/s & 150MB/s.

The real issue is that the USB 2.0 port on the Macbook Air maxes out. The theoretical maximum data rate in USB 2.0 is 480 Mbit/s (60 MB/s) per controller and is shared amongst all attached devices. So even if you get a 150MB/s USB drive, you'll top out at around 60MB/s.

Summary

Boot into Linux (Live or installed) and run sudo grub-install /dev/sdX where sdX is the file connected to your USB drive. To find the location of your USB drive use sudo parted -l or sudo fdisk -l ^[1] (I am not sure how this will work with UEFI firmware)

Main

My issue was I have a portable USB hard drive that I use for backups. I set my BIOS to first boot from USB because, sometimes I have to boot a live OS image from USB. When I would reboot my system, the system would try to boot the portable hard drive and hang.

• First, I tried clearing the boot flag of the partition. The boot flag had no effect as most modern boot loaders are indifferent to it and it is mostly used by legacy OS's.^[2]
• Second, I tried zeroing out the first 446 bytes of the USB drive in the hopes that the BIOS would see nothing and just move on to the next drive.^[3] Turns out the BIOS does not work that way. As near as I can tell, you (the user) set your boot order in the BIOS config. If the BIOS detects media where you told it to look, it will "connect" to the device, copy the first sector (512 bytes) into ram and start executing code. If the area is zeroed out the machine will just hang.
• Finally, I tried the method detailed in the summary section. grub-install was able to find all of my OS's and now I do not have to unplug the USB to boot.

---

[1] https://askubuntu.com/q/180023
[2] https://unix.stackexchange.com/a/23588/183350
[3] The first sector (512 bytes) is the Master Boot Record (MBR). The MBR has two sections: the Master Partition Table and the Master Boot Code. The Master Boot Code goes from byte 0-446 and contains the code that the system will use to boot the specified partition. Bytes 447-512 contain the actual partition table. If this is damaged or zeroed the system may not be able to read the partitions. http://www.dewassoc.com/kbase/hard_drives/master_boot_record.htm
[4] https://unix.stackexchange.com/questions/259143/how-does-grub-stage1-exactly-access-load-stage-2