Visit Open-E website
Results 1 to 8 of 8

Thread: System crash

  1. #1

    Default System crash

    Hi all

    I'm using the DSS 6 and had system crash. Meaning the iSCSI Volumes were not accessible, the same for the web interface. The system replied on the IP.

    After cold reboot the system is online again. The error log is empty - any idea how to see what happened and how to solve the issue?

    Thanks
    Norbert

  2. #2
    Join Date
    May 2008
    Location
    Hamburg, Germany
    Posts
    108

    Default

    Quote Originally Posted by norbert.miescher
    Hi all

    I'm using the DSS 6 and had system crash. Meaning the iSCSI Volumes were not accessible, the same for the web interface. The system replied on the IP.

    After cold reboot the system is online again. The error log is empty - any idea how to see what happened and how to solve the issue?

    Thanks
    Norbert
    Norbert,

    have you had a look at the system logs? (Not the web-accessible error log, but the files you get when you download the system log zip file). As these are mostly Linux-typical log files, you might find interesting information in those files, hopefully pointing to the actual cause of the hang.

    Regards,
    Jens

  3. #3

    Default

    Hi Jens

    Thanks for the input. I downloaded the file, actually it's a compressed file with many, many logs. Where would you suggest to check for such a "system hang"? I could imagen, the system had not enough memory. Could this be a cause? I'm using 2GB for two iSCSI hosts.

    Thanks
    Norbert

  4. #4
    Join Date
    May 2008
    Location
    Hamburg, Germany
    Posts
    108

    Default

    Hi Norbert,

    the dmesg* files are a good starting point for this.

    Concerning memory: Have a look at the internal memory statistics - I assume that you'll see most of the memory being used as file system cache. We're running a DSS V6 64bit as a FC target for approx 15 servers, with 4GB of memory, and most of it (90%? Can't look right now) is used for buffering. So "only 2GB" shouldn
    t be a reason for a system crash, only for missing performance ;-)

    With regards,
    Jens

  5. #5

    Default

    did you check your raid array to see if it is OK?
    was there any other activity going on when the system crashed?

  6. #6

    Default

    Quote Originally Posted by jmo
    Hi Norbert,

    the dmesg* files are a good starting point for this.
    Hi Jens

    I chekced the dmesg files and found some inputs:

    scst: ***ERROR*** Unsupported command 0x5e

    scst: ***ERROR*** Unsupported command 0x25

    Do you have an idea what this does mean?

    Thanks

  7. #7
    Join Date
    May 2008
    Location
    Hamburg, Germany
    Posts
    108

    Default

    Quote Originally Posted by norbert.miescher
    Hi Jens

    I chekced the dmesg files and found some inputs:

    scst: ***ERROR*** Unsupported command 0x5e

    scst: ***ERROR*** Unsupported command 0x25

    Do you have an idea what this does mean?

    Thanks
    Looks to me like the scst package (responsible for iSCSI and fiber channel target support) has received the commands 0x5e / 0x25, which seemingly are not supported by SCST. Or, but in my eyes less probably, SCST tried to issue these commands and the receiving end returned an error.

    From what I could find on the net, 0x25 is SCMD_READ_CAPACITY and 0x5e translates to SCMD_PERSISTENT_RESERVE_IN.

    Have you updated / modified / reconfigured your iSCSI initiators, thus causing those commands?

    With regards,
    Jens

  8. #8

    Default

    Hey Norbert

    what type of enviroment are you running?
    are you using any vmware/hyper-v ?
    do you have the latest dss version ?
    was there anything in the critical error.log file
    any other error messages at the bottom of dmesg2

Posting Permissions

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