[SOLVED] Kali Linux 'dd: error writing /dev/sdb: no space left'
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kali Linux 'dd: error writing /dev/sdb: no space left'
Hello,
So I'm trying to make a live USB for Kali Linux and I was just about to put the ISO for Kali on the USB until I got this error.
"dd: error writing '/dev/sdb:': No space left on device
1978+0 records in
1977+0 records out
1036660736 bytes (1.0 GB, 989 MiB) copied, 27.7732 s, 37.3 MB/s"
My USB is 16 GB and the Kali ISO is only 3. Is there anyway to fix this?
I'm very new to this, so please explain it in as much detail as you can while still remaining in Layman's terms.
Please post the output of "fdisk -l" as root.
Also, what was the dd command that you used?
Also, if you're new to Linux, you shouldn't be using Kali. Even Kali's developers say that it's not for people new to Linux. It's for security professionals who already know exactly what they're doing.
Last edited by suicidaleggroll; 01-24-2017 at 06:03 PM.
Please post the output of "fdisk -l" as root.
Also, what was the dd command that you used?
Also, if you're new to Linux, you shouldn't be using Kali. Even Kali's developers say that it's not for people new to Linux. It's for security professionals who already know exactly what they're doing.
Yes I know that its very difficult, but I only have one specific thing I have to do on it and then I wont use it again. But thats not important, the output i got was
If it is plugged in, it's either not sdb (maybe that's your DVD drive?) or it's gone wrong.
You also have an extra : when setting the output file on the dd command
Quote:
The EXACT command i used was dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb: bs=512k
should be
Code:
The EXACT command i used was dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
That means your dd command probably created a new file in /dev called sdb: and filled it up until your /dev ran out of free space.
Try unplugging your USB drive then running 'dmesg -c' to print and clear dmesg. Then plug the USB drive back in and run 'dmesg' and see what it says. It should show that you have plugged in a USB storage device and tell you what partitions are on it.
Last edited by af7567; 01-24-2017 at 07:00 PM.
Reason: the bold : didn't really stand out in the quote
sounds like the drive is not formatted properly, and the system cannot see the actual size of it. have you used this device for another ISO? if so, then you need to format it again, double check that it reports the correct size then try the command again
If it is plugged in, it's either not sdb (maybe that's your DVD drive?) or it's gone wrong.
You also have an extra : when setting the output file on the dd command
should be
Code:
The EXACT command i used was dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
That means your dd command probably created a new file in /dev called sdb: and filled it up until your /dev ran out of free space.
Try unplugging your USB drive then running 'dmesg -c' to print and clear dmesg. Then plug the USB drive back in and run 'dmesg' and see what it says. It should show that you have plugged in a USB storage device and tell you what partitions are on it.
Well, how could i check if its my dvd drive? And Im not sure how it could have gone wrong, i followed the instructions to the tee without error. And how can i delete that file? I also cleared all the partitions on it before this. Thats what the instructions said to do. Ill let you know what happens when i run dmesg.
sounds like the drive is not formatted properly, and the system cannot see the actual size of it. have you used this device for another ISO? if so, then you need to format it again, double check that it reports the correct size then try the command again
Formatting a device has nothing to do with what you want to do. What you get that chance, run dmesg as described above. The device name (be it sdb, sdc, whatever) will be shown, for example, if I plug a drive into my port:
If it is plugged in, it's either not sdb (maybe that's your DVD drive?) or it's gone wrong.
You also have an extra : when setting the output file on the dd command
should be
Code:
The EXACT command i used was dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
That means your dd command probably created a new file in /dev called sdb: and filled it up until your /dev ran out of free space.
Try unplugging your USB drive then running 'dmesg -c' to print and clear dmesg. Then plug the USB drive back in and run 'dmesg' and see what it says. It should show that you have plugged in a USB storage device and tell you what partitions are on it.
When I ran the revised command I should have done, it just says that directory doesnt exist.
If it is plugged in, it's either not sdb (maybe that's your DVD drive?) or it's gone wrong.
You also have an extra : when setting the output file on the dd command
should be
Code:
The EXACT command i used was dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
That means your dd command probably created a new file in /dev called sdb: and filled it up until your /dev ran out of free space.
Try unplugging your USB drive then running 'dmesg -c' to print and clear dmesg. Then plug the USB drive back in and run 'dmesg' and see what it says. It should show that you have plugged in a USB storage device and tell you what partitions are on it.
I couldnt post the output i got the first time I ran dmesg -c because it exceeded the amount of characters, but this was the output I got with the USB plugged in using dmesg.
Code:
[ 388.508243] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 388.841175] usb 1-1: New USB device found, idVendor=0781, idProduct=5575
[ 388.841183] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 388.841187] usb 1-1: Product: Cruzer Glide
[ 388.841190] usb 1-1: Manufacturer: SanDisk
[ 388.841192] usb 1-1: SerialNumber: 20043512301B01803B24
[ 388.978711] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 388.981028] scsi host3: usb-storage 1-1:1.0
[ 388.981278] usbcore: registered new interface driver usb-storage
[ 388.996652] usbcore: registered new interface driver uas
[ 389.994105] scsi 3:0:0:0: Direct-Access SanDisk Cruzer Glide 1.27 PQ: 0 ANSI: 6
[ 389.996103] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 390.018961] sd 3:0:0:0: [sdb] 30316544 512-byte logical blocks: (15.5 GB/14.5 GiB)
[ 390.033505] sd 3:0:0:0: [sdb] Write Protect is off
[ 390.033515] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 390.051196] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 390.144847] sdb:
[ 390.212902] sd 3:0:0:0: [sdb] Attached SCSI removable disk
Last edited by SilentJustice; 01-24-2017 at 09:10 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Kali Linux 'dd: error writing /dev/sdb: no space left'
