From: jdbeard@patriot.net   
      
   On 11/16/2012 06:51 PM, TJ wrote:   
   > On 11/15/2012 07:22 PM, Adam wrote:   
   >> TJ wrote:   
   >>> Shoulda learned how to run it from the command line instead of   
   >>> doing it   
   >>> through MCC. Probably would have had some feedback that way.   
   >>   
   >> I'd say cancel MCC and start again with 'mke2fs' for each   
   >> partition from   
   >> the command line.  My usual is "mke2fs -ccjv -t ext4 /dev/sd??"   
   >> but read   
   >> the man page first.  You may want to use -m as mentioned in   
   >> this thread.   
   >>   Note -c is used twice for a read/write test.  With -v, it   
   >> will keep   
   >> you informed of its progress.  Over 30 hours sounds quite   
   >> within reason   
   >> for a ~1 TB partition.   
   >>   
   >> Adam   
   >   
   > Hmmmm. Trying the r/w test, just to see what's what. 39 minutes   
   > in, it says it's 0.25% done. At that rate, it'll be finished in   
   > something like 11 days.   
   >   
   > Sorry, Adam. I'm not willing to wait that long.   
      
   I looked around on the Western Digital site.  If you really want   
   to do a thorough check of the hard drive, you need to download   
   WDC's *.iso for DataLifeGuard or some such, boot that, and use   
   that to play with the drive.   
      
   As mentioned for the WDC disks I use, it appears all the WDC hard   
   drives are providing their own remapping and other maintenance   
   via a computer-aided controller on the drive itself.  Running the   
   Linux/UNIX badblock routine is pointless.   
      
   Cheers!   
      
   jim b.   
      
   --   
   UNIX is not user unfriendly; it merely   
         expects users to be computer-friendly.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)