On Saturday 03 July 2010 08:48:18 fe...@crowfix.com wrote: > I want a bigger micro SD card in my cell phone it came with just 2GB), > so I bought a 16GB one complete with carrier to fit in a standard SD > slot. My plan was to turn off the phone, remove the 2GB micro SD > card, make a tarball of what is on there, put in the 16GB one and > untar things, and put the 16GB one in the phone. > > No luck. /dev shows for devices, sd[fghi], and neither mount nor > fdisk knows what to do with them. /var/log/messages has this:
I had a similar issue with the 8G (class 4) card I got for my phone. No matter what I did, it wouldn't work in the SD slot. Other cards did, but not that one. Eventually I just stuck it in a multi-card expansion unit that plugs into USB and it worked just fine. I suspect issues with the card itself - possibly timing related and this confuses the controller. But I never proved this one way or another. Maybe you can try a similar USB unit? They are dirt cheap. My on-board SD controller for comparison: 03:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 03:09.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12) 03:09.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 03:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12) > > Jul 2 22:15:54 xxx kernel: [568715.643244] usb 1-4.2.1: new high speed USB > device using ehci_hcd and address 16 Jul 2 22:15:54 xxx kernel: > [568715.730704] usb 1-4.2.1: New USB device found, idVendor=058f, > idProduct=6362 Jul 2 22:15:54 xxx kernel: [568715.730708] usb 1-4.2.1: > New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 2 22:15:54 > xxx kernel: [568715.730712] usb 1-4.2.1: Product: Mass Storage Device Jul > 2 22:15:54 xxx kernel: [568715.730714] usb 1-4.2.1: Manufacturer: Generic > Jul 2 22:15:54 xxx kernel: [568715.730716] usb 1-4.2.1: SerialNumber: > 058F312D81B Jul 2 22:15:54 xxx kernel: [568715.731643] scsi7 : > usb-storage 1-4.2.1:1.0 Jul 2 22:15:55 xxx kernel: [568716.732144] scsi > 7:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0 > Jul 2 22:15:55 xxx kernel: [568716.732744] scsi 7:0:0:1: Direct-Access > Generic USB CF Reader 1.01 PQ: 0 ANSI: 0 Jul 2 22:15:55 xxx kernel: > [568716.733367] scsi 7:0:0:2: Direct-Access Generic USB SM Reader > 1.02 PQ: 0 ANSI: 0 Jul 2 22:15:55 xxx kernel: [568716.734088] scsi > 7:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0 > Jul 2 22:15:55 xxx kernel: [568716.735972] sd 7:0:0:0: Attached scsi > generic sg5 type 0 Jul 2 22:15:55 xxx kernel: [568716.736777] sd 7:0:0:1: > Attached scsi generic sg6 type 0 Jul 2 22:15:55 xxx kernel: > [568716.737650] sd 7:0:0:2: Attached scsi generic sg7 type 0 Jul 2 > 22:15:55 xxx kernel: [568716.738408] sd 7:0:0:3: Attached scsi generic sg8 > type 0 Jul 2 22:15:56 xxx kernel: [568717.229510] sd 7:0:0:1: [sdg] > Attached SCSI removable disk Jul 2 22:15:56 xxx kernel: [568717.230883] > sd 7:0:0:2: [sdh] Attached SCSI removable disk Jul 2 22:15:56 xxx kernel: > [568717.231639] sd 7:0:0:3: [sdi] Attached SCSI removable disk Jul 2 > 22:15:56 xxx kernel: [568717.232135] sd 7:0:0:0: [sdf] Very big device. > Trying to use READ CAPACITY(16). Jul 2 22:15:56 xxx kernel: > [568717.233510] sd 7:0:0:0: [sdf] Using 0xffffffff as device size Jul 2 > 22:15:56 xxx kernel: [568717.233519] sd 7:0:0:0: [sdf] 4294967296 512-byte > logical blocks: (2.19 TB/2.00 TiB) Jul 2 22:15:56 xxx kernel: > [568717.234503] sd 7:0:0:0: [sdf] Write Protect is off Jul 2 22:15:56 xxx > kernel: [568717.234507] sd 7:0:0:0: [sdf] Mode Sense: 03 00 00 00 Jul 2 > 22:15:56 xxx kernel: [568717.234510] sd 7:0:0:0: [sdf] Assuming drive > cache: write through Jul 2 22:15:56 xxx kernel: [568717.236749] sd > 7:0:0:0: [sdf] Very big device. Trying to use READ CAPACITY(16). Jul 2 > 22:15:56 xxx kernel: [568717.237875] sd 7:0:0:0: [sdf] Using 0xffffffff as > device size Jul 2 22:15:56 xxx kernel: [568717.238874] sd 7:0:0:0: [sdf] > Assuming drive cache: write through Jul 2 22:15:56 xxx kernel: > [568717.238879] sdf: > Jul 2 22:15:56 xxx kernel: [568717.241760] sd 7:0:0:0: [sdf] Unhandled > sense code Jul 2 22:15:56 xxx kernel: [568717.241764] sd 7:0:0:0: [sdf] > Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Jul 2 22:15:56 xxx > kernel: [568717.241770] sd 7:0:0:0: [sdf] Sense Key : Medium Error > [current] Jul 2 22:15:56 xxx kernel: [568717.241778] Info fld=0x0 > Jul 2 22:15:56 xxx kernel: [568717.241781] sd 7:0:0:0: [sdf] Add. Sense: > CIRC unrecovered error Jul 2 22:15:56 xxx kernel: [568717.241787] sd > 7:0:0:0: [sdf] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 Jul 2 > 22:15:56 xxx kernel: [568717.241799] end_request: I/O error, dev sdf, > sector 0 Jul 2 22:15:56 xxx kernel: [568717.241803] Buffer I/O error on > device sdf, logical block 0 > > I don't remember now if this was the 2GB or 16GB micro SD card, but I > know it wasn't 2TB! > > Is there some trick to reading micro SD cards? I read the SD card > from a camera often with no problems, and it is 1 or 2 GB. If it > matters any, this micro 16GB SD card and its carrier are Polaroid. > > > I suppose I could just USB mount the phone with the 2GB card, copy off > everything, mount the phone with the 16GB card and copy everything back. -- alan dot mckinnon at gmail dot com
