LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 11-28-2016, 04:59 PM   #31
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Original Poster
Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242

Quote:
Originally Posted by Emerson View Post
This whole thread is a mess. Troubleshooting this is really simple.

0. Plug in your device and see if kernel recognizes it. If not proceed to a store and buy a new one.
1. Assuming kernel can see it and device node is created as sdX check it out with fdisk -l /dev/sdX. If the readout makes sense go ahead and start using it, create a new partition table or put a filesystem on raw device.
2. If readout does not make sense one could try nuking the existing possibly corrupted MBR and see if that helps. If not, proceed to a store and get a new one.

At all times you must be sure you are working on correct device, otherwise bad things can happen.

Lets see how our OP handled it. First he posted a snippet of kernel log showing a 8 GB device with 3 unreadable partitions on it, claiming this is a 64 GB SD card with two partitions. Obviously it was not.
Then he posted another snippet of kernel log showing the device was not recognized by kernel. Yet he claimed he was successful using dd on it. Impossible.
As a result a simple troubleshooting has been turned into a series of actions that do not make sense.
this is what that 64GB Micro SD Card is saying in dmesg right now

Code:
[ 4627.988514]  sdc: sdc1 sdc2 sdc3
[ 4627.993099] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[ 4628.301431] FAT-fs (sdc3): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 4628.530471] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 4639.463461] usb 4-1.1: USB disconnect, device number 13
[ 4646.802706] usb 4-1.1: new high-speed USB device number 14 using ehci-pci
[ 4646.883328] usb-storage 4-1.1:1.0: USB Mass Storage device detected
[ 4646.883690] scsi host6: usb-storage 4-1.1:1.0
[ 4647.939037] scsi 6:0:0:0: Direct-Access     Mass     Storage Device   1.00 PQ: 0 ANSI: 0 CCS
the partitions looked to be screwed up and whatever else is wrong with it.... because they were formatted to FAT32

the only thing I have plugged into my USB PORT is a 64GB micro SD Card that Gparted cannot see. but doing this anyways gets me this

Code:
userx@voided1.what~>> sudo dd if=/dev/zero of=/dev/sdc
dd: writing to '/dev/sdc': No space left on device
16373793+0 records in
16373792+0 records out
8383381504 bytes (8.4 GB, 7.8 GiB) copied, 9.35844 s, 896 MB/s
I have no reason to lie...


mod Now Gparted is seeing it as a 7.81GiB unallocated like it was doing with my USB Stick until I got windows involved and it formatted my STICK not SD Card out to the right size which was 16GB for the Stick not SD CARD which is 64GB

Last edited by BW-userx; 11-28-2016 at 05:09 PM.
 
Old 11-28-2016, 05:30 PM   #32
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Original Poster
Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
Code:
userx@voided1.what~>> sudo blkid
/dev/sda1: UUID="fa98942f-4219-4f0c-a9b1-0c3e2eda77e8" TYPE="ext4" PARTUUID="0f3f3740-01"
/dev/sda2: UUID="1bf3ce11-f34a-4e76-aab8-35d821739122" TYPE="ext4" PARTUUID="0f3f3740-02"
/dev/sda3: LABEL="ssdData" UUID="361c2abd-5393-4f12-af4d-6ef881f99a48" TYPE="ext4" PARTUUID="0f3f3740-03"
/dev/sdb1: LABEL="System Reserved" UUID="16BE1703BE16DAD7" TYPE="ntfs" PARTUUID="0004ed67-01"
/dev/sdb2: UUID="6602CF6F02CF42B3" TYPE="ntfs" PARTUUID="0004ed67-02"
/dev/sdb3: UUID="5550a765-506a-4ca6-aedc-b1c660dbb486" TYPE="ext4" PARTUUID="0004ed67-03"
/dev/sdb4: UUID="2cbaed98-039f-45d4-bf0d-4eb200009ec4" TYPE="ext4" PARTUUID="0004ed67-04"

