Quantum Snap Server M4100 fsck=27

[nevniv]

Hey all,

I'm having a problem with my snap server (see title for make). I'm not too familiar with snap servers and we don't seem to have a manual handy. I couldn't find one on this site; just a data/information sheet. Could someone direct me to a manual or let me know what the heck is going on with my server.

Here's what's wrong:

Nobody rebooted it and out of the blue the disks went offline. I power cycled it and that didn't help, so I logged into it..

RAID5 - Large data protection disk
Error. Fatal error during disk check.
View the disk log for details.
Total MB 85gig, Free MB Unknown

Message Source Date Time
E File System Check : FSCK fatal error = 27 Disk 60000 7/21/2009 12:01:44 PM
E File System Check : Partially allocated inode I=137533 Disk 60000 7/21/2009 12:01:44 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 7/21/2009 12:01:35 PM
W File System Check : partition is NOT clean. Disk 60000 7/21/2009 12:01:34 PM
I File System Check : Executing fsck /dev/rraid0 /force /fix Disk 60000 7/21/2009 12:01:34 PM
E File System Check : FSCK fatal error = 27 Disk 60000 7/21/2009 11:57:07 AM
E File System Check : Partially allocated inode I=137533 Disk 60000 7/21/2009 11:57:07 AM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 7/21/2009 11:56:58 AM
W File System Check : partition is NOT clean. Disk 60000 7/21/2009 11:56:57 AM
I File System Check : Executing fsck /dev/rraid0 /force /fix Disk 60000 7/21/2009 11:56:57 AM
E File System Check : FSCK fatal error = 27 Disk 60000 7/21/2009 9:33:45 AM
E File System Check : Partially allocated inode I=137533 Disk 60000 7/21/2009 9:33:45 AM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 7/21/2009 9:33:36 AM
W File System Check : partition is NOT clean. Disk 60000 7/21/2009 9:33:35 AM
I File System Check : Executing fsck /dev/rraid0 /fix Disk 60000 7/21/2009 9:33:35 AM
E File System Check : FSCK fatal error = 27 Disk 60000 7/20/2009 3:45:21 PM
E File System Check : Partially allocated inode I=137533 Disk 60000 7/20/2009 3:45:21 PM
E File System Check : Partially allocated inode I=31494 Disk 60000 7/20/2009 3:45:14 PM
E File System Check : Partially allocated inode I=31493 Disk 60000 7/20/2009 3:45:14 PM
E File System Check : Partially allocated inode I=31492 Disk 60000 7/20/2009 3:45:14 PM
E File System Check : Partially allocated inode I=6207 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6206 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6205 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6204 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6203 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6202 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6201 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6200 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6199 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6198 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6197 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6196 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6195 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6194 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6193 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6192 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6191 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6190 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6189 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6188 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6187 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6186 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6185 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6184 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6183 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6182 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6181 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6180 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6179 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6178 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6177 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6176 Disk 60000 7/20/2009 3:45:13 PM
E File System Check : Partially allocated inode I=6175 Disk 60000 7/20/2009 3:45:13 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 7/20/2009 3:45:12 PM
W File System Check : partition is NOT clean. Disk 60000 7/20/2009 3:45:12 PM
I File System Check : Executing fsck /dev/rraid0 /fix Disk 60000 7/20/2009 3:45:12 PM

I tried to run a repair twice today to no avail. Is my RAID degraded, or flat out shot to shit?

Thanks in advance if you can tell me, or if you know where I can get the manual and figure it out for myself.

[blue68f100]

You are have a HD problem. One of the LED's on the front panel should indicate which drive. Look through the log files and see if it indictes which HD is bad.

From debug try
in de


Read the FAQ's it may help.
I would recommend running SpinRite on all of the HDs. It does require you to remove the HD and install in a PC (With NO Other HD Installed). Spinrite can do a lot of repairs. If a Windows OS sees the snap hd it you wll loose all data on it, the reason for removing all HD's except the one being tested.

[nevniv]

First of all, thanks you for replying

All of the disk LEDs are blank. When it boots up they light up in sequence and then they go out. I thought maybe it is related to something I saw in the FAQ earlier:

"HW versions 1 & 2 have a problem on reporting failed drives, and require a cable modification."

I could be wrong, of course.

Since the log said Disk 60000, wouldn't that mean Disk 1? Disk 2 = 60008, Disk 3 = 60010, etc.

To worsen the situation, I thought I'd clean the snap server since it's a paper weight for now anyway. I unplugged it, cleaned the inside, and re-racked it and now I'm having trouble seeing it on the network I'm having a bad week! When it boots up the drive lights blink in sequence, then after a few seconds everything seems to sporadically blink and that is when I can ping the server. After a few seconds of the weird blinking, I can't ping the box and it goes back to a steady link light but unlit net light. So I have to figure this mess out before I can diagnose the drives.

Anyway, thank you again for your help. I'll let you know what happens.

[blue68f100]

Sounds like the drive order changed.

On a 4 drive snapOS HD are 10000, 10008, 10010, 10018. 40000 = raid 0 share, 50000 is Raid1 and 60000 = Raid5

If you have assist see if it sees the share. Is the Link LED solid? if not it's not seeing the router/switch. Check the cable, replace cable, move to a different port.

[Terry Kennedy]

Originally Posted by nevniv

I'm having a problem with my snap server (see title for make). I'm not too familiar with snap servers and we don't seem to have a manual handy. I couldn't find one on this site; just a data/information sheet. Could someone direct me to a manual or let me know what the heck is going on with my server.

Here's a couple of Overland Storage links for useful manuals:
Snap Server 4100 Field Service Guide
Snap Server Administrator Guide

Here's what's wrong:
Nobody rebooted it and out of the blue the disks went offline. I power cycled it and that didn't help, so I logged into it..

First thing to check is that all the LEDs are doing the appropriate thing. All of D1 through D4 should be blinking green (in no set pattern) during activity. If one of them is yellow, that would indicate a failure of the associated drive. If that's the case, make sure that you replace the correct drive - if the server sees that a second drive has changed, it will become upset and not want to rebuild the RAID set.

RAID5 - Large data protection disk
Error. Fatal error during disk check.
View the disk log for details.
Total MB 85gig, Free MB Unknown

85GB is pretty small for a RAID 5 set of 4 drives - that server was likely built with 30GB drives, most likely Quantum Fireballs.

In a server of that age, the installed RAM is pretty tiny as well. I've seen 4100's with 64GB. The maximum limit is 256MB and you need a low-profile part if you expect to get the cover back on. It is garden-variety PC100 memory, no parity.

I mention this because once your system is to the state where it can actually perform the filesystem check, if there isn't enough free memory it will default to a swap-based check, which will take approximately forever.

Some commands to try, which should give you more info to post back here: First, go to http://your-snap-name/config/debug which will give you a command box.

Commands to try:

in ver       : report hardware and OS version
in dev       : report device info
deb mem      : report on installed / used memory
in lo t      : report error log from this boot
in lo p      : report permanent error log from this boot; use << at top to step back

None of those should damage anything. Report back and we'll see where to go from there.

[nevniv]

Thanks for the reply, Terry. I know it's been a while, I have been messing with it.

I got my hands on a copy of Spinrite v6 and I ran it on all four drives. I picked level 4. It took about 7 hours.

You're right, the drives are ~30GB. I just checked the cache memory, 64MB!

Disk Status says "Checking 5% Complete" and it stays there for a long time.

Below are the commands you asked me to run. At the very end is what the event log says now

08/05/2009 14:40:12 Command: in ver

Product: 2 - "Laser/Spinnaker: 4 drive IDE" - Platform Bytes "2.2.1"
Server-3.4.803, Build Date: Jan 15 2003 18:04:19
This is the NON-Debug executable, and was built by KEVIN
You are logged in as user ROOT (local)

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

08/05/2009 14:40:31 Command: in dev

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 26872 Private Mounted
Label:Private Contains system files only
Unique Id: 0x36334AE17794E367 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): 29316608 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 25840 Private Mounted
Label:Private Contains system files only
Unique Id: 0x4A96A68C380941B0 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): 29316608 Fixed

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


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


08/05/2009 14:40:48 Command: deb mem

