Kraken Clone Part 2

Just a quick one. With the Kraken running a basic 3mm silica wick and a 1.8ohm coil at 7 watts, I was getting a foul almost fizzy flavour. A bit of research suggested that the washers on the centre pin were not stainless steel. On inspection of my device, the washers were becoming scorched and rusty. I've replaced the washers with stainless steel ones. I've also replaced all the screws with equivalent stainless hex bolts. In my humble opinion its easier to fasten the coil in place using a hex bolt and key. It also looks pretty cool...

Before:

After:

More soon, no doubt.

D

Kraken Clone Part 1

Well, I said I'd probably end up doing something on here that was connected to vaping and so here it is! Having given up cigs back in September, I been spending most of my time "smoking" on a selection of KangerTech EVODs and mini-protanks. However, I've recently been getting an itch for something with a bit more grunt. So, I bought a clone of the ViciousAnt "Kraken" genesis-style atomizer. This cost me about £9 from a friendly chinese vendor and is a real work of art. It looks, feels, and vapes, just wonderful. However, it is apparent from the forums on the vendors website that all is not well. Some of the clones have a short which renders the device inoperative and dangerous. So, I opened mine up. This next photo identifies a problem in the centre post - its just not drilled out very well! Happily, once apart like this, the problem "burr" can be filed away and, as an added precaution, the centre pin can be wrapped in heat shrink or electrical tape, just to be clear. The video below explains how to remove and replace the centre pin.

More soon, no doubt.

D

Windows 8 slow file copy....

Not really something I've made or fixed but, rather, a problem I've solved.

A few weeks ago one of the 1TB drives in my Raid1 (Mirror) array failed. But it was OK because the remaining 1TB drive in the array was still working and my data was safe. I should say here that the OS (Windows 8 x64) is installed on a separate drive which is not part of the array. Then, more recently, I auto upgraded Windows 8 to 8.1. The upgrade went smoothly but when I came to update my media libraries in the Music App, it was apparent something had gone very wrong. For whatever reason, the upgrade had wrecked the partition on the remaining 1TB drive and the files (of which there were many precious ones) were totally inaccessible. Having tried a few data recovery programs, the only one which seemed capable of recovering the files in the original directory structure and with their original names was GetData's Recover My Files.

So, with a copy duly purchased and a fresh 1TB drive to hand, I recovered all my files - about 900GB worth. At this point I decided to make a new array using brand new 2TB drives. This went without incident and I now have 1.8TB of usuable space. But the main problem was with transferring the files from the 1TB drive to the new Raid array. The transfer would start ok with the drives in the array writing at about 70MB/s but after about 10 seconds the transfer would slow to a crawl or completely stop, although the Task Manager also showed that disk activity remained at 100%. A few minutes would pass and the process would start again, and then stop, and so on. At a rough calculation, it was going to take about three weeks to transfer the data. So, I Googled for a solution. I tried many of the different things suggested (switching off Defender, disabling indexing, disabling thumbnails, and so on). About an hour ago I was ready to give up but thought I'd have one last go, starting from fresh. This meant deleting and then remaking the array. In Disk Management, I received the usual message about the new "drive" and the option to make it either MBR or GPT. This got me thinking. When I first started this exercise yesterday I checked the difference between MBR and GPT and since the total usable size of my array was less than 2TB, I'd selected MBR. This time I picked GPT and the problem with the slow/peculiar data transfer is no more.

Just thought I'd share that in case it helps anyone else.

More soon, no doubt....

D

First post....

... just to help me whilst I'm sorting the layout of this blog.

 More soon, no doubt...

 D