64GB SD Card no longer getting any recognizing

Emerson · 11-28-2016, 10:05 AM

OK, one issue at the time. This SD card shows size 8 GB and three partitions on it. You sure this is your SD card and not some other USB stick you had plugged in? If it is, go ahead and use dd to nuke the partition table and use your favorite fdisk to try and create a new partition table.

BW-userx · 11-28-2016, 10:21 AM

OK I fixed that USB Stick problem. With Windows Disk Management. It is a 16GB USB Stick. that problem is solved. BUT,

My micro SD Card, causes my system to hang if I have it plugged in while booting. Telling me that it sees it because it is trying to see if it is suppose to boot off of it. But causes it to hang until I unplug it, then I can boot into grub menu to get into Linux.
using that SD Card converter that takes a micro SD Card

Code:

[  262.521919] mmc0: error -110 whilst initialising SD card

USB Stick SD Card reader I now get this

Code:

userx@voided1.what~>> lsusb
Bus 004 Device 004: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo
Bus 004 Device 003: ID 0461:4dce Primax Electronics, Ltd 
Bus 004 Device 008: ID 14cd:1212 Super Top microSD card reader (SY-T18)

dmesg

Code:

[  364.224270] usb-storage 4-1.1:1.0: USB Mass Storage device detected
[  364.224782] scsi host6: usb-storage 4-1.1:1.0
[  365.275403] scsi 6:0:0:0: Direct-Access     Mass     Storage Device   1.00 PQ: 0 ANSI: 0 CCS

but not seeing what is plugged into the reader. which is that 64GB Mcro SD card itself.

Emerson · 11-28-2016, 10:43 AM

Looks like your SD card is dead.

BW-userx · 11-28-2016, 11:12 AM

Quote:

Originally Posted by Emerson

Looks like your SD card is dead.

it is writing to something

Code:

userx@voided1.what~/Downloads>> sudo dd if=RebeccaBlackOS_i386.iso of=/dev/sdc && sync
2709504+0 records in
2709504+0 records out
1387266048 bytes (1.4 GB, 1.3 GiB) copied, 19.4703 s, 71.3 MB/s

Emerson · 11-28-2016, 11:15 AM

Look, dd is not accessing the hardware directly, there is Linux kernel in between. If your Linux kernel cannot "see" your SD card (meaning device node sdX is not created upon insertion) then dd cannot write to it, nor can any partitioning tool access it.

BW-userx · 11-28-2016, 11:20 AM

Quote:

Originally Posted by Emerson

Look, dd is not accessing the hardware directly, there is Linux kernel in between. If your Linux kernel cannot "see" your SD card (meaning device node sdX is not created upon insertion) then dd cannot write to it, nor can any partitioning tool access it.

then why did cfdisk open it up after I dd 'd to a non seen sd card?

Emerson · 11-28-2016, 11:25 AM

That I do not know, I'm not there watching over your shoulder. You are saying there was no device node sdc associated with your SD card and dd was still able to write to it? That's mystery world for me.

BW-userx · 11-28-2016, 11:41 AM

Quote:

Originally Posted by Emerson

That I do not know, I'm not there watching over your shoulder. You are saying there was no device node sdc associated with your SD card and dd was still able to write to it? That's mystery world for me.

Yeah if I have the sd card reader pluged into the USB Port then try to dd to it, it will give me no device error, then if I slip the SD Card into that reader then run dd again it will wite to it, and if I command line cfdisk to it, it will bring it up, but only show the amount dd created, but if I try Gparted then it does not see it. so .. burp.. I donno...

thanks for your help.

Emerson · 11-28-2016, 11:47 AM

Can you create a filesystem on it without partitioning? Can you delete/create partitions on it with cfdisk?

BW-userx · 11-28-2016, 11:52 AM

Quote:

Originally Posted by Emerson

Can you create a filesystem on it without partitioning? Can you delete/create partitions on it with cfdisk?

that is just what I was thinking. there has to be a low level tool to reset that stuff -- them numbers that it has, start point, and end point, that I got a read up on and learn.

with cfdisk it does not show me the entire 64GB just how much DD burned to it from an iso.

Emerson · 11-28-2016, 12:01 PM

So can you create an filesystem on it or not? Did you try and nuke the existing partition table and try to create a new one? (I'm getting tired of this.)

rokytnji · 11-28-2016, 03:53 PM

Can you point out where I told you to dd parted logic to the usb pen drive in this thread?

BW-userx · 11-28-2016, 04:16 PM

Quote:

Originally Posted by rokytnji

Can you point out where I told you to dd parted logic to the usb pen drive in this thread?

I was just referencing that that program you suggested screwed up my Stick, not you, which I got that fixed NP not that you lead me to do that... the stick is fixed, that SD CARD is not. ... ... ...

Emerson · 11-28-2016, 04:22 PM

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.

BW-userx · 11-28-2016, 04:42 PM

Quote:

Originally Posted by Emerson

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.

ok Mr. CALL ME A LAIR

yes it was a 64GB SD CARD split into two partitions 32GB each.....

call me a liar again and I will report you....

Quote:

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.

TWO that is what it is doing ... call me a lair again.. keep going

it was seeing it for a little while...

to correct that statmeant After I screws up my usb Stick I used Linux and Windows to get that one back