republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
3871
Share Topic
Posting?
Post a:
Post a:
Links: ·Posting Guidelines ·BELARC Advisor ·BIOS Beep Codes ·Equip. ID FAQ ·Mobo Finder ·Where to Buy Hardware
AuthorAll Replies


Rexter
YeeHaw

join:2002-11-17
cloud 9

Mirra M-250 Hack

I'm interested in using MagicJack for my home phone service. One of the things that I dislike about it, is that it requires your Windows machine to be on, and logged in to operate. I got to thinking. I should just piece together a basic XP system to be a designated Phone server, Looking through my stock-piles of misc crap, I found just the thing. I have one of these.
»reviews.cnet.com/soho-servers/mi···025.html
Despite the fairly good review, this thing is about the stupidest, most worthless backup device ever invented, but it uses a standard VIA EPIA mainboard.
»www.via.com.tw/en/products/embed···ndex.jsp
Not the fastest little thing, but I'll bet it'll run XP, and the MagicJack software just fine. Here's where the problem begins. Mirra, now owned by Sygate, put considerable effort, and money into making sure this device would always be the worthless piece of shit they designed it to be. God forbid you actually make it into something useful. The BIOS is locked down tight. You can't reset the Password, and you can't reflash the BIOS with the VIA tools. I found this article, where someone found a way to hack into it.
»eurowonka.blogspot.com/?zx=9d00b737744f1647

Friday, March 06, 2009
Reclaiming my Mirra
I own a Mirra M-250 personal server. I originally purchased the device to serve as an easy backup solution for part of my home network. One day it was replaced with another solution and I set the Mirra on a shelf. I took it down today with the intention of converting it into a small Linux box for the lab.

DISCLAIMER
No warranties, either express or implied, are hereby given for anything provided by Eurowonka (this includes "data", "process", or "software".) All data, process, or software is supplied as is, without any guarantee. The user assumes all responsibility for damages resulting from the use of the data, process, or software, including, but not limited to, a voided warranty on your Mirra/Seagate product, the loss of all data and configuratiom from your Mirra/Seagate product, the permanent loss of all function for your Mirra/Seagate product, loss of all data from other hard drives on computers used during the process.

HARDWARE
The hardware for the M-250 I own is a custom case that includes a EPIA 5000 Revision E motherboard. The RAM is 64MB of PC133 memory and a Seagate Barracuda 7200RPM 250GB IDE hard drive.

The motherboard has a full compliment of components for being so small: PS2 ports, VGA, LPT, TV out, NIC, USB, AC 97 sound, COM, power leads for case fans, one PCI slot, two IDE connectors.

As shipped, the Mirra has covers over the VGA, LPT, COM, and front USB ports. These can be removed easily. The PS2 ports are covered by a piece of permanent shielding on the back of the unit.

NOTE: The Mirra devices were manufactured for several years so the hardware inside your unit may differ from my device.

BOOTING
Connecting a VGA monitor, USB keyboard, and USB mouse allows you to monitor and control the boot process. There should be a Mirra splash screen during which you can press the DELETE key to trigger the BIOS configuration program.

The BIOS asks for a password. A quick search of the Internet did not reveal the default Mirra password. My assumption was that a CMOS clear should take care of the password. Checking the VIA web site, I was able to verify which model of EPIA motherboard I had and I downloaded the manual.

NOTE: VIA has several versions of their mini-ITX EPIA motherboard. My model happened to be the original EPIA. It is possible that your device may have a different motherboard model or maybe an entirely different mini-ITX motherboard brand inside. Verify carefully which motherboard you have to ensure that the manual and software are appropriate for your device.

Version 1.31 (dated Sept 23, 2008) of the EPIA manual had the motherboard schema on page 12. Jumper J10 is for clearing the CMOS on this revision of the board. I followed the procedure on page 37.

NOTE: Verify that the power is off to the unit before clearing the CMOS to prevent possible damage. The power supply is so quiet in these units it is best when you just unplug the unit from power to clear CMOS.

Upon reboot, the BIOS password was still intact. At this point I figured something was up. A quick search of the Internet turned up the cause. Mirra had modified the BIOS to ensure a CMOS clear would not erase the password.

SOLUTION
In order to remove the BIOS password, the OEM BIOS image had to be reloaded. This process is made a little trickier by the hardware configuration of the Mirra.

NOTE: By opening the Mirra case you will void any warranty you have with Mirra/Seagate for your device. This may also preclude you from using their support services on a pay basis as well.

NOTE: Modifying the hard drive from the Mirra will erase all Mirra data and configuration from it. Do not modify or format this drive unless you intend to lose all data on it and never use is as a Mirra drive again. You should be able to use a different drive but I did not test that possibility.

1) Download an ISO image for FreeDos v1.0 (»www.freedos.org/freedos/files/) and burn a bootable CD of the base or full install.

