
UNSOLVED
M
maddykrish
22 Posts
0
2603
June 6th, 2011 22:00
Data movers in reset state
Hi
The data movers are in reset state.
[root@Alinta_Tal_NAS nasadmin]# /nas/sbin/getreason
10 - slot_0 primary control station
0 - slot_2 reset
0 - slot_3 reset
All the file systems are in mounted state. No impact.
[root@Alinta_Tal_NAS nasadmin]# /nasmcd/sbin/getreason -e
10 - slot_0 primary control station
0 - slot_2 reset (Post Code = 0x61 ; Mid Code = 0x80 ; Blade Code = 0x2c)
0 - slot_3 reset (Post Code = 0x61 ; Mid Code = 0x80 ; Blade Code = 0x2c)
NAs service are up and running fine.
[root@Alinta_Tal_NAS nasadmin]# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 2063536 1415828 542884 73% /
/dev/hda1 31079 2748 26727 10% /boot
none 1033164 0 1033164 0% /dev/shm
/dev/nde1 1818352 804836 921144 47% /nbsnas
/dev/hda5 2063504 650744 1307940 34% /nas
/dev/ndf1 1818352 349088 1376892 21% /nas/var
/dev/nda1 136368 37828 98540 28% /nas/dos
Could anyone suggest is this a code bug ? NAS code is 5.5.29.1 . Model is NS 40G.
Thanks
Krishna Prasad.S
Responses (6)
Solutions (0)
gbarretoxx1
2 Intern
•
366 Posts
717
0
Posted June 7th, 2011 20:00
Hi,
This seems to be something related to the Control Station monitoring part.
Try to reboot the Control Station, and wait around 15 minutes.
Anyway, this NAS code must be upgraded ASAP.
Gustavo Barreto.
Reply Rainer_EMC
6 Operator
•
8645 Posts
717
0
Posted July 7th, 2011 09:00
did you fix it? how?
Rainer
Reply

Peter_EMC
674 Posts
717
0
Posted June 6th, 2011 23:00
Hmm,
5.5.29.1 was released in April 2007.
5.5.x.x. was end of support on Dec 31th 2010.
It sound like a bug.
Please upgrade your system to minimum NAS 5.6 or 6.0
Regards
Peter