problems trying to mount SDHC card ....

Sun Oct 26 12:57:34 UTC 2014

On 10/26/14 07:48, Polytropon wrote:
> On Sun, 26 Oct 2014 07:37:46 -0500, William A. Mahaffey III wrote:
>> On 10/25/14 23:29, Polytropon wrote:
>>> On Sat, 25 Oct 2014 18:39:14 -0500, William A. Mahaffey III wrote:
>>>> .... I am trying to mount some SDHC cards through a USB reader
>>>> (Transcend USB 2.0) with an eye towards using them to create bootable
>>>> drives for a Raspberry Pi B+.
>>> In that case, you probably won't have anything to do
>>> with mounting the SD card (especially not as a MS-DOS
>>> file system). The thing you're going to do here probably
>>> isn't much more than "dd if=pi.img of=/dev/da0", and
>>> Xfce is not able to help here. When the image has been
>>> written, there's probably a file system different from
>>> FAT on the card.
>>
>> Aaaaaaahhhhh .... That clarifies much .... I work w/ the device
>> directly, not MSDOS .... Beauty, ace ;-) ....
> The Xfce desktop doesn't have much tools for this
> specific kind of use, so you are probably safe to
> ignore error messages because they just state the
> already obvious. :-)
>
>
>
>>>> When I try to view the drive through
>>>> XFCE's 'flash File Manager' (from top toolbar) it pops up an error
>>>> dialog saying:
>>>>
>>>> mount_msdosfs: can't find or load "msdos_iconv" kernel module
>>>> mount_msdosfs: msdos_iconv: operation not permitted.
>>> Is the card currently formatted? What does
>>>
>>> 	# fdisk da0
>>>
>>> say (if /dev/da0 is the SD card reader)? Or with today's
>>> tools,
>>>
>>> 	# gpart show da0
>>
>> [root at kabini1, /etc, 7:30:02am] 495 % gpart show da0
>> =>      63  31127489  da0  MBR  (14G)
>>           63      8129       - free -  (4M)
>>         8192  31119360    1  !12  (14G)
>>
>> [root at kabini1, /etc, 7:30:06am] 496 %
> Okay, so no "DOS primary partition" there, no msdosfs-related
> file system.
>
>
>
>>> Also check the dmesg entries in relation to the card reader.
>>> Anything suspicious?
>> nothing at all, it's dated 3:03 A.M. this morning ....
> Good, so the reader picks up the card properly.
>
>
>
>>> In case the card is formatted with FAT, can you _manually_
>>> mount it?
>>   From my messages file this A.M.:
>>
>> Oct 26 07:29:49 kabini1 kernel: ugen3.2: <vendor 0x05e3> at usbus3
>> Oct 26 07:29:49 kabini1 kernel: umass0: <vendor 0x05e3 USB Storage,
>> class 0/0, rev 2.00/9.03, addr 2> on usbus3
>> Oct 26 07:29:49 kabini1 kernel: umass0:  SCSI over Bulk-Only; quirks =
>> 0x4100
>> Oct 26 07:29:49 kabini1 kernel: umass0:4:0:-1: Attached to scbus4
>> Oct 26 07:29:49 kabini1 kernel: (probe0:umass-sim0:0:0:0): REPORT LUNS.
>> CDB: a0 00 00 00 00 00 00 00 00 10 00 00
>> Oct 26 07:29:49 kabini1 kernel: (probe0:umass-sim0:0:0:0): CAM status:
>> SCSI Status Error
>> Oct 26 07:29:49 kabini1 kernel: (probe0:umass-sim0:0:0:0): SCSI status:
>> Check Condition
>> Oct 26 07:29:49 kabini1 kernel: (probe0:umass-sim0:0:0:0): SCSI sense:
>> ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
>> Oct 26 07:29:49 kabini1 kernel: (probe0:umass-sim0:0:0:0): Error 22,
>> Unretryable error
>> Oct 26 07:29:49 kabini1 kernel: da0 at umass-sim0 bus 0 scbus4 target 0
>> lun 0
>> Oct 26 07:29:49 kabini1 kernel: da0: <Generic STORAGE DEVICE 0903>
>> Removable Direct Access SCSI-6 device
>> Oct 26 07:29:49 kabini1 kernel: da0: Serial Number 000000000903
>> Oct 26 07:29:49 kabini1 kernel: da0: 40.000MB/s transfers
>> Oct 26 07:29:49 kabini1 kernel: da0: 15199MB (31127552 512 byte sectors:
>> 255H 63S/T 1937C)
>> Oct 26 07:29:49 kabini1 kernel: da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
>>
>>
>> All I see is the device name (da0), no further partitions referenced ....
> This is okay. The card reader, when attached, doesn't
> determine the card's size (no card in it), and da0 then
> is created correctly. I think this looks correct.
>
> Keep in mind that /dev/da0 is equivalent to /dev/da0c,
> where 'c' means "the whole device" or "the whole partition
> covering the whole device" in MBR-speak. So _if_ there
> is only one partition on it, /dev/da0 will correspond
> to that partition ("dedicated"). If a MBR partition
> table has been added, the "s1" part appears. And if
> that slice carries more than one partition, the other
> letters ('a' for a boot partition, 'b' for swap, 'd'
> up to 'h' for other partitions) may appear.
>
> In regards of SD cards, it's sometimes helpful to
> issue the command
>
> 	# true > /dev/da0
>
> to have the system "re-taste" the card to make it
> aware of what slices and/or partitions may reside on
> it. I have to do this regularly with my build-in card
> reader, or I won't be able to mount the SD card.
>
> Example:
>
> crw-r-----  1 root  operator    0, 129 2014-10-26 06:11:23 /dev/da1
> crw-r-----  1 root  operator    0, 162 2014-10-26 12:48:41 /dev/da1s1
>
> The 2nd file (used for the mount command, representing
> a MS-DOS file system on that card) does not appear when
> the card is inserted, even though the reader is recognized:
>
> da1: <Generic Flash HS-MS/SD 4.55> Removable Direct Access SCSI-0 device
> da1: 40.000MB/s transfers
> da1: Attempt to query device size failed: NOT READY, Medium not present
>
> It's required to issue the command mentioned above to
> make it appear. Afterwards, mounting works as expected.
>
> % df -h /media/sd
> Filesystem    Size    Used   Avail Capacity  Mounted on
> /dev/da1s1    1.9G    208M    1.7G    11%    /media/sd
>
> The act of mounting of course happens manually here.
>
>
>
>>>> I am doing this as an ordinary user, something in fstab or amd.conf ?
>>> I'm surprised you get any reaction at all. I never got
>>> automounting to work with Xfce...
>> It's not exactly working for me either, only if I separately prompt an
>> automount from CLI in another window :-/ ....
> I got it working exactly once, after several hours,
> with Gnome, HAL, automounter, a "rewrite" of /sbin/umount,
> and other embarrassing things I'd like to forget (or which
> I already forgot because they were so terrible). :-)
>
>
>
>>> If you have the automounting stuff via HAL and DBUS,
>>> your /etc/fstab won't probably have an entry for the
>>> SD card reader, and /etc/amd.conf is probably totally
>>> out of scope here. Maybe this is an expression of the
>>> growing incompatibilities between Linux (where Xfce
>>> has been created for) and FreeBSD?
>>>
>>> I'm a bit surprised about the "msdos_iconv" kernel
>>> module, which should be present. Can you manually
>>> load it, maybe via /boot/loader.conf?
>>
>> Could I load it w/ kldload (if it's there to load) ?
> Yes, that should be possible.
>
> You can verify if it's working with a card that _definitely_
> has a MS-DOS file system on it, for example a SD card from
> a digital camera.
>
>
>
>

*bingo* !!! Everything worked AOK .... *Boooyah* !!!! It shows up 
mounted under /media/flash, msdos, AOK .... Thx :-) !!!!

-- 

	William A. Mahaffey III

  ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                            -- Gen. George S. Patton Jr.