2) Remove the hard drive from the Mirra and place it in another computer as the only HD. It should be configured as a master IDE drive already. The second computer should also have a CD drive configured as master IDE drive on another IDE channel.

NOTE: If there are other hard drives in this second computer you may accidentally delete the data on them. It is safer if the Mirra hard drive is the only one inside this second computer.

3) Boot the second computer from the Free Dos CD in Live mode. Choose 1 from the boot: prompt to continue and then choose 5 to boot Live CD.

4) Switch to X: drive and CD to path X:\FDOS\BIN. The CD drive showed up as X: on my configuration. It may be different on yours.

5) Run the following Free Dos commands in order:

FDISK /CLEARALL --- erase everything on HD permanently
FDISK /PRI:64 -------- create a 64MB partition on the HD
FDISK /ACTIVATE:1 -- make the partition active
FDISK /MBR ---------- populate HD MBR with Free Dos boot software
FORMAT C: /U /S ---- format the partition to be bootable C: drive

6) Download the files needed to reimage the BIOS

AWDFLASH.EXE »www.biosmods.com/download.php
EPIA0207.BIN »www.via.com.tw/en/products/mainb···rd_id=21

NOTE: Although the VIA web site has BIOS flash programs, they will not work with your Mirra until you re-image the BIOS. As long as the Mirra BIOS is installed, the OEM flash programs will fail and say that there is a mismatch between the flash program and the ROM chip. The Award flash program (I used v8.83) works as long as the ROM chip is compatible.

NOTE: EPIA0207.BIN is the OEM BIOS image for my model of Mirra server. I verified that the DOS flash program from VIA supported the ROM chip id (39SF020A) on my unit. The ROM chip is in the corner of the motherboard closest to the front USB ports. It is important that you verify that you have the correct ROM chip and software to prevent issues.

7) Copy the unzipped files for awdflash.exe and epia0207.bin (or your motherboard's correpsonding software) on to the 64MB partition of the Free Dos C: drive.

8) Replace the Mirra hard drive back in the Mirra and connect it.

NOTE: Make sure the hard drive is configured as the master IDE drive. If you unplugged the Mirra IDE cable, make sure it is plugged back into the correct IDE socket. On my motherboard it is the IDE connector closest to the front of the case.

NOTE: If you can plug the Mirra into a UPS or other uninterruptible power source this is preferred. When dealing with BIOS flashing, a power outage during the process can rarely cause unrepairable damage.

9) Attempt to boot the Mirra with the drive. The Free Dos OS should boot up.

NOTE: If you see the screen populated with "L 99 99 99 ..." on boot, this means that the MBR of the disk has not been converted to Free Dos. You will need to apply the Free Dos MBR to the hard drive before it will boot. This involves running the Free Dos FDISK application with the /MBR parameter.

10) Run the awdflash.exe (or your motherboard's corresponding flash) program. Upload the OEM BIOS image to the ROM.

NOTE: The awdflash.exe program will allow you to backup the current BIOS image. If you never intend to use the Mirra as a Mirra backup device again, this is unnecessary.

11) Turn off the machine and unplug it from the power source. Clear the contents of the BIOS.

12) Plug the Mirra back into the power source and boot it up. The splash screen should be changed to a VIA splash screen. You should be able to go into the BIOS configuration now using the DELETE key on boot.

By hooking up a CD to the Mirra hardware, you should be able to install several different operating systems. The VIA web site has drivers for Windows OS of various flavors. There are also Linux drivers on the VIA arena web site.

Usually the RAM is one of the first hardware items to get upgraded. If on boot, you get nothing but a blinking green LED by the power button, you may not have seated your RAM completely. Power down and seat the RAM chips again to fix this problem.

So, I'm thinking "Cool! that's what I need to do!" Trouble is, there are a few things that are not working as described. First of which,there is no X:\freedos\BIN. There is an X:\freedos, but no BIN there. There is also an A:\freedos, but no BIN there either. No real concern the fdisk commands seem to work even if I'm in another folder. So I went through the steps of preparing the HD. It didn't listen when I told it to make a 64MB partition. It make it like 73MB or something, but I'm sure that's okay. Everything else seemed to work good, except the drive doesn't boot. I double checked that the drive is active. Perhaps the fdisk /mbr is not doing what it should. How Can I verify this? The other issue is the biosmods.com link is dead. The site is still there. I'm just not sure what that link was pointing at.

If you have any thoughts on this, I'd appreciate it.

Thanks

--
With every new wave of optimism, or pessimism, we are ready to abandon history, and time tested principles, but we cling tenaciously and unquestioningly to our prejudices. (Benjamin Graham)


asdfdfdfdfdfdfdf

@Level3.net

You formatted using the switches specified?
The /s is the system command which will also copy kernel.sys and command.com over to the root directory of the drive.

Does the drive have kernel.sys and command.com in the root directory?