Total System Physical Memory: 67108864
File System Memory Allocated: 6709632
Memory To be Written: 0
Memory On Loan: 0
Loan Count: 0
Heap Memory: 33310448
Memory In Use: 23889248
Objects Allocated: 17
Communication Memory Allocated: 1524152
Memory In Use: 464236
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 16364
Handles Allocated:4679
Handles In Use: 371
SDB Volatile Memory Allocated: 98304
Memory In Use: 192
Handles Allocated: 11705
Handles In Use: 7
System has been configured!

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


08/05/2009 14:41:08 Command: in lo t

Requested: Log=Temporary, Boot=N/A Direction=Fwd Types=All Source=All

08/05/2009 14:38:26 61 S SYS | System Initialization : Server v3.4.803
Build Date: Jan 15 2003 18:04:19
Boot Count: 61
08/05/2009 14:38:26 61 D SYS | Executable built by KEVIN
08/05/2009 14:38:26 61 D SYS | Hardware platform:2.2.1 Model:2 (64 MBytes) S/N:504831
08/05/2009 14:38:27 61 D SYS | ETH: Reset- Eaddr set to 00 C0 B6 07 B3 FF
08/05/2009 14:38:27 61 D SYS | Update IP...
08/05/2009 14:38:27 61 I NET | INIT: Setting IP address to 192.168.2.152
08/05/2009 14:38:27 61 D SYS | Update IP...
08/05/2009 14:38:27 61 D SYS | Initial file system BIO cache size is 6709632 bytes, 808 buffers
08/05/2009 14:38:27 61 D SYS | DISK: Initial ARBs: 808 Memory: 132512
08/05/2009 14:38:27 61 D SYS | Code Page set to 437
08/05/2009 14:38:27 61 D SYS | QDL System is DISABLED
08/05/2009 14:38:27 61 D SYS | Disk cache flush enabled
08/05/2009 14:38:27 61 D SYS | SNMP agent enabled for ReadWrite.
08/05/2009 14:38:27 61 D SYS | AFP: not started
08/05/2009 14:38:27 61 D SYS | 'FTPD' started.
08/05/2009 14:38:27 61 D SYS | Update WorkGroup...
08/05/2009 14:38:32 61 D SYS | Intf: 0, dev: 0: Model: QUANTUM FIREBALLP LM30
08/05/2009 14:38:32 61 D SYS | Firmware Rev: A35.0700 Serial #: 186021733157
08/05/2009 14:38:32 61 D SYS | Intf: 1, dev: 0: Model: QUANTUM FIREBALLP LM30
08/05/2009 14:38:32 61 D SYS | Firmware Rev: A35.0700 Serial #: 186021733185
08/05/2009 14:38:33 61 D SYS | Intf: 2, dev: 0: Model: QUANTUM FIREBALLP LM30
08/05/2009 14:38:33 61 D SYS | Firmware Rev: A35.0700 Serial #: 186021733142
08/05/2009 14:38:33 61 D SYS | Intf: 3, dev: 0: Model: QUANTUM FIREBALLP LM30
08/05/2009 14:38:33 61 D SYS | Firmware Rev: A35.0700 Serial #: 186021733148
08/05/2009 14:38:33 61 D SYS | RAID5Initialize: creating 16 worker threads
08/05/2009 14:38:33 61 D SYS | RAID5InitializeCache: allocated cache of 16336KB
08/05/2009 14:38:33 61 I L00 | File System Check : Executing fsck /dev/ride0g /fix /fixfatal
08/05/2009 14:38:33 61 I L00 | File System Check : partition is clean.
08/05/2009 14:38:33 61 D SYS | Update FDB 0x10006...
08/05/2009 14:38:33 61 I L00 | File System : Opened FDB for device 0x10006
08/05/2009 14:38:33 61 D SYS | Scheduled ACL Set and Propagate at /priv/os_private for FDB_ID_12
08/05/2009 14:38:33 61 I L00 | File System Check : Executing fsck /dev/ride1g /fix /fixfatal
08/05/2009 14:38:33 61 D SYS | Propagate on /priv/os_private: Success - 8 files, 0 dirs; Errors - 0 files, 0 dirs
08/05/2009 14:38:33 61 I L00 | File System Check : partition is clean.
08/05/2009 14:38:33 61 D SYS | No FDB, or FDB corrupt. Reverting to shadow FDB
08/05/2009 14:38:33 61 D SYS | Reverting to Default FDB: FDB missing or invalid
08/05/2009 14:38:33 61 D SYS | Reverting to Default FDB: Quotas have been turned Off
08/05/2009 14:38:33 61 I L01 | File System Check : Executing fsck /dev/rraid0 /force /fix /fixfatal
08/05/2009 14:38:33 61 W L01 | File System Check : partition is NOT clean.
08/05/2009 14:38:33 61 D SYS | Fsck - Using primary superblock
08/05/2009 14:38:34 61 D SYS | 23336048 bytes pre-allocated
08/05/2009 14:38:34 61 D SYS | Memory allocation for i-node cache: 90% of free RAM
08/05/2009 14:38:34 61 D L01 | File System Check : Failed to allocate 16350722 bytes for rcd_lncntp!!!
08/05/2009 14:38:34 61 D SYS | -- Swap-based Fsck --
08/05/2009 14:38:34 61 D SYS | 4483 i-node cache blocks, cache hash table: 1531 entries
08/05/2009 14:38:34 61 D SYS | 256 i-nodes per generic cache block
08/05/2009 14:38:34 61 D SYS | 170 i-nodes per directory cache block
08/05/2009 14:38:34 61 I L01 | File System Check : ** Phase 1 - Check blocks and sizes
08/05/2009 14:39:43 61 D SMB | SMB : Becoming master browser for TECHCENTER

