[SOLVED]16GB SD doesn't mount - 8GB does ???

[cozzykim]

This is strange (to me anyway, I'm probably missing something obvious as usual )

I have an 808 #16 camera which can be used in removable disk mode to view files on its (micro) SD card.

This works fine with a 2GB or 8GB card (formatted in camera as FAT32) and the notification pops up to offer "Open with File Manager" as normal

I've bought a 16GB Lexar card (formatted in camera as FAT32 (LBA) ) and the card doesn't mount in removable disk mode.

cat /proc/partitions shows the card as being present:

Code: [Select]

$ cat /proc/partitions
major minor  #blocks  name

   8        0  488386584 sda
   8        1  156288000 sda1
   8        2          1 sda2
   8        5   12587368 sda5
   8        6    4089928 sda6
   8        7  315410728 sda7
   8       16   15637504 sdb
   8       17   15633408 sdb1

but CYC>Local Disks>Manage disk partitions doesn't show the disk as present.

The camera/disk combination works OK in removable disk mode in win7.

What am I missing

Thanks

[muungwana]

unplug it from the computer,wait for 3 seconds,plug it back in,wait for 3 seconds and then run the following command on the terminal and give its output

dmesg | tail -n 30

[cozzykim]

Code: [Select]

dmesg | tail -n 30
sd 9:0:0:0: [sdb] Unhandled sense code
sd 9:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 9:0:0:0: [sdb]  Sense Key : Medium Error [current]
sd 9:0:0:0: [sdb]  Add. Sense: Unrecovered read error
sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 20 00 00 00 08 00
end_request: I/O error, dev sdb, sector 8192
sd 9:0:0:0: [sdb] Unhandled sense code
sd 9:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 9:0:0:0: [sdb]  Sense Key : Medium Error [current]
sd 9:0:0:0: [sdb]  Add. Sense: Unrecovered read error
sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 20 00 00 00 08 00
end_request: I/O error, dev sdb, sector 8192
sd 9:0:0:0: [sdb] Unhandled sense code
sd 9:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 9:0:0:0: [sdb]  Sense Key : Medium Error [current]
sd 9:0:0:0: [sdb]  Add. Sense: Unrecovered read error
sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 20 00
end_request: I/O error, dev sdb, sector 0
sd 9:0:0:0: [sdb] Unhandled sense code
sd 9:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 9:0:0:0: [sdb]  Sense Key : Medium Error [current]
sd 9:0:0:0: [sdb]  Add. Sense: Unrecovered read error
sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
end_request: I/O error, dev sdb, sector 0
sd 9:0:0:0: [sdb] Unhandled sense code
sd 9:0:0:0: [sdb]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sd 9:0:0:0: [sdb]  Sense Key : Medium Error [current]
sd 9:0:0:0: [sdb]  Add. Sense: Unrecovered read error
sd 9:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
end_request: I/O error, dev sdb, sector 0
Is that it?

Thanks

[muungwana]

Those read errors explains what you are seeing.

Can you check to make sure everything is attached properly.Unplug every relevant connection and plug them back in and make sure they are plugged in good and try again.

If that does not work then an explanation will be that the card is defective and windows can tolerate its defectiveness.

[cozzykim]

New USB cable, different USB port, no difference.

I found a USB card reader, the card mounts OK in there and shows FAT32 (LBA)

[Just17]

Can the new card be formatted outside of the camera and then used?

If so I would delete the partition/s and the MBR, create a new set up and format the partitions before inserting it into the camera.

Maybe use Gparted for this ...  and create a clean MBR, partition table and partitions.

[cozzykim]

I've just done a full (not quick) format from a Win utility (SD card formatter 3.1).

PCLOS - Still not mounting when in the camera. The camera records to the card OK and the files are playable in VLC. Card still mounts OK in a normal card reader.

I'll try deleting the partitions as you suggest, could this be something to do with a hidden security partition?

(BTW, the reason I need to see the card when in the camera is that the setup utility GUI (Java based) requires this, but I'm also curious now to find out what the problem is )

[Just17]

I'll try deleting the partitions as you suggest, could this be something to do with a hidden security partition?

I wasn't aware there was one.

Post the output of

fdisk -l    (minus lower case L)

as it relates to the card.

[cozzykim]

This is a screenshot from GParted after I told it to ignore read write errors:

Hmm, can't embed photobucket IMG and no option to upload to forum, sorry

GParted basically says "partition table - not recognised" and "partition unallocated", "file system unallocated", "size 14.91GiB"

fdisk -l /dev/sdc reports "Cannot open /dev/sdc"

Completely stumped here, it works fine in the camera

[Just17]

I would compare those results to results from similar tests on the 8GB card.

If the 8GB card looks OK to fdisk & Gparted then I would be inclined (after backing up any data I wanted to keep) to wipe the 16GB card properly and rebuild the MBR/partition table and recreate the partition and format it.

If you are doing this it might be best to write zeros to the first MB or two of the card to ensure it is properly cleaned.

[cozzykim]

I would compare those results to results from similar tests on the 8GB card.

If the 8GB card looks OK to fdisk & Gparted then I would be inclined (after backing up any data I wanted to keep) to wipe the 16GB card properly and rebuild the MBR/partition table and recreate the partition and format it.

If you are doing this it might be best to write zeros to the first MB or two of the card to ensure it is properly cleaned.

Thanks, I just did all that, and was typing this below as you posted; The only thing I haven't done is write zeros to the 4MB boot sector (if that's what it is), how do I do that? :

Okay,

I redid everything with GParted, deleted, new partition FAT32, shrank the size to exactly the same as my Samsung 8GB card, set all flags the same, same Label.

It still doesn't mount and GParted says read errors when it's in the camera (as a removable drive of course), force GParted to read it and it says all unallocated.

The card then works perfectly in the camera, files readable when in the normal card reader.

Works in my Android tablet too

I'll try the camera forum, ask if anyone has used a Lexar 16GB card, but I don't think they'll be much help as it only has this problem under Linux as far as I can tell.

Weird

[Just17]

In Gparted after selecting the correct device, go to the Device Menu and from there create a new MBR/partition table structure.

You might want to consider using   dd   to write zeros to the beginning of the card first, to ensure there is nothing left there that is causing the problems.

dd  if=/dev/zero  of=/dev/sdZ  bs=1M  count=1    (zeros the first 1MB of the drive specified)

where sdZ corresponds to your card ......  you MUST be sure of this, as an error here would wipe out whatever disk you apply it to.

[cozzykim]

Done, no different

I think I might try a different make of card, I know that the camera works with cards up to 32GB so.............

Thanks for your help & patience, I'm still game to try anything else you can come up with.

[Just17]

Nothing else comes to mind unfortunately.

If the beginning of the card has been zero'd and a new structure put in place then there is nothing left over that could be interfering.

But so that I understand .....  you zero'd and recreated the structure & partition/s and formatted them outside the camera.
Could you then access those partitions on PCLOS, with the card in a card reader?

In the camera you then could not access the card .........  but could you access it if it was subsequently taken out of the camera, and again put into a card reader?

I am trying to figure out if it is something written to the card while in the camera, or if it is the camera interface that is causing the problem.

[Just17]

This might be the answer to your problems ......  incompatible card ......

http://www.rcgroups.com/forums/showpost.php?p=20509794&postcount=1706