NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN2120/Win2008R2 - iSCSI errors (disk event 51)
Hi,
I am experiencing a massive outage with RN2120. It has 3 iscsi LUNs dedicated to 3 W2008R2 servers - one physical and 2 virtuals, running in Hyper-V environment.
Everything worked like a charm for ~6 months, but now there is a weird problem - time to time all 3 windows systems get LOTS of warnings DISK event 51 - page exchange error - and sometimes shares get disconnected. After I reboot everything, things get back - but after randomly short period of time I get the same warning - and disconnection of LUNs.
The problem is one of the LUNs is exchange server database - and such a behavior is extremely bad for exchange.
Servers and NAS are connected to the same 1Gb AlliedTelesis switch (which is basically in factory settings - no vlans/routing etc). NAS shows up as "healthy".
ANy ideas would be much appreciated.
I am experiencing a massive outage with RN2120. It has 3 iscsi LUNs dedicated to 3 W2008R2 servers - one physical and 2 virtuals, running in Hyper-V environment.
Everything worked like a charm for ~6 months, but now there is a weird problem - time to time all 3 windows systems get LOTS of warnings DISK event 51 - page exchange error - and sometimes shares get disconnected. After I reboot everything, things get back - but after randomly short period of time I get the same warning - and disconnection of LUNs.
The problem is one of the LUNs is exchange server database - and such a behavior is extremely bad for exchange.
Servers and NAS are connected to the same 1Gb AlliedTelesis switch (which is basically in factory settings - no vlans/routing etc). NAS shows up as "healthy".
ANy ideas would be much appreciated.
12 Replies
- The disks are OK, according to the log:
Device: sdb
Controller: 0
Channel: 0
Model: ST2000NM0033-9ZM175
Serial: <REMOVED BY MODERATOR>
Firmware: SN03
Class: SATA
RPM: 7200
Sectors: 3907029168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e361280
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 39
Start/Stop Count: 16
Power-On Hours: 3513
Power Cycle Count: 16
Load Cycle Count: 165
Device: sda
Controller: 0
Channel: 1
Model: ST2000NM0033-9ZM175
Serial: <REMOVED BY MODERATOR>
Firmware: SN03
Class: SATA
RPM: 7200
Sectors: 3907029168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e361280
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 42
Start/Stop Count: 16
Power-On Hours: 3513
Power Cycle Count: 16
Load Cycle Count: 163
Device: sdd
Controller: 0
Channel: 2
Model: ST2000NM0033-9ZM175
Serial: <REMOVED BY MODERATOR>
Firmware: SN03
Class: SATA
RPM: 7200
Sectors: 3907029168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e361280
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 42
Start/Stop Count: 16
Power-On Hours: 3513
Power Cycle Count: 16
Load Cycle Count: 165
Device: sdc
Controller: 0
Channel: 3
Model: ST2000NM0033-9ZM175
Serial: <REMOVED BY MODERATOR>
Firmware: SN03
Class: SATA
RPM: 7200
Sectors: 3907029168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e361280
Health Data:
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
End-to-End Errors: 0
Command Timeouts: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 39
Start/Stop Count: 16
Power-On Hours: 3513
Power Cycle Count: 16
Load Cycle Count: 164 - There's a weird thing in system logs - massive occurence of messages like that:
[Sun Mar 1 15:30:16 2015] vfs_writev() returned -28
Does it mean that device has problems writing information to disks? - Can you send me your logs (see the sending logs link in my sig)?
What firmware version are you running?
Do you have bitrot protection or snapshots enabled?
Are your LUNs thin or thick?
Do you have Sync Writes enabled/disabled?
If your problem is urgent you may wish to call support. Note that considering when you purchased the device and that it is the weekend, you would need to purchase a contract. - Hi MDGM :) Glad you're here. I've sent you the logs already.
I am running 6.2.2, applied update yesterday (in hope that it will fix the problem). It was running 6.1.7 (?) previously, there was no bitrot checkbox (as far as I can remember). When I applied 6.2.2 two out of three LUNs have bitrot (and I cannot uncheck the box).
So ,three LUNS:
1. Files (no bitrot, thick, sync writes allowed) - 3Tb
2. Exchange#1 - 1Tb, thin, bitrot enabled - can not be disabled, sync writes allowed
3. Exchange#2 - 1Tb, thin, bitrot enabled - can not be disabled, sync writes allowed - It seems that the device itself feels bad: I can't create LUNs thoug there's free disk space, folders for NFS are also not being created with error pre_proc_add_share failed..
- The space on your volume is fully allocated.
Do you have a backup?
You could perhaps try deleting an old snapshot. If that works you may then need to run a balance on your data volume. - Weird. What took you to this conclusion? Interface shows that ~1Tb is available for allocation. Is it a bug?
However, this would be an explanation..
I can't delete any snapshot, web-interface throws an error. - This is not a bug. Volume maintenance can be used to help minimises the chances of this happening.
Label: '0e361280:data' uuid: f9a5c388-0cd7-45c6-a260-fd9bea9af7eb
Total devices 1 FS bytes used 4.29TiB
devid 1 size 5.44TiB used 5.44TiB path /dev/md127
Btrfs v3.17.3
=== filesystem /data ===
Data, single: total=5.44TiB, used=4.29TiB
System, DUP: total=8.00MiB, used=600.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=2.00GiB, used=1.50GiB
Metadata, single: total=8.00MiB, used=0.00B
There is no unallocated space that can be allocated to metadata. The Metadata DUP is full (0.5GB is reserved)
Do you have a backup? - I was able to copy critical info from it. Do you want me to reset it to factory?
- That sounds like the answer here.
Thick LUNs with no bitrot would be what you want. Disabling sync writes may help with performance.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
