3200 Not Mounting All Volumes

[Schnoober]

Hi,

I have a 3200 which I have put through the changes of three ROMs now. Started out Sharp, went to OZ then to pdaXrom and full circle sort of to Cacko, which I have decided I like.

The PDAXROM install required repartitioning disks. This caused the erasure of some key files in the hdd partitions. That causes the "hdd not initialised" error at boot time. Ctrl-c gets me past it.

Among other bits of information, I found a file at Trisoft
http://www.trisoft.de/en_c3200howto.htm under "Restore the harddisk." In that file are some instructions to for partitioning. and some vague information about files that are missing.

I also read this, which is only available on the wayback machine it would seem. It's about 3100s.
http://web.archive.org/web/20050205134428/...fag.com/zaurus/

So I wiped the Z, I repartitoned according to the info at trisoft,  NAND restored,I ran the install for Cacko and all seemed well but now hdd1 mounts as read only, hdd2 makes an error at boot and does not mount. hdd3 seems fine.

I'm very confused about these files that belong in /hdd1/ and /hdd2/. I'm not sure how I'm supposed to get them there.

Is the 3200 supposed to read this from cf at the first boot? because it does not appear to have done so.

In the diagnostic menu I see something called HDD restore. What is that?

at boot the screen reads:

Code: [Select]

EXT3-fs mounted filesystem with ordered data mode
mounted /hdd1
VFS: Can't find ext3 filesystem on dev ide0(3.2).
mount: mounting /dev/hda2 on /hdd2 failed: Invalid argument
HDD2 Error!! qstart check battery !
Control-c continues boot but hda1 is read-only and hda2 won't mount. This results in further problems.

Thanks if you can help, or even if you can't.

[pelrun]

That page you say is about 3100's is actually about 3000's... and the 3000's are *very* different to the 3100/3200.

See Meanie's site for more info; essentially on the 3100/3200 hdd1 and hdd2 are empty 9Mb ext2 partitions. hdd1 can contain a recovery tarball but that isn't required to be there.

Don't get the hda and hdd mixed up... isn't hda an inserted CF drive?

[Schnoober]

That page you say is about 3100's is actually about 3000's... and the 3000's are *very* different to the 3100/3200.

Yes, I've been trying to decipher what's relevant and what's not. The mention of a 3100 is a typo sorry. I did know that there are differences, but I got some useful info from this page anyway. Is it preserved anywhere other than the internet archive?

See Meanie's site for more info; essentially on the 3100/3200 hdd1 and hdd2 are empty 9Mb ext2 partitions. hdd1 can contain a recovery tarball but that isn't required to be there.

This is the part that confuses me. I'll have look at Meanie's. I've been there before, but it's long and I must have missed it. Thanks.

Don't get the hda and hdd mixed up... isn't hda an inserted CF drive?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=147030\"][{POST_SNAPBACK}][/a][/div]

Well as far as I understand /hdd1 is the mounted volume and /dev/hda1 is the source file/hardware for the mount. What the sources are can change depending on what cards are inserted when the Z boots. So if no card is inserted hdd1 is /dev/hda1. If a CF card is inserted the card gets /dev/hda1 and hdd1 gets /dev/hdc1. This way the card comes earlier in the boot process making it possible to boot from an image on the card.

[Schnoober]

Ok,

If it's so that I don't need any specific files in the hdd directories then why is it that trisoft's file offering exists at all?

Here's the complete readme from the file I downloaded from them:

Contents of the system-partitions for the SL-C3200

TRIsoft / Marc Stephan / April 11th, 2006



Use the information in this document at your own risk.

TRIsoft is not liable for any damages that may result from

these informations.





SL-C3200 HDD-Partition table:

/dev/hda1  Start 1  End 20  Blocks 10048+  id 83 System Linux

/dev/hda2  Start 21 End 40  Blocks 10080  id 83 System Linux

/dev/hda3  Start 41 End 11905 Blocks 5979960 id c System Win95 FAT32 (LBA)



Note:

While using the fdisk on the Zaurus, double check that you set the

correct parameters for the drive. They have to be:

16 heads / 63 sectors/track / 11905 cylinders

All of this I have done once again skipping nothing.

Format the partitions with:

mke2fs -j /dev/hda1

mke2fs -j /dev/hda2

mkfs.vfat -F 32 /dev/hda3

This is done again also, skipping nothing.
Now if I reboot I get the error "HDD not initialised."

/hda1 and /hda2 are 9.5 MB partitions. Each one contains a ".sys" and

a "lost+found" directory. The contents of the .sys-directories are

in this file.



Files in /hdd1/.sys :

hdimage2.tgz  (2149 Bytes, contains japanese web-bookmarks - hurray !)

hdlist1.dat (85 Bytes, no clue what it's good for)



Files in /hdd2/.sys :

contlist.dat (74327 Bytes)

hdlist2.dat (1264 Bytes)

hdlist3.dat (1519 Bytes)

This is great, but how do I get these files into the appropriate places?  

The Zaurus will display an error like "HDD not initialized" if the

directories and files are missing. Just restoring the partition table

won't make an SL-C3200 happy.

Hope this clarifies. I should have just posted this in the first place.

Thanks if anyone can help.

[TRIsoft]

Hi Schnoober,

If it's so that I don't need any specific files in the hdd directories then why is it that trisoft's file offering exists at all?

this is, because if you use the SHARP Rom, the Zaurus will check
if these files exist on startup. If not, you'll get these nice "HDD
not initialized" messages.

This is great, but how do I get these files into the appropriate places?

These files are also contained in the SLC3200SYSPART.zip .
Copy these files on a CF card, boot your Zaurus to command line
using the "D"+"B" + PwrOn procedure.
Mount /hdd1 and /hdd2 manually. Insert the CF card and copy
the files to the right places (the CF card is accessable at /mnt/cf ).
Then reboot and everything should be fine.

///TRIsoft

Marc Stephan

[Schnoober]

These files are also contained in the SLC3200SYSPART.zip .
Copy these files on a CF card, boot your Zaurus to command line
using the "D"+"B" + PwrOn procedure.
Mount /hdd1 and /hdd2 manually. Insert the CF card and copy
the files to the right places (the CF card is accessable at /mnt/cf ).
Then reboot and everything should be fine.

Marc,


Thank you very much for your reply.
All is working well now.
I was having a great deal of trouble getting things to mount and umount which made it obviously hard to move the files.
In fact, once I had performed the steps in your readme correctly all the volumes mounted correctly. That done, I could reboot, ctrl-C past the "HDD not initialised" error and open Konsole.
From there it was easy to umount hdd1 and mount -w /dev/hdc1 hdd1. Then all the volumes were read and write, and I was able to copy the files as per your instructions.

Everything working! Thanks for the help.
Sorry if I've been a bit of a dolt.