Tag Archive for synology

Top 10 Tekhead Posts of 2016

I’m pleased to say that I upped my game somewhat over the past year, managing to churn out 62 posts in 2016, more than double the 28 posts I produced in 2015!

There were a few other interesting trends over the previous year. The balance between VMware and other subjects has definitely shifted for me, where for example, I wrote well over a dozen posts on AWS.

I guess this is probably representative of both my recent role change, as well as the shift in my customers from being 90%+ VMware houses, to a broad mix of different cloud platforms, both public (AWS / Azure) and private (VMware / OpenStack).

This trend is only going to accelerate in the future, and I suggest Scott Lowe’s Full Stack Journey podcast would be well worth your time subscribing to for great information on how to avoid being left behind as our industry morphs over the coming years!

thecloud

It’s worth noting that this trend is also mirrored in the top 5 articles alone, which include popular newer technologies such as Docker and AWS. That said, it’s great to see the Intel NUC Nanolab series is still as popular as ever, and people are obviously still keeping their vSphere skills and certs up to date, based on the VCP delta study guide popularity.

You may also have noticed that I have been a little quieter of late. The main reasons for this have been down to starting my new role earlier this year, studying for exams, plus a number of other projects I’ve been involved in (such as the Open TechCast podcast). Hopefully I can find a little more balance between them all in 2017, though I already have a couple of podcasts, a VMUG presentation, and a possible exam lined up for January so I’m not really helping myself on that front!

Tekhead Post Stats 2016

So, enough jibber jabbing! Here follows the top 10 most popular posts of the past 12 months.

Tekhead Top 10 Posts of 2016
  1. My Synology DSM Blue LED issue was actually just a failed drive!
  2. Installing Docker on Ubuntu Quick Fix
  3. NanoLab – Running VMware vSphere on Intel NUC – Part 1
  4. Fix for VMware Remote Console unrecoverable error: (vmrc)
  5. AWS Certified Solutions Architect Associate Exam Study Guide & Resources
  6. VCP6-DCV Delta Exam (2V0-621D) Study Guide and Exam Experience
  7. NetApp – Is this the dawn of a new day?
  8. NanoLab – Part 10 – Your NUCs are nice and cool, but what about your stick?
  9. Index of Tekhead.it Blog Posts on Amazon AWS
  10. Quick Fix for “The task was canceled by a user” when deploying OVA in vCenter 6

Something Mike Preston and I discussed on our recent Open TechCast podcast episode, was how it can be a little frustrating as a blogger that often an opinion piece which took ages to write and edit will get a small number of views, whilst a quick tip which took a couple of minutes to jot down, might get thousands or even tens of thousands over time!

Gladly, my top 10 this year includes both types, so my time wasnt completely wasted! 🙂

Anyway thats enough from me for now; all the best for 2017 folks!

Top 5 Posts of 2015 on Tekhead.org

This is just a very quick note to say thank you, everyone, for your awesome support and continued readership over the past year! Without that I don’t know that I would put in the effort!

I very much hope that the content produced continues to be of some use in the coming year…

Moving swiftly on to the Top 5 most popular posts of 2015; they were as follows:

  1. My Synology DSM Blue LED issue was actually just a failed drive!
  2. NanoLab – Running VMware vSphere on Intel NUC – Part 1
  3. Installing Docker on Ubuntu Quick Fix
  4. Docker Part 1 – Introduction and HOWTO Install Docker on Ubuntu 14.04 LTS
  5. NanoLab – Running VMware vSphere on Intel NUC – Part 2

I can’t say I’m surprised with the Synology post popularity, as there are far more Synology users out there than virtualisation and storage admins I should think… not 100% my usual reader demographic. 😉

The Nanolab series continues in popularity, which warms my cockles! They make for an awesome homelab, and I have a handful of posts almost ready to go for 2016 to continue this series.

Finally, and most interestingly considering current industry trends, the Docker HOWTO series has definitely proven very popular, even though so far I have stuck to the absolute basics! I will definitely endeavour to expand on this series throughout this year.

