LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 01-24-2017, 09:13 PM   #16
goumba
Senior Member
 
Registered: Dec 2009
Location: New Jersey, USA
Distribution: Current: Debian and OpenSUSE. Past: Arch, RedHat (pre-RHEL). FreeBSD & OpenBSD novice, Hackintosh
Posts: 1,193
Blog Entries: 7

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335

Code:
dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
should work in your case, from that output.
 
Old 01-25-2017, 06:41 AM   #17
af7567
Member
 
Registered: Nov 2012
Posts: 208

Rep: Reputation: 69
From the output of that dmesg it shows that your USB drive has been detected and it is 16GB like you said, and it is sdb. It doesn't really matter about what was output with dmesg -c, that was just to clear the old data so you knew the only messages shown were to do with you plugging in the USB device.

With sdb being detected, as shown by dmesg then your command should work

Code:
dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
Make sure you are in the right directory so that the iso file can be found, or put the full path to it on the if option, eg:
Code:
dd if=/home/user/Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
 
Old 01-25-2017, 09:14 AM   #18
SilentJustice
LQ Newbie
 
Registered: Jan 2017
Posts: 23

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by goumba View Post
Code:
dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
should work in your case, from that output.
Nope, I still get the same error. What do I do now?
 
Old 01-25-2017, 09:15 AM   #19
SilentJustice
LQ Newbie
 
Registered: Jan 2017
Posts: 23

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by af7567 View Post
From the output of that dmesg it shows that your USB drive has been detected and it is 16GB like you said, and it is sdb. It doesn't really matter about what was output with dmesg -c, that was just to clear the old data so you knew the only messages shown were to do with you plugging in the USB device.

With sdb being detected, as shown by dmesg then your command should work

Code:
dd if=Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
Make sure you are in the right directory so that the iso file can be found, or put the full path to it on the if option, eg:
Code:
dd if=/home/user/Desktop/kali-linux-2016.2-amd64.iso of=/dev/sdb bs=512k
I tried that, and and it still didnt work. I got the exact same error.
 
Old 01-25-2017, 09:54 AM   #20
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,573

Rep: Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138
Are you sure the drive is good?
Could you post the output of fdisk -l now that the drive is being recognized?
 
Old 01-25-2017, 10:22 AM   #21
SilentJustice
LQ Newbie
 
Registered: Jan 2017
Posts: 23

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by suicidaleggroll View Post
Are you sure the drive is good?
Could you post the output of fdisk -l now that the drive is being recognized?
Im 100% certain the drive is good. I got it from best buy the same day I tried to make it bootable.

This is what the output came back to

Code:
Disk /dev/sda: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbecf30ae

Device     Boot    Start      End  Sectors Size Id Type
/dev/sda1  *        2048 79691775 79689728  38G 83 Linux
/dev/sda2       79693822 83884031  4190210   2G  5 Extended
/dev/sda5       79693824 83884031  4190208   2G 82 Linux swap / Solaris
 
Old 01-25-2017, 11:27 AM   #22
af7567
Member
 
Registered: Nov 2012
Posts: 208

Rep: Reputation: 69
fdisk -l might not show /dev/sdb because it doesn't have a partition table (dmesg showed that it has no partitions).

What does the ls command show you

Code:
ls -l /dev/sd*
With the USB plugged in I would expect something like

Code:
brw-rw---- 1 root disk 8,  0 Jan 25 11:45 /dev/sda
brw-rw---- 1 root disk 8,  1 Jan 25 11:45 /dev/sda1
brw-rw---- 1 root disk 8,  2 Jan 25 11:45 /dev/sda2
brw-rw---- 1 root disk 8,  4 Jan 25 11:45 /dev/sda5
brw-rw---- 1 root disk 8, 16 Jan 25 11:45 /dev/sdb
 
Old 01-25-2017, 11:31 AM   #23
SilentJustice
LQ Newbie
 
Registered: Jan 2017
Posts: 23

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by af7567 View Post
fdisk -l might not show /dev/sdb because it doesn't have a partition table (dmesg showed that it has no partitions).

What does the ls command show you

Code:
ls -l /dev/sd*
With the USB plugged in I would expect something like

Code:
brw-rw---- 1 root disk 8,  0 Jan 25 11:45 /dev/sda
brw-rw---- 1 root disk 8,  1 Jan 25 11:45 /dev/sda1
brw-rw---- 1 root disk 8,  2 Jan 25 11:45 /dev/sda2
brw-rw---- 1 root disk 8,  4 Jan 25 11:45 /dev/sda5
brw-rw---- 1 root disk 8, 16 Jan 25 11:45 /dev/sdb
This was the output:

Code:
brw-rw---- 1 root disk 8, 0 Jan 25 12:29 /dev/sda
brw-rw---- 1 root disk 8, 1 Jan 25 12:29 /dev/sda1
brw-rw---- 1 root disk 8, 2 Jan 25 12:29 /dev/sda2
brw-rw---- 1 root disk 8, 5 Jan 25 12:29 /dev/sda5
The USB was plugged in
 
