Snap 4100 Crash a little help needed

[webboy]

disk log errors:
E File System Check : FSCK fatal error = 26 Disk 60000 5/31/2007 10:38:42 AM
E File System Check : Bad state 0 for inode I=2058380 Disk 60000 5/31/2007 10:38:42 AM
W File System Check : INode 284164 is missing a back link to its parent inode 284160 Disk 60000 5/31/2007 10:38:29 AM
I File System Check : ** Phase 2 - Check pathnames Disk 60000 5/31/2007 10:38:00 AM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 60000 5/31/2007 10:38:00 AM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 5/31/2007 10:18:19 AM
W File System Check : partition is NOT clean. Disk 60000 5/31/2007 10:18:18 AM
I File System Check : Executing fsck /dev/rraid0 /force /fix /fixfatal Disk 60000 5/31/2007 10:18:18 AM
E File System Check : FSCK fatal error = 39 Disk 60000 5/31/2007 10:08:37 AM
E File System Check : Bad state 0 for inode I=2027660 Disk 60000 5/31/2007 10:08:37 AM
I File System Check : ** Phase 4 - Check reference counts Disk 60000 5/31/2007 10:08:21 AM
I File System Check : ** Phase 3 - Check connectivity Disk 60000 5/31/2007 10:08:21 AM
W File System Check : INode 7411200 is missing a back link to its parent inode 7409664 Disk 60000 5/31/2007 10:08:21 AM
W File System Check : INode 284164 is missing a back link to its parent inode 284160 Disk 60000 5/31/2007 10:07:25 AM
I File System Check : ** Phase 2 - Check pathnames Disk 60000 5/31/2007 10:06:56 AM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 60000 5/31/2007 10:06:56 AM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 5/31/2007 9:47:17 AM
W File System Check : partition is NOT clean. Disk 60000 5/31/2007 9:47:16 AM
I File System Check : Executing fsck /dev/rraid0 /fix Disk 60000 5/31/2007 9:47:16 AM


Model 4000 series
Software 3.4.803 (US)
Hardware 2.2.1
BIOS 2.4.437

[re3dyb0y]

Whats the problem?

Its crashed so its checking the disks are all ok

[webboy]

It never finishes 5th reboot


RAID5 - Large data protection disk
Error. Fatal error during disk check.
View the disk log for details.

details in first post

05/31/2007 13:09:33 Command: info devices

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22472 Private Mounted
Label:Private Contains system files only
Unique Id: 0x404300ED6EF1E890 Mount: /priv Index: 12 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 78150656 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 22216 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2C171FB92223C14C Mount: /pri2 Index: 13 Order: 1
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 78150656 Fixed

Logical Device: 60000 Position: 1 RAID Size (KB): 233166552 Free (KB): 0 Public Unmounted
Label:RAID5 Large data protection disk
Unique Id: 0x03F0E3F63C062D7F Mount: /0 Index: 0 Order: 255
Partition: 10000 Physical: 10007 R 60000 Size (KB): 77722184 Starting Blk: 53431 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 78150656 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 77722184 Starting Blk: 53431 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 78150656 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 77722184 Starting Blk: 53431 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 78150656 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 77722184 Starting Blk: 53431 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 78150656 Fixed


------------
Command executed without error.

[blue68f100]

It sound like you have a drive failing. Or your MB has not had the modifications done.

Look at the complete log (show all). It should indicate which drive is failing.

If you have SpinRite, use to to check the drives.

[Phoenix32]

Originally Posted by blue68f100

Or your MB has not had the modifications done.

This was my first thought....

[webboy]

Looks like Mod was done on this snap. FB1 has little diodes with a jumper attached.

CPU fan is/was not spinning at all. Rebooting to see if it will repair the raid.

Will post back later

[blue68f100]

The fan is temp controlled, so it should cycle.

[Phoenix32]

Originally Posted by webboy

Looks like Mod was done on this snap. FB1 has little diodes with a jumper attached.

CPU fan is/was not spinning at all. Rebooting to see if it will repair the raid.

They are resistors, but sounds like the mod is there...

The CPU fan is temp controlled, and the 4100 seems to only turn on when the CPU gets VERY hot...

Sounds like intermitent drive failure (or even multiple). Or, if in C/S, you may be getting errors due to speed setting issues...

[webboy]

well i managed to drop drive 2 out of the raid thinking that was the one going bad and still no luck it repairs/rebuilds the array and then crashes somewhere around 51%.