cinner Posted April 19, 2008 Posted April 19, 2008 With regards to my newest piece of equipment... http://www.newegg.com/Product/Product.aspx...N82E16822136149 The drive is much, much quieter than my last mass storage drive. But this is simply unacceptable: [imgburn log excerpt] W 14:01:54 Waiting for buffers to recover... W 14:01:55 Waiting for hard disk activity to reach threshold level... I 14:01:56 Writing Image... W 14:02:04 Waiting for buffers to recover... W 14:02:28 Waiting for hard disk activity to reach threshold level... I 14:02:30 Writing Image... W 14:02:51 Waiting for buffers to recover... W 14:03:01 Waiting for hard disk activity to reach threshold level... I 14:03:03 Writing Image... W 14:03:11 Waiting for buffers to recover... W 14:03:34 Waiting for hard disk activity to reach threshold level... I 14:03:37 Writing Image... W 14:03:44 Waiting for buffers to recover... W 14:03:47 Waiting for hard disk activity to reach threshold level... I 14:03:49 Writing Image... W 14:04:04 Waiting for buffers to recover... W 14:04:12 Waiting for hard disk activity to reach threshold level... I 14:04:13 Writing Image... W 14:06:14 Waiting for buffers to recover... W 14:06:17 Waiting for hard disk activity to reach threshold level... I 14:06:18 Writing Image... W 14:07:06 Waiting for buffers to recover... W 14:07:44 Waiting for hard disk activity to reach threshold level... I 14:07:46 Writing Image... [there is a lot more but everyone gets the picture by now] No multitasking. Only an attempted 8x burn that averaged 3.4x. Epic fail? Many reviews of this drive warned that the drive was slower. I wanted a quieter drive, and I got what I wanted, but I could not have foreseen speed being this much of a factor. Looks like I was wrong. Does anyone else here use a GP drive? Should it really be this slow? And if so, how could anyone at Western Digital possibly believe that crippled, lame technology is a good idea under any circumstance?
volvofl10 Posted April 19, 2008 Posted April 19, 2008 hows the drive connected ? and post the full log from before the excert you posted
LIGHTNING UK! Posted April 19, 2008 Posted April 19, 2008 Do some benchmarks using 'HD Tune' or something.
dontasciime Posted April 19, 2008 Posted April 19, 2008 get a tool from western digital and knock drive in sata 2 300 if your board supports it and knock drive in sata 1 150 if you board does not handle sata 2 or NCQ if that drive has that feature. See if you can also set the drive to not spin down to 5400 rpm as well and look at features that make it green and see if you can disable them. check which sata port you are using on the board you have, if on a raid sata port change to another, change sata cable as last resort and update drivers if third party like jmicron consider letting windows use standard ms drivers especially if your board has nforce chipset. Also set bios to IDE mode for sata and not AHCI It might even have a tiny jumper to set sata mode on hard drive itself
cinner Posted April 20, 2008 Author Posted April 20, 2008 Thanks for the responses. And sorry about not posting full log, I did not keep it. I just finished another burn. Here is the full log. W 21:09:29 Waiting for hard disk activity to reach threshold level... I 21:09:31 Writing Image... W 21:09:52 Waiting for buffers to recover... W 21:09:57 Waiting for hard disk activity to reach threshold level... I 21:10:00 Writing Image... W 21:10:42 Waiting for buffers to recover... W 21:10:45 Waiting for hard disk activity to reach threshold level... I 21:10:47 Writing Image... W 21:11:01 Waiting for buffers to recover... W 21:11:02 Waiting for hard disk activity to reach threshold level... I 21:11:03 Writing Image... W 21:11:29 Waiting for buffers to recover... W 21:11:30 Waiting for hard disk activity to reach threshold level... I 21:11:32 Writing Image... W 21:12:17 Waiting for buffers to recover... W 21:12:50 Waiting for hard disk activity to reach threshold level... I 21:12:52 Writing Image... W 21:13:02 Waiting for buffers to recover... W 21:13:53 Waiting for hard disk activity to reach threshold level... I 21:13:54 Writing Image... W 21:14:25 Waiting for buffers to recover... W 21:14:59 Waiting for hard disk activity to reach threshold level... I 21:15:00 Writing Image... W 21:15:07 Waiting for buffers to recover... W 21:15:33 Waiting for hard disk activity to reach threshold level... I 21:15:34 Writing Image... W 21:15:39 Waiting for buffers to recover... W 21:15:50 Waiting for hard disk activity to reach threshold level... I 21:15:51 Writing Image... W 21:16:09 Waiting for buffers to recover... W 21:16:10 Waiting for hard disk activity to reach threshold level... I 21:16:11 Writing Image... W 21:17:46 Waiting for buffers to recover... W 21:18:20 Waiting for hard disk activity to reach threshold level... I 21:18:22 Writing Image... W 21:18:30 Waiting for buffers to recover... W 21:18:34 Waiting for hard disk activity to reach threshold level... I 21:18:36 Writing Image... W 21:19:08 Waiting for buffers to recover... W 21:19:23 Waiting for hard disk activity to reach threshold level... I 21:19:24 Writing Image... W 21:19:43 Waiting for buffers to recover... W 21:19:46 Waiting for hard disk activity to reach threshold level... I 21:19:49 Writing Image... I 21:20:16 Synchronising Cache... I 21:20:17 Closing Track... I 21:20:28 Finalising Disc... I 21:21:04 Image MD5: 246cd80b722bc67018bdb26c6634189e I 21:21:07 Operation Successfully Completed! - Duration: 00:14:13 I 21:21:07 Average Write Rate: 5,624 KB/s (4.1x) - Maximum Write Rate: 11,172 KB/s (8.1x)I 21:21:07 Cycling Tray before Verify... W 21:21:20 Waiting for device to become ready... I 21:21:26 Device Ready! I 21:21:27 Operation Started! I 21:21:27 Source Device: [0:1:0] PHILIPS DVD+-RW DVD8631 GD30 (E:) (ATA) I 21:21:27 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: YUDEN000-T02-00) I 21:21:27 Image File: -==/\/[bUILD IMAGE]\/\==- I 21:21:27 Image File Sectors: 2,210,320 (MODE1/2048) I 21:21:27 Image File Size: 4,526,735,360 bytes I 21:21:27 Image File Volume Identifier: hello_world I 21:21:27 Image File Application Identifier: IMGBURN I 21:21:27 Image File Implementation Identifier: ImgBurn I 21:21:27 Image File File System(s): ISO9660, UDF (1.02) I 21:21:27 Verifying Sectors... I 21:36:33 Device MD5: 246cd80b722bc67018bdb26c6634189e I 21:36:33 Image MD5: 246cd80b722bc67018bdb26c6634189e I 21:36:33 Operation Successfully Completed! - Duration: 00:15:06 I 21:36:33 Average Verify Rate: 4,884 KB/s (3.5x) - Maximum Verify Rate: 15,067 KB/s (10.9x) And also ImgBurn gave me the following error once, during writing: Cannot read from file:M:\helloworld.wav reason: data error (cyclic redundancy check). Hit retry once and it was all good. I've never had a burn fail me. I can still access M:\helloworld.wav, and M:\helloworld.sfv checksum is ok (even though it takes about 25 seconds to complete). HD Tune, I had not thought of that... Any more info that might help, I will post. I got this drive brand new just over a month ago. Using sata2, and cable is good because I reused the one that was connected to my old hard drive.
LIGHTNING UK! Posted April 20, 2008 Posted April 20, 2008 CRC errors and failing SMART... I'd deffo run the full set of WD tests on it and see if it passes. If it doesn't, just RMA it.
dontasciime Posted April 21, 2008 Posted April 21, 2008 and cable is good because I reused the one that was connected to my old hard drive. does not mean it still works, I re used a one from a sata dvd rom and it was broken. Change it as the last thing to try, you are probally correct in thinking there is nothing wrong with it but it has to be changed to rule it out.
cinner Posted April 21, 2008 Author Posted April 21, 2008 ^^ thanks Lightning UK, WD's diagnostic software found bad sectors on this drive. I am definitely going to try and get RMA (after I write zeros to it a few times). I rarely purchase hard drives, and this is the first time I've had one go bad. Thanks for helping me catch this so early. ^good point, I will use a new cable when I get a replacement for this drive.
fk0 Posted May 8, 2008 Posted May 8, 2008 I have troubles with the same disk, i had problems of underruns with the previous disk that was an Seagate st3500320as but i never found what the problem was, so i moved it to another machine and installed a WD5000AACS green power; it's faster in terms of sequential read but is't a little slower on seek, now the problem seem to be worse. In fact when i write a dvd at 4x 6x or 8x 10x the ram buffer empty in a few second and only the device buffer work. however if i don't access the disk with other programs i don't have any underrun. Now came the strange thing, i tried to read from a dvd full to a iso and i got 0.6X of speed read, the buffer it's always empty and the disk it's so slow to access in any way like if 100 programs are using it. So after the various routein test on the disk that show it's working well i tried a commandline iso extractor that reach approx 14X at the final part of the dvd (and the disk is still working well). Duplicate a file on the same partition usually give 15 to 25mb/s , out on another disk 40, toher programs doesn't seem to have disk speed troubles , only imgburn.
dontasciime Posted May 11, 2008 Posted May 11, 2008 Dunno what your exactly saying but I would be testing that drive for errors with the WD Lifeguard (diagnostic tool from their site) and return it if any are found. ImgBurn is not responsible for the slowness of your drive.
LIGHTNING UK! Posted May 11, 2008 Posted May 11, 2008 I'm sure that once it's kicked into gear properly it'll write at full speed from ImgBurn too. ImgBurn is only using standard Windows API calls. Sometimes they just need a bit of a hard kick and random accessing can help achieve that! (I have a couple myself)
cinner Posted May 18, 2008 Author Posted May 18, 2008 I wanted to update my status here and say that after a quick and flawless rma from Western Digital, my burns and everything else have been working very well. If this drive is any slower than other SATA drives I've used, I haven't noticed. And right now HD Tune is telling me the green power is 5 degrees cooler than my OS drive. Time to get to work on this new stack of TYG02.
Recommended Posts