Hi, Luis Speciale wrote: > > unmountDisk /dev/disk1 > > sudo dd if=./debian-9.1.0-amd64-netinst.iso of=/dev/disk1 bs=1m
Dominique Dumont wrote: > Shouldn't that be: > sudo dd if=./debian-9.1.0-amd64-netinst.iso of=/dev/disk bs=1m The "1" in "disk1" seems to be the equivalent to our "a" in "sda": http://osxdaily.com/2016/08/09/find-disk-id-device-node-identifier-mac/ http://cdn.osxdaily.com/wp-content/uploads/2015/11/diskutil-list-find-disk-id-identifier-mac.jpg In general i doubt that the way of copying to USB stick is to blame, because Luis came to GRUB installing, which happens from the running GNU/Linux, afaik. More technical, the Debian amd64 ISOs have their MBR from ISOLINUX file "isohdpfx.bin" without "partok" feature (= MBR file "isohdppx.bin"). I.e. it would not boot ISOLINUX and then a Linux kernel if it sat in a partition with nonzero offset from the device start. http://www.syslinux.org/wiki/index.php?title=Isohybrid#MBR_selection If the machine boots via EFI, then it would not have found the partition table of the ISO which marks the EFI system partition. Regrettably i cannot say anything that would help Luis, but that the problem must be somewhere else. The message (is it literally that text ?) indicates that it could be related to program grub-update in the booted GNU/Linux. Have a nice day :) Thomas