If you have ever received this message, after probably being drained with panic thinking you have lost everything

I had this issue after trying to install Bootcamp, silly me should have just stuck to VMWare Fusion like normal people.

Anyway, most people say hold the option key, but you may find that that doesn’t work because you have not even got as far as the post beeps (C major chord for all you geeks)

Anyway what you need to do, is if you have disk stuck in you can eject this by holding down the mouse button and restarting after 10-20 seconds it will eject, job 1 done.

Next you need to reset the PRAM settings, which is done by holding down a 4 key combination:

Cmd (ALT) + Option key + P + R

this will then post with the C Major chord and then you can let go and it will boot into MAC OSX, then once in just double check that the Mac is your main start up disk to stop this happening again

that is in setting > startup disk

not that it matters but i did all this on a Macbook Pro running OSX Lion (issue came after trying to install BootCamp)

Hope this helps,

thanks for reading

If you are getting No Airport Card Installed, sometimes after a crash, here is what to do:
try this first off, it has worked every time for me,
Turn Machine off, then power on with the Ctrl, Option, P & R keys pressed, once it has cycled, then you can let it boot.

Hey presto, airport card is back

If you have also had issues with your Linkstation LS-GL keeps turning off, here is a brief fix for it.

Error Codes:
LED Flash Codes:
3 flashes – Partition problem with hard drive. Reformat the hard drive.
4 flashes – Fan problem.
5 flashes – ROM problem.
6 flashes – Hard Drive can not be recognized.
7 flashes – Problem with motherboard (RAM, LAN, or Hard Drive controller).

mine was showing as 4 flashes – Fan problem.

but the fan after testing was fine. so i followed this procedure using a TFTP update then a firware refresh.

this enabled me to build a new NAS drive without access to the old one.

So i upgraded my 250Gb drive to a 1TB drive

A TFTP boot requires a little bit of finesse and a tiny bit of luck.  9 times out of 10 when a NAS constantly says “System Now Booting”, E04 (or 4 DIAG light flashes depending on the NAS) or doesn’t show up on the NAS Navigator after a long period of time after an EM boot attempt, then chances are that you need to perform this method.  So, without further delay let’s get to it.

What you’ll need:

-  The NAS Navigator client

-  Your NAS model’s latest firmware

I used a download from the buffalo site version 1.15 (8mg download)

-  Your NAS model’s TFTP boot image which you can find here

ftp://24.153.165.234/array1/share/nas-recovery/

or a direct link for LS-GL

ftp://24.153.165.234/array1/share/nas-recovery/TFTP%20Boot%20Recovery%20LS-GL%201.11.exe

***(NOTE: Some older NAS models may not have a TFTP solution available, if you cannot find your model in the listing please DO NOT attempt to use the TFTP program of another model.)***

Make sure your firewall/anti-virus software is disabled.

Performing the TFTP boot:

1.        Directly connect your NAS to your computer via an Ethernet cable (crossover isn’t necessary).

2.        Set your computer’s NIC (Network Interface Card) to a static IP address of 192.168.11.1

3.       Run the TFTP program for your respective NAS and have the files extracted to your desktop

4.       Boot the device using the EM walkthrough steps.

(Whilst NAS is off, hold reset button in on back, and turn on, it plays some silly tune, then your in)

5.       Open the TFTP folder and run the program TFTP Boot.exe with the icon:

6.       A command prompt similar to the one shown below should appear:

7.       When the NAS boots up it will make a request to the IP address 192.168.11.1 (which is what your computer should be set at) and the terminal should look something like this:

8.       If it doesn’t show the blocks served, try the process again. Some user have reported that after the device shows the error, holding the function button down for 5 seconds can provoke the TFTP requests.

After you see blocks of data being served the NAS typically boots to Emergency Mode at which point you can perform a firmware update. All you need to do from here is run the LSUPDATER.exe

After that has finished jobs done.

You should now have a fully working NAS drive with the std shares setup ie \\LS-GL347\share

defualt username: admin        password: password

Hope this helps, many thanks

Here goes, pics from my travels