userx@voided1.what~>> sudo dd if=/dev/zero of=/dev/sdc seek=64GB
dd: writing to '/dev/sdc': No space left on device
16373793+0 records in
16373792+0 records out
8383381504 bytes (8.4 GB, 7.8 GiB) copied, 9.65143 s, 869 MB/s
@Emerson

check that photo MR. Call me a LIAR
Attached Thumbnails
Click image for larger version

Name:	64GB-IMG_20161128_172749.jpg
Views:	18
Size:	202.4 KB
ID:	23639  
 
Old 11-28-2016, 06:18 PM   #33
michaelk
Moderator
 
Registered: Aug 2002
Posts: 25,898

Rep: Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985
Try zeroing the MBR or create a new partition table. Then pull and reinsert the card reader so the memory card is reread. That should "reset" it back to its full size.
 
Old 11-28-2016, 06:23 PM   #34
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675

Rep: Reputation: Disabled
Quote:
Originally Posted by michaelk View Post
Try zeroing the MBR or create a new partition table. Then pull and reinsert the card reader so the memory card is reread. That should "reset" it back to its full size.
I have told this at least three times. I'm a big fan of clear thinking, something that is totally missing here in this thread. Bailing.
 
Old 11-28-2016, 06:28 PM   #35
michaelk
Moderator
 
Registered: Aug 2002
Posts: 25,898

Rep: Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985Reputation: 5985
Yes you did.
 
Old 11-28-2016, 06:41 PM   #36
Timothy Miller
Moderator
 
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, EndeavourOS, OpenSUSE, KDE Neon
Posts: 4,015
Blog Entries: 27

Rep: Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523Reputation: 1523
Please try and remain civil.

If you feel another user isn't listening to you trying to help, don't insult them, just leave.

I'm not giving any infractions or closing thread, but keep it polite.

Thanks.
 
Old 11-28-2016, 06:48 PM   #37
Jjanel
Member
 
Registered: Jun 2016
Distribution: any&all, in VBox; Ol'UnixCLI; NO GUI resources
Posts: 999
Blog Entries: 12

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
When the 'impossible' appears to be happening, maybe it isn't [happening]

ls -l /dev/sdc

dd ... of=/dev/sdZZZZZZZ; ls -l /dev/sdZ*

Wouldn't it be a 'kick' IF a *data file* /dev/sdc was making poor >1990s udev choke...

A *WILD* fwiw psychic-reading, but /dev/st0 happened to someone I was helping dozens of years ago...
 
Old 11-28-2016, 06:48 PM   #38
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Original Poster
Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
Quote:
Originally Posted by Timothy Miller View Post
Please try and remain civil.

If you feel another user isn't listening to you trying to help, don't insult them, just leave.

I'm not giving any infractions or closing thread, but keep it polite.

Thanks.
are you telling me I insulted someone?
 
Old 11-28-2016, 06:49 PM   #39
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675

Rep: Reputation: Disabled
Quote:
Originally Posted by Timothy Miller View Post
Please try and remain civil.

If you feel another user isn't listening to you trying to help, don't insult them, just leave.

I'm not giving any infractions or closing thread, but keep it polite.

Thanks.
Leaving as per moderator suggestion. Bye.
 
Old 11-28-2016, 06:56 PM   #40
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Original Poster
Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
Quote:
Originally Posted by Jjanel View Post
When the 'impossible' appears to be happening, maybe it isn't [happening]

ls -l /dev/sdc

dd ... of=/dev/sdZZZZZZZ; ls -l /dev/sdZ*

Wouldn't it be a 'kick' IF a *data file* /dev/sdc was making poor >1990s udev choke...

A *WILD* fwiw psychic-reading, but /dev/st0 happened to someone I was helping dozens of years ago...
I do not know what that means, BUT
when I do this then bring up gparted and it now sees it as what dd did to it, then tells me I cannot create a new partition because it does not have enough space error. tell me that I am not seeing what is before my eyes.

was that just another fancy way of saying what?

the mbr and or partitions are screwed up...

Last edited by BW-userx; 11-28-2016 at 06:58 PM.
 
