I upgraded from MT 2.9.41 to 3.0beta7 via webox …
then I gave the command for restart and now I cant get to my MT … why?
Is this normal… ?
connect to it via keyboard+monitor and see what happens. of course it is not normal
I can’t do that my pc is 5m from the top of the roof …
Can I save the data somehow ?
open winbox loader and hit the ... button to see if it finds your router
It dosen’t
Then the only choice you have is to get close to the box and see what happened
I took the CF disk out and I conected it to diferent computer… MT worked there… then I tried to upgrade it one more time … in primary computer MT didn’t worked… I’ve downgrade it to version 2.9.42 and now MT works …
I don’t know why 3.0beta7 dosen’t works …
i have tested beta7 on RB112 RB153 RB532 and RB532A and i had no problems with downgrading to version 2.9 afterwards
It vouldn’t be a problem If I could log in to the router
The router didn’t respond in any way…
Why do the normal versions work fin and the first beta thah I try dosen’t… ?
I don’t mean to sound overly cynical, but…
…hmm, could the answer to your question possibly have anything to do with the fact that the normal version (as you call it) is normal and the beta version is beta? 
If MT thought it was ready for release as production code, they wouldn’t have labelled it “beta!”
It might work for some (it did for me, in my limited testing…), but not for others. It depends on the hardware you’re running it on, the way you went about installing it, the configuration (if there was one) that it imported during the upgrade, and bugs still extant in the beta code.
I’m not trying to discourage anyone from running the beta code, testing the beta code, playing with the beta code, taking it around the block for a spin. But questions like “why does the stable version work and the beta version doesn’t” seem a little obvious and pointless/non-productive.
If the same 3.0beta7 install works on one machine but not on another, you might put the disk back in the machine it works on, generate a supout, and send it to support along with a description of the hardware that you tried running it on along with the symptoms. Maybe they can figure out what’s wrong.
– Nathan
Hi,
I had a similar thing when upgrading an x86 server from 2.9.x to 3.0rc5. When I connected a monitor it said:
Loading system with initrd
Uncompressing Linux… Ok, booting the kernel.
ERROR: Could not find disk!
Please attache it somewhere else.
The CF card was secondary master so I tried it in the primary master but same error. I have the exact same hardware running 3.0rc2 but think that may have been a cleen install of v3 (i.e not an upgrade from v2). The box does have dual processors so could that be the issue as v2 will only use 1 CPU but v3 makes use of both?
I use v3 RC4 with Intel 1,8 Celeron processor and when I try to upgrade it to RC5 I get same error…
you also had installed RC4 on the CF and upgraded to RC5 and got that error?
No, my installation is on hdd…
I also have the same problem. We initially installed RouterOS v2.9.x on the machine. It worked fine untill it started crashing at irregular intervals. I contacted MT and they told me to send them a support out. I never did this because shortly afterwards 2 other servers of the same brand crashed 
I then contacted the supplier and took the servers back. After some “research” they found that the motherboards and the CPU’s where incompatible
To cut a short story long, they replaced the CPU’s and now, with everything the same(hardware wise) except the CPU, I am also getting this message when I plug in the monitor:
Loading system with initrd
Uncompressing Linux… Ok, booting the kernel.
ERROR: Could not find disk!
Please attach it somewhere else.
We bought a level 4 license for the server and I feel that its the same box and I don’t have to get a new license.
What is common between all our hardware that is failing? Is everyone using single or dual processors? Are they AMD or P4?
We had this problem on a Supermicro box with dual Xeon 1.8GHz CPU’s and 1G rambus ram.
We are using a Intel Pentium 4 3.20Ghz processor(single core with HT), with 1 Gb Ram. 80Gb (no raid) sata drive. The motherboard is a Tyan server motherboard. As per my previous post, the only difference between the original and the current box is the CPU.
We are using a CF in ours so it would appear there is nothing common between the 2 
please make the support output file from the version where it boots, so we could check what could cause that problems and send it to support@mikrotik.com
That is going to be a problem, seeing that it does not start RouterOS. The only thing that we can give you is:
Loading system with initrd
Uncompressing Linux… Ok, booting the kernel.
ERROR: Could not find disk!
Please attach it somewhere else.
This seems to be the only thing that phendry and I have in common.