For all those paranoid about high LCC counts, like myself, here is the solution that worked for me:

 

1. Downloaded FDOEMCD.builder.zip from http://www.fdos.org/bootdisks/.

2. Added wdidle3.exe to CDROOT folder. ( http://www.synology.com/support/faq_ima ... didle3.zip )

3. Executed MAKEISO.BAT to create new FDOEM.ISO CD image file.

4. Burned FDOEM.ISO to CD and viola - it will boot to DOS and allows wdidle3 to run.

5. Disabled wdidle3 timer on all discs (I'm actually using WD20EADS)

 

courtesy of http://forum.synology.com/enu/viewtopic.php?f=124&t=20907

 

Followed the steps, executed \D to disable intelipower logic, which did not disable it but set to 62

minutes instead. Well, works for me nevertheless.

 

As of this morning my parity drive of 12 days of in service had:

274 hours and the LCC of 4418, which comes down to 16 per hour.

Don't know what's causing that, as the other WD greens and the previous

parity WD green all have counts of 20-34. Perhaps some new firmware, or

the fact that I installed unmenu a couple of weeks ago...

 

Anyway, after firmware changes, it's been about 10 hour since then, the count

went up by exactly 1, to 4419. Seems to be working. Paranoia can go to sleep now.

 

It's good to know there's a solution for your issue, even if we don't know why there was an issue. It's odd as others, myself included, with EADS didn't have the issue.

More info here.

 

http://forum.synology.com/enu/viewtopic.php?f=124&t=20907

 

I had to get the wdidle3.exe program from another link.

 

FWIW, There is also a way to boot a floppy disk right from syslinux when you use memdisk.

The procedure is a little more involved, Yet it's a possibility.

FWIW, There is also a way to boot a floppy disk right from syslinux when you use memdisk.

The procedure is a little more involved, Yet it's a possibility.

Yes, you don't really need to burn any CDs.  I've used memdisk to boot all kinds of .iso distros right from the same syslinux.cfg of unRAID.

This precious little tool (memdisk) is in fact part of the syslinux package.  Just put it on your flash key and you're good to go.

Then add something like this in your syslinux.cfg

label DOS
  kernel memdisk
  append iso initrd=FDOEM.ISO

Hmm, I did not know about the append iso syntax. Thanks.

 

This makes it usable for bootable diagnostic cdrom images from hard drive vendors.

 

FWIW, There is also a way to boot a floppy disk right from syslinux when you use memdisk.

The procedure is a little more involved, Yet it's a possibility.

Yes, you don't really need to burn any CDs.  I've used memdisk to boot all kinds of .iso distros right from the same syslinux.cfg of unRAID.

This precious little tool (memdisk) is in fact part of the syslinux package.  Just put it on your flash key and you're good to go.

Then add something like this in your syslinux.cfg

label DOS
  kernel memdisk
  append iso initrd=FDOEM.ISO

 

Awesome. I cannot say how much i will use this. How did i not know this could be done. nice one

Awesome indeed!  Took me a long time to discover that...

I was sure there HAD to be something that can do that! 

 

Here's an excerpt of the syslinux.cfg on my unRAID server:

label Parted Magic (Live CD)
  kernel memdisk
  append iso initrd=pmagic-4.9.iso

label Hard Disk Sentinel for DOS
  kernel memdisk
  append iso initrd=hdsdos.iso

label cpuidtest
  kernel cpuidtest.c32

label dmitest
  kernel dmitest.c32

label Memtest86+
  kernel memtest

 

Speaking of which, Parted Magic 4.10 is out now. 

 

http://partedmagic.com/

 

Thanks for noticing!

 

I hate to be a thread necromancer, but is the wdidle procedure safe to do on an active unRaid array?

I tried following this.  I was able to get this part going.  However once I selected the fdoem option I was given a choice between booting from the cd or using the harddisk.  If i selected the cd option, I was at the c:/ prompt.  However when I would type wdidle3.exe /d the unraid machine would just reboot.  If I selected the harddisk option, it would freeze.  What am I doing wrong?

I tried following this.  I was able to get this part going.  However once I selected the fdoem option I was given a choice between booting from the cd or using the harddisk.  If i selected the cd option, I was at the c:/ prompt.  However when I would type wdidle3.exe /d the unraid machine would just reboot.  If I selected the harddisk option, it would freeze.  What am I doing wrong?

 

Anyone???