Visit Open-E website
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 26

Thread: Unexpected Shutdown when initializing iSCSI Volume

  1. #11
    Join Date
    Oct 2008
    Posts
    69

    Default

    After the crash in init volume lv000 : (lv000 1.5 To, lv001 1.4To, lv002 70GB) we restart server and it finish the init without any other trouble.

    I removed everything and restart with 10 volumes of 100GB, we'll see.

  2. #12
    Join Date
    Oct 2008
    Posts
    69

    Default

    OK shutdown on lv0006 à 45%...

  3. #13
    Join Date
    Oct 2008
    Posts
    69

    Default

    hmmm lv0006 was the only volume with replication activated... (my mistake)

  4. #14
    Join Date
    Oct 2008
    Posts
    69

    Default

    OK shutdown again without any replication volume :

    lv0000 100.00GB OK
    lv0001 200.00GB OK
    lv0003 400.00GB 99% => Shutdown
    lv0002 300.00GB Waiting
    lv0004 500.00GB Waiting
    lv0005 600.00GB Waiting
    lv0006 700.00GB Waiting

  5. #15

    Default

    Can you obtain the Areca logs and send them to the support ticket 1009172 and send them to Areca for verification. Also we see a very high load from the CPU and engineers think it could be something with the RAID, recommend to do a RAID verify.

    Also check to see if there is a another IP Address that is using the same address as the DSS 172.16.0.1 (Printer, PC... or other).
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  6. #16
    Join Date
    Oct 2008
    Posts
    69

    Default

    It's done Todd

    I have sent everything to support.

  7. #17
    Join Date
    Oct 2008
    Posts
    69

    Default

    Complete checking of volume done with ARECA, no errors.

  8. #18

    Default

    Ok, let's do a couple of things to nail this issue as best we can. Do the following:

    1) Run the Repair Filesystem tool from the Extended tools (CTRL + ALT + X) menu from the console. They system will reboot.

    2) Then test again to see if it crashes again.

    3) If it Crashes again - run the memtest - After system is booting from POST, hit the escape key or tab key. You will get a basic menu to run the memtest - let that run for 1-2 hrs.

    4) Run the Demo-CD version of DSS from the website link below. Then test, I want to verify if it is the USB module.

    http://www.open-e.com/account/demo/
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  9. #19
    Join Date
    Oct 2008
    Posts
    69

    Default

    First thing, thanks a lot for your help and patience, Todd.

    So :

    1) Remove LV !!Warning!!
    There are no NAS LV.

    For info, i've done a complete delete of Unit when migrating from 32bit to 64bit.

    3) Memtest, i've done this test too before, just after the fail update on DOM USB (4 hours without any problem)

    4) I 'll try the Demo CD as soon as i can.

  10. #20

    Default

    No problem on working this out with you, as now it is becoming interesting how your system is not working like so many. Let's keep trying several things.

    1) Use the Repair Filesystem tool not the Remove LV ...

    Just create a NAS LV and then run it.

    Or just go to the last step to try the Demo-CD route to rule out the USB module.
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •