joekrahn wrote:Have you tried loading the factory firmware instead of OpenMSS? It is possible that the firmware modifications are causing a problem that only shows up when initializing a new disk. Also, you might try to zero out the MBR on the replacement disk.
bow2evil wrote:just wondering ive seen some stuff reguarding "dd if=/dev/zero of=/dev/hda" i would guess its a simple linux command but do you run it befor boot and nuke or after. and what does it do attach some type of file system to the hdd or what?
joekrahn wrote:To really see what is going on, it would help to have a console, which takes some hardware work.
npe wrote:Just to make sure...You've replaced the old drive with a new drive?
You may check that the new drive is set to Cable Select (CS) on the IDE interface.
Nothing else will work.
Usually there is a jumper settings table written on the outside of the disk.
Set the interface to Cable Select (CS) and retry the firmware download.
IDE disks of the Parallel ATA (PATA) type gives you the opportunity to select Master (M), Slave (S) and Cable Select (CS) type of operation. Possibly a few other settings too.
Of interest in this context is CS.
Which means that the computer (in this case the MSS) finds and designates the drive as master or slave depending on the location of the of the disk on the IDE cable.
A normal IDE cable has two connectors for IDE units and one for the motherboard. If You attach two IDE drives to the cable (both set to CS) the disk at the end of the cable will be designated as master and the disk at the "middle" connector on the cable will be designated as slave.
When it comes to the MSS the cable only have two connectors. One at each end of the cable. Nevertheless You have to set the disk You install to CS.
Like the original disk was jumpered.
Users browsing this forum: No registered users and 3 guests