Alexander John

Thoughts, notes & the occasional opinion.

Author: Alexander John (Page 3 of 6)

I am an IT Professional and Web Developer living and working in the United Kingdom. I describe myself as an IT generalist as I have worked in a wide variety of IT and web fields and technologies. Whilst I am Microsoft Certified Professional (MCP), I utilise a wide variety of technologies including Linux and Android in day-to-day work.

I am a founder and director of a SME orientated Web service company Calzada Media Limited where my daily workload varies from web development through to IT infrastructure management.

Configuring RAID1 on LG N2A2 NAS

21 September 2011 / / 17 Comments

I recently purchased an LG N2A2 2 Bay NAS to use as my primary disk to disk backup solution. As per LG’s recommendation – a big shiny sticker on the box – I upgraded the firmware to the latest version before using the NAS in anger. This new firmware (6674) has a far improved interface and capabilities than than provided with the firmware shipped with the NAS. The downside is that all of the online help documentation is in Korean.

As my knowledge of Korean is non-existent, working out how to configure the NAS’ disks to RAID1 required more than a little help from Google Translator. Detailed below is how I configured RAID1. As usual, this information is provided “AS IS” and you use it at entirely your own risk.

Caution: ensure you backup all data on the NAS prior to performing this task. This process will irretrievably wipe all existing data you may have stored on the NAS.

1. Log into the web management interface of the NAS using the admin username and password (by default this is ‘admin’ and ‘admin’).

2. On the homepage of the web interface, click on the Volume option. If it is not present, go to the Configuration section via the links on the left of the page to find it.

3. If your NAS volumes have never been altered from their as shipped state, the volumes list should contain two separate volume (see screenshot 1).

NAS RAID Screenshot 1

Screenshot 1

To configure RAID1, both of these volumes must be deleted. Click on the Delete button next to each volume to do this. You will be prompted to confirm the deletion (see screenshot 2). Enter the admin password and click on *OK* to confirm the volume deletion. Once deleted, a confirmation message will appear (see screenshot 3).

Screenshot 2

Screenshot 2


Screenshot 3

Screenshot 3

4. Once both volumes have been deleted, the volumes list just show the two unused disks (see screenshot 4). To start creating the RAID1 volume, click on the Create New Volume button.

Screenshot 4

Screenshot 4

5. The next dialog will list the available unused disks. Click/select both Disk 1 and Disk 2. By default, the option RAID1: data protection/duplication structure should automatically be selected under 2. Select a volume formation type, if not, select it (see screenshot 5).

Screenshot 5

Screenshot 5

6. The create new volume dialog is actually larger than its’ containing window. To proceed, scroll down using the scroll bar on the right and click on the Create Volume button to start the RAID1 creation process (see screenshot 6).

Screenshot 6

Screenshot 6

7. The creation process will now begin. A small dialog will appear showing the progess of the volume creation (see screenshot 7). Once completed, this dialog will update to display an OK button. Click on this button to continue.

Screenshot 7

Screenshot 7

8. You will not be returned to the volume listings which will show a single volume comprising of two disks in RAID1 formation (see screenshot 8).

NAS Screenshot 8

Screenshot 8

Important: The volume is not yet ready for use.

Please note the status message of Volume is being created. (Creating Raid) 0% in screenshot 8. The new volume is still being configured for RAID. Only start writing data once this status value changes to normal (see screenshot 9). This process may take several hours, and the status message does not dynamically update. You will need to close the Volume window and then re-open it to get an up-to-date status message.

NAS RAID Screenshot 9

Screenshot 9

 

Getting HDMI sound working on an ASUS ATI/AMD 4350

5 August 2011 / / 0 Comments

When I built my HTPC earlier this year, I replaced the elderly graphics card within the old chassis I was using with an ASUS 4350. I don’t pretend to be anywhere near an expert on graphics cards, but the limited research I did led me to believe that this card would be ideal. Relatively cheap, passively cooled and delivered full HD via HDMI.

What I did not know then, but what I discovered following installation, is that this card does not output sound via HDMI without some driver jiggery-pokery. You would see a message similar to this one in the Sound properties dialog within Windows.

In short, neither the supplier driver nor the updated Catalyst drivers from AMD/ATI include the relevant Realtek audio driver. The solution is relatively simple: you download and install the latest HDMI audio driver from Realtek.

This is what I did earlier this year and my HTPC worked without a hitch until I mistakenly updated the AMD/ATI Catalyst drivers through Microsoft Update which promptly broke it. Needless to say, I hadn’t written down how to get this working so I had to find out all over again from scratch.

