Hello Mr. Feyrer, Background: After two hard drive failures, I'm hoping to speed the recovery process next time by making backup images with g4u. I was unable to get v2.1 to send an image to my ftp server (Got two different ftp? error messages such as "cannot assign address..."? and google was no help) so I upgraded to v2.2 b2 and plugged in a firewire drive as the target.
Copydisk: My source Maxtor drive and target LaCie drive both claim "160GB", but I realize they could be very different nonetheless. "copydisk wd0 sd0" seemed to run as expected up to 160GB, then finished with a "short" write error? message and declared 160xxxxxxxxx bytes had been copied. Apparently the target is actually (slightly) smaller than the source, but the source only has 6.1 GB of data on it, so I thought I'd probably lose only zeros. Instead, my Suse 10.0 Konqueror reports that the external LaCie drive (still) contains 0 folders and 0 files. :-( This is not the failure I'd expect if my clone destination were too small, so I am writing in case this is a bug in v2.2 beta 2. I'm guessing this is either: (1) a bug in v2.2 beta2 (2) an expected failure given the "short" write problem, because some essential bytes are stored at then end of the drive or something, or (3) not an error, because copydisk is not a clone and the target contains bytes which g4u could still somehow copydisk back to reconstruct a lost drive. Thanks for g4u Jeff Bronez ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ g4u-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/g4u-help