So that’s it for now, just a quick one. I hope you all had an awesome New Year (I spent mine this year watching Star Wars: The Force Awakens woohoo!) and wish you all the best for the exciting things to come in 2016!

Cannot See Any iSCSI Devices on Synology from a vSphere Host

Just a quick fix I discovered this weekend. It’s probably quite specific but hopefully if you come across this in future it will save you some time.

I had just finished rebuilding the second node in my lab from 5.1 with a fresh install. I added the software iSCSI initiator and connected it to my iSCSI target (Synology DS412+) using Dynamic Discovery. I then rescanned for a list of devices, and although I was picking up the IQN for the iSCSI server, I couldn’t see any devices!

I tried lots of things including removing and re-adding the initiator, messing with iSCSI bindings, but nothing! Very frustrating.

After a bit of googlage, I came across this KB article from VMware:

Cannot see some or all storage devices in VMware vCenter Server or VirtualCenter (1016222)

Although this was specific to VI3/vSphere 4, it did trigger a thought! Just before I built the new node, I rejigged all of my storage LUNs, deleting 3 old ones in the process (which just so happened to be the first 3 LUNs on my NAS). What I believe this caused is that the LUNs were viewed by node 1 as different LUN IDs on node 2, so they refused to show up!

So now, the fix. Incredibly simple as it turns out:

  1. Created three new temp 10GB LUNs on my old NAS which would then assume LUN IDs 1/2/3 as they originally had (before I deleted them).
  2. Rescan the new node of the cluster for storage
  3. Confirmed all of the LUNs are now visible
  4. Deleted the three temp LUNs from the Synology (I don’t plan to add any more nodes for now so I have no need of these temp LUNs, but as they’re thin provisioned anyway it actually wouldn’t hurt to leave them there).
  5. Rescan the ESXi host again to ensure it can still see the LUNs.
  6. Job done!

Synology iSCSI Devices

Not much to it, but worth a quick post I thought as this simple issue wasted a chunk of my time!

My Synology DSM Blue LED issue was actually just a failed drive!

This weekend I spent several hours trying to resolve an issue with my Synology DS413j which I use for backing up my other two Synology hosts (DS412+).

I was experiencing many of the symptoms in the following post, yet I was convinced I could not have been hacked, as this server is not available to the internet! Not only that but I recently updated DSM (2-3 weeks ago) so wondered if this could be the cause?…

http://forum.synology.com/enu/viewtopic.php?f=108&t=82141

After following the full 11 step fix (minus the migratable step as it wouldn’t work), I still had a box which was unresponsive. My symptoms were:

  • Power LED light blinks blue
  • I could not log into the DSM console
  • DSM login simply says “Processing, please wait” forever or eventually times out
  • I was able to ping DSM
  • I could not reset DSM using the reset button on the back of the device
  • Booting of the device took a very long time (up to 20 mins) and Synology Assistant shows “Starting Services…” for a very long time
  • Even after following rebuild steps I could not get the Synology Assistant to show “Migratable”
  • Once booted I could see the SMB shares and access them intermittently

After much head scratching I decided to take each of the drives in turn and test them on my Windows desktop. I have 4 drives in the host, 2x Seagate and 2x WD Red. If any of them were going to fail I believed the Seagate would be at fault, so I tested those first. I plugged in disk number one, ran some tests, all ok. I then plugged in disk number two, and discovered that windows would not even mount the drive. Not only that but it was actually causing device manager to hang.

Faulty drive identified, I powered on the Synology with the remaining 3 drives only. Much to my relief, the system booted within a minute and started to beep, warning me I was missing a drive. DSM is now responding just fine.

I have now ordered a new WD Red drive to replace the failed Seagate (which was out of its very short warranty of course!).

Moral of the story: If your box looks like it may have been hit by SynoLocker but it was never on the internet, try testing all the drives in turn. You may just save yourself a few hours / days of pain!

One other wee tip is to also enable SSH access. I’m not sure if I could have logged in via SSH in the hung state, but it may have given me another troubleshooting avenue.

%d bloggers like this: