DOM boot failed - DOM update failed

Hi all there,

The first few test boots with the new iSCSI-ENTERPRISE went well. I had all the nice screens as printed in the manual. The screen said: "Model Open-E iSCSI ENTERPRISE, Version 1.51.IE00000000.1376, Release date 2006-01-04"

Some days later reboots from iSCSI-Enterprise DOM failed with: "Error loading Operating System".

Cross-checking hardware, power cable, IDE socket etc. showed everything seems OK. I then tried to update the DOM v1.51 to v1.71 from the ISO-image CD. So I downloaded the ISO file and burned it on a CD. During the update process the iSCSI-Enterprise DOM was positioned in IDE0-master. The ISO-image CD in IDE1-master did boot. Then the screen said:

Then the update process stops with:
"Initializing System ... <CR> Unable to update (0x7F) ..."

My Questions:
1. Is something wrong in my processes?
2. Can I do something different to get the DOM booting again? I seems that the DOM lost its operating system.
3. Is the DOM maybe defective?

Please help ...
hopefully, Robert

--------------
MB: Asus A8N-SLI, 2x GigaLan, 2x PCIe(8x), 2x PCIe(1x)
MB-Chipset: Nvidia nForce2
CPU: AMD A64 3200+
Grafic: Simple XVGA Card with PCI, 32 MB
HDs: 8x 400GB Seagate ST 3400633AS Baracuda Sata2
Raid Controller: Areca ARC 1220 (8ch) in first PCIe(8x)
Raid-Set0#01 (hd#1-7) plus 1 hot-spare (hd#8)
1800 GB data-vol-set Raid1
40 GB srv1-boot-vol-set
40 GB srv2-boot-vol-set
40 GB srv3-boot-vol-set
XP-Boot-HD: 160 GB Sata1, Sata-Controler on mainboard.

Try downloading the ISO image from our web site Software Updates: [2006-08-25]
iSCSI Enterprise update ver. 1.69 build 2143 . You are doing the update correct. When booting with the CD ISO the update should take over. If this happens again please contact use at support@open-e.com to get RMA# so we can ship out DOM immediately.

Partitions on DOM deleted

During experiments with DSS triela we have accidentaly deleted partitions on DOM with NAS Enterprise. Is it possible to repair them using update CD? Or some other way?

you can try updating the dom to repair it.
use the latest version of the product that you have