eventLogGetRecord() printed 49 records at 08/05/2009 14:41:08

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


08/05/2009 14:41:24 Command: in lo p

Requested: Log=Permanent Boot=<< 61 Direction=Fwd Types=All Source=All

eventLogGetRecord() failed: [5] at 08/05/2009 14:41:24

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


Event log;

I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 8/5/2009 2:38:34 PM
W File System Check : partition is NOT clean. Disk 60000 8/5/2009 2:38:33 PM
I File System Check : Executing fsck /dev/rraid0 /force /fix /fixfatal Disk 60000 8/5/2009 2:38:33 PM

Thanks for the help! It's much appreciated. I miss my data

[Terry Kennedy]

Originally Posted by nevniv

08/05/2009 14:38:33 61 I L01 | File System Check : Executing fsck /dev/rraid0 /force /fix /fixfatal
08/05/2009 14:38:33 61 W L01 | File System Check : partition is NOT clean.
08/05/2009 14:38:33 61 D SYS | Fsck - Using primary superblock
08/05/2009 14:38:34 61 D SYS | 23336048 bytes pre-allocated
08/05/2009 14:38:34 61 D SYS | Memory allocation for i-node cache: 90% of free RAM
08/05/2009 14:38:34 61 D L01 | File System Check : Failed to allocate 16350722 bytes for rcd_lncntp!!!
08/05/2009 14:38:34 61 D SYS | -- Swap-based Fsck --
08/05/2009 14:38:34 61 D SYS | 4483 i-node cache blocks, cache hash table: 1531 entries
08/05/2009 14:38:34 61 D SYS | 256 i-nodes per generic cache block
08/05/2009 14:38:34 61 D SYS | 170 i-nodes per directory cache block
08/05/2009 14:38:34 61 I L01 | File System Check : ** Phase 1 - Check blocks

That's the swap-based fsck I mentioned earlier. Are the disk activity lights flashing at this point? Adding RAM would make the check run faster, but if the swap-based one errors out, then the fast one would as well.

Disk Status says "Checking 5% Complete" and it stays there for a long time.

In this case, I'd suggest installing a larger memory module. It is a generic PC100 part, no parity needed.

[nevniv]

I don't think they're flashing. After everything flashes during the initial powerup, I'm not sure they usually do blink. One of the sticky's here say that HW versions 1 and 2 require a cable modification to report a failed drive so I thought maybe the LEDs are just messed up. I don't know.

Unfortunately, the ethernet port is a little messed up. You have to hold the wire a certain way for the connection to be made, so I propped the cable up against something to try and hold it in place. It was working for a while and then I lost network connectivity again (someone probably moved it a little). I have to keep fiddling with it to try and get connected again. It's been about two days so hopefully it's at 10% by now, at least then I'd know it's doing something!

