ComputerX Posted January 23, 2006 Report Share Posted January 23, 2006 Any idea why we are getting this? Disk 5 in a 5 disk set filled up. I enabled grooming but I don't believe that a grooming was ever successful. About the same time the drive where the catalogs are stored filled up. Grooming never succeeded and backups started failing with errors like this. Code: - 1/19/2006 11:05:06 AM: Copying RetroRestore on On Boot (D:) 1/19/2006 11:05:06 AM: No files need to be copied Grooming Backup Set Blue... Grooming Backup Set Blue failed, error -808 (key/refnum search failed) 1/19/2006 11:38:28 AM: Execution stopped by operator Duration: 00:33:21 (00:33:21 idle/loading/preparing) So I deleted the catalog and am attempting to rebuild but that is failing also. Errors like thi. Code: + Executing Recatalog at 1/22/2006 8:22 PM (Execution unit 1) To Backup Set Blue... TMemory: heap 8500 256.1 M virtual 15 82.5 M commit 82.5 M purgeable 981 zero K Pool:pools, users 4470 495 max allowed mem 307.0 M max block size 8,192 K total mem blocks 1 8,192 K used mem blocks 1 8,192 K file count, size 1 8,192 K requested 8515 324.2 M purgeable 981 zero K avail vm size 194,031,616 B TMemory::mhalloc: VirtualAlloc(109.0 M, MEM_RESERVE) failed, error 8 TMemory: heap 8501 256.1 M virtual 15 82.5 M commit 82.5 M purgeable 981 zero K Pool:pools, users 4470 495 max allowed mem 307.0 M max block size 8,192 K total mem blocks 1 8,192 K used mem blocks 1 8,192 K file count, size 1 8,192 K requested 8516 324.2 M purgeable 981 zero K avail vm size 194,031,616 B TMemory::mhalloc: VirtualAlloc(109.0 M, MEM_RESERVE) failed, error 8 Backup Set format inconsistency (6 at 779903989) 1/23/2006 11:45:07 AM: Execution incomplete Completed: 3354313 files, 743.8 GB Performance: 870.1 MB/minute Duration: 14:19:05 (00:46:56 idle/loading/preparing) The machine has 1 GB of RAM and plenty of CPU. The storage set is about 1.2 TB. Any idea what it could be? Memtest86 says the memory is fine. Dan Link to comment Share on other sites More sharing options...
natew Posted January 26, 2006 Report Share Posted January 26, 2006 Hi What version of Retrospect 7 are you using? Make sure to get the latest application update and driver updates from the EMC Dantz updates site. Thanks Nate Link to comment Share on other sites More sharing options...
ComputerX Posted January 26, 2006 Author Report Share Posted January 26, 2006 The latest Retrospect and the next to latest RDU. The read me from the RDU didn't mention bug fixes so I didn't install it. Each time I attempt a backup to this set Retrospect starts rebuilding the catalog and eventually stops offering me a choice to save or delete what it has done so far. I save then reboot the server. Then I try a backup and start the process over. I keep trying to find a pattern but every time I think I have something repeatable something new happens. The Retrospect GUI has frozen with the CPU at 100% while FileMon shows this. Code: 1 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 2 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: * 3 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 4 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 5 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION C:\ SUCCESS FileNameInformation 6 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION C:\ SUCCESS FileFsVolumeInformation 7 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION C:\ SUCCESS FileFsAttributeInformation 8 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 9 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 10 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION C:\ SUCCESS FileFsFullSizeInformation 11 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 12 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 13 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION C:\ SUCCESS FileNameInformation 14 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION C:\ SUCCESS FileFsSizeInformation 15 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 16 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 17 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: WINDOWS 18 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 19 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 20 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: * 21 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 22 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 23 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: WINDOWS 24 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 25 11:31:35 AM Retrospect.exe:568 OPEN D:\ SUCCESS Options: Open Directory Access: All 26 11:31:35 AM Retrospect.exe:568 DIRECTORY D:\ SUCCESS FileBothDirectoryInformation: * 27 11:31:35 AM Retrospect.exe:568 CLOSE D:\ SUCCESS 28 11:31:35 AM Retrospect.exe:568 OPEN D:\ SUCCESS Options: Open Directory Access: All 29 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION D:\ SUCCESS FileNameInformation 30 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION D:\ SUCCESS FileFsVolumeInformation 31 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION D:\ SUCCESS FileFsAttributeInformation 32 11:31:35 AM Retrospect.exe:568 CLOSE D:\ SUCCESS 33 11:31:35 AM Retrospect.exe:568 OPEN D:\ SUCCESS Options: Open Directory Access: All 34 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION D:\ SUCCESS FileFsFullSizeInformation 35 11:31:35 AM Retrospect.exe:568 CLOSE D:\ SUCCESS 36 11:31:35 AM Retrospect.exe:568 OPEN D:\ SUCCESS Options: Open Directory Access: All 37 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION D:\ SUCCESS FileNameInformation 38 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION D:\ SUCCESS FileFsSizeInformation 39 11:31:35 AM Retrospect.exe:568 CLOSE D:\ SUCCESS 40 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 41 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: WINDOWS 42 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 43 11:31:35 AM Retrospect.exe:568 OPEN D:\ SUCCESS Options: Open Directory Access: All 44 11:31:35 AM Retrospect.exe:568 DIRECTORY D:\ SUCCESS FileBothDirectoryInformation: * 45 11:31:35 AM Retrospect.exe:568 CLOSE D:\ SUCCESS 46 11:31:35 AM Retrospect.exe:568 OPEN H:\ SUCCESS Options: Open Directory Access: All 47 11:31:35 AM Retrospect.exe:568 DIRECTORY H:\ SUCCESS FileBothDirectoryInformation: * 48 11:31:35 AM Retrospect.exe:568 CLOSE H:\ SUCCESS 49 11:31:35 AM Retrospect.exe:568 OPEN H:\ SUCCESS Options: Open Directory Access: All 50 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION H:\ SUCCESS FileNameInformation 51 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION H:\ SUCCESS FileFsVolumeInformation 52 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION H:\ SUCCESS FileFsAttributeInformation 53 11:31:35 AM Retrospect.exe:568 CLOSE H:\ SUCCESS 54 11:31:35 AM Retrospect.exe:568 OPEN H:\ SUCCESS Options: Open Directory Access: All 55 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION H:\ SUCCESS FileFsFullSizeInformation 56 11:31:35 AM Retrospect.exe:568 CLOSE H:\ SUCCESS 57 11:31:35 AM Retrospect.exe:568 OPEN H:\ SUCCESS Options: Open Directory Access: All 58 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION H:\ SUCCESS FileNameInformation 59 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION H:\ SUCCESS FileFsSizeInformation 60 11:31:35 AM Retrospect.exe:568 CLOSE H:\ SUCCESS 61 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 62 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: WINDOWS 63 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 64 11:31:35 AM Retrospect.exe:568 OPEN H:\ SUCCESS Options: Open Directory Access: All 65 11:31:35 AM Retrospect.exe:568 DIRECTORY H:\ SUCCESS FileBothDirectoryInformation: * 66 11:31:35 AM Retrospect.exe:568 CLOSE H:\ SUCCESS 67 11:31:35 AM Retrospect.exe:568 OPEN I:\ SUCCESS Options: Open Directory Access: All 68 11:31:35 AM Retrospect.exe:568 DIRECTORY I:\ SUCCESS FileBothDirectoryInformation: * 69 11:31:35 AM Retrospect.exe:568 CLOSE I:\ SUCCESS 70 11:31:35 AM Retrospect.exe:568 OPEN I:\ SUCCESS Options: Open Directory Access: All 71 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION I:\ SUCCESS FileNameInformation 72 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION I:\ SUCCESS FileFsVolumeInformation 73 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION I:\ SUCCESS FileFsAttributeInformation 74 11:31:35 AM Retrospect.exe:568 CLOSE I:\ SUCCESS 75 11:31:35 AM Retrospect.exe:568 OPEN I:\ SUCCESS Options: Open Directory Access: All 76 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION I:\ SUCCESS FileFsFullSizeInformation 77 11:31:35 AM Retrospect.exe:568 CLOSE I:\ SUCCESS 78 11:31:35 AM Retrospect.exe:568 OPEN I:\ SUCCESS Options: Open Directory Access: All 79 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION I:\ SUCCESS FileNameInformation 80 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION I:\ SUCCESS FileFsSizeInformation 81 11:31:35 AM Retrospect.exe:568 CLOSE I:\ SUCCESS 82 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 83 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: WINDOWS 84 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 85 11:31:35 AM Retrospect.exe:568 OPEN I:\ SUCCESS Options: Open Directory Access: All 86 11:31:35 AM Retrospect.exe:568 DIRECTORY I:\ SUCCESS FileBothDirectoryInformation: * 87 11:31:35 AM Retrospect.exe:568 CLOSE I:\ SUCCESS 88 11:31:35 AM Retrospect.exe:568 OPEN J:\ SUCCESS Options: Open Directory Access: All 89 11:31:35 AM Retrospect.exe:568 DIRECTORY J:\ SUCCESS FileBothDirectoryInformation: * 90 11:31:35 AM Retrospect.exe:568 CLOSE J:\ SUCCESS 91 11:31:35 AM Retrospect.exe:568 OPEN J:\ SUCCESS Options: Open Directory Access: All 92 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION J:\ SUCCESS FileNameInformation 93 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION J:\ SUCCESS FileFsVolumeInformation 94 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION J:\ SUCCESS FileFsAttributeInformation 95 11:31:35 AM Retrospect.exe:568 CLOSE J:\ SUCCESS 96 11:31:35 AM Retrospect.exe:568 OPEN J:\ SUCCESS Options: Open Directory Access: All 97 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION J:\ SUCCESS FileFsFullSizeInformation 98 11:31:35 AM Retrospect.exe:568 CLOSE J:\ SUCCESS 99 11:31:35 AM Retrospect.exe:568 OPEN J:\ SUCCESS Options: Open Directory Access: All 100 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION J:\ SUCCESS FileNameInformation 101 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION J:\ SUCCESS FileFsSizeInformation 102 11:31:35 AM Retrospect.exe:568 CLOSE J:\ SUCCESS 103 11:31:35 AM Retrospect.exe:568 OPEN C:\ SUCCESS Options: Open Directory Access: All 104 11:31:35 AM Retrospect.exe:568 DIRECTORY C:\ SUCCESS FileBothDirectoryInformation: WINDOWS 105 11:31:35 AM Retrospect.exe:568 CLOSE C:\ SUCCESS 106 11:31:35 AM Retrospect.exe:568 OPEN J:\ SUCCESS Options: Open Directory Access: All 107 11:31:35 AM Retrospect.exe:568 DIRECTORY J:\ SUCCESS FileBothDirectoryInformation: * 108 11:31:35 AM Retrospect.exe:568 CLOSE J:\ SUCCESS 109 11:31:35 AM Retrospect.exe:568 OPEN K:\ SUCCESS Options: Open Directory Access: All 110 11:31:35 AM Retrospect.exe:568 DIRECTORY K:\ SUCCESS FileBothDirectoryInformation: * 111 11:31:35 AM Retrospect.exe:568 CLOSE K:\ SUCCESS 112 11:31:35 AM Retrospect.exe:568 OPEN K:\ SUCCESS Options: Open Directory Access: All 113 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION K:\ SUCCESS FileNameInformation 114 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION K:\ SUCCESS FileFsVolumeInformation 115 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION K:\ SUCCESS FileFsAttributeInformation 116 11:31:35 AM Retrospect.exe:568 CLOSE K:\ SUCCESS 117 11:31:35 AM Retrospect.exe:568 OPEN K:\ SUCCESS Options: Open Directory Access: All 118 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION K:\ SUCCESS FileFsFullSizeInformation 119 11:31:35 AM Retrospect.exe:568 CLOSE K:\ SUCCESS 120 11:31:35 AM Retrospect.exe:568 OPEN K:\ SUCCESS Options: Open Directory Access: All 121 11:31:35 AM Retrospect.exe:568 QUERY INFORMATION K:\ SUCCESS FileNameInformation That goes on for a very long time. Eventually FileMon showed access to the catalog with the GUI still frozen and the CPU still at 100%. Then the GUI came back and this was in the log. Code: + Executing Immediate Backup at 1/25/2006 11:14 AM (Execution unit 2) To Backup Set Blue... - 1/25/2006 11:14:43 AM: Copying RetroRestore on On Boot (D:) 1/25/2006 11:14:43 AM: No files need to be copied TMemory: heap 5912 187.1 M virtual 14 92.5 M commit 92.5 M purgeable 89 zero K Pool:pools, users 2940 49 max allowed mem 307.0 M max block size 8,192 K total mem blocks 1 8,192 K used mem blocks 1 8,192 K file count, size 0 zero K requested 5926 230.2 M purgeable 89 zero K avail vm size 414,265,344 B TMemory::mhalloc: VirtualAlloc(118.5 M, MEM_RESERVE) failed, error 8 TMemory: heap 5913 187.1 M virtual 14 92.5 M commit 92.5 M purgeable 89 zero K Pool:pools, users 2940 49 max allowed mem 307.0 M max block size 8,192 K total mem blocks 1 8,192 K used mem blocks 1 8,192 K file count, size 0 zero K requested 5927 230.2 M purgeable 89 zero K avail vm size 414,265,344 B TMemory::mhalloc: VirtualAlloc(118.5 M, MEM_RESERVE) failed, error 8 Backup Set format inconsistency (6 at 1027643561) 1/26/2006 11:47:29 AM: Snapshot stored, 9 KB 1/26/2006 11:50:34 AM: Comparing RetroRestore on On Boot (D:) 1/26/2006 11:53:30 AM: 1 execution errors Duration: 1 00:38:49 (01:05:34 idle/loading/preparing) I'm going to reboot now and see what happens. I will install the latest RDU while I am at it. This storage set spans 5 250 GB disks and I thought the catalog file might be too big. When I left yesterday it was over 6 GB. Now the catalog is back down to 2.2 GB. How can I get this working without losing 1.2 TB of data in the backup set? Dan Link to comment Share on other sites More sharing options...
natew Posted February 2, 2006 Report Share Posted February 2, 2006 Hi By latest you mean Retrospect 7.0.326 right? These are memory allocation errors i.e. Retrospect couldn't get enough memory to process this data. How much memory do you have on this machine? Make sure you have at least 2 or 3 gigs of free space on the system disk too. Nate Link to comment Share on other sites More sharing options...
ComputerX Posted February 2, 2006 Author Report Share Posted February 2, 2006 It is version 7.0.326. The machine has a gig of memory. There are 2.2 GB free on the system volume. I also noticed that the "System Cache" in the task manager was using a lot of memory. It was using 595,596 and Retrospect was using 306,036 when I started this thread. Retrospect regularly locks its GUI. I have see a 14 hour delta between the time shown in the Retrospect GUI and the system time. According to FileMon it is still busy so I allow it to run. I used to kill the process when it got like that and I wonder if I did some damage. I have a backup currently running to that storage set. It has been running for 94 hours but FileMon is still showing activity in the catalog file so I am letting it run. Does grooming take place when the proactive server is running? Dan PS Currently Retrospect is using 79,536 and the system cache is 177,112. I am just a little into swap and the GUI is responding. Link to comment Share on other sites More sharing options...
natew Posted February 10, 2006 Report Share Posted February 10, 2006 Hi This could be pretty tight depending on how many executions are running and how many files are being backed up. Freeing up some space on the system disk or adding RAM would be a good place to start. Grooming could be running. That can certainly take a lot of memory and CPU. How much free space is available on the disk where the backup set is stored? Nate Link to comment Share on other sites More sharing options...
ComputerX Posted February 10, 2006 Author Report Share Posted February 10, 2006 The volume with the catalog files had 60GB free. I just cleaned up the system drive (transferred a storage set to DVDs) and it now has over 7GB free. The catalog file just got out of sync after working for several days. I think I am going to bite the bullet and wipe the storage set. I hate to lose over a TB of backups but I have two other sets that have been going fine for a while now so I have duplicates of the most recent 15% or so. Is 7.5 any more stable than 7 is? Dan Link to comment Share on other sites More sharing options...
Mayoff Posted February 11, 2006 Report Share Posted February 11, 2006 7.5 fixes many of the grooming issues user's have reported. Link to comment Share on other sites More sharing options...
ComputerX Posted February 12, 2006 Author Report Share Posted February 12, 2006 I updated to 7.5 and it managed to run just over 12 hours before crashing. At least it had the decency to write to the assert_log. 7.0 didn't do that. The errors keep seeming like memory errors but I have run memtest on this box for over 72 hours without an error. Sometimes it seems like I have more problems writing to the SATA drives than the PATA drives. Here is the start of the latest crash from the log. Code: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX OS: Windows 2000 version 5.0 (build 2195), Service Pack 4, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.5\Retrospect.exe, version 7.5.251 Exception occurred on 2/11/2006 at 3:53:30 AM Exception code: C0000005 ACCESS_VIOLATION Fault address: 609756BE 0001:000746BE PCVOL.DLL Thread ID: 000004C0, Name: Execution thread EAX:00000000 CS:001B EIP:609756BE EFlags:00010246 EBX:02EF4FBC SS:0023 ESP:478B3E38 EBP: 478B47F0 ECX:02D88F9C DS:0023 ESI:02F1C5A0 FS: 003B EDX:4062AE85 ES:0023 EDI:00000000 GS: 0000 Module Fn (symbol or seg:offset in DLL) Args =============== ================================= ======================================================================= PCVOL.DLL tptrHLoad +A7E 02F8C434 108AD00C 02F3F434 02DE1764 00000040 0000000E 478B48AC 478B48D8 meson.dll ModuleData::send +4E7 02F8C434 'Thld' 108AD00C 02F3F434 02DE1764 00000040 0000100E 478B48AC Link to comment Share on other sites More sharing options...
ComputerX Posted February 12, 2006 Author Report Share Posted February 12, 2006 Another question... Do you have any recommendations for "best practices"? What is the best OS for Retrospect? Should I compress catalogs or not? Server scripts vs. backup scripts? I generally use all server scripts except for duplicat scripts. Should I switch my servers over to backup scripts? If I use backup scripts is there a way to have them use whatever set is available? I use external firewire drives for my primary backups and I don't change them on a regular schedule. Dan Link to comment Share on other sites More sharing options...
michaeln Posted February 14, 2006 Report Share Posted February 14, 2006 Hi, This could be an issue with the volume the backup data resides on. If possible, could you try copying the disk backup set data to another drive (might be hard if your set is a TB) and then run backups. Also, did you try rebuilding the catalog first with 7.5? Ideally it's best to keep multiple smaller sets (for redundancy and speed performance purposes) instead of one large set. Personally I have managed to groom a 1.3 TB set with 7.5 but I wouldn't recommend letting the disk backup set get this big. Link to comment Share on other sites More sharing options...
mauricev Posted February 15, 2006 Report Share Posted February 15, 2006 Quote: Personally I have managed to groom a 1.3 TB set with 7.5 but I wouldn't recommend letting the disk backup set get this big. That's not big. Link to comment Share on other sites More sharing options...
ComputerX Posted February 15, 2006 Author Report Share Posted February 15, 2006 The set has 5 250 GB drives. There used to be a sixth drive but I never got much data on it so I tend to forget about it now. The problems do seem to appear once drives five and six start storing data. The first four drives are PATA and the last two are SATA. I have exercised all the drives pretty well and tested them with several utilities. The current drives don't have a problem. I have also tried two different SATA controllers. I recatalogged without the last three drives and it seems to be working well now with the data being stored on the fourth (PATA) drive. It has only been a few days. We will see how it goes. The six drives were the way the system was originally designed. There were to be two 750 GB sets. The internal drives were never reliable so I got a pair of external (firewire) 1 TB drives that get the real backups now. Since I have the internal drives I am using them for a third set that also includes the media files that I don't usually back up. The firewire drives have been reliable. I don't intend to groom them. They are staggered so I can recycle and still have a couple months data on the other set. I was hoping to groom the set on the internal drives. I am going to buy another gig of memory. 7.5 doesn't seem to have the problems that 7.0 has but it can't hurt. If I have to completely rebuild the internal set I think I will put the SATA drives first and see if the problem is a SATA problem or a storage set size problem. Dan Link to comment Share on other sites More sharing options...
natew Posted February 22, 2006 Report Share Posted February 22, 2006 Hi I have talked to customers in the past who had problems using PATA and SATA drives together. There were problems in transferring data between the two and all kinds of errors resulted. Are the drivers for both controllers up to date? Chipset drivers for the motherboard are another thing to look into. Thanks Nate Link to comment Share on other sites More sharing options...
ComputerX Posted February 22, 2006 Author Report Share Posted February 22, 2006 Yep. Drivers are all up to date and I have tried older drivers and Microsoft drivers too. In fact I have two parallel instalations of Windows since I thought maybe it was something funky in the OS install. Do you have a Windows OS preference? I have thought about trying XP Pro or 2003 instead of 2000. Dan Link to comment Share on other sites More sharing options...
natew Posted March 1, 2006 Report Share Posted March 1, 2006 Hi Any of thos OSes should work. The customer I worked with before felt it was a hardware issue. Here is something to try if your disks support it- Disable the write cache on the hard drives on the RAID controller. It will slow things down but it will also make things more stable. Thanks Nate Link to comment Share on other sites More sharing options...
ComputerX Posted March 1, 2006 Author Report Share Posted March 1, 2006 I've only had two crashes since going to 7.5. But now I'm getting more 519 errors than before :-( Dan Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.