Snap server fatal errors
Snap 4100 server with fatal errors on a RAID5 (400GB of data) and that's not the bad part. Ok ready for this one?
On Sunday I shut this Snap server down and moved it to a diff rack. it would not power backup, I reseat as many parts as possable, still died so I go home to weep. On Monday morning still died, at 3:20pm the Snap powers up by it's self. So I start coping off 1 of 4 folders and leave for the evenning. On Tuesday morning it's died as a door knob again, again I reseat all parts and this time I put in a new CMOS battery thinking maybe the clock is broken and maybe my RAID5 does not know how to boot. NOTHING! it's still died as a knob. At 3:20 POW! again it powers back up by it's self. Now I start coping off two more folders and leave for the night. This morning (WED) it's died as a door knob again, now it's 3:20pm and sure enough it powers back up by it's self. I'm now coping off the last folder. Show below is the log I get when it is running. ANY SUGGESTIONS!
==========================
08/22/2007 3:24:47 ERROR File System Check : Bad state 0 for inode I=206935
==========================
The previous message occurred in the following context within the system log:
08/22/2007 3:24:47 INFORMATION System Initialization : Initialization Complete! Memory to be released: 29944224 bytes.
08/22/2007 3:24:47 ERROR File System Check : FSCK fatal error = 39
08/22/2007 3:24:47 ERROR File System Check : Bad state 0 for inode I=206935
08/22/2007 3:24:45 WARNING File System Check : Summary information bad (Salvaged)
08/22/2007 3:24:45 WARNING File System Check : Blk(s) missing in bit maps (Salvaged)
08/22/2007 3:24:45 WARNING File System Check : Free blk count(s) wrong in superblk (Salvaged)
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 5 - Check cylinder groups
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 4b - Check backlinks
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 4 - Check reference counts
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 3 - Check connectivity
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 2 - Check pathnames
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 1b - Rescan for more duplicate blocks
08/22/2007 3:20:45 INFORMATION SMB : Resolved IP address (192.168.1.26) for domain controller BAILEY.
08/22/2007 3:20:35 INFORMATION SMB : Located domain controller BAILEY via TCP/IP.
08/22/2007 3:20:25 INFORMATION DHCP/BOOTP: Setting IP address to 192.168.1.43
08/22/2007 3:20:21 INFORMATION File System Check : ** Phase 1 - Check blocks and sizes
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/ride3a /force /fix /fixfatal
08/22/2007 3:20:20 INFORMATION File System : Opened FDB for device 0x60000
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/rraid0 /fix
08/22/2007 3:20:20 INFORMATION File System : Opened FDB for device 0x1000E
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/ride1g /fix /fixfatal
08/22/2007 3:20:20 INFORMATION File System : Opened FDB for device 0x10006
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/ride0g /fix /fixfatal
08/22/2007 3:20:14 System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 11
On Sunday I shut this Snap server down and moved it to a diff rack. it would not power backup, I reseat as many parts as possable, still died so I go home to weep. On Monday morning still died, at 3:20pm the Snap powers up by it's self. So I start coping off 1 of 4 folders and leave for the evenning. On Tuesday morning it's died as a door knob again, again I reseat all parts and this time I put in a new CMOS battery thinking maybe the clock is broken and maybe my RAID5 does not know how to boot. NOTHING! it's still died as a knob. At 3:20 POW! again it powers back up by it's self. Now I start coping off two more folders and leave for the night. This morning (WED) it's died as a door knob again, now it's 3:20pm and sure enough it powers back up by it's self. I'm now coping off the last folder. Show below is the log I get when it is running. ANY SUGGESTIONS!
==========================
08/22/2007 3:24:47 ERROR File System Check : Bad state 0 for inode I=206935
==========================
The previous message occurred in the following context within the system log:
08/22/2007 3:24:47 INFORMATION System Initialization : Initialization Complete! Memory to be released: 29944224 bytes.
08/22/2007 3:24:47 ERROR File System Check : FSCK fatal error = 39
08/22/2007 3:24:47 ERROR File System Check : Bad state 0 for inode I=206935
08/22/2007 3:24:45 WARNING File System Check : Summary information bad (Salvaged)
08/22/2007 3:24:45 WARNING File System Check : Blk(s) missing in bit maps (Salvaged)
08/22/2007 3:24:45 WARNING File System Check : Free blk count(s) wrong in superblk (Salvaged)
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 5 - Check cylinder groups
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 4b - Check backlinks
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 4 - Check reference counts
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 3 - Check connectivity
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 2 - Check pathnames
08/22/2007 3:24:44 INFORMATION File System Check : ** Phase 1b - Rescan for more duplicate blocks
08/22/2007 3:20:45 INFORMATION SMB : Resolved IP address (192.168.1.26) for domain controller BAILEY.
08/22/2007 3:20:35 INFORMATION SMB : Located domain controller BAILEY via TCP/IP.
08/22/2007 3:20:25 INFORMATION DHCP/BOOTP: Setting IP address to 192.168.1.43
08/22/2007 3:20:21 INFORMATION File System Check : ** Phase 1 - Check blocks and sizes
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/ride3a /force /fix /fixfatal
08/22/2007 3:20:20 INFORMATION File System : Opened FDB for device 0x60000
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/rraid0 /fix
08/22/2007 3:20:20 INFORMATION File System : Opened FDB for device 0x1000E
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/ride1g /fix /fixfatal
08/22/2007 3:20:20 INFORMATION File System : Opened FDB for device 0x10006
08/22/2007 3:20:20 INFORMATION File System Check : partition is clean.
08/22/2007 3:20:20 INFORMATION File System Check : Executing fsck /dev/ride0g /fix /fixfatal
08/22/2007 3:20:14 System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 11
scrathcyboy
So summarize what you need answered in one sentence, 1-2 lines long.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the reply rid,
No one else has access to the server but myself. It's a backup server. I'll try swaping out the power supply since I do not find any scheduling/automated shutdown options. As for the error logs it seems that one of the drives maybe bad or maybe it's related to the power supply.
No one else has access to the server but myself. It's a backup server. I'll try swaping out the power supply since I do not find any scheduling/automated shutdown options. As for the error logs it seems that one of the drives maybe bad or maybe it's related to the power supply.
ASKER
Suspect power supply, I'll replace, reformat drives and replace drive 4 since it is bad. Create RAID5. I won't be able to get to this for a few weeks so I'm closing question now. Thanks