View Single Post
Unread 09-17-2006, 03:07 AM   #1
radio
Cooling Neophyte
 
radio's Avatar
 
Join Date: Aug 2006
Location: central US
Posts: 67
Default Rebuild error FSCK fatal error = 8

I put the Snap 4000 (Server v4.0.860) with 4 320Gb in a RAID 5 configuration into production and started copying files to it tonight. There was a thunderstorm tonight, and I gather the power went out because when I went in the Snap was powered off. I guess the UPS is shot.

Disk status included "Error: Unable to allocate memory"


Here is the recent log:

I System Initialization : Initialization Complete! Memory to be released: 30450768 bytes. System 9/17/2006 2:03:23 AM
E File System Check : FSCK fatal error = 8 Disk 60000
RAID 5 9/17/2006 2:03:23 AM
E File System Check : Failed to allocate 10930276 bytes for update bitmap!!! Disk 60000
RAID 5 9/17/2006 2:03:23 AM
W File System Check : partition is NOT clean. Disk 60000
RAID 5 9/17/2006 2:03:22 AM
I File System Check : Executing fsck /dev/rraid0 /force /fix /fixfatal Disk 60000
RAID 5 9/17/2006 2:03:22 AM
I File System : Opened FDB for device 0x1000E Disk (Priv) 9/17/2006 2:03:22 AM
I File System Check : partition is clean. Disk (Priv) 9/17/2006 2:03:22 AM
I File System Check : Executing fsck /dev/ride1g /fix /fixfatal Disk (Priv) 9/17/2006 2:03:22 AM
I File System : Opened FDB for device 0x10006 Disk (Priv) 9/17/2006 2:03:22 AM
I File System Check : partition is clean. Disk (Priv) 9/17/2006 2:03:22 AM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 9/17/2006 2:03:22 AM
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:35
Boot Count: 29 System 9/17/2006 2:03:17 AM
I System Shutdown : In Progress... System 9/17/2006 2:02:38 AM
I System Shutdown : in 3 seconds System 9/17/2006 2:02:35 AM
I System Initialization : Initialization Complete! Memory to be released: 30450768 bytes. System 9/17/2006 2:00:45 AM
E File System Check : FSCK fatal error = 8 Disk 60000
RAID 5 9/17/2006 2:00:45 AM
E File System Check : Failed to allocate 10930276 bytes for update bitmap!!! Disk 60000

RAID 5 9/17/2006 2:00:45 AM
W File System Check : partition is NOT clean. Disk 60000
RAID 5 9/17/2006 2:00:44 AM
I File System Check : Executing fsck /dev/rraid0 /force /fix /fixfatal Disk 60000
RAID 5 9/17/2006 2:00:44 AM


My first guess is not enought memory, so -

Command: debug memory

Total System Physical Memory: 67108864
File System Memory Allocated: 37160400
Memory To be Written: 0
Memory On Loan: 0
Loan Count: 0
Heap Memory: 32117904
Memory In Use: 31111168
Objects Allocated: 23
Communication Memory Allocated: 1524152
Memory In Use: 465908
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 16044
Handles Allocated:4679
Handles In Use: 358
SDB Volatile Memory Allocated: 98304
Memory In Use: 192
Handles Allocated: 11705
Handles In Use: 7


Looks like 64M is not enough to rebuild large disks.

Questions:

Does the wisdom here on Procooling agree with me? Is this clearly a ram problem?
Yes-> Where can I get the specs on the ram I need?
No -> Anything else I can try?

Why could I build the array in the first place, but not allocate the memory for the bitmap now?

I tried to find the FAQ section on procooling, but couldn't. Either it's really late, and I'm braindead or it was replaced by the WIKI. I was sure there was info in the FAQ that's not in the WIKI.
radio is offline   Reply With Quote