Slow SSD Boot with long OtherKernelInitDuration delay

**cluberti** · 25 Oct 2011

Agreed - let us know what you find when you're able to swap out hardware.

Raillex · 25 Oct 2011

Looks like others have experienced long boot delays when pairing SSD boot drives with WD storage drives. Anyone else using a WD Black as a storage drive?

http://forums.whirlpool.net.au/forum....cfm?t=1671373

essenbe · 25 Oct 2011

Yes, I have a 1TB FAEX WD Black, a 500GB Seagate, 1TB Samsung and a 1.5TB Samsung. I have very quick boot times. No problem for me.

Raillex · 26 Oct 2011

I pulled a working WD 500GB SATA storage drive from my other system, swapped it for the 2TB drive, and started it up. Unfortunately, I can't even get to the bios screen. Never had that happen before.

Now what.

Edit: ... and it works just fine back in my old rig. Why would my Z68 bios refuse to post? I even tried plugging it into the Marvel controller. One beep, and black screen.

BTW, the new rig posted just fine with the WD 2TB reinstalled.

gregrocker · 26 Oct 2011

Sometimes code on the HD will make it appear not to POST, although it may be reading enough code to stop it from recognizing HD.

I just troubleshot one of these on an eMachine which had beein reimaged and wouldn't POST, quickly determining it is the HD by unplugging it.

In that case the solution was to move the HD to another machine to clean boot code with Diskpart: Clean and Clean All with Diskpart Command

Raillex · 26 Oct 2011

gregrocker said:

Sometimes code on the HD will make it appear not to POST, although it may be reading enough code to stop it from recognizing HD.

You're right! I forgot I had cut and pasted the contents of an ancient laptop's C: drive onto a storage drive years ago, and that folder ultimately found its way to the WD 500GB drive. Perhaps the new rig's UEFI bios picked this up where the standard bios on my old Windows 7 machine could not.

Raillex · 26 Oct 2011

gregrocker said:

In that case the solution was to move the HD to another machine to clean boot code with Diskpart: Clean and Clean All with Diskpart Command

I use Acronis to back up my boot drive, and the backups are on the WD 500GB drive. Will I screw up the backups by running this?

**cluberti** · 26 Oct 2011

If you clean a partition, you effectively remove the data on it, yes - you can usually recover the data with recovery programs, but it's best to back up a drive/partition before you "clean" it.

Raillex · 26 Oct 2011

Now this is more like it.

I located a relatively empty SATA storage drive (a 74GB Raptor) from my old machine, ran the clean command on it, removed the uninitialized drive from the machine, and then connected it to the same SATA 6 port the 2TB WD drive was connected to. Booted up, and jetted right into Windows. Partitioned the Raptor in Windows, rebooted, and no delay whatsover rebooting. Checked event viewer, and it timed the boot at 18 seconds.

I think I'm going to copy the contents of the 2TB WD onto my old machine, run a clean command under diskpart on it, and repartition.

Raillex · 26 Oct 2011

gregrocker said:

Sometimes code on the HD will make it appear not to POST, although it may be reading enough code to stop it from recognizing HD.

I just troubleshot one of these on an eMachine which had beein reimaged and wouldn't POST, quickly determining it is the HD by unplugging it.

In that case the solution was to move the HD to another machine to clean boot code with Diskpart: Clean and Clean All with Diskpart Command

And this was the solution. You're a champ, Greg!

Boot time with the WD storage drive connected is now only 17.65 seconds. All I had to do was copy my files to another PC, run diskpart with the clean command on the offending WD, reboot with the uninitialized WD still in the 6GB/s port, format the WD through Windows disk manager, and copy the drive's contents back onto it.

You've all been extremely helpful, and I really, really appreciate it.