Help - Search - Members - Calendar
Full Version: Restore Needs Renaming Backup Files
OESF Forums > General Forums > General Support and Discussion > Software
moi
After a time-losing experience trying OZ/GPE, a NAND backup and a complete HD restoration process lead me into my first-day Sharp 1.01 ROM

The problem is when I try to restore a soft backup. It doesn't find backup files, not in the CF nor the SD slot, unless I rename them from what they used to be, i.e.

2006-07-02-22-46.backup_SLC3200-JP-1

to literally:

2006-07-02-22-46.backup_SLC3200-JP-unknown


Does anyone knows why this change in behaviour (re-nandflashing didn't do the trick, and the backups aren't readable anymore unless I rename them) ?.

Thanks.
bam
dunno, but your iguana's nails need some serious trimming.
dougeeebear
Sounds like a cacko rom thing to me.
Cresho
I know the answer to the question. I expirienced this exact problem myself and it pissed me off as well. It is related to your hdd internal because you did not restore it correctly. until you restore it correctly to its original state, you will always have this problem. here...ill look for my post where i posted the solution and ill tell you how i fixed my problem exxactly.
Cresho
and here is the answer to your question.


If you need help in restoring your drive, i can help. What is going on is that the creation of the partition rely on the information embedded in the hardisk hdd1 or 2 to name the file. The unknown part comes because you did not install a file correctly or its not mounted correctly. In other words, the backups are fine its just that it cant identify your zaurus in creating the backup. that is where the unknown part comes in. of course, your zaurus backup will never work for me since its named differently than my version.

http://www.oesf.org/forums/index.php?showtopic=19679&hl=
moi
Wow, I really thank you for taking your time to answer and try to help me smile.gif

QUOTE(Cresho @ Jul 26 2006, 10:26 PM)
I know the answer to the question.  I expirienced this exact problem myself and it pissed me off as well.  It is related to your hdd internal because you did not restore it correctly.  until you restore it correctly to its original state, you will always have this problem.  here...ill look for my post where i posted the solution and ill tell you how i fixed my problem exxactly.
*


Absolutely possible, I wanted to try OZ/gpe and either at flashing or reflashing
I first partitioned by mistake my cf card (left in the slot by mistake) instead of the MD. Then realised and repartitioned MD and proceeded correctly, but when reflashing back to cacko I had to use trisofts files for rebuilding the MD (I'm sure something went wrong, 'cause I did it two times), so maybe in the second time I also missed something and this makes the JP-unknown thing.

QUOTE(Cresho @ Jul 26 2006, 10:27 PM)
and here is the answer to your question.

If you need help in restoring your drive, i can help.  What is going on is that the creation of the partition rely on the information embedded in the hardisk hdd1 or 2 to name the file.  The unknown part comes because you did not install a file correctly or its not mounted correctly.  In other words, the backups are fine its just that it cant identify your zaurus in creating the backup.  that is where the unknown part comes in.  of course, your zaurus backup will never work for me since its named differently than my version.

http://www.oesf.org/forums/index.php?showtopic=19679&hl=
*


As per the link, your solution was restoring the HD to its original state. The procedure I followed was this one, specially the last post.

Did you do something different, or any other way to accomplish this restore to its original content? (that's what I'm really looking for)

to be a bit more specific, do you think 'rebuilding' again the HD (fdisk, and copying trisoft's files), would do the trick?

Thank you
Cresho
as far as i can tell, whipe out the microdrive completely. THen use trisofts stuff to restore the microdrive.

what i did different was.........hmmmm

create partitions sizes as directed
reboot

create the partition type with the fdisk tool
reboot

mount the partitions
reboot

copy files into each partitions
reboot

then you should be able to backup-restore at this point.

that is how i solved that problem. or you know what else? while your system is running, use terminal, tkcexplorer, or treeexplorer to delete the files in the hdd1 and 2 besides lost and found and but the files back in there, after you backup your disk of course...and reboot and then do a back up and restore file and see if it helped. the problem is related to the hdd1 and 2.
moi
QUOTE(Cresho @ Jul 27 2006, 01:42 AM)
as far as i can tell, whipe out the microdrive completely.  THen use trisofts stuff to restore the microdrive.

what i did different was.........hmmmm

create partitions sizes as directed
reboot

create the partition  type with the fdisk tool
reboot

mount the partitions
reboot

copy files into each partitions
reboot

then you should be able to backup-restore at this point.

that is how i solved that problem.  or you know what else?  while your system is running, use terminal, tkcexplorer, or treeexplorer to delete the files in the hdd1 and 2 besides lost and found and but the files back in there, after you backup your disk of course...and reboot and then do a back up and restore file and see if it helped.  the problem is related to the hdd1 and 2.
*


Thanks for your reply Cresho, tree explorer could not handle the hdd1 and hdd2 files (something ownership options didn't let me erase the files), so decided the way rebooting to the command line.

here's my experience following your steps, and typing literally the same on this message and on the zaurus:

CODE
Starting point: Working Cacko 1.23 Full, with the backup/restore problem.
an SD card containing the files from trisoft at dir SLC3200SYSPART/hdd1sys and [...]/hdd2sys
no CF card in the slot

Reboot with D+B to command-line

login as root
fdisk /dev/hda
   'o' to clear partition
   'w' to write changes

reboot
D+B to command-line
login as root

fdisk /dev/hda
   create 3 partitions
   establish the third's Id as 'c' -> Win95 FAT32 (LBA)
   (first and second, by default, type 83 -> Linux)

reboot
D+B to command-line
login as root

mke2fs -j /dev/hda1
mke2fs -j /dev/hda2
mkfs.vfat -F 32 /dev/hda3

reboot
D+B to command-line
login as root

mount /dev/hda1 /hdd1
mount /dev/hda2 /hdd2

reboot
D+B to command-line
login as root

mkdir /hdd1/.sys
mkdir /hdd2/.sys
cp /mnt/card/SLC3200SYSPART/hdd1sys/* /hdd1/.sys/
cp /mnt/card/SLC3200SYSPART/hdd2sys/* /hdd2/.sys/
reboot

The same SD has in dir "Backup_Files" the file ending in -JP-unknown, which is read
the -JP-1 one does not appear.

Making a backup creates a -JP-unknown file...


Thanks for any ideas to solve this.
moi
Well, some info

The hdd1+hdd2 issue and the nand flash rely on the same basis. I couldn't make my system recognise my first backup, with my original nand flash, using trisoft's hdd1sys and hdd2sys files.

If I want to use their hdd files I have to nand flash their rom. This way everything works, my first backup is recognised, and my subsequent backups are labelled ending in JP-1.

As I did my best to learn and achieved a nand backup the first time I boot the machine, and I achieved a soft backup blindly (totally jap) after that very first reboot, I wanted to use my own nand.

Does someone has a copy of the original hdd1 and hdd2, and would be so kind of PM them?.

Thanks.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.