[cobalt-users] New install resorting to previous install

["Robert Fitzpatrick" <robert@xxxxxxxxxxx>]

Got a new RaQ3i and loading it for first time. I only had one drive when
testing it to be sure it was good, so I loaded 4i OS. Brought in a
second hd and loaded a 4r iso previously downloaded and burned to CD,
booted CD from machine on network, booted RaQ4r from net, and the RaQ4i
OS is still on the machine. So, you think, the CD is actually 4i and go
and burn another one, same thing. I added storage in the GUI to be sure
there was nothing wrong with the drive or controller for the second
drive, everything loaded fine with the right sizes, etc. I then removed
the extra storage using the GUI, all OK. So, you think, it's the source,
but I wanted to be sure before I waste my time downloading another iso
because I could swear the first CD was used to load a RaQ4r before.
Brought up the two hard drives on a RedHat box and deleted everything
from them using Webmin, did a 'fdisk -l' and nothing on the two drives.
This is where it gets weird -> Put the two drives back in the RaQ,
booted from net, goes through the first tests (MFG, etc.), starts to
load rpm's, then starts shutting down, reboots backup with the same IP
and hostname previously given to the machine and all is back to the same
4i load I did before. I go into storage in the GUI and see the second
drive with a big red 'X' denoting it's disabled, try deleting it or
editing it, nothing happens - just the page reloads with the same
status. However, the first drive functioning normally with 4i loaded.
Remember, these drives were completely wiped prior to the last install,
how did it know the second drive name, hostname, or IP? Where is that
coming from? Or were they wiped? Can something still be on the disk when
'fdisk -l' shows nothing for the drives. I did 'fdisk -l' after I
deleting each partition and each time the partition that was removed no
longer showed up.....

Any ideas?

--
Robert