Ok... I"m at a loss.
Situation:
5500, Sharp 3.1, Lexar 1G SD, PNY 128M CF
I had the SD card able to mount and read/write data. I had several IPK's installed on it. Then I realized all of a sudden that I couldn't install anything to SD. I just chalked it up to the usual "Must be installed in memory" routine. However, today I noticed that I couldn't install ANYTHING to SD. Then I noticed it was mounted read-only.
So I search the forums and find several threads on "do an FSCK on the corrupt file-system and it should work".
Ok... I did that, and no success. I've reformatted the SD using my CentOS box. I've formatted it in VFAT, and in EXT2 (4k blocks and 1k blocks). The SD can be written from Windoze.
Every time I install the card into the system it mounts read-only. I can't mke2fs /dev/mmcda1 as the command always comes back saying the disk is read-only.
Dmesg returns:
# dmesg
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
EXT2-fs: Unrecognized mount option noatimei
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
cramfs: wrong magic
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
MSDOS FS: IO charset utf8
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
VFS: busy inodes on changed media.
mmcda: mmcda1
Most of what dmesg spits out is a foreign language to me, so I don't know what it's telling me, nor what I can do to change it's attitude.
FSTAB has:
/dev/mmcda1 /mnt/card vfat rw,noatime,noauto,owner 0 0
The card is currently formatted as vfat, but using "auto" detect didn't change anything either.
Has my 5500 lost it's mind on how to mount SD? I have a PNY 128M formatted vfat that doesn't even show up.
And no.... I don't have the write-protect tab switched to "LOCK".
My faithful 5500 is not being so faithful at the moment, and I don't know how to make it any better.
I was trying to move to Crow/Cacko, but every time I tried "fdisk /dev/mmcda" I would get "partition table is not writable". However, it clearly is from CentOS fdisk. I also got "Unable to mount mmcda1" from mke2fs from the Crow ROM setup.
What makes me think it is my 5500 losing it is that every once in awhile I would perform some magic and get the SD to mount rw. I have been unable to determine what the sequence may be.
Can anybody give me a direction to pursue in fixing this? I know I'm rambling a bit, as I'm a bit shell-shocked on all of this at the moment.
