Sponsored Content
Full Discussion: Strange FAT filesystem
Top Forums UNIX for Advanced & Expert Users Strange FAT filesystem Post 302674837 by HJarausch on Friday 20th of July 2012 12:56:34 PM
Old 07-20-2012
Strange FAT filesystem

My Garmin GPS device has a slot for an SD card. I'm using a 32 GB SD card which holds 22 GB data currently.

If I attach my device to a USB port it shows two devices, the internal memory and the SD card. I have no problems with the internal memory which holds only 2 GB of data.

I can mount both as a FAT32 system, but listing (ls) the large SD card based file system shows only rubbish (many question marks and dots).
Fdisk is telling me, it's a FAT32 partition.

BUT, when I start Windows7 under Virtualbox on the very same hardware, I can list the device just fine and CHKDSK doesn't find any errors. And Windows claims it's a FAT32 system.

I've even tried to execute mount.exfat-fuse but it cannot find an exfat file system.

Has anybody an idea what's going on?

Many thanks for a hint,
Helmut.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

format fat partition in unix

I got a FAT partition mounted as /mnt, as I believed you only can mount partitions when they are formated, but when I want to copy a file to the /mnt partition I only get errors...should I format it or do I have to change settings? I only can work through the "WebMin" (a GREAT TOOL!) cause I'm... (2 Replies)
Discussion started by: NaRtHeXs
2 Replies

2. Filesystems, Disks and Memory

Loopback files on a FAT based Filesystem?

I'm trying to set up a set of loopback files on a digital music player so I can carry a QEMU virtual machine with me. The digital music player in question is the Rio Karma and the filesystem it uses is omfs. Based on what I read at the Rio Karma FS page:... (1 Reply)
Discussion started by: deckard
1 Replies

3. Hardware

SATA drive FAT recover

I had ACER aspiron one netbook with dual bootable (Windows XP and Debian). Recently I found XP is messy and Debian has new version published. I plan to recover XP and install new version of Debian. But I failed to recover XP from Hidden Partition. I thought it is because I install GRUB in the... (15 Replies)
Discussion started by: sinnud
15 Replies

4. UNIX for Advanced & Expert Users

FAT-Client Server installation

I'm going to build a Fat-Client server, I have planed to Use Ubuntu.11.4. Please Help me for doing this. What are the packages I need to install? What is the step I need to follow, what needs to be configure in LDAP Server,DHCP Server and etc, Is there and Document or tutorial ? ... (3 Replies)
Discussion started by: ungalnanban
3 Replies

5. Fedora

SD's, fsck, dmesg, freezing, and the Corrupt FAT-fs

Up until today I haven't had a problem using an SD card with Fedora ( 25 ) but when I went to insert the SD adapter with the micro-sd card this time, the computer froze. It has frozen every time since. It is still reading the card, and after a minute or two of losing control of the GUI and terminal... (4 Replies)
Discussion started by: Beta_OmegaAdinf
4 Replies

6. Linux

Converct fat pc to thin client

I have old pc with 1gb ram and i wont to convert him to thin clint to connect rdp windos With software i need to install on my computer? I am new in linux.. Sent from my SM-J5108 using Tapatalk (10 Replies)
Discussion started by: popcoern
10 Replies
pcram(7D)																 pcram(7D)

NAME
pcram - PCMCIA RAM memory card device driver SYNOPSIS
memory@<socket>/pcram@<technology>,0:c memory@<socket>/pcram@<technology>,0:c,raw The PCMCIA RAM memory card device driver supports disk-like I/O access to any standard PCMCIA static random access memory (SRAM) card and dynamic random access memory (DRAM) card. The driver supports standard PCMCIA SRAM/DRAM cards that contain a Card Information Structure (CIS). RAM card densities in the 512Kilobytes to 64Mbyte range are supported. PRECONFIGURATION
If a PC card memory device is recognized, the pcram device driver is automatically loaded, the physical address allocated, and special files created (if they do not already exist). Known Problems and Limitations The Solaris pcmem driver is not capable of handling "combo" memory cards with multiple types of memory on them (for example, combined SRAM and nonvolatile FLASH). Inserting such a card into a system running the Solaris software may cause a system panic. Because the PC card memory device is designed as a pseudo-floppy diskette type, the only utility that can be used for formatting is fdfor- mat(1). CONFIGURATION
Configuration topics include initial installation and configuration, identifying an unrecognized device, special files, using PC card mem- ory devices, and hot-plugging. Initial Installation and Configuration 1. Install the Solaris software. 2. Boot the system. 3. Insert the card. Identifying an Unrecognized Device If you insert a memory device and it is not recognized (no special files created), use the prtconf command. 1. Become root. 2. Run the prtconf -D command to display the configuration recognized by the system. A recognized device will appear in the prtconf out- put. For example: # prtconf -D . . . pcic, instance #0 (driver name: pcic) . . . memory, instance #0 (driver name: pcmem) pcram, instance #0 (driver name: pcram) 3. If your memory device does not appear at the end of the prtconf output, it is not supported and cannot be used with the pcram driver. Special Files The special files created for PC card memory devices act like disks and have names in the form /dev/dsk/c#t#d#p# or /dev/dsk/c#t#d#s#. Abbreviations used in the names are: o c# Controller # o t# Card technology type #, defined as follows: 0 Null--no device 1 ROM 2 OTPROM (One Time PROM) 3 UV EPROM 4 EEPROM 5 Flash EPROM 6 SRAM 7 DRAM o d# Device region of type #, usually zero o p# fdisk partition # o s# Solaris slice # Note - A device name can be specified either by a partition name (p#) or a slice name (s#), but not both. Using PC Card Memory Devices Since the Solaris Volume Management software recognizes PC Card memory devices, no special vold configuration is required. If you do not want to use vold to manage your PC card memory devices, comment out the use pcmem line in the /etc/vold.conf file. To comment out a line, insert a # character at the beginning of the line. PC Card memory devices do not need to have file systems on them, though typically, before using a new PC Card memory card, you will want to create a file system on it. DOS PCFS is the best format to use. (You can use virtually any file system format on a PC card memory card, but most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. See "Using a PCMCIA Memory Card" in the OpenWindows Advanced User's Guide.) Note - If you want to redirect the output of a tar command (or dd or cpio) to a PC card memory device, first create a file system on the card, using the fdformat(1) command without arguments. The card must be reformatted before it can be written on again. Hot-Plugging If a memory card is removed while in use, the device driver returns errors until the memory card is inserted into the appropriate socket. Close and reopen the device with the card reinserted, and the memory card will work. o If you remove the card while in use as a file system, unmount the file system using the umount command. Then reinsert the card and remount the file system using the mount command. o If you remove the card and interrupt a tar or cpio process, stop the process, reinsert the card, and restart the process. /kernel/drv/pcram pcram driver /dev/dsk/cntndnsn block files /dev/rdsk/cntndnsn raw fileswhere: cn controller n tn technology type n 0x1ROM,0x2OTPROM,0x3EPROM, 0x4EEPROM,0x5FLASH,0x6SRAM, 0x7DRAM dn technology region in type n sn slice n fdformat(1), pcmcia(7D), dkio(7I), pcmem(7D) 23 Oct 2000 pcram(7D)
All times are GMT -4. The time now is 11:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy