Weird Problem With 3100, Repartitioned Md And Usb

[silencer51]

I have repartitioned my microdrive as follows:

/dev/hda1 -> 512mb swap
/dev/hda2 -> 2048mb ext2
/dev/hda3 -> 1440mb fat32

With pdaxrom 1.1.0beta both hda2 and hda3 get automounted on startup to /mnt/ide2 and ide3 respectively.

However, after I connected my Z to my Windows Box and set USB mode to mass storage device and copied over some files to the fat32 partition, /dev/hda3 has stopped automounting.

I am sure this has caused it to stop automounting, I rebooted immediately after. I tried setting USB mode to network,to see if this caused the problem, but no.

I can still mount it manually and it works ok.

Perhaps when you connect it via USB to an XP box, XP does something stupid to the partition?

Any ideas on how to fix this? And how to enable swap upon startup automatically?

Thanks in advance

[silencer51]

OK, this is really weird...

After a while (about 3-4 minutes) /dev/hda3 gets mounted automagically! WTF!?

I noticed that after the system has booted and I log on, there is disk activity (green led flashes on and off). And when it ends, I mount -l and see /dev/hda3 has been mounted automatically. Weird, huh? Anyone seen any similar behaviour?

[silencer51]

Actually it takes closer to 6-8 minutes and is really annoying... I tried messing with ide.opts in /etc/pcmcia but with no results...

[silencer51]

Also trying to reboot withing these 6-8 minutes takes a loooong time, it seems it has to wait out whatever the internal cf is doing. When rebooting it stays on "Stop CF Services" for minutes.

What could be wrong? I'll try to fdisk my MD again and delete and recreate the fat32 partition...

[km2783]

I had a similar problem, both my CF and MD were not mounting.  I had to pull the battery out to get it sorted out.  I could mount the CF in X w/ the CF/SD Monitor, or do them both manually via terminal commands, but until I pulled the battery it wouldn't do it automatically, even after rebooting.  I have not been able to duplicate my problem, however

**edit** My MD is exactly as it came from Sharp, and the CF was formatted in a digital camera years ago.

[silencer51]

I don't think our problems are similar... Something is very very wrong here.

I fdisked the fat32 partition again and formatted it... No improvement.

Another observation:

At boot, the intense disk activity begins when loading the bluetooth modules. After that, when I log in, I notice that I cannot start windowmaker for as long as the MD is doing it's thing! I get an error about a library missing. After these 6 minutes, the microdrive stops r/w and then I can start everything fine and hda3 shows as mounted. WTF!?

[Deviant25]

Hey, i belive your problem is that you have allot of apps installed on hda2, when the things boots it will try to run ipkg-link to all the stuff after it mounts hda2... then once that is done it will mount hda3... hence why the disc activity shoots for like 10 mins.. then magically once it stops activity it will work/mount/reboot correctly

so if this is the answer to your problem.. then well ur in the same position as me  .. i just wait till its all loaded then i make sure not to reboot unless i have to

[silencer51]

This would explain my problem (I have almost 500mb of packages installed), but why would ipkg-link run on startup? I though it only ran after I installed a package and added the proper symlinks. Right?  

[Meanie]

This would explain my problem (I have almost 500mb of packages installed), but why would ipkg-link run on startup? I though it only ran after I installed a package and added the proper symlinks. Right? 
[div align=\"right\"][a href=\"index.php?act=findpost&pid=112408\"][{POST_SNAPBACK}][/a][/div]

maybe it is because ipkg-link was originally intended for installation to an external cf/sd card which could be ejected and swapped with another card. this means that it had to unlink every linked file when the disk was ejected and relink every file when it was inserted again. this makes sense for an external card, but for hdd2 which is internal, this wouldn't make sense but might be what is happening.

[adf]

of course it is kinda convenient or relink on reboot if you make a lot of changes.

[silencer51]

Is there any way to alter the boot and shutdown sequence to stop ipkg-link from running (when mounting and unmounting CF cards including the microdrive)? Since I intend to install all packages to /dev/hda2, there is no need for it...