File System Check : FSCK fatal error = 39
 

Any one have any idea what this means? File System Check : FSCK fatal error = 39
I get this no matter what i do, no matter how many drives are in the snap 4100,

Log for disk: Drive2 - Single disk

Severity legend: I=Information, W=Warning, E=Error, F=Fatal Error, S=Server Startup
Message Source Date Time
E File System Check : FSCK fatal error = 39 Disk 10008 2/22/2006 1:18:28 PM
E File System Check : Bad state 7 for inode I=370448 Disk 10008 2/22/2006 1:18:28 PM
W File System Check : Summary information bad (Salvaged) Disk 10008 2/22/2006 1:18:21 PM
W File System Check : Blk(s) missing in bit maps (Salvaged) Disk 10008 2/22/2006 1:18:21 PM
W File System Check : Free blk count(s) wrong in superblk (Salvaged) Disk 10008 2/22/2006 1:18:21 PM

Re: File System Check : FSCK fatal error = 39
 

These errors are on one drive labled 10008 which is drive 2. Are you runing a raid 5 array. Salvage: I think is in reference to an array that may be trying to rebuild or recover, with a bad drive. And may not be able to find a hot spare.

Can you give me more info on your configuration. OS, HW, BIOS, ram, weather JVM is running.
Also look at the drives in disk utilities. It may give some insight.
If you are running RAID 5 all drives in the array are suppose to be within 2-3% capacity.

Re: File System Check : FSCK fatal error = 39
 

Right now im in the process of rebuilding the raid 5 array using 40 gig drives to see if that works. I have the feeling it just doesnt like the matched (4) 80 gig WD800 i had in it.

Software 4.4.803 (us) hardware 2.2.1 Bios 2.4.437 ram 64 megs

At the time of the original posting i only had 2 drives in it as JBOD.

Right now the snap is rebuilding the backup disk. total capacity is 112,089 as expected. when this is done i can try anything.

Re: File System Check : FSCK fatal error = 39
 

There has been some drives that the snaps don't like, in particularly EIDE drive. Seagates, Hitachi seams to be the only drives that have not had some kind of problem. Maxtor's seams to have the most due to their EIDE interface. WD have been random. Your max is 120gig, due to the fact that the 4100 does not support LBA48bit.

Re: File System Check : FSCK fatal error = 39
 

So do we know what an error 39 is for sure? I am going to cough it up to the face that it just didnt like the WD800BB's. Funny though i think my other snap is using the same drives. And I know My Snap 4400 has WD2000JB's in it.

The Raid is still rebuilding ive been down this road before. I'll have to transfer data to it to make sure its stable. Ive had it blow up before after all looked good. Transfered about 40 gigs then BLAMO. cracked Raid.

Sure could use a guardian os my Current OS Version: 2.6.050 (Snap 4400)

Re: File System Check : FSCK fatal error = 39
 

Just looked up the WD800BB drive, it's an EIDE drive. They have been know to cause problems. The 4400 has newer/different HD controllers.

Re: File System Check : FSCK fatal error = 39
 

Im going to have to open up the other snap and see whats in it..

Re: File System Check : FSCK fatal error = 39
 

What do you know about the 4400's? What is the max HD size that they can handle?
Model=4400
Software=2.6.050
Hardware=5.0.0
Bios=3A01
Framework=1.2
VM=1.4.1_01-b01

Re: File System Check : FSCK fatal error = 39
 

The 4400 use the Guardian OS? as appose to Snap OS, 10/100/1000 gig ports (2), option expansion port iSCSI?, capacity from 480 to 720gig, Drives are suppose to be hot swapable. Standard ram was 256-512 depending on capacity. Don't know if os is stored in flashram. Never have messed with one or seen one.

These support large disk, max I don't think that is a problem, since they shipped units 4 x 160gigs.

I think this was SnapAppliance 1st attempt at making a unit that was field servicable.

It also uses a 1.26ghz PIII

Re: File System Check : FSCK fatal error = 39
 

Well lo and behold i managed to pull my other 4100 out of the rack/closet, opened it up and its loaded with WD800 born on date 3 months older than the ones sitting on my desk. Same drives. Interesting the server numbers are less then 1500 apart. And all rev numbers are pretty much the same between the 2 boxes. I may have to try this process all over again.

Re: File System Check : FSCK fatal error = 39
 

Snap 4100 resurected with Maxtor Diamond 10 6L200P0 200gig PATA133 HD's

Re: File System Check : FSCK fatal error = 39
 

As lone as the capacty is within 2-3% they should work. There are utilities out there if you need to adjust the capacty.

It's allway nice to have an happy ending.