Old 11-28-2016, 07:02 PM   #41
Jjanel
Member
 
Registered: Jun 2016
Distribution: any&all, in VBox; Ol'UnixCLI; NO GUI resources
Posts: 999
Blog Entries: 12

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
huh? Is /dev/sdc a 'device' (as it should be, or a plain file)?
file /dev/sdc
 
Old 11-28-2016, 07:19 PM   #42
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Original Poster
Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
Code:
[   47.078796] usb 2-1.1: Product: Mass Storage Device
[   47.078801] usb 2-1.1: Manufacturer: Generic
[   47.078805] usb 2-1.1: SerialNumber: 121220130416
[   47.079442] usb-storage 2-1.1:1.0: USB Mass Storage device detected
[   47.080640] scsi host9: usb-storage 2-1.1:1.0
[   48.084569] scsi 9:0:0:0: Direct-Access     Mass     Storage Device   1.00 PQ: 0 ANSI: 0 CCS
[   52.531097] sd 9:0:0:0: [sdc] Attached SCSI removable disk
it sees that something is there other then just the cheep plastic USB Stick SD Card reader
 
Old 11-28-2016, 07:24 PM   #43
Jjanel
Member
 
Registered: Jun 2016
Distribution: any&all, in VBox; Ol'UnixCLI; NO GUI resources
Posts: 999
Blog Entries: 12

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
IF willing, remove all the external gadgets, and post the output of [exactly]:
ls -l /dev/sd*
 
Old 11-28-2016, 07:26 PM   #44
BW-userx
LQ Guru
 
Registered: Sep 2013
Location: Somewhere in my head.
Distribution: Slackware (15 current), Slack15, Ubuntu studio, MX Linux, FreeBSD 13.1, WIn10
Posts: 10,342

Original Poster
Rep: Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242Reputation: 2242
Quote:
Originally Posted by Jjanel View Post
IF willing, remove all the external gadgets, and post the output of [exactly]:
ls -l /dev/sd*
Code:
userx@SlackDaddy~>> ls -l /dev/sd*
brw-rw---- 1 root disk 8,  0 Nov 28 19:24 /dev/sda
brw-rw---- 1 root disk 8,  1 Nov 28 19:24 /dev/sda1
brw-rw---- 1 root disk 8,  2 Nov 28 19:24 /dev/sda2
brw-rw---- 1 root disk 8,  3 Nov 28 19:24 /dev/sda3
brw-rw---- 1 root disk 8, 16 Nov 28 19:24 /dev/sdb
brw-rw---- 1 root disk 8, 17 Nov 28 19:24 /dev/sdb1
brw-rw---- 1 root disk 8, 18 Nov 28 19:24 /dev/sdb2
brw-rw---- 1 root disk 8, 19 Nov 28 19:24 /dev/sdb3
brw-rw---- 1 root disk 8, 20 Nov 28 19:24 /dev/sdb4
-rw-r--r-- 1 root root   446 Nov 28 19:23 /dev/sdc
 
Old 11-28-2016, 07:27 PM   #45
Jjanel
Member
 
Registered: Jun 2016
Distribution: any&all, in VBox; Ol'UnixCLI; NO GUI resources
Posts: 999
Blog Entries: 12

Rep: Reputation: 364Reputation: 364Reputation: 364Reputation: 364
QUICK: rm /dev/sdc
 
  


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
RHEL 6.5 no longer recognizing keyboard or mouse Ciffy Linux - Server 3 08-28-2014 04:27 PM
Problems with openSUSE 11.1 recognizing Dazzle* Multi-Card reader and 8G SDHC card chubbs Linux - Newbie 0 02-20-2010 10:49 PM
ndiswrapper -l not recognizing wireless card zensufi Linux - Wireless Networking 10 02-08-2005 11:12 PM
Recognizing USB card reader when card is inserted hqo201 Fedora 0 08-02-2004 05:08 PM
recognizing wireless card dbkluck Debian 5 01-16-2004 10:53 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:53 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