C3000 Restoration Issue

[stderr]

First i'd like to apologize if there is yet a thread covering this topic.

I followed the restoration instructions on the xflag.com (http://www.xlfag.com/zaurus/), but i'm having troubles with the hdd1.tar.gz.

Can someone tell me, what files are supposed to be in this archive ? Or even better what should be placed in the /hdd1 and /hdd2 directories.

Thanks.

[ThC]

Hi,

If you followed the instructions given on that site it should simply work (I followed them a few time by the letter without any problem) ... btw here is what I can tell you on the /hdd1 and /hdd2 structures :
/hdd1 contain .sys/ and usr/ directories ... the .sys dir contain hdimage2.tgz which is the default content of hdd2 and a file named hdlist1.dat which contain a listing of all the files present in /hdd1 and the usr/ dir contain usr.rom , bin.rom, sbin.rom, QtPalmtop.rom etc ... (as you can see by simply opening the archive) ... the /hdd2 directory is repopulated from the hdimage2.tgz during first boot of the device (or when you reset it using the maintenance menus).

Hope that can help you btw I didn't understand well what you wanted ? (the file listing you can have it by simply open the archive on your desktop computer as it's a standard tar.gz archive)

[stderr]

Hi,

If you followed the instructions given on that site it should simply work (I followed them a few time by the letter without any problem) ... btw here is what I can tell you on the /hdd1 and /hdd2 structures :
/hdd1 contain .sys/ and usr/ directories ... the .sys dir contain hdimage2.tgz which is the default content of hdd2 and a file named hdlist1.dat which contain a listing of all the files present in /hdd1 and the usr/ dir contain usr.rom , bin.rom, sbin.rom, QtPalmtop.rom etc ... (as you can see by simply opening the archive) ... the /hdd2 directory is repopulated from the hdimage2.tgz during first boot of the device (or when you reset it using the maintenance menus).

Hope that can help you btw I didn't understand well what you wanted ? (the file listing you can have it by simply open the archive on your desktop computer as it's a standard tar.gz archive)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106669\"][{POST_SNAPBACK}][/a][/div]

Thanks for reply, that makes sense. The problem i have is that in the phase when the fresh japanese should come up 'in several minutes' nothing happens. When i reset it after nothing happens for minutes, it says HDD not initialized.
When i exctracted the hdd1.tar.gz from cf to hdd1, there were many symlinks errors, so i tought it might be a problem with the archive...

[ThC]

It might help to know how you bricked your Z and which steps you followed from the tutorial (did you restore your NAND ? did you reflash your kernel ? what kernel did you reflash with ? ... I don't remember needing it for that purpose but you may try using gnu-tar instead of tar to decompress the hdd1.tar.gz file ... or maybe use the --format=oldgnu option for your tar if you once replaced tar with gnu-tar and didn't make the NAND restore ...
Do you have any error with hdd while booting in D+B mode and mounting it ?

[stderr]

It might help to know how you bricked your Z and which steps you followed from the tutorial (did you restore your NAND ? did you reflash your kernel ? what kernel did you reflash with ? ... I don't remember needing it for that purpose but you may try using gnu-tar instead of tar to decompress the hdd1.tar.gz file ... or maybe use the --format=oldgnu option for your tar if you once replaced tar with gnu-tar and didn't make the NAND restore ...
Do you have any error with hdd while booting in D+B mode and mounting it ?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106672\"][{POST_SNAPBACK}][/a][/div]

thx for reply.

 I installed OpenBSD,  than while trying to repartition the wd0 accidently destroyed the fs. Than i had to reflash NAND to remove the obsd bootloader, no errors so far. I reflashed the kernel also, with the zImage-v18a-C3000.bin, but the tux logo never shown up, no errors though. I also have no troubles mounting the hdd.

[stderr]

Thanks for the gnu-tar hint, the problem is solved.