Announcement

Collapse
No announcement yet.

Disk too slow - a different question

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stereodesign
    replied
    AFA as a distributor saying it is fixed ... I never take anything a seller says as the truth until I actually see the proof.
    My tongue was firmly in my cheek when I wrote this, afterall this is the distributor who said no such fault existed, until I suggested they read this forum for evidence to the contrary.

    However, as GV acknowledge that the problem is real and, I would hope, keep distributors informed of developments I am confident that all will be well with v5.0, or at least v5.1......;-)

    Leave a comment:


  • Aristotelis
    replied
    could you try raid0 for testing
    Just for the record - I tried raid0 in the same system... same behaviour...

    Stormtest results
    Before "Disk too slow" message: Read:220MB/S, Write: 210MB/S
    After "Disk too slow" message: Read: 25MB/S, Write: 3MB/S

    In my case at list these results indicate that capturing with edius somehow decreases the speed of the disks

    Now I'm going back to v4.24 for more testing

    Leave a comment:


  • GrassValley_KH
    replied
    Pat has nailed it - we're most definitely aware of the issue that some people are experiencing.

    But no information as to a timeframe for fixing it has been announced in an official capacity - be it in 4.x or beyond. Given the difficulty in accurately reproducing the issue, the investigation has been long and frustrating for all involved.

    Leave a comment:


  • pjsssss
    replied
    For those of us that follow this forum closely, I don't think that there is any doubt that something was introduced from 4.5 on that randomly causes this error. Despite many attempts I don't think a single cause has ever been identified, which makes it very hard to fix. Usually it has nothing to do with the disk speed at all.

    As DD suggested, other SW will capture with no problems. This alone suggests that it is definetely an Edius problem. I do know that GV is aware of the problem and is working on it. I also would not suggest a reformat as a cure.

    AFA as a distributor saying it is fixed ... I never take anything a seller says as the truth until I actually see the proof.

    Leave a comment:


  • Aristotelis
    replied
    Originally posted by Stereodesign View Post
    All this is very interesting but, Ediusv4.23 no disk too slow error. Ever.
    Exact same hardware Edius v4.5 Disk too slow error. Its a bug in v4.5.
    IMO this forum has provided more than enough evidence to GV that it is a v4.5 bug. No doubt this has all been taken on board and it will have been fixed in v5.0
    I'm very close to agree with you Stereodesign...
    Can someone from GV make that official?
    Many users don't use the extra features available in version 4.5-4.61 so I believe that they wouldn't mind going back to version 4.24 for a while in order to solve that major problem...

    Leave a comment:


  • Stereodesign
    replied
    All this is very interesting but, Ediusv4.23 no disk too slow error. Ever.
    Exact same hardware Edius v4.5 Disk too slow error. Its a bug in v4.5.
    IMO this forum has provided more than enough evidence to GV that it is a v4.5 bug. No doubt this has all been taken on board and it will have been fixed in v5.0

    Leave a comment:


  • Aristotelis
    replied
    could you try raid0 for testing
    I will do that! however I don't like RAID0 - it is too risky...
    Same problem with RAID10 also (with 4 drives)

    are 3 drives enough for raid5 and video editing?
    180MBS Read, 140MBS Write is more that enough I think...

    also, I have not heard good things about onboard raid5 controllers
    I have being using the asus onboard controllers for the past two years without problems...

    Leave a comment:


  • antonsvideo
    replied
    are 3 drives enough for raid5 and video editing?

    also, I have not heard good things about onboard raid5 controllers

    could you try raid0 for testing

    Leave a comment:


  • Aristotelis
    replied
    Asus P5KR
    Intel 6850
    2GB Kingston DDR2 800
    ATI HD3870
    1 Seagate 160GB system drive
    3 Seagate 1TB RAID 5 array - using the onboard controller

    I have the above system next to me and I can reproduce that behaviour every time...

    Clean install of Windows/Edius
    Clean formated RAID 5 array - results from Stormtest: 180MB/S Read, 140MB/S Write
    1. Start capturing with Edius (Canopus HQ 1440x1080 50i) - After a few hours the disc too slow error appears
    2. Checking the RAID 5 array with stormtest: 4MB/S Read, 3MB/S Write
    3. I format the drive and check with stormtest again: 180MB/S Read, 140MB/S Write
    I have done the above steps 5-6 times, I even replaced all hdds... I have seen the same problem in different configurations as well...

    has anyone checked the read/write speed of the drive after the "disk too slow" error?

    Leave a comment:


  • DigitalDave
    replied
    Well given that capturing with other SW works on the same drives there is the first suggestion.

    I had this happen on a brand new system and always at the same point on a tape - having checked Fragmentation and run a speed check and then a search on the Forums, I swapped C Drive caddies and recaptured to the same Drive with E3.61 without a problem. Others use Scenalyzer or DVCapture.
    I dont think ANYONE who has experienced this message has traced it back to the hard drive/raid.
    My guess is, as with a Bug in the Capture module in 1.5 or 2 that dropped audio this is more to do with data corruption.

    DD

    Leave a comment:


  • Aristotelis
    replied
    DigitalDave that wasn't an advice at all!! I just described my findings and I really hope that someone will give me a better solution!!!

    Can you suggest something better than restarting the system because I have already tried that numerous times without results!!

    Leave a comment:


  • DigitalDave
    replied
    Originally posted by Aristotelis View Post
    I have seen the problem in many different configurations (RAID5 or 10 mostly). However I always use an HDD test utility (stormtest) to check if the disks are indeed slow.
    I found that if I check the disk before capturing the speed is ok. I check the disk again after the "disk too slow" error and I see that the speed has decreased dramatically... After that the only guaranteed solution to make the disk fast again is to format it…
    Somehow capturing with edius sometimes destroys something on the disks...
    That’s the only logical explanation I can give…
    This problem has nothing to do with disc speed.
    A dropout on a tape can cause it.
    Restarting the PC can "cure it".
    Those who have experienced this can capture the same footage to the same drives with other capture SW so to suggest reformatting the drive as a cure is ......?????

    Leave a comment:


  • Aristotelis
    replied
    I have seen the problem in many different configurations (RAID5 or 10 mostly). However I always use an HDD test utility (stormtest) to check if the disks are indeed slow.
    I found that if I check the disk before capturing the speed is ok. I check the disk again after the "disk too slow" error and I see that the speed has decreased dramatically... After that the only guaranteed solution to make the disk fast again is to format it…
    Somehow capturing with edius sometimes destroys something on the disks...
    That’s the only logical explanation I can give…
    Last edited by Aristotelis; 07-03-2008, 10:46 AM.

    Leave a comment:


  • Stereodesign
    replied
    Its a bug in Edius 4.5 onwards. Some people suffer it all the time, others not.
    It does not appear to be due to any particular type of hardware configuration either, I have two identical PC's, one suffers the other does not.

    The UK distributor assures me that the problem has been dealt with in v5.0

    Leave a comment:


  • antonsvideo
    replied
    Originally posted by DMS Video View Post
    Two of my editing pcs are Premiere 6.5 Canopus Storm systems. Both computers are the same. I use various types of removable drives that I swap from time to time. I recently had a problem with one of the drives. I was digitizing sd footage and it kept stopping indicating that the disk was too slow. I read the sticky. The first thing I tried was reformatting the drive (320gb). I then digitized a 172gb project without a problem. A day later I decided to begin digitizing another smaller project onto the same drive and I experienced nothing but problems. Disk too slow. So I decided to try a defrag. The defrag literally took 24 hours. Even though I reformatted the drive, for some reason, it REALLY needed a defrag. after waiting a full day I put the drive back into the computer and now it's worse than ever. I can't even digitize 30 seconds. Just as a test I took the drive out of that particular computer and put it into the other one (exact same specs) and there's no problem whatsoever. It's digitizing as I type. Any ideas as to why this may be happening only in one computer?

    I hope to have less problems when I switch to the new Edius laptop

    Thanks

    David
    DMS
    what drive? IDE? SATA? SAS? SCSI? external USB2 etc?

    Leave a comment:

Working...
X