JeFF
Member
Mine is formatted as FAT, and I think this is not recognised by the pandora?
So in which format does my sd card needs to bet? Ext?
So in which format does my sd card needs to bet? Ext?
ive heard people saying that journaling damages the memory over time, as it does a lot of read/write, thats why some dont like to use it on nand, sd,usb memory. i could be completely off here though
I've had (before) poor experience with ext2 and ext3 fs's on SD; at the tiem we were hacking the firmware like mad (long ago) and so crashes were frequent (esp for me, I had extra issues than the other devs), and in the face of crashes, I found ext2 and ext3 would corrupt very quickly; FAT for all its flaws does tend to survive crashes pretty well .... and of course works with ay device you slap it into. (Also, after huge long writes of many files, a 'sync' operation takes significantly longer on e3 than e2 than fat; when I was resetting OSes onto SD 10 times a night (those were the days), waiting a couple minutes just for e3 to sync drove me nuts. So my experience is probably different than current, but I've just stuck to what worked
So I tend to always use fat32 on SD
jeff
So, I'm getting weird behaviour (with Fat32).
I have 3 SDHC cards: 16G SDHC, 16G SDHC MicroSD, 8G SDHC MicroSD
I formatted them to Fat32 on Windows, and dragged across my pnd files
and roms.
The first day things seemed fine, but noticed the card wouldn't umount.
Then the weirdness kicked in. A rom that loaded one way wouldn't load the
next, then an app wouldn't load and so on.
dmesg was showing block errors.
So, I started trying other cards and slots.
This is the output I get now.
cat msd_slot1.txt (8Gb microsd in slot1 of the panda)
[19080.454864] mmc0: host does not support reading read-only switch. assuming write-enable.
[19080.463073] mmc0: new high speed SDHC card at address 88f7
[19080.469055] mmcblk0: mmc0:88f7 SU08G 7761920KiB
[19080.474029] mmcblk0: p1
[19080.962432] FAT: bogus number of reserved sectors
[19080.967193] VFS: Can't find a valid FAT filesystem on dev mmcblk0.
[19081.128448] FAT: bogus number of reserved sectors
[19081.133209] VFS: Can't find a valid FAT filesystem on dev mmcblk0.
removed:
[19186.180908] mmc0: card 88f7 removed
[19186.219940] FAT: Directory bread(block 8192) failed
[19186.224884] FAT: Directory bread(block 8193) failed
[19186.229827] FAT: Directory bread(block 8194) failed
[19186.234741] FAT: Directory bread(block 8195) failed
p$ cat sd_slot1.txt (16 full size SD in slot1)
[19243.985107] mmc0: host does not support reading read-only switch. assuming write-enable.
[19243.993286] mmc0: new high speed SDHC card at address b368
[19243.999298] mmcblk0: mmc0:b368 SDC 15756288KiB
[19244.004364] mmcblk0: p1
[19244.529113] FAT: invalid media value (0xb9)
[19244.533386] VFS: Can't find a valid FAT filesystem on dev mmcblk0.
[19244.689636] FAT: invalid media value (0xb9)
[19244.693878] VFS: Can't find a valid FAT filesystem on dev mmcblk0.
[19293.798065] mmc0: card b368 removed
[19293.818847] FAT: Directory bread(block 30776) failed
[19293.824035] FAT: Directory bread(block 30777) failed
[19293.829040] FAT: Directory bread(block 30778) failed
[19293.834136] FAT: Directory bread(block 30779) failed
[19293.839202] FAT: Directory bread(block 30780) failed
SD card into a usb 2.0 reader:
[ 1896.141448] usb 1-2: new high speed USB device using ehci-omap and address 2
[ 1896.299957] usb 1-2: configuration #1 chosen from 1 choice
[ 1896.322387] scsi0 : SCSI emulation for USB Mass Storage devices
[ 1896.330047] usb 1-2: New USB device found, idVendor=14cd, idProduct=8123
[ 1896.336853] usb 1-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 1896.344024] usb 1-2: Product: USB 2.0 SD MMC READER
[ 1896.349182] usb 1-2: Manufacturer: SDMMC MA8123
[ 1896.353759] usb 1-2: SerialNumber: 812320080329
[ 1896.358367] usb-storage: device found at 2
[ 1896.358367] usb-storage: waiting for device to settle before scanning
[ 1901.353485] scsi 0:0:0:0: Direct-Access USB 2.0 SD MMC Reader PQ
: 0 ANSI: 0 CCS
[ 1901.378723] sd 0:0:0:0: [sda] 31512576 512-byte hardware sectors (16134 MB)
[ 1901.386505] sd 0:0:0:0: [sda] Write Protect is off
[ 1901.391357] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 1901.391387] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 1901.485595] sd 0:0:0:0: [sda] 31512576 512-byte hardware sectors (16134 MB)
[ 1901.493377] sd 0:0:0:0: [sda] Write Protect is off
[ 1901.498229] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 1901.498229] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 1901.504394] sda: sda1
[ 1901.508575] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 1901.514526] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1901.523986] usb-storage: device scan complete
[ 1902.185028] FAT: invalid media value (0xb9)
[ 1902.189300] VFS: Can't find a valid FAT filesystem on dev sda.
[ 1902.351013] FAT: invalid media value (0xb9)
[ 1902.355285] VFS: Can't find a valid FAT filesystem on dev sda.
It does seem like the cards are corrupting.
So I used the HP USB format tool (will try the panasonic one next)
to format my SD16 again, then on the PC ran h2testw_1.4 on it.
It found no errors and wrote 16Gb of data and verified.
I am getting the same symptoms on all 3 cards, and all are
supposedly reputable cards. I can't find any problems on the PC.
I might try a Ubunutu comparison later, but most of time I
am using Windows PCs, so want to be able to use stock FAT formats
to interchange data.
ID
Here;Does anyone know how to add NTFS to the Pandora? We need a guide. I don't have mine yet and have never used Ångström Linux.