| View previous topic :: View next topic |
| Author |
Message |
vmatherly
n00b
Joined: 21 May 2005
Posts: 41
Location: New England, USA
|
 Posted: Tue Oct 09, 2007 8:13 pm Post subject: Raid Array Crash |
 |
|
Hello All,
I had a power outage that killed my 400GB Raid 0 Array. I can't seem to get it back online now. Its a Compaq SA5300 Controller connected to an external shelf housing 14 36GB 10K SCSI drives. I was using ext3.
Here is the output of fsck:
| Code: |
e2fsck 1.39 (29-May-2006)
/dev/ida/c0d0p1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 55181731, block 10, offset 3076: directory corrupted
Salvage? yes
Entry 'x^A^S^@^B^@^B^@^D^A^O^@^@^A^S^@x^A^S' in ??? (55181731) has rec_len of 1024, should be 1028.
Fix? yes
Directory inode 55980017, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (55980017) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54834878, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54834878) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54831366, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54831366) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54836481, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54836481) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54828217, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54828217) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54824842, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54824842) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54831524, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54831524) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54826323, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54826323) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 54826318, block 0, offset 3072: directory corrupted
Salvage? yes
Entry '^@^A^S^@x^A^S^@^B^@^B^@^H^A^O' in ??? (54826318) has rec_len of 1280, should be 1536.
Fix? yes
Directory inode 56479943, block 0, offset 2952: directory corrupted
Salvage? yes
Entry '^B^@^B^@^H^A^O^@^@^A^S^@x^A^S^@^B^@^B' in ??? (56479943) has rec_len of 1280, should be 1416.
Fix? yes
Directory inode 53777822, block 4, offset 3124: directory corrupted
Salvage? yes
Entry 'x^A^S^@^B^@^B^@^I^A^O^@^@^A^S^@x^A^S' in ??? (53777822) has rec_len of 1024, should be 1076.
Fix? yes
Pass 3: Checking directory connectivity
'..' in /lost+found/#54192040 (54192040) is <The NULL inode> (0), should be /lost+found (12).
Fix? yes
Couldn't fix parent of inode 54192040: Couldn't find parent directory entry
'..' in /lost+found/#54192168 (54192168) is <The NULL inode> (0), should be /lost+found (12).
Fix? yes
Couldn't fix parent of inode 54192168: Couldn't find parent directory entry
'..' in /lost+found/#54637581 (54637581) is <The NULL inode> (0), should be /lost+found (12).
Fix? yes
Couldn't fix parent of inode 54637581: Couldn't find parent directory entry
'..' in /lost+found/#55826601 (55826601) is <The NULL inode> (0), should be /lost+found (12).
Fix? yes
Couldn't fix parent of inode 55826601: Couldn't find parent directory entry
'..' in /lost+found/#55873696 (55873696) is <The NULL inode> (0), should be /lost+found (12).
Fix? yes
Couldn't fix parent of inode 55873696: Couldn't find parent directory entry
'..' in /lost+found/#56265464 (56265464) is <The NULL inode> (0), should be /lost+found (12).
Fix? yes
Couldn't fix parent of inode 56265464: Couldn't find parent directory entry
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/ida/c0d0p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/ida/c0d0p1: ********** WARNING: Filesystem still has errors **********
214647 inodes used (0%)
10073 non-contiguous inodes (4.7%)
# of inodes with ind/dind/tind blocks: 197245/192345/190689
19704835 blocks used (17%)
0 bad blocks
251 large files
15461 regular files
7782 directories
57437 character device files
67677 block device files
35500 fifos
9 links
0 symbolic links (0 fast symbolic links)
30781 sockets
--------
214647 files
|
Anyone have any suggestions as to how to fix this?
_________________
Victor Matherly
Wave Communications,Inc
www.wave-communications.com
wanna see why they call him animal? |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54852
Location: 56N 3W
|
| Posted: Tue Oct 09, 2007 8:36 pm Post subject: |
|
|
vmatherly,
It looks like your raid assembled properly or you would have a lot more errors than that.
Some of your data is lost but fsck has dome what it can. Mount the file system read only, if you can mount it at all and look round. You will find some of your recovered directories, files and file fragments in lost and found, where they will be named with their inode numbers.
Your file system is not consistant and must not be written on, you risk overwriting things. If it mounts read only, recover what you can then remake the file system from scratch.
fsck often makes the situation worse, not better. By allowing it to make changes to the filesystem, you have lost the opportunity to make images of the drives, so you have an 'undo' facility.
Power outs and raid0 are a bad combination. With 14 drives you increase your chances of problems by 14 times.
Invest in a UPs and a couple of 500G drives so you can have at least alternate backups.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
vmatherly
n00b
Joined: 21 May 2005
Posts: 41
Location: New England, USA
|
| Posted: Tue Oct 09, 2007 11:57 pm Post subject: |
|
|
Well I guess the good news for me is that almost everything important was backed up. Everything accept for my windows domain controller Vmware files (which I am in the process of replacing with a gentoo samba/ldap box). Is there an easier way to search through the lost and found directory. All that I have left of the drive is a huge amount of files and directories named after the inode numbers.
Thanks for the help!
_________________
Victor Matherly
Wave Communications,Inc
www.wave-communications.com
wanna see why they call him animal? |
|
| Back to top |
|
|
vmatherly
n00b
Joined: 21 May 2005
Posts: 41
Location: New England, USA
|
| Posted: Wed Oct 10, 2007 12:43 pm Post subject: Raid Array Crash [Solved] |
|
|
Ahh I do have real files in the lost and found directory! Found what I was looking for, Thanks for your help
_________________
Victor Matherly
Wave Communications,Inc
www.wave-communications.com
wanna see why they call him animal? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
