Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[celticguy42]

I'm getting these errors in my log, then the 3200 is rebooting... I have 2 initiators - 1 running Windows Server 2003, the other running Windows Server 2008.  This has happened 3 times in the last week or so.  I'm running the latest firmware (have been for almost 2 months).

Category:    SCSI
Severity:    Warning
EventID:    SCSI Status
Source:    SCSI
Summary:    Initiator ID 0, Target ID 5, LUN 0, Unit Attention, Reported LUNs data has changed

SequenceID    3681
Event    Non-zero SCSI Status
Initiator_ID    0
Target_ID    5
LUN    0
Volume_Number    2
Command    Read 10
Status    Check
Sense_Key    Unit Attention
Sense_Info    Reported LUNs data has changed
SKSV    0x0
Field_Pointer    0x0
Sense_Info_bits_00-31    0x0
Sense_Info_bits_32-63    0x0
SCSI_Flags    0x90
SCSI_Task_Flags    0x3
Process_Flags    1

Category:    SCSI
Severity:    Warning
EventID:    Task Management Request
Source:    SCSI
Summary:    Target ID 4, Initiator ID 3, LUN 0, Logical Unit Reset

SequenceID    3684
Event    Task Management Request
Initiator_ID    3
Target_ID    4
LUN    0
Volume_Number    1
Process_Flags    1

Category:    SCSI
Severity:    Warning
EventID:    Task Management Request
Source:    SCSI
Summary:    Target ID 4, Initiator ID 3, LUN 0, Aborted command completed in 0 seconds

SequenceID    3685
Event    Aborted command completed
Initiator_ID    3
Target_ID    4
LUN    0
Time_Command_Received    0x54b42
Time_Command_Aborted    0x54b42
Time_Command_Completed    0x54b42
Total_Time    0x0
Abort_to_Completion_Time    0x0
SCSI_CDB_Bytes_0_3    0x88000000
SCSI_CDB_Bytes_4_7    0x573e
SCSI_CDB_Bytes_8_11    0xa1120000
SCSI_CDB_Bytes_12_15    0x400000
Process_Flags    1

Category:    SCSI
Severity:    Warning
EventID:    SCSI Status
Source:    SCSI
Summary:    Initiator ID 3, Target ID 4, LUN 0, Unit Attention, LU reset occurred

SequenceID    3686
Event    Non-zero SCSI Status
Initiator_ID    3
Target_ID    4
LUN    0
Volume_Number    1
Command    Synchronize Cache 10
Status    Check
Sense_Key    Unit Attention
Sense_Info    LU reset occurred
SKSV    0x0
Field_Pointer    0x0
Sense_Info_bits_00-31    0x0
Sense_Info_bits_32-63    0x0
SCSI_Flags    0x10
SCSI_Task_Flags    0x3
Process_Flags    1

Category:    System
Severity:    Error
EventID:    General message
Source:    Startup
Summary:    BUG-CHECK Reason: I8K BUG-CHECKed(0)

SequenceID    3687
Text1    BUG-CHECK Reason: I8K BUG-CHECKed(0)

Category:    SCSI
Severity:    Error
EventID:    Bugcheck
Source:    SCSI
Summary:    Command in System too Long

SequenceID    3688
Process_Flags    1

Category:    System
Severity:    Error
EventID:    General message
Source:    Startup
Summary:    BUG-CHECK Timeout occurred waiting for RCP

SequenceID    3689
Text1    BUG-CHECK Timeout occurred waiting for RCP

[willgart]

I have suffered the same issue.
during a copy of a large file, the DSN-3200 has rebooted and I'm seeing the same type of error and messages.

[willgart]

I'm suffering the issue multiple time in 1 day now!!!!
I'm able to reproduce it (not always but near...) by doing important activity through SQL Server 2005.
like running complex queries or processing OLAP cubes.
this heavy trafic cause the issue.
DLink says it could be related to the power system, but connecting the system to a power full UPS don't solve the issue.

sometimes the system reboot without any dump error logged.

[willgart]

there is a new firmware available the 2.5.1.81
we crash less often, but we still have issues.

[☠]

SequenceID    3686
Event    Non-zero SCSI Status
Initiator_ID    3
Target_ID    4
LUN    0
Volume_Number    1
Command    Synchronize Cache 10
Status    Check
Sense_Key    Unit Attention
Sense_Info    LU reset occurred
SKSV    0x0
Field_Pointer    0x0
Sense_Info_bits_00-31    0x0
Sense_Info_bits_32-63    0x0
SCSI_Flags    0x10
SCSI_Task_Flags    0x3
Process_Flags    1

Your Reboots are being caused by sync_cache.   which should ONLY be used for small random writes to databases and NOT for large file transfers.  it can cause havok to RAID5 volumes causing the unit to bugcheck/reboot.