How To Re-mount Microdrive In Pdaxii13v2?

[jdmoorman]

After a re-boot, my C3100 running pdaxii1v2 now no longer mounts the microdrive.

mount:
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw)
/proc on /proc type proc (rw)
none on /dev type tmpfs (rw)
/dev/mmcda1 on /mnt/card type vfat (rw,noatime)

df:
Filesystem        1k-blocks       Used  Available    Use%  Mounted on
/dev root             123904     92420     31484      75%     /
none                    12288        12     12276       0%     /dev
/dev/mmcda1          4012032   3732832      93%     /mnt/card


The partition manager shows 3 partitions (type 83, type 82, type c) as I originally created them.
So I'm guessing that the microdive is ok, but the process that mounts it on boot is broken.

Is there an easy fix for this?

[Capn_Fish]

I'd try running fsck on them first to make sure they're OK, if you haven't already.

[jdmoorman]

I'd try running fsck on them first to make sure they're OK, if you haven't already.

fsck /dev/hda3
fsck 1.34 (25-Jul-2003)
e2fsck 1.34 (25-Jul-2003)
fsck.ext2: No such deice or addesss while trying to open /dev hda3
Possibly non-existent or swap device?

mount /dev/hda3 /data
mount: /dev/hda3 is not a valid block device

no cf card was inserted

[Capn_Fish]

Is hda3 normally a data partition? Have you tried checking dmesg for potential errors? Maybe

Code: [Select]

pccardctl eject 0;pccardctl insert 0
would help?

[jdmoorman]

Is hda3 normally a data partition? Have you tried checking dmesg for potential errors? Maybe

Code: [Select]

pccardctl eject 0;pccardctl insert 0
would help?

The plot thickens . . .
pccardctl -v
-bash: pccardctl: command not found

with cf card inserted
mount /dev/hda1 /mnt/cf
mount: /dev/hda1 is not a valid block device

mount /dev/hdc1 /mnt/cf
mount: /dev/hdc1 is not a valid block device

dmesg
STAT=-x2142
of pdxa_sd_wait_id_response: response time out (cmd=01 MMC_STAT=0x2142)
(above line repeated ~110 times)
SD Driver Initialized.
sharp_mmcsd 0.30 12 OCT 2004
pdxa_sd_wait_id_response: response time out (cmd=01 MMC_STAT=0x2142)
pdxa_sd_wait_id_response: response time out (cmd=01 MMC_STAT=0x2142)
[SD]-clustsize = 10000
Partition check:
 mmcda: mmcda1
 mmcda: mmcda1
 mmcda: mmcda1
MSDOS FS: IO charset utf8
 mmcda: mmcda1
EXT2-fs: unable to read superblock
 mmcda: mmcda1
EXT2-fs: unable to read superblock
VFS: busy inodes on changed media
 mmcda: mmcda1
mice: PS/2 mouse device common for all mice
start checkf battery !
pxa+mcmcia_init(0)

Yet I can boot from the cf card (power+OK), go into the flash utils and read the microdrive partitions.

Once booted from the nand, however, it dosen't recognize the microdrive or the cf card, but does see and mount the sd card just fine.

[Capn_Fish]

Sorry, it should be "cardctl" not "pccardctl." I'm too used to 2.6.x kernels

[jdmoorman]

Sorry, it should be "cardctl" not "pccardctl." I'm too used to 2.6.x kernels

Thanks!
cardctl ident
Socket 0:
product info: "SanDisk", "SDP", "5/3 0.6"
manfid: 0x0045, 0x0401
function: 4 (fixed disk)
Socket 1:
product info: "HITACHI", "microdrive"
manfid: 0x0319 0x0000
function: 4 (fixed disk)

pccardctl eject 0;pccardctl insert 0 and pccardctl eject 1;pccardctl insert 1 execute without comment.

results of mount /dev/hdxx is unchanged: /dev/hdxx is not a valid block device

Any ideas?

[Capn_Fish]

What happens if you try:

Code: [Select]

cardctl eject 0
cardctl insert 0
fsck /dev/hdax
where x is a partition number (make sure it exists in /dev/)?

I'm starting to think you may need somebody more experienced to help you.

[jdmoorman]

What happens if you try:

Code: [Select]

cardctl eject 0
cardctl insert 0
fsck /dev/hdax
where x is a partition number (make sure it exists in /dev/)?

I'm starting to think you may need somebody more experienced to help you.

Executing the cardctl commands individually seem to run ok (with out complaint or error).
cardctl -ident finds the drives, after cardctl insert x.

fsck /dev/hda1 complains "no such device or address while trying to open /dev/hda1"
ls /dev/hd* lists drives a-c with partitions 1-8.

Since cardctl can read the drive's identity, and the partition manager can read the partitions, my speculation is that the hardware is ok.
Maybe the dev files are corrupt?

I guess I could do a re-flash, re-partition, re-image, re-update  .  .  ., but I'd hate to loose the data on the microdrive and the hours spent installing, upgrading, configuring, etc.

Thanks for your help.

[Capn_Fish]

Hmm... Drives /dev/hdxy (x being a letter and y being a number) sounds fishy. Normally the drives don't appear unless their inserted, and I can guarantee that you don't have three IDE disks. Maybe something in udev is corrupted/messed up? Could somebody else with pdaXii13 confirm that having all of those disks present is not normal?

[Drake01]

Hmm... Drives /dev/hdxy (x being a letter and y being a number) sounds fishy. Normally the drives don't appear unless their inserted, and I can guarantee that you don't have three IDE disks. Maybe something in udev is corrupted/messed up? Could somebody else with pdaXii13 confirm that having all of those disks present is not normal?

I just checked on my C3200 and it does list the devices that jdmoorman described.  Strange, since my desktop system certainly doesn't list that many.

[Jon_J]

After a re-boot, my C3100 running pdaxii1v2 now no longer mounts the microdrive.

Did you have 3 partitions after you first installed pdaxii13 ?
(one ext3 for programs, one for swap, and one vfat for FAT)
Or to rephrase my question,
Did you follow Meanies instructions when first installing pdaxii13 about formatting the drive during the installation setup.

If you had a "GOOD" setup after first installing pdaxii13, and now your partitions have "disappeared" after using pdaxii13, I am sorry I don't have an answer to that particular problem.
Hopefully Meanie will see this and be able to help. I would think the mounting of the hard drive on boot would be handled the same or similar as in pdaXrom beta3.
Sorry, I didn't read the entire post when I first replied.

The partition manager shows 3 partitions (type 83, type 82, type c) as I originally created them.
So I'm guessing that the microdive is ok, but the process that mounts it on boot is broken.

What is the "partition manager"? Is that in the setup screen? (I haven't re-flashed in a long time and have forgot the choices in the setup screen.)
If you decide to reflash, make sure you follow the instructions carefully when it comes to partitioning the hard drive. It can sometimes be confusing because, over several version changes of the installer, the prompts for formatting and partitioning the hard drive have changed.
Below is "mount" and "df" commands on my pdaxii13v2 C3200. (Note, I leave my 1GB CF (hda1) inserted at all times, hence the hdc1 and hdc3)

Code: [Select]

root-:) mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (rw)
/proc on /proc type proc (rw)
none on /dev type tmpfs (rw)
/dev/hdc1 on /mnt/ide type ext3 (rw,noatime)
/dev/hdc3 on /data type vfat (rw,noatime,nosuid,nodev)
none on /dev/pts type devpts (rw)
/dev/root on /mnt/user type jffs2 (rw)
/dev/mmcda1 on /mnt/card type vfat (rw,noatime)
/dev/hda1 on /mnt/cf type vfat (rw,noatime)

root-:) df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/root               123904     95404     28500  77% /
none                     12288        16     12272   0% /dev
/dev/hdc1              2115276     76808   1931016   4% /mnt/ide
/dev/hdc3              3593540    139428   3454112   4% /data
/dev/mmcda1            1979828    428084   1551744  22% /mnt/card
/dev/hda1              1013028    668184    344844  66% /mnt/cf

[jdmoorman]

Well, I re-flashed/imaged/upgraded/re-configured/un-installed/installed to get the system working again.
It worked fine, for a while; microdrive worked as it should; then I rebooted.
All is woe - the same problem has repeated.
Either I have a hardware problem or pdaxxiiv2 is not stable, at least as I am trying to set it up.

I'll probably go back to cacko and monitor developments in the pdaxrom for a future try.

[Capn_Fish]

pdaXii13 v2 is in alpha, unless I am mistaken. Perhaps you should try pdaXii13 (v1)?

[jdmoorman]

My guess is that there is a hardware problem (NAND?).

I tried to reflash to cacko, which seemed to go fine, but got the following on boot:

 . . .
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Spitz audio driver initialize
Sharp SL series flash device: 10000000 at 0
Using static partision definition
Creating 1 MTD partitions on "sharpsl-flash":
0x00140000-0x007f0000 : "Filesystem"
NAND devicef: Manufacture ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MB 3.3v)
Creating 3 NTD partitions on 'NAND 128MB 3.3v":
0x00000000-0x00700000 : "smf"
0x00700000-0x02700000 : "root"
0x02700000-0x08000000 : "home"
Linux Kernel Card Services 301.31
 options: [pm]
Intel PXA250/210 PCMCIA (CS release 301.31)
pxa_pcmcia_init(0)
pxa_pcmcia_init(1)
Backlight Driver Initialized
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 bucketd, 4Kbytes
TCP: Hash tables configured (established 4096 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NetWinder Floating Point Emulator V0.97 (double precision)
IrCOMM protocol (Dag Brattli)
cramfs: wrong magic
FAT: bogus logical sector size 381
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing init memory: 84K
modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.20/mdules.dep
 (No such file or directory)
mount: Mounting /boot/usr.bin on /usr failed: No such device
/etc/rc.d/rc.rofilesys: line 187: /usr/local/etc/console/encoding: No such file or directory
/etc/rc.d/rc.rofilesys: line 18888: /usr/local/etc/console/phonetic: No such file or directory
depmod: Can't open /lib/modules/2.4.20/modules.dep for writing
Unknown flash (not normal NAND)
Unknown flash (not normal NAND)
Unknown flash (not normal NAND)
Unknown flash (not normal NAND)
INIT: Entering runlevel: 5
cardmgr[132]: socket 0: ATA/IDE Fixed Disk
cardmgr[132]: executing: 'modprobe ide_cs 2>&1'
cardmgr[132]: + modprobe: Can't open dependencies file /lib/modules/2.4.20/modules.dep (No such file or directory)
cardmgr[132]: modprobe exited with status 255
cardmgr[132]: module /lib/modules/2.4.20/pcmcia/ide_cs.o not available
cardmgr[132]: get dev info on socket 0 failed: Resource temporarily unavailable
cardmgr[132]: socket 1: ATA/IDE Fixed Disk
survive: /usr/sbin/inetdf: No such file or directory
Generating RSA key for SSH v2
/etc/rc.d/rc5.d/S17ssh: line 20: /usr/bin/ssh-keygen: No such file or directory
Generating DSA key for SSH v2
/etc/rc.d/rc5.d/S17ssh: line 25: /usr/bin/ssh-keygen: No such file or directory
Generating RSA key for SSH v1
/etc/rc.d/rc5.d/S17ssh: line 30: /usr/bin/ssh-keygen: No such file or directory
survive: /usr/sbin/rpc.portmap: No such file or directory
cardmgr[132]: get dev info on socket 1 failed: Resource temporarily unavailable
ERROR: /usr/sharp/etc/launch.conf -- can no open file
ERROR: launch.conf -- can not open file
/sbin/launch : launch.conf not found
ERROR: /usr/sharp/etc/launch.conf -- can not open file
. . .

I know this comes from the cacko rom vs. the pdaxrom, but it does add info to the situation - which does not seem to be pdaxrom problem.  Unless some of you software wizards have some insight as to what is causing the (above) problems, it looks like I have a dead Z.