I tried to wirte Linux ISO image on that card and after that SD card seems to be broken - originally it was FAT32 but after that it pretends to be ext3 ( but it isn’t) - I was unable to write that image on that SD card for some reason ( I did it via windows…)
An error occurred while accessing '1.5 GiB Removable Media', the system responded: The requested operation has failed: Error mounting /dev/sdc1 at /run/media/robert/ef41a57c-ac25-49ca-8e4d-d5690abfb35d: Command-line `mount -t "ext3" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc1" "/run/media/robert/ef41a57c-ac25-49ca-8e4d-d5690abfb35d"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so.
dmesg | tail
[184239.118944] sd 10:0:0:0: [sdc] Attached SCSI removable disk
[184271.938482] sd 10:0:0:0: [sdc] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[184271.939091] sd 10:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[184271.943189] sdc: sdc1
[184276.150727] EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem
[184276.158314] JBD2: no valid journal superblock found
[184276.158319] EXT4-fs (sdc1): error loading journal
[184520.737917] EXT4-fs (sdc1): mounting ext3 file system using the ext4 subsystem
[184520.744301] JBD2: no valid journal superblock found
[184520.744310] EXT4-fs (sdc1): error loading journal
How exactly did you do that? And which ISO image?
- originally it was FAT32 but after that it pretends to be ext3 ( but it isn’t)
Yes it is (probably).
You overwrote your SD card with the ISO’s content (at least partly), so there is no FAT32 filesystem on it any more.
If the ISO contained an ext3 filesystem, your SD card now contains an ext3 filesystem as well.
To make your SD card usable again, re-partition it.
Maybe wipe out the partition table first.
See also here:
https://en.opensuse.org/SDB:Live_USB_stick#How_to_recover_the_USB_stick_for_.22normal.22_use_again
how to repartition it? I’ve to mount it first to format it
an maybe that’ll help
dmesg -H | grep "usb"
+0.132217] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000003] usb 3-4: hub failed to enable device, error -22
+0.089717] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000002] usb 3-4: hub failed to enable device, error -22
+0.155381] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.006742] usb 1-1.3: reset full-speed USB device number 4 using ehci-pci
+0.138070] usb 1-1.4: reset high-speed USB device number 5 using ehci-pci
[Aug26 01:03] usb 3-1: new high-speed USB device number 4 using xhci_hcd
+0.166323] usb 3-1: New USB device found, idVendor=1004, idProduct=618e
+0.000007] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
+0.000003] usb 3-1: Product: LGE USB Device
+0.000003] usb 3-1: Manufacturer: LG Electronics Inc.
+0.000003] usb 3-1: SerialNumber: 80A358187042233000
+0.001486] usb-storage 3-1:1.4: USB Mass Storage device detected
+0.000457] scsi9 : usb-storage 3-1:1.4
+0.084050] usb 1-1.4: reset high-speed USB device number 5 using ehci-pci
+0.045827] usb 1-1.3: reset full-speed USB device number 4 using ehci-pci
+0.228191] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000002] usb 3-4: hub failed to enable device, error -22
+0.152881] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000002] usb 3-4: hub failed to enable device, error -22
+0.152962] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.078628] usb 1-1.3: reset full-speed USB device number 4 using ehci-pci
+0.034627] usb 1-1.4: reset high-speed USB device number 5 using ehci-pci
+0.238206] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000001] usb 3-4: hub failed to enable device, error -22
+0.152781] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000002] usb 3-4: hub failed to enable device, error -22
+0.153084] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
[Aug26 02:09] usb 3-1: USB disconnect, device number 4
[Aug26 02:11] usb 3-1: new high-speed USB device number 5 using xhci_hcd
+0.166370] usb 3-1: New USB device found, idVendor=1004, idProduct=618e
+0.000007] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
+0.000004] usb 3-1: Product: LGE USB Device
+0.000002] usb 3-1: Manufacturer: LG Electronics Inc.
+0.000003] usb 3-1: SerialNumber: 80A358187042233000
+0.001691] usb-storage 3-1:1.4: USB Mass Storage device detected
+0.000428] scsi10 : usb-storage 3-1:1.4
+0.082202] usb 1-1.4: reset high-speed USB device number 5 using ehci-pci
+0.055895] usb 1-1.3: reset full-speed USB device number 4 using ehci-pci
+0.228163] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000001] usb 3-4: hub failed to enable device, error -22
+0.152884] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
+0.000001] usb 3-4: hub failed to enable device, error -22
+0.153016] usb 3-4: reset high-speed USB device number 2 using xhci_hcd
No.
You cannot format a mounted partition.
Use YaST->System->Partitioner or Windows’ partitioner or fdisk to remove all partitions and create a FAT32 partition over the whole card.
If that doesn’t work for some reason, try the things in the link I posted to completely erase the card.
I see 2 devices on /dev/sdc one is LGE platform - 14.84 GB - that’s SD card and /dev/sdc1 ext3 Linux native - can’t it be Internal ROM of my phone ??? or that’s not possible I’ve cyanogenmod
/dev/sdc is the card itself, and /dev/sdc1 is the one partition, apparently formatted with ext3 now.
- can’t it be Internal ROM of my phone ??? or that’s not possible I’ve cyanogenmod
Well, it definitely is not the ROM of your phone. 
(ROM=Read Only Memory)
You never told that you were talking about a phone.
But then, you still didn’t say what you did exactly.
So the SD card is inside your phone and you connected it via USB?
I thought you overwrote the card with a Linux ISO?
Or didn’t you?
If you did, you wiped out everything that’s on it, and you yourself said it should be FAT32.
So reformat /dev/sdc1 with FAT32, I’d say.
Maybe better make a full backup of the card before you do that though, to be safe.
E.g.:
dd if=/dev/sdc of=card_backup.img
so I formated it to ext4 ( just for fun and I will use it on Linux so…) but my moblie can’t read it ??? ( android) and the expert paritioner also don’t display it. But here’s output of dmesg after I plug it in usb port ( in that USB adapter for SD cards)
dmesg | tail
[277145.996708] usb 1-1.2: New USB device found, idVendor=090c, idProduct=6200
[277145.996715] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[277145.996718] usb 1-1.2: Product: Generic USB2.0 card
[277145.996721] usb 1-1.2: Manufacturer: Silicon Motion, Inc.
[277145.996724] usb 1-1.2: SerialNumber: 12345678901234567890
[277145.997323] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[277145.997907] scsi20 : usb-storage 1-1.2:1.0
[277147.002768] scsi 20:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0 CCS
[277147.003918] sd 20:0:0:0: Attached scsi generic sg3 type 0
[277147.004915] sd 20:0:0:0: [sdc] Attached SCSI removable disk
How exactly did you do format it to ext4?
And I thought you wanted to create a FAT32 partition?
Apparently you now created an invalid filesystem on the device itself.
But here’s output of dmesg after I plug it in usb port ( in that USB adapter for SD cards)
Apparently there’s no partition. So create one.
And format that with a filesystem of your choice.
sorry for bothering you - the SD card adapter is pretty strange - I need to push that card with my finger, when I release the finger disk=SD card disappears.
The (unmounted) device in question should be reported by
sudo /sbin/fdisk -l
eg /dev/sdb then zero it completely with
sudo dd if=/dev/zero of=/dev/sdb
After this you should be able to use your favourite partitioning tool to format as you like.
Ah, so not securely inserting properly.