Old 01-25-2017, 11:36 AM   #24
af7567
Member
 
Registered: Nov 2012
Posts: 208

Rep: Reputation: 69
Something is broken somewhere. Your dmesg output showed that the USB was definitely plugged in and was /dev/sdb, but /dev/sdb doesn't exist. If you check dmesg output again do you see anything saying about USB disconnected (even though it is still plugged in)? If you plug it in then immediately check "ls -l /dev/sd*" is it shown then? It could be a bad connection on the USB port.
 
Old 01-25-2017, 11:54 AM   #25
goumba
Senior Member
 
Registered: Dec 2009
Location: New Jersey, USA
Distribution: Current: Debian and OpenSUSE. Past: Arch, RedHat (pre-RHEL). FreeBSD & OpenBSD novice, Hackintosh
Posts: 1,193
Blog Entries: 7

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
Quote:
Originally Posted by af7567 View Post
fdisk -l might not show /dev/sdb because it doesn't have a partition table (dmesg showed that it has no partitions).
While it has no partitions, fdisk would still show the size of the device itself.

Last edited by goumba; 01-25-2017 at 11:55 AM.
 
Old 01-25-2017, 12:03 PM   #26
SilentJustice
LQ Newbie
 
Registered: Jan 2017
Posts: 23

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by af7567 View Post
Something is broken somewhere. Your dmesg output showed that the USB was definitely plugged in and was /dev/sdb, but /dev/sdb doesn't exist. If you check dmesg output again do you see anything saying about USB disconnected (even though it is still plugged in)? If you plug it in then immediately check "ls -l /dev/sd*" is it shown then? It could be a bad connection on the USB port.
No, nothing shows that its disconnected.
I quickly took out the usb then plugged it back in and ran the 1s -1 /dev/sd*. It actually showed up. This was the output:

Code:
brw-rw---- 1 root disk 8,  0 Jan 25 12:53 /dev/sda
brw-rw---- 1 root disk 8,  1 Jan 25 12:53 /dev/sda1
brw-rw---- 1 root disk 8,  2 Jan 25 12:53 /dev/sda2
brw-rw---- 1 root disk 8,  5 Jan 25 12:53 /dev/sda5
brw-rw---- 1 root disk 8, 16 Jan 25 12:56 /dev/sdb
and if it is bad connection, do I just change ports?
 
Old 01-25-2017, 12:05 PM   #27
suicidaleggroll
LQ Guru
 
Registered: Nov 2010
Location: Colorado
Distribution: OpenSUSE, CentOS
Posts: 5,573

Rep: Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138Reputation: 2138
goumba is correct, fdisk will still show the device information even if there is no partition table, the partition table is corrupt, etc.

Are you pressing an eject button or similar in your system? Some distros will actually eject the drive completely when you do that, so the only way for it to be recognized again is to unplug/replug it. Or is there anything else you're doing to the drive between plugging it in, showing us the dmesg output, running dd, and then running fdisk?

Maybe try unplugging it, plugging it back in, and then running fdisk -l. An I/O error during the dd dump might be causing the drive to disconnect itself.

Also - purchasing it new is absolutely no guarantee that it's good. Drives come DOA all the time.
 
1 members found this post helpful.
Old 01-25-2017, 12:36 PM   #28
SilentJustice
LQ Newbie
 
Registered: Jan 2017
Posts: 23

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by suicidaleggroll View Post
goumba is correct, fdisk will still show the device information even if there is no partition table, the partition table is corrupt, etc.

Are you pressing an eject button or similar in your system? Some distros will actually eject the drive completely when you do that, so the only way for it to be recognized again is to unplug/replug it. Or is there anything else you're doing to the drive between plugging it in, showing us the dmesg output, running dd, and then running fdisk?

Maybe try unplugging it, plugging it back in, and then running fdisk -l. An I/O error during the dd dump might be causing the drive to disconnect itself.

Also - purchasing it new is absolutely no guarantee that it's good. Drives come DOA all the time.
Thank you so much! I think I just figured it out. It wasnt reading it at first, so I quickly pulled it out and plugged it in. I ran the dd command again and it worked! I think it worked because whatever was stopping kali from reading the USB didnt have time to make that error.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
kernel: end_request: I/O error, dev sdb, sector 0 sandeep002gupta Linux - Server 3 08-23-2016 09:22 AM
Need larger tmp space - error writing temporary file: No space left on device deepGC Linux - Newbie 6 06-06-2015 05:55 AM
[SOLVED] Error opening /dev/sdb:Permission denied Neo@Matrix Linux - Newbie 20 09-20-2011 09:39 PM
Linux Error: 28: No space left on device renguzi Linux - Newbie 4 12-11-2008 09:32 PM
Stuck at 5.5. Linux-2.6.22.5 API Headers ERROR no space left on device bucovaina78 Linux From Scratch 2 11-30-2008 04:26 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 08:13 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration