Err:NoDisk.... Connect AS

[SatSearcher]

Getting this error message on my AZBox Elite and it's refusing to boot up. Read that some people with the premium version have had this error, something to do with the HDD, but Elite doesn't have a HDD so does anyone have any idea whats up? Is my AZBox knackered?

[Dig Deep]

If it reads the usb the put a new fresh copy of the FW on the usb and re-do all

[SatSearcher]

It does read the USB, but when i try to upgrade from it, it says failed then tries to boot again, which fails also!

[freeman01]

Hi Satsearcher

Is your problem solved ?

regards

[SatSearcher]

Yes seems to be at the moment, but don't really know why or how! Read somewhere about the memory chip inside that has a switch on it, tried switching it the other way, didn't work, switched it back, then it worked, but only once! The next attempt at a reboot resulted in the same error message, so sort of gave it up as a bad job, left it unplugged for a couple of days. Plugged it back in after 2 days and it booted fine and has done since, but still just waiting for it to happen again!

[Blagi]

It reads a bit [if you're a Yank]: "...connect ass" [as in ar*e]... :D For OS to give a you a bit more of their good rodgering... :D

Sorry, just had to... :D

Carry on, with AZ mysteries... We do have a few, don't we... ;)

[happyhammer]

Read somewhere about the memory chip inside that has a switch on it, tried switching it the other way, didn't work, switched it back, then it worked, but only once!

can you provide any details on what/where this switch is oe even a link to where you read about it?

thx

[pr2]

Hi,

Which operations do you perform on your Azbox to get it in this state?
Do you install E2 on it? Do you install the boot from USB (FW4USB)?

Pr2

[SatSearcher]

can you provide any details on what/where this switch is oe even a link to where you read about it?

thx

I found out about this here: https://www.satpimps.co.uk/showthread.php?t=123234 it's the 5th reply.

Didn't have E2 installed at the time, did try it a few weeks ago but went back to original FW and it worked fine for a couple of weeks till this happened!

[g ali]

i had this problem before so i tried all possibilties jtag recovering az tutorial bought a new cf card and an adaptor and a new 1GB dom with no joy untill i came across a thread in another known forum then realized that my problem was hardware with the great help from the gentleman who started the thread i managed to rise my box from the dead the hardware in question was QF3 check whether it's toasted hope your eyesight is good enough if it is then you will need a bit of soldering am afraid good luck
:respect-055:

[SatSearcher]

Just to revive this thread, i had this problem back in march, couldn't seem to fix it so just left the box off for a few days, next time i tried booting it, it worked, and has done till now, but now getting this problem again! Tried all the above but no luck, anyone else got any advice on this?

[PsiDOC]

The no disk will come up if the DOM is playing up on the elite. As a first line of trouble shooting simply pop it out and then put it back in. Sometimes it needs reseating. If that doesn't work then try replacing it and reloading a firmware. They're not that expensive (under £20 for a 2 - 4 GB one on that famous auction site).

Psi

[SatSearcher]

Thanks for the info. So if i take the cover off, which bit is the DOM? Don't want to be pulling the wrong bit out!

[PsiDOC]

The dom is a dark coloured box that sits into a standard 40 pin hard drive connector on the main board. It's about 5cms long, 3cms tall and 0.8 cms wide and looks a bit like this:
51286
You can't miss it.

Psi

PS: Sorry for the late reply. Been away for a few days with the missus.

[SatSearcher]

Thanks for that, found it, taken it out and reinserted it a few times, still no joy! Flicked the switch on it too but that didn't make any difference either! If i buy a new DOM is it likely to fix this problem or could it be that the box is just knackered? Found a 2gb one for sale for £17, is it worth buying?

[iq180]

had this problem too here is what i did, load firmware 0.9.5308 on a usb now rename it patch in lower case, now turn off the az with the power switch and put
the usb in the az and turn the power back on and you should get the blue screen now format the app and then load the firmware after that you will need
to ues a DOMEraser to clean out the DOM.

[SatSearcher]

Thanks, but it won't even let me do that! The VFD display is booting, checking then straight to the error message, doesn't even recognize the USB stick.

[iq180]

did you rename the firmware = patch = and nothing else just patch.

[SatSearcher]

Yes, tried patch.bin, and just patch, same result!

[iq180]

you need to remove the keep alive memory battery for about 30 min with all the power off and then try to force load firmware 5308

[SatSearcher]

Will try it, but how do you remove the keep alive battery, and which bit is it?

[iq180]

it looks like a large watch battery and it is silver, you will need to push over the clip just enougth to slide the battery out, do this with the power supply unpluged from the reciver.

[SatSearcher]

Ok, will try it later, can't just now as the missus is watching telly. Will report back if i have any luck! Thanks for the advice.

[SatSearcher]

Tried that, still no luck, just comes up with the error message before you can try doing anything!

[iq180]

try firmware 0.9.2372, it was reported that firmware 0.9.2371 would load but i cant find that # firmware so just keep trying older firmware.
good luck hope you get it going.

[SatSearcher]

Will try, but i'm not hopeful. Think the DOM has had it! Ordered a new one earlier in the week but it's coming from hong kong so might be a couple of weeks before i get it. Will try some older firmwares though, it might work!

[iq180]

you mite want to google a how to on this but i did read that you can remove the DOM from the az box and put it in a computer, i think it uses a ide conector
and you can clean it this way, but i have not tried it.

[SatSearcher]

Well, got my new DOM from hong kong, and that seems to have sorted it out, the DOM must've been totally fried! Thanks to everyone who tried to help me with this problem, much appreciated!