On 09/26/2016 11:27 AM, Kevin Cummings wrote:
> On 09/25/16 22:15, fred roller wrote:
>> [root@Jehovah Downloads]# dd
>> if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M
>> dd: error writing '/dev/sda1': No space left on device
>> 32+0 records in
>> 31+0 records out
>> 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
>> Lawrence, for installing based on the information above try:
>> dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M
>> for your understanding... the "./" in front of the filename notes
>> location to the system as "in my current directory" but irregardless
>> illegal operand came from the space between the "=" and the
"F" in your
>> second attempt. The first failure of running out of space is because dd
>> was directed to a partition sda1. Also, be sure this is your usb drive,
>> my experience is that sda is usually the hard drive. Broken down sda1
>> is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices
> Err, ah, sd=scsi disk. A long time ago, the ATA drivers (and Serial ATA
> driver) were re-written to use the same SCSI disk interface as SCSI
> disks were using. And, as it turns out, USB disks too. Thus, we have
> no more "hd" disks (where the "hd" stood for "hard
disk"). Every disk
> is an "sd" these days.
>> sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the
>> device. With that try the following command WITHOUT the usb plugged in:
>> ls /dev/sd*
>> which should give you something like:
>> /dev/sda /dev/sda1 /dev/sda2 /dev/sda3
>> Then re-run the same command WITH the usb plugged in which should give
>> you something like:
>> /dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
>> This last letter to appear is the one you want and without the number.
>> So be REAL sure you have your usb device letter correct and:
>> dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M
>> will work.
>> If you want to easily understand the command line I suggest you go
>> through this quick course:
>> It is a great primer for understanding all we are talking about and can
>> be done in about an evening.
>> Caution: "dd" is an aggressive program so be sure of the variables
>> writing to in the "of=" parts of the command. Also, the
>> "status=progress" part is optional, lets you see your progress of the
I'd also recommend using a smaller block size--even though it will take
longer to do the operation. The actual block size of an ISO image is
2048 bytes (2KiB). However, as most ISO images are in multiples of 1MiB,
using a 1MiB block size gives you a cleaner operation (IMHO) and doesn't
put as much strain on your memory (a 1MiB buffer versus a 16MiB buffer).
I also tend to use "oflag=direct" for direct I/O rather than buffered.
Thus, my standard mechanism for this is:
dd if=/path/to/iso/image.iso of=/dev/sdX bs=1M oflag=direct
That uses a 1MiB block size. dd's use of multipliers can be odd, so
"man dd" to read up on those.
It's worked well for me. Your mileage may vary. Batteries not included,
But Rick, the OP was trying to dd into /dev/sda
How can it be that the system boots off of some disk that is not /dev/sda,
and /dev/sda is empty? and is a usb flash???
Also, why would the op get a message to the effect "disk is full"
when it is a 32GB flash?
My suspicion is that it is not a USB disk, and that it is a very old and
small IDE disk.