Disclaimer: It is not generally recommended to download and install drivers directly from OEMs. Your first port of call should be the company that manufacturered the product you are using (in this case ASUS). If you follow these steps, you are doing so entirely at your own risk.

  1. (Optional) Head over to AMD and grab the latest Catalyst drivers for the card (http://support.amd.com/us/psearch/Pages/psearch.aspx?type=2.4.1&product=2.4.1.3.38&contentType=GPU+Download+Detail)
  2. Go to Realtek’ High Definition downloads site (http://www.realtek.com.tw/downloads/downloadsCheck.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false).
  3. Check/tick the option Iaccept to the above and then click on the Next button.
  4. Scroll down the list ofWindows drivers until you find the entry ATI HDMI Audio Device (it will be in red text). Click on one of the three download links to the right to download the driver.
    • There are a couple of possible gotchas when downloading
      1. Last time I tried, none of the US download locations worked. The links just redirected back to step 2 above
      2. The downloads are FTP transactions that can take upto several minutes to stat. So don’t worry if nothing happens immediately.
  5. Once downloaded, install the driver. You should be prompted to restart your computer once completed, if not, do so anyway.
  6. Upon restart, sound may still appear to be disabled. The trick here is to pull out the HDMI connection and then replace it. Once this is done, the HDMI sound connection should be detected and work.

 

The moral of this particular story: Sometimes, it is necessary to document things you do with your home systems.

 

Resetting Webmin password for Ubuntu

27 July 2011 / / 0 Comments

The inevitable happened: I forgot the password for Webmin on one of my Ubuntu servers. In my defence, it is a server that I principally manage via SSH. Being Ubuntu, the necessary files are not in the same place as Webmin documentation. However, a quick Google search found a blog post with the solution. For my own records, I am duplicating below:

  1. Open a shell or SSH session on the target server
  2. Enter the command
    • /usr/share/webmin/changepass.pl /etc/webmin username password
    • Where username = webmin username. For me this was root
    • And password = new password.
  3. Login to Webmin to test

Thanks to and original information from http://ranawd.wordpress.com/2010/06/14/reset-webmin-password-for-ubuntu/

Given the number of password I seemingly have to remember, I think it is time that I employed some for of Password Safe.

«
»

Reset Webmin Password for ubuntu

June 14, 2010 by S.M. Saidur Rahman

13 Votes

I found this problem at the first time when webmin installed. Also this happens to everyone at one time or another. You go on vacation and when you come back, you forget all of the passwords on your computer.

I failed logging in several times and then Webmin blocked my IP. Getting localhost blocked isn’t a good thing to see. So I searched the Internet for a way to reset the password and I found this procedure:

1. Login to your computer as root. Type on browser address bar https://localhost:10000/
2. If you are running a Debian distribution (ubuntu), enter the following command:
/usr/share/webmin/changepass.pl /etc/webmin username password
3. Login to Webmin with your reset password.
4. eNjoY!

Remotely managing disks on Windows 2008/Hyper-V Server R2

8 July 2010 / / 0 Comments

As I’m mooting some hardware upgrades to my bash’n’crash Hyper-V server, I wanted to check out a few things with regards to it’s performance and general health. I duly fired up Server Manager, but was thwarted when I tried to use Disk Management and got the message of RPC Server is unavailable. I checked the Firewall, and the requisite rules (see below) were enabled. I recycled the Virtual Disk Service and still had no luck.

After hunting around a while I found a Technet Forum post that covered this. You have to enable the necessary inbound rules both on the server being managed and the managing computer. Once I had done this, and restarted Server Manager, I could access Disk Management.

For reference, the two rules that need to be enabled are:

Remote Volume Management – Virtual Disk Service (RPC)

Remote Volume Management – Virtual Disk Service Loader (RPC)

As per the Technet post, I found that you don’t need the Remote Volume Management (RPC-EPMAP) rule enabled. Needless to say, I only enabled both rules for the Domain firewall profile.

Automatically Loading PSHyperV Library

6 July 2010 / / 0 Comments

Late last year I wrote about getting the Powershell Management Library for Hyper-V (PSHyper-V) up and running on my Hyper-V installation. Although a newer version of the library was released in January, I simply hadn’t gotten around to updating my server. If I’m honest, beyond the occasional restart following an update (or powercuts – thanks for nothing EDF Energy) all of the Hyper-V servers under my care tend to sit the corner and are generally forgotten about. Far more attention is paid to the Virtual Machines than the actual host upon which they rely.

One change between the versions of PSHyperV has been the change from a standard script to a powershell module. As I prefer for the library to be automatically loaded, this required a change to the user’s powershell profile. The slight fly in the ointment is that I had forgotten how to do this, so here is a quick reprise for my own memory.

1. Open Powershell. If you are within a command prompt, type cmd /c start powershell to open a new powershell window.

2. In Powershell, type $profile. This will get you the full path to where your profile is stored. Your profile is a powershell script that executes whenever a Powershell prompt is opened. The profile will look something liek this:

C:\Users\<your username>\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

3. Your profile file may or may not exist. If you have not already used it elsewhere, the chances are that it doesn’t. To create a new profile file, enter new-item $profile -itemtype file -force in Powershell.

4. Now open the profile file. If you are using Server Core or Hyper Server R2, you can still use Notepad (it is present, but missing a few features). So enter notepad $profile in Powershell.

5. Within Notepad, enter the Import-Module command for PSHyperV. If you install PSHyperV using the supplied install.cmd, this path should be like

Import-Module “c:\Program Files\modules\hyperv\hyperv.psd1”

6. Once done, save the file and exit Notepad.

7. To test, open a new Powershell prompt and type Get-VM. If everything has gone as planned, you will get a list of all of the VMs present on your Hyper-V server.

This process will only work for the current logged on user. If you have multiple user accounts on Hyper-V, you will need to repeat this process for all that require access.

Finally, if you have not already done so you will need to set the execution policy for Powershell. I’ve found that all you require is RemoteSigned. To set this, enter set-executionpolicy remotesigned within Powershell.

Powershell Tip #1
In Powershell, type $profile.

PS C:\Program Files\Microsoft\AxFuzzer> $profile
C:\Users\mengli\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

That points to where your profile is stored at. This is a powershell script that executes upon the start up of any powershell prompt for the current user. Go ahead and make the file. In my case, I made a new file at the location by typing this:

new-item $profile -itemtype file -force

Now, open the file and you can put in things like this:
set-executionpolicy unrestricted
. \\meng\shared\powershell\hyperv.ps1
set-executionpolicy remotesigned

Every new powershell prompt that you

Getting System Information from the command line or Powershell

2 October 2009 / / 1 Comment

Although there are any number of tools available to gather and collate information regarding the configuration and composition of a computer, these are often overkill when all you wish to learn is one or more basic details like the processor type, memory, computer name etc.

A quick shortcut is to gather this information from the command line or Powershell. Windows XP and later includes in the systeminfo utility. Typing this at the command prompt will produce information similar to this:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
c:\systeminfo
Host Name:                 SOMEPC
OS Name:                   Microsoft Windows 7 Ultimate
OS Version:                6.1.7100 N/A Build 7100
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          SomeOwner
Registered Organization:
Product ID:                00428-321-7001132-70186
Original Install Date:     04/05/2009, 10:29:33
System Boot Time:          28/09/2009, 13:50:08
System Manufacturer:       Dell Inc.
System Model:              Latitude D820
System Type:               X86-based PC
Processor(s):              1 Processor(s) Installed.
[01]: x86 Family 6 Model 14 Stepping 8 GenuineIntel ~2000 Mhz
BIOS Version:              Dell Inc. A09, 04/06/2008
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume2
System Locale:             en-gb;English (United Kingdom)
Input Locale:              en-gb;English (United Kingdom)
Time Zone:                 (UTC) Dublin, Edinburgh, Lisbon, London
Total Physical Memory:     3,326 MB
Available Physical Memory: 858 MB
Virtual Memory: Max Size:  8,313 MB
Virtual Memory: Available: 5,500 MB
Virtual Memory: In Use:    2,813 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    somedomain.lan
Logon Server:              \\SOMEDC
Hotfix(s):                 4 Hotfix(s) Installed.
[01]: KB958830
[02]: KB969497
[03]: KB970789
[04]: KB970858
Network Card(s):           3 NIC(s) Installed.
[01]: Intel(R) PRO/Wireless 3945ABG Network Connection
Connection Name: Wireless Network Connection
DHCP Enabled:    Yes
DHCP Server:     10.10.0.1
IP address(es)
[01]: 10.10.0.100
[02]: fe80::901:8ac7:5a6b:1f56
[02]: Broadcom NetXtreme 57xx Gigabit Controller
Connection Name: Local Area Connection
Status:          Media disconnected

If you are using Powershell – if not, why not? – the get-wmiobject win32_computersystem command will return rudimentary details regarding the host PC.

1
2
3
4
5
6
7
PoSH>get-wmiobject win32_computersystem
Domain              : somedomain.lan
Manufacturer        : Dell Inc.
Model               : Latitude D820
Name                : SOMEPC
PrimaryOwnerName    : SomeOwner
TotalPhysicalMemory : 3487690752

Windows Task Scheduler Keyset does not exist Error

1 October 2009 / / 1 Comment

Task Scheduler is one of those great little components that once you set it, you tend to forget it. One of the Windows 2003 servers I tend has been running scheduled tasks flawlessly for over a year until they suddenly stopped one day. Every time I went to open/edit and individual task’s properties, a dialog with the following message appeared:

1
2
3
General page initialization failed.
The specific error is:0x80090016: Keyset does not exist
An error has occurred attempting to retrieve task account information. You may continue editing the task object, but will be unable to change task account information.

A solution to this problem is not readily apparent, more so after the ubiquitous net search returns results that relate to Windows 2000, not 2003. After some playing, and with reference to the MS KB article http://support.microsoft.com/default.aspx?scid=kb;en-us;246183, I got the Task Scheduler working again doing the following:

  1. Stop the Cryptographic service
  2. Delete the contents of the C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\S-1-5-18 folder – as a precaution, I made a backup first.
  3. Start the Cryptographic service (a server restart may be required)
  4. Re-assign the Run As user account for every required scheduled task

Getting Powershell Management Library for Hyper-V (PSHyper-V) up and running

28 September 2009 / / 1 Comment

One of the great capabilities of Powershell is the ability to extend its’ functionality through new libraries. One I am currently playing with is the Powershell Management Library for Hyper-V, or PSHyper-V. For Server Core and Hyper-V Server users, the cmdlets contained within this library add a new dimension of functionality and capabilities, and enable admins to reduce their reliance on Hyper-V manager to perform otherwise simple tasks.

Although you can load the library upon demand, there is another method available whereby it may be preloaded as part of your windows profile.

  1. Download the latest recommended release of PSHyper-V from http://www.codeplex.com/PSHyperv
  2. Copy the contents of the ZIP archive onto your Hyper-V server. In my instance, these were to a folder called c:\powershell
  3. To get your profile path, type the following from with a Powershell prompt:
    1
    $profile

    You will typically get something like:

    1
    C:\Users\your_user_name\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
  4. The file Microsoft.PowerShell_profile.ps1 is the Powershell script that is executed upon the startup of any Powershell prompt for your user account. In most circumstances, this script doesn’t exist, so you will need to create it (it is worth checking first). To create the script, enter the following into a Powershell prompt
    1
    new-item $profile -itemtype file -force
  5. Now edit this file and add the path to PSHyper-V.ps1 into it. In my example, this is as follows:
    1
    . c:\powershell\PSHyper-V.psq

    Note the dot-space prior to the file path. This is required to execute the script.
    (Editing this file on server core or Hyper-V server can be a bit of trial. In the end, I did it remotely.)

  6. That’s it. To test it, either start a new Powershell prompt. If all is well, a list of the loaded PSHyper-V cmdlets will be shown.

Thanks to the author of the Technet blog post from which I have sourced most of the information for this.

Virtual Server to Hyper-V: Parallel port driver service failed to start error

24 September 2009 / / 1 Comment

I’m currently migrating a substantial number of virtual machines (VMs) from Virtual Server to Hyper-V server. Although this is a fairly painless process, a common error for Windows VMs relates to the parallel port service. The system eventlog error goes something like:

The parallel port driver service failed to start due to the following error:  The service cannot be started, either because it was disabled or because it has no enabled devices associated with it.

The reason for this is quite simple: Virtual Server supported parallel ports, whilst Hyper-V doesn’t. Typically, any basic VM created through VS will incorporate a virtual parallel port even once the Hyper-V integration components includes in the new HAL are installed.

There are two options here, you can either manually hack your way through Windows removing all traces of the parallel port, or much simpler, completely disable the parallel port service. The latter is somewhat easier, and may be accomplished in a matter of minutes:

  1. Backup your registry
  2. Open Regedit
  3. Go to HKLM > System > CurrentControlSet > Services > ParPort
  4. Change the start parameter value to 4.
  5. Restart your server – optional, but I do this to confirm this has worked.

That’s it. Upon the next restart, you should not get any service alert for the parallel port.

Getting list of network interface in Linux

23 September 2009 / / 0 Comments

For those of us used to Windows management tools, getting a comprehensive list of data regarding installed hardware on a Linux box can be a little daunting. Whilst recently migrating a virtualised ubuntu box, I needed to find out just what network hardware was in use.

Within a linux shell, type the following

lshw -class network

This will produce a full list of all installed network hardware. For newbies, the define name you are probably looking for is called logical name.

« Older posts Newer posts »

© 2025 Alexander John

Theme by Anders Norén — Up ↑