anthoc Posted July 27, 2002 Report Share Posted July 27, 2002 I have been talking directly to my reseller for Retrospect in Australia, the LaCie distributor and Dantz in the US concerning our predicament. I'll summarize (trying not to cry). Two weeks agowe discovered that one of the RAID volumes we have running on our OSX server 10.1.4 had died overnight causing a server reboot. This was the beginning of a domino effect that caused us to lose critical data from the month of July. We have a dual channel ATTO scsi 3 card with two external 160MB/s SUN Mircosystems SCSI packs. Each pack runs six 10krpm Seagate 18GB disks. We use OSXS RAID to mirror disk 1 in pack 1 with disk 1 in pack 2 and so on, to create six fully mirrored 18GB volumes. We use a firewire LaCie enclosure with a Sony AIT1 tape drive as a backup medium. Retrospect server 5.0.205 is installed on the server and backs up the desktop volume as a priority and then backs up network volumes. We did not have the new RDU file installed. Also running is the Retrospect email alert system (Applescript) which emails out a short report of the backup each day. Very useful since it's all we have left to prove we had complete backups until July 18th. On Saturday 19th July the server was reported as being unavailable. Further investigation revealed that the internal disk was unbootable, the DVD-ROM drive was not able to be used to boot from a CD (disk would not even spin up), and when in despair we finally replaced the internal drive, the RAID set caused immediate kernel panics. Disconnecting one of the external disk pack allowed us to boot up and copy off four disks worth of data from the other pack. The remaining two failed disks could not be accessed no matter which utility we used. Finally we reinstalled a fresh OSX server on a new internal disk (soon to be duplicated on a second internal disk) and we were able to reformat all external disks, destroying the RAID set, and restore 4 of the disks to their former state. Here's the catch. We had saved the backup set file in the recommended location on the internal hard disk. Because it failed we lost all backup set catalog files. No problem - we'll just recreate the backup sets from the tapes. But every tape had some form of corruption and although we were able to retrieve data backed up on 26th June, the worst corruption occurred in data backed up in July, the data we needed. Ironic. Repeated recreate and rebuild attempts failed with corrupt catalog file errors. Importantly the log showed 'out of memory' as the last error in every attempt. Is this a Retrospect problem?? We suspect that there may yet be a problem using firewire AIT drives and OSX RAID with Retrospect. Unable to pinpoint the cause we have replaced the internal drive and will duplicate it using Retrospect every night to another internal drive. The Apple RAID option has been abandoned in favour of disk duplication using Retrospect from one disk pack to the other every night. This is in addition to incremental daily backups as before. A shell script will copy the catalog files from the server to another server every night after the backup to safeguard the library index. And we will verify backups frequently by restoring entire disks and checking the files. It's a lesson we have learned the very hard way. Has anyone experienced problems with OSXS, Apple RAID and firewire AIT tape drives? I'd still like to know what happened. Thanks for any help. Link to comment Share on other sites More sharing options...
AmyJ Posted July 29, 2002 Report Share Posted July 29, 2002 Can you provide specific information about the tape drive? While in Retrospect, go to Configure > Devices > Device Status, and list Vendor, Product and Version for your tape drive. In reply to: We use a firewire LaCie enclosure with a Sony AIT1 tape drive as a backup medium. Did this drive come natively in a Firewire enclosure or did you configure it yourself? Is your Firewire drive on a chain with other Firewire drives or is it isolated? Were there any errors during the original backups, that you can recall? Link to comment Share on other sites More sharing options...
anthoc Posted July 30, 2002 Author Report Share Posted July 30, 2002 The enclosure was supplied as is from La Cie Australia with the AIT drive installed. Model for the AIT drive is Sony SDX-420C 0102 Sony AIT DC (5.01). The drive is the only device on the firewire bus. We have the ATTO scsi card installed along with two Asante ethernet cards. The original backup logs were lost (another lesson) but we did have the apple events feature activated so that Retrospect emailed the logs to us every night. The logs show the usual execution errors mainly because we have some japanese language file names and Retrospect doesn't like them. Logs were emailed as normal with backup reports stating successful backups until 18th july when everything fell apart. A sample of on log is below. From: Anthony O'Connell Date: Thu Jul 18, 2002 03:07:47 pm Australia/Melbourne To: peterd@192.168.71.62 Subject: 7/18/02 3:07:46pm Backup Server Report Report generated by Retrospect, Copyright 2002 Dantz Development Corporation. ---------------------- From Backup Server: Retrospect Backup Server backed up 0 volume(s) in the last 12 hours. Backup Server reported no errors. From: <*************@**********> Date: Thu Jul 18, 2002 03:07:16 am Australia/Melbourne To: <*************@**********> Subject: 7/18/02 3:07:16am Error in Backup Server Report Report generated by Retrospect, Copyright 2002 Dantz Development Corporation. ---------------------- From Backup Server: Volume " Local Desktop:Pireaus" completed successfully, copying 42 files for 23496 K with 3 errors. Script "Ork" finished copying volume " Local Desktop:Pireaus" to destination "Mindy [001]". Duration: 36 seconds. ---------------------- Volume " Local Desktop:Docs" completed successfully, copying 0 files for 0 K with 0 errors. Script "Ork" finished copying volume " Local Desktop:Docs" to destination "Mindy [001]". Duration: zero seconds. ---------------------- Volume " Local Desktop:tmp" completed successfully, copying 0 files for 0 K with 0 errors. Script "Ork" finished copying volume " Local Desktop:tmp" to destination "Mindy [001]". Duration: zero seconds. --------------------- Volume " Local Desktop:user" completed successfully, copying 6 files for 760 K with 0 errors. Script "Ork" finished copying volume " Local Desktop:user" to destination "Mindy [001]". Duration: 20 seconds. ---------------------- Volume " Local Desktop:users1" completed successfully, copying 162 files for 24312 K with 188 errors. Script "Ork" finished copying volume " Local Desktop:users1" to destination "Mindy [001]". Duration: 33 seconds. ---------------------- Volume " Local Desktop:user2" completed successfully, copying 3 files for 176 K with 0 errors. Script "Ork" finished copying volume " Local Desktop:user2" to destination "Mindy [001]". Duration: 13 seconds. ---------------------- Volume " Local Desktop:users3" completed successfully, copying 27 files for 49598 K with 27 errors. Script "Ork" finished copying volume " Local Desktop:users3" to destination "Mindy [001]". Duration: 34 seconds. ---------------------- Volume " Local Desktop:Programs" completed successfully, copying 104 files for 31618 K with 13 errors. Script "Ork" finished copying volume " Local Desktop:Programs" to destination "Mindy [001]". Duration: 38 seconds. ---------------------- Volume " Local Desktop:Mikey" completed successfully, copying 10 files for 63419 K with 0 errors. Script "Ork" finished copying volume " Local Desktop:Mikey" to destination "Mindy [001]". Duration: 54 seconds. ---------------------- Volume " Local Desktop:Disk2" completed successfully, copying 0 files for 0 K with 0 errors. Script "Ork" finished copying volume " Local Desktop:Disk2" to destination "Mindy [001]". Duration: zero seconds. ---------------------- Volume " Local Desktop:Disk4" completed successfully, copying 0 files for 0 K with 0 errors. Script "Ork" finished copying volume " Local Desktop:Disk4" to destination "Mindy [001]". Duration: zero seconds. ---------------------- Retrospect Backup Server backed up 42 volume(s) in the last 12 hours. Backup Server reported 21 errors. Link to comment Share on other sites More sharing options...
AmyJ Posted July 31, 2002 Report Share Posted July 31, 2002 Can you please verify: You are getting out of memory errors rebuilding a backup set catalog while booted into OS X? How much memory do you have on this computer? Also, you indicated that you are getting corrupt catalog errors - what are the exact error messages that you are getting? Link to comment Share on other sites More sharing options...
anthoc Posted July 31, 2002 Author Report Share Posted July 31, 2002 768 MB built in. I would have thought would be enough. I have tried to rebuild the catalog files on both OS X and OS X Server (different machines) with the same results. I've attached a copy of the log file below down to the point where it gives up with an out-of-memory error. Sorry about the size of the posting. I've included the whole log from a single tape recatalog process. Retrospect version 5.0.205 launched at 26/7/2002 9:00am + Retrospect Driver Update, version 2.8.103 + Executing Recatalog at 26/7/2002 9:06am To backup set Mindy [001]… Bad backup set header found (0xb338ae3d at 2,254,366). Backup set format inconsistency (6 at 2254824) Backup set format inconsistency (4 at 2766336) Backup set format inconsistency (4 at 3278336) Backup set format inconsistency (4 at 3790336) Backup set format inconsistency (4 at 4302336) Backup set format inconsistency (4 at 4814336) Backup set format inconsistency (4 at 5326336) Bad backup set header found (0x65004a00 at 5,511,192). Backup set format inconsistency (4 at 6023168) Backup set format inconsistency (4 at 6535168) Bad backup set header found (0x616e0d73 at 6,923,277). Backup set format inconsistency (6 at 6923582) Backup set format inconsistency (4 at 7435264) Backup set format inconsistency (4 at 7947264) Backup set format inconsistency (4 at 8459264) Backup set format inconsistency (4 at 8971264) Backup set format inconsistency (4 at 9483264) Backup set format inconsistency (6 at 9698065) Backup set format inconsistency (4 at 10209792) Bad backup set header found (0x3e0a0909 at 10,672,645). Backup set format inconsistency (6 at 10672678) Backup set format inconsistency (4 at 11184640) Backup set format inconsistency (4 at 11696640) Bad backup set header found (0x483b0100 at 11,788,311). Bad backup set header found (0x69616c6f at 11,788,319). Backup set format inconsistency (6 at 11788391) Backup set format inconsistency (4 at 12300288) Backup set format inconsistency (4 at 12812288) Backup set format inconsistency (4 at 13324288) Backup set format inconsistency (4 at 13836288) Backup set format inconsistency (4 at 14348288) Backup set format inconsistency (4 at 14860288) Backup set format inconsistency (4 at 15372288) Backup set format inconsistency (4 at 15884288) Backup set format inconsistency (4 at 16396288) Backup set format inconsistency (4 at 16908288) Backup set format inconsistency (4 at 17420288) Backup set format inconsistency (4 at 17932288) Backup set format inconsistency (4 at 18444288) Backup set format inconsistency (4 at 18956288) Backup set format inconsistency (4 at 19468288) Backup set format inconsistency (4 at 19980288) Backup set format inconsistency (4 at 20492288) Backup set format inconsistency (4 at 21004288) Backup set format inconsistency (4 at 21516288) Backup set format inconsistency (4 at 22028288) Bad backup set header found (0x6f006600 at 22,279,192). Backup set format inconsistency (6 at 22279361) Backup set format inconsistency (4 at 22791168) Backup set format inconsistency (4 at 23303168) Backup set format inconsistency (4 at 23815168) Backup set format inconsistency (4 at 24327168) Backup set format inconsistency (4 at 24839168) Backup set format inconsistency (4 at 25351168) Bad backup set header found (0x72742056 at 25,559,567). Backup set format inconsistency (6 at 25559625) Bad backup set header found (0x72742056 at 25,634,318). Bad backup set header found (0x30322031 at 25,661,977). Bad backup set header found (0x6f6f6b6d at 25,907,207). Bad backup set header found (0x64696374 at 26,090,512). Bad backup set header found (0x29207769 at 26,449,417). Bad backup set header found (0x726f6261 at 26,551,325). Bad backup set header found (0x6e3c2f6b at 26,556,945). Bad backup set header found (0x6f72697a at 27,223,578). Backup set format inconsistency (12 at 27448324) Bad backup set header found (0x65433055 at 25,351,301). Backup set format inconsistency (4 at 25401472) Bad backup set header found (0x6c006c00 at 25,742,994). Bad backup set header found (0x1108636f at 25,746,058). Bad backup set header found (0x650a004d at 25,747,086). Backup set format inconsistency (6 at 25747102) Bad backup set header found (0x233a2321 at 25,747,604). Bad backup set header found (0x6f752073 at 25,751,693). Bad backup set header found (0x03626364 at 25,754,253). Bad backup set header found (0x34203138 at 25,758,365). Backup set format inconsistency (4 at 25795712) Bad backup set header found (0x61012000 at 25,797,255). Backup set format inconsistency (6 at 25797460) Bad backup set header found (0xbe003800 at 25,929,356). Backup set format inconsistency (6 at 25929542) Bad backup set header found (0x20202020 at 25,930,886). Backup set format inconsistency (6 at 25931166) Bad backup set header found (0x6e120001 at 25,987,220). Backup set format inconsistency (6 at 25987519) Bad backup set header found (0x20000800 at 26,090,642). Backup set format inconsistency (6 at 26090782) Bad backup set header found (0x3022204c at 26,091,651). Backup set format inconsistency (6 at 26092111) Bad backup set header found (0x73636170 at 26,163,864). Backup set format inconsistency (4 at 26183808) Bad backup set header found (0x206e762d at 26,430,094). Backup set format inconsistency (4 at 26942080) Backup set format inconsistency (4 at 27454080) Backup set format inconsistency (4 at 27966080) Bad backup set header found (0x23204e65 at 28,078,210). Bad backup set header found (0x57364f61 at 28,099,223). Bad backup set header found (0x4a756e20 at 28,233,879). Bad backup set header found (0x726b293b at 28,241,049). Bad backup set header found (0x6d652063 at 28,253,836). Bad backup set header found (0x743e0a54 at 28,259,475). Bad backup set header found (0x4d006100 at 28,363,924). Bad backup set header found (0x5f313022 at 28,364,436). Backup set format inconsistency (4 at 28822144) Bad backup set header found (0x2f452d4d at 28,929,693). Bad backup set header found (0xe056a159 at 28,965,527). Bad backup set header found (0xaf30bf30 at 28,967,068). Backup set format inconsistency (6 at 28967135) Bad backup set header found (0xffffffff at 28,994,212). Bad backup set header found (0x06fffcff at 28,995,201). Backup set format inconsistency (6 at 28995486) Bad backup set header found (0xda313587 at 29,105,306). Backup set format inconsistency (6 at 29105310) Bad backup set header found (0x696e673e at 29,236,362). Bad backup set header found (0x08508b45 at 29,237,908). Backup set format inconsistency (6 at 29238363) Backup set format inconsistency (4 at 29749888) Backup set format inconsistency (4 at 30261888) Backup set format inconsistency (5 at 30535812) Backup set format inconsistency (6 at 30535877) Backup set format inconsistency (4 at 31047808) Bad backup set header found (0x7f1f3de1 at 31,438,492). Backup set format inconsistency (6 at 31438533) Bad backup set header found (0xffffffff at 31,509,149). Bad backup set header found (0x63617264 at 31,529,609). Bad backup set header found (0x45520949 at 31,673,490). Backup set format inconsistency (4 at 32185472) Backup set format inconsistency (4 at 32697472) Bad backup set header found (0x3d010000 at 32,713,371). Bad backup set header found (0x3d226874 at 32,745,092). Backup set format inconsistency (4 at 32747648) Backup set format inconsistency (4 at 32883328) Bad backup set header found (0x643a2066 at 32,891,022). Bad backup set header found (0x20477261 at 32,904,351). Bad backup set header found (0x656e3c2f at 32,909,973). Backup set format inconsistency (4 at 33021056) Bad backup set header found (0x65740954 at 33,021,584). Backup set format inconsistency (4 at 33533568) Bad backup set header found (0x093c6b65 at 33,574,532). Bad backup set header found (0x2d657272 at 33,684,622). Bad backup set header found (0x1c000400 at 33,790,593). Bad backup set header found (0xdaf54263 at 33,827,466). Bad backup set header found (0x8b307cff at 33,829,019). Backup set format inconsistency (6 at 33829374) Bad backup set header found (0x68010000 at 33,928,848). Backup set format inconsistency (6 at 33929252) Bad backup set header found (0xffffffff at 33,941,131). Backup set format inconsistency (6 at 33941630) Bad backup set header found (0x6e120001 at 34,117,780). Backup set format inconsistency (6 at 34117919) Bad backup set header found (0x400abb5c at 34,215,072). Backup set format inconsistency (6 at 34215275) Backup set format inconsistency (6 at 34227093) Bad backup set header found (0x3a203c6e at 34,253,958). Bad backup set header found (0x25374243 at 34,398,853). Backup set format inconsistency (4 at 34910848) Backup set format inconsistency (4 at 35422848) Bad backup set header found (0x6e642043 at 35,877,523). Backup set format inconsistency (6 at 35877543) Bad backup set header found (0x414d6341 at 36,049,042). Bad backup set header found (0x6f722079 at 36,062,360). Bad backup set header found (0x6c626f78 at 36,065,427). Bad backup set header found (0x2876312e at 36,145,294). Bad backup set header found (0x5b287d3c at 36,198,543). Backup set format inconsistency (4 at 36710528) Bad backup set header found (0x6472656e at 36,747,910). Bad backup set header found (0x723e3c2f at 36,840,076). Bad backup set header found (0x3030315d at 36,847,759). Bad backup set header found (0xffffffff at 36,883,616). Backup set format inconsistency (6 at 36884117) Bad backup set header found (0x02000400 at 36,885,642). Backup set format inconsistency (6 at 36885844) Bad backup set header found (0x036c0061 at 37,054,087). Backup set format inconsistency (6 at 37054873) Bad backup set header found (0xffffffff at 37,056,667). Backup set format inconsistency (6 at 37057118) Bad backup set header found (0x1000523a at 37,106,325). Backup set format inconsistency (6 at 37106700) Bad backup set header found (0x1fc0c082 at 37,237,908). Backup set format inconsistency (6 at 37238502) Bad backup set header found (0x636f6d70 at 37,240,450). Backup set format inconsistency (6 at 37240675) Bad backup set header found (0x362c3530 at 37,241,475). Bad backup set header found (0x7474703a at 37,245,585). Backup set format inconsistency (6 at 37245704) Bad backup set header found (0x2f2f2f2f at 37,360,780). Backup set format inconsistency (4 at 37503616) Backup set format inconsistency (4 at 38015616) Backup set format inconsistency (4 at 38527616) Bad backup set header found (0x430d320d at 39,003,293). Backup set format inconsistency (4 at 39544960) Backup set format inconsistency (4 at 40056960) Backup set format inconsistency (4 at 40568960) Not enough memory 26/7/2002 11:14:13am: Execution incomplete. Completed: 172917 files, 38.9 GB Performance: 311.8 MB/minute Duration: 02:07:54 (00:00:23 idle/loading/preparing) Link to comment Share on other sites More sharing options...
rang Posted August 1, 2002 Report Share Posted August 1, 2002 Interesting. I actually came to the forum tonight to ask about a similar problem. I have a LaCie AIT+ FireWire drive (the type with both USB and 1394) and had occasion a couple of days ago to try to retrieve an older snapshot from the media. I got an error, at which point I decided to verify the backup set, and then rebuild the catalog. Both the verification and rebuild gave me a set of errors very similar to yours (including the bad backup set headers). I'm running on a G4 Cube, Mac OS X 10.1.5 (but some of the backups predate that), with Retrospect 5.0.205 and the latest driver update (though again, the backups mostly predate it of course). I'm going to try backing up to a new tape tonight to see if I still get the errors. I'm not sure which model of Sony drive this is, as I've got a backup in progress right now and can't check. Link to comment Share on other sites More sharing options...
anthoc Posted August 1, 2002 Author Report Share Posted August 1, 2002 There well be a bug here with the Retrospect re-catalogging function either related to the driver update (the update may fix it) or to the OS X version of Retrospect. All of the problem tapes were created per-RDU. I have rebuilt the server and achieved what appear to be successful backups every night to clean tapes. We haven't tried a restore or re-catalog yet. Hard to do with a production server and 45 users. I very interested to know if you have the same model drive as we do. For your info we have adopted a belt and braces approach after the server collapse. 1. At 8pm we backup each individual disk from scsi channel 1 to individual disks in scsi channel 2 using retrospect backup to a combined data and catalog file. 2. At 10pm we backup both sets of disks to the AIT tapes. 3. At 5am we ftp the catalog files from the main server to another server to protect the files from internal disk failure 4. Every day we duplicate the internal boot disk using Carbon Copy Cloner utility by Mike Bombich This doesn't solve the original problem nut it might help better secure our data in the future. Link to comment Share on other sites More sharing options...
rang Posted August 1, 2002 Report Share Posted August 1, 2002 I do have the Sony SDX-420C (Sony AIT DC 5.01 driver) ... same drive, probably the same enclosure too. I completed a full backup onto a new tape overnight and started a verification this morning. It should be interesting to see what happens; if it's a problem which was fixed by RDU that would be good to know (but calls out for better release notes). Link to comment Share on other sites More sharing options...
CallMeDave Posted August 1, 2002 Report Share Posted August 1, 2002 In reply to: For your info we have adopted a belt and braces approach... This is great. It even has a bit of elastic 'round the waist to keep things tidy! The ftp feature of the Macintosh version of Retrospect is one of its hidden gems; something that they never added to the Windows version. Dave Link to comment Share on other sites More sharing options...
rang Posted August 2, 2002 Report Share Posted August 2, 2002 So far, so good. A backup last night followed by a verify came up with no problems. I'm wondering now whether this was (a) fixed by one of the updates to Retrospect; ( something which only appears once there are a number of snapshots on the tape; © something which happens at random; or (d) related to backing up without catalog compression and then turning on compression later [this latter just because it's the only unusual thing I can think of with my backups]. I'll keep monitoring it to see what happens. Link to comment Share on other sites More sharing options...
rang Posted August 2, 2002 Report Share Posted August 2, 2002 Well, just found this on LaCie's web site. I wonder if it's still accurate? Time to drop them an email.... (When did I buy that drive anyway?) Q: Is my LaCie AIT1 U&I external USB 2.0 and FireWire Tape drive compatible with Retrospect Backup 5.0 for Mac OS X 10.1.2 or later? No. As of April 2002, the LaCie AIT1 U&I Tape drive is not compatible with Mac OS X and Retrospect Backup 5.0 when using the FireWire interface. A firmware update (for Oxford 911 bridge) is required to add tape drive functionality for Mac OS X and Retrospect 5. Please check bi-monthly with LaCie tech support or online support page for availability of this firmware. IMPORTANT! For the current time, please use the AIT1 U&I drive with Retrospect 4.3 and Macintosh systems (with native FireWire) running Mac OS 9.0.4 or later. This firmware update for Oxford 911 bridge applies to Mac OS X systems and does not affect or is required for Windows PC users. Link to comment Share on other sites More sharing options...
rang Posted August 3, 2002 Report Share Posted August 3, 2002 Heard back from La Cie technical support today ... and there is a firmware update for the drive available. It's built into the SilverLining 6.5.4a update. My drive had version 1.33 of the firmware; the one which LaCie says is required for reliable operation with Retrospect 5 and MacOS X is 1.34. In reply to: Thanks for contacting LaCie Technical Support. You should have a copy of Silverlining on the LaCie disk that came with the drive. Boot your computer into OS 9 and install the LaCie Firewire Support extension and the Silverlining Control Panel. Update to version 6.4.5a with the updater found on our website. Reboot. Follow the instructions below. The drive should have version 1.34 minimum installed. Bridge Update -- Boot your computer natively into OS 9.x 0. Install the latest version of Silverlining (6.4.5a), including the USB and/or Firewire support. These extensions are necessary for updating the drive. Reboot the computer. (If the Silverlining CD has 6.4.5a on it, then boot the computer from that CD if you are able.) 1. Open the Silverlining Pro Control Panel (SL), then turn the drive on and cable it in directly to the computer. Do NOT go through a hub. Click on the "Scan" button in SL. 2. Find the bus listed that the drive is connected to, and on that, find the drive. It will read something like: "Disk 0: ST360017A" or "DVD-RAM 0: Pioneer". If the drive shows as "Unknown", check and be sure the LaCie extensions are turned on. 3. Select this line so it highlights, then go up to Special on the Menu Bar and select "Update Firewire Firmware" (or USB as the case may be.) If a window pops up saying "Unable to reliably access this drive...", check the list of items below and make sure the correct device is selected. Then click OK. 4. Now, there should be a window up stating: "About to update firmware from version x.x.x to version x.x.x." Unless this was the window to pop up first and both versions are identical, click OK to run the update. 5. When the update is run, uncable the drive and shut it off. Close out of SL and open the Extensions Manager. Set the selected set to where it should be, or turn off the Lacie extensions if necessary. (They are not required at all with 9.1 or higher, and should also be turned off when using Toast.) Reboot the computer. Turn the drive back on and cable it in. The drive should now behave properly on Macs and PCs. 6. If the first attempt to update the firmware fails, try one more time. If it fails again, most like the firmware is bad and the drive will need repair. Link to comment Share on other sites More sharing options...
anthoc Posted August 4, 2002 Author Report Share Posted August 4, 2002 Thanks to everyone for their help. We'll be calling La Cia Australia first thing Monday to find out about upgrading our firmware version. We didn't get a CD or cleaning tape with our drive because it was the first in the country and probably came from the US directly to us without La Cie Aus knowing this problem. Funnily enough, we sent our dodgy tapes back to La Cie last week and they were able to catalog them all successfully. Seems like they have the newer firmware already so even though you may think you have corrupt data on your tapes, the data is probably there and retrievable with the firmware upgrade. Thanks again. Link to comment Share on other sites More sharing options...
lv2ski Posted August 5, 2002 Report Share Posted August 5, 2002 Yes, Ox911 Firmware 1.34 is native in the Silverlining Pro 6.4.5a Updater. Which is available on their Support, Driver download web page. http://www.lacie.com/support/drivers/index.cfm Their FAQ is out of date. With Retrospect 5.0.205, it will support the AIT1 U&I under Mac OS X 10.1.2 just fine. Link to comment Share on other sites More sharing options...
anthoc Posted August 6, 2002 Author Report Share Posted August 6, 2002 Just confirmed that we had the old firmware version. We upgraded yesterday to 1.34. Great work everybody. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.