The awdflash.exe that is being linked to at biosmods is the bios flashing utility you need to flash the bios of the mirra motherboard. The *.bin file is the actual bios image used.

The reason for the specific choice of that awdflash.exe utility is:

quote:
Although the VIA web site has BIOS flash programs, they will not work with your Mirra until you re-image the BIOS. As long as the Mirra BIOS is installed, the OEM flash programs will fail and say that there is a mismatch between the flash program and the ROM chip.
Also did you confirm your rom chip. If you have a different rom chip the specific bios image file might not be appropriate:

quote:
I verified that the DOS flash program from VIA supported the ROM chip id (39SF020A) on my unit. The ROM chip is in the corner of the motherboard closest to the front USB ports. It is important that you verify that you have the correct ROM chip and software to prevent issues.
If you are confused about why you are doing any of the things specified post questions and I'll answer what I can.

It's not registering with me why the partition needs to be 64MB. If anyone can answer this I would appreciate it.


Rexter
YeeHaw

join:2002-11-17
cloud 9

Thanks for taking the time to post.

Did you find the awdflash program that the deal link was trying to point to?

I'm a little confused about fdisk /mbr. What does that do?

After the format c:/u /s the drive is empty. dir shows the drive as empty.
--
With every new wave of optimism, or pessimism, we are ready to abandon history, and time tested principles, but we cling tenaciously and unquestioningly to our prejudices. (Benjamin Graham)



asdfdfdfdfdfdf

@Level3.net

reply to Rexter
btw the sys command, like fdisk, can trash a working OS installation if you direct it to the wrong drive. This is why the site you linked to suggested removing other drives from your machine as a safety measure.

"NOTE: If there are other hard drives in this second computer you may accidentally delete the data on them. It is safer if the Mirra hard drive is the only one inside this second computer."



asdfdfdfdfdfdf

@Level3.net

reply to Rexter

quote:
Did you find the awdflash program that the deal link was trying to point to?
The article claims to use the v8.83 of awdflash.exe. Phoenix absorbed award and this is no longer readily provided by phoenix.
I found this version at jetway(another mb manufacturer). It should work. I can't be absolutely sure.

»www.jetwaycomputer.com/Download.html
Here is the link to the file itself:

»www.jetwaycomputer.com/download/AWDFLASH.EXE

quote:
I'm a little confused about fdisk /mbr. What does that do?
It rewrites the master boot record which is the first sector of the disk. This is what the bios loads after post and the code here reads the partition table info and then loads the boot sector of the partition that is marked as active. This boot sector then loads the OS kernel. The format /s command or the sys command is what sets up the partition boot sector and puts the kernel code into the root directory.

quote:
the drive is empty. dir shows the drive as empty.
These are hidden system files. In order to see them you should try a number of different switches.

make sure the proper drive is the current drive.
cd \ to make sure the root directory is the current directory

Then try each of the following in turn:
dir /a
dir /ah
dir /ahs

One of these commands should properly list files with the hidden and system attributes in the directory.

If you are seeing nothing then it looks as if the sys files are not there.

If this is the case an alternative is to use the sys command. I will go into that as the next step if it appears as if no files are there. If you do see some files list them here.


Rexter
YeeHaw

join:2002-11-17
cloud 9

Yea, no files listed with any of those dir commands. I used the sys command, and now the drive boots. OK, on to the next step. I'm going to try out that BIOS you pointed to.

I'll let you know...............
--
With every new wave of optimism, or pessimism, we are ready to abandon history, and time tested principles, but we cling tenaciously and unquestioningly to our prejudices. (Benjamin Graham)



asdfdfdfdfdfdf

@Level3.net

reply to Rexter
Make sure you check your motherboard rom chip, as stated in the eurowonka instructions to make sure you have the same. If not we will need to do more research.

Also keep in mind you need both the awdflash.exe utility (to do the flashing) and the EPIA0207.BIN file for the actual bios image, assuming your chip is the same as his.



Rexter
YeeHaw

join:2002-11-17
cloud 9

Yes, mine is the same chipset that this guy has. I've flashed the bios, and reset the password. It looks like this bitch is officially unlocked! I'm going to try the XP install now.



asdfdfdfdfdfdf

@Level3.net

reply to Rexter
Good, I'm glad it went smoothly.
Thank you for the update.



Rexter
YeeHaw

join:2002-11-17
cloud 9

1 edit

Click for full size
Mirra M-250 Phone Server
This thing only had 64MB of PC100 ram. I increased it to 256MB. It had a 250GB HD. I figure, why wast it. I'll use that somewhere else. I dropped in a massive 4.3GB HD. That should do the trick.

It's good to go! I just need to find a good location to place it, and wire it into the home phone system.

Thanks for your help.
--
With every new wave of optimism, or pessimism, we are ready to abandon history, and time tested principles, but we cling tenaciously and unquestioningly to our prejudices. (Benjamin Graham)

Sunday, 03-Jun 05:11:41 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics