The continuing saga of the Naughty NAS

[Steverobbins]

First things first. I told you so. 
  Drive errors on my ls-chl are not, in fact, drive errors. Code 30 is "disk has been disconnected from the array" and thats not possible on a one disk system. Its not even a code for this model.
  But I am open minded. I purchased a new disk identical if a little slimmer than the original, but a segate barracuda no less.
Disassembled the NAS, put in the new drive and rebooted Code 6 Corrupted firmware.
  Took out the new drive put in the old drive and lo....Code 30. Apparently the firmware isnt firmware, Its stored on the disk.
  Now for the fun part. I can not format the new drive using a cradle and the NAS and the NAS Nav tells me there is a comms error with the NAS. I did a reset to factory and still I have trouble. Admittedly with the old drive in but you would think that it would solve more problems than it creates. 
  But now the NAS is tripping over its self constantly and takes its self offline or hides it's self. I need a way to solve this before decide there's no point in using any buffalo product in the future and opt for something cheaper that actually works.

[davo]

 Why can't you format the new HDD in a cradle??

[Steverobbins]

Lol. I don't know. Thats why I posted here. I can't even flash the firmware nothing is working.

[Steverobbins]

And now I can not talk to the NAS. I can ping it and it will reply. but i can not talk to it using NAS Nav or web page. What a fantastic piece of kit. Currently I am trying to think of other things to Distract myself so I don't have multiple sarcasams!