We just threw out a ton of memory a couple weeks ago, I'll have to see if there's anything left. Do you know if there's a max capacity for the slot?

[Terry Kennedy]

Originally Posted by nevniv

We just threw out a ton of memory a couple weeks ago, I'll have to see if there's anything left. Do you know if there's a max capacity for the slot?

The last time I tried it, a 512MB module was only recognized as 256MB but worked ok at that size. However, the cover couldn't be reinstalled as it wasn't a low-profile module.

[nevniv]

Wow! I found a 128mb stick from another snap server that was collecting dust. I put that in, and wow! It did the disk check in a matter of minutes. The drive is back up and running and it is "Rebuilding backup disk" now.

I can now access all the data on it (I'm making a backup on other storage as we speak just in case).

Thank you very much all of you for the help! I thought this data was long gone. Thank you!

[blue68f100]

If SpinRite hangs at 5% that is where the snap table is kept. Failure here, replace the HD.

[nevniv]

It was the snap server checking itself on bootup which was stuck at 5%. I believe Terry Kennedy was saying that happened because of the cache memory.

The SpinRite completed on all four of the drives. I don't think it found anything because the results didn't seem to show any errors if I was reading it correctly. The first page had entirely blue blocks.

Anywho, when I left it rebuilding Friday, I had access to all of the data. I just need to fiddle with the loose NIC and get it working long enough to get all of the data off and I'll be all set.

Thanks for following up

[Terry Kennedy]

Originally Posted by nevniv

It was the snap server checking itself on bootup which was stuck at 5%. I believe Terry Kennedy was saying that happened because of the cache memory.

Anywho, when I left it rebuilding Friday, I had access to all of the data. I just need to fiddle with the loose NIC and get it working long enough to get all of the data off and I'll be all set.

If you intend to use the server after you back it up, I could replace the wonky Ethernet connector, install the ECO that will let large drives work without corruption, and put a 256MB (max size) memory module in there. I'd also check and replace (if needed) the case, power supply, and CPU fans. I'd also install the latest OS that is freely available from Overland.

I'd do that for free if you cover the shipping both ways (I'm just outside New York City) plus some beer money for my pit crew (see below). I also have rack ears, replacement front bezels (if yours is cracked), etc. for reasonable prices.

This would probably need to wait until sometime in early October when the race season winds down - my crew and I travel around the country with my race car, and the big end-of-season race series is 4 days in mid-September, followed by the telling of war stories, and everybody eventually getting back home (I drive the race car between events myself - had a bad experience a couple years ago when the truck carrying it broke down and then got hijacked on the return trip). It'll be about 1500 miles back home, not including any detouring I plan to do along the way - out-of-the-way tracks at the end of the season can be loads of fun.

[nevniv]

I was thinking that we might end up using it still, but now I'm not so sure.

I rebooted it because it lost network connectivity again while I was getting the data off. I didn't get even 10% of the data before it lost connection.

I rebooted it and now it fails during the self-check again. This time it's error = 34 instead of error = 27


Message Source Date Time
E File System Check : FSCK fatal error = 34 Disk 60000 8/10/2009 12:47:08 PM
E File System Check : Inode = 182787 - Bad indirect addr[1]: 573486 Disk 60000 8/10/2009 12:47:08 PM
E File System Check : Partially allocated inode I=147485 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147484 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147483 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147482 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147481 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147480 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147479 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147478 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147477 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147476 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147475 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147474 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147473 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147472 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147471 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147470 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147469 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147468 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147467 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147466 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147465 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147464 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147463 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147462 Disk 60000 8/10/2009 12:47:06 PM
E File System Check : Partially allocated inode I=147461 Disk 60000 8/10/2009 12:47:06 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 60000 8/10/2009 12:46:57 PM
W File System Check : partition is NOT clean. Disk 60000 8/10/2009 12:46:56 PM
I File System Check : Executing fsck /dev/rraid0 /fix Disk 60000 8/10/2009 12:46:56 PM


I'm going to buy some dynamite. BANG!!!!!


edit: I spoke to management. They might be interested in your offer but I'm not sure yet. Have to give them details and I probably have to get the data back lol