Hi Linux Pepole, I have a debian box (sarge (I think)) with a 2.6.8-3.386 kernel. I recently upgraded to 2.6.18 to get checkarray working in Mdadm (it needs a kernel high than 2.6.15 to function) as there is not a lot of point in having a raid system if it doesn't keep an eye on itself :)
Anyhow well it went very wrong not 100% sure how, I'm running a highpoint 1640 with the 2.16 driver with 4 x WD 200 GB drives. Now when the system goes to mount the array it stats the array is corrupted. When I run FSCK I get this: fsck 1.37 (21-Mar-2005) Group descriptors look bad... trying backup blocks... Inode table for group 1842 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1843 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1844 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1845 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1846 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1847 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1848 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1849 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1850 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1851 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1852 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1853 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1854 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1855 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1856 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1857 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1858 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1859 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1860 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1861 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1862 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1863 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1864 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1865 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1866 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1867 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1870 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1871 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1872 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1873 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1874 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1875 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1876 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1877 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes Inode table for group 1878 is not in group. (block 0) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes And so on for at least another 200-300 blocks once it finishes it then does it first pass: /dev/md0 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Error allocating 512 contiguous block(s) in block group 1842 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1843 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1844 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1845 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1846 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1847 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1848 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1849 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1850 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1851 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1852 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1853 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1854 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1855 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1856 for inode table: Could not allocate block in ext2 filesystem Error allocating 512 contiguous block(s) in block group 1857 for inode table: Could not allocate block in ext2 filesystem Keeps going that way for all of the blocks. then i tgoes all the back to the start over and over (ininite loop). I can access the drives using debugfs. but when i try to "cd" into a directory it claims the directory is an inode not a directory. So, Any suggestion or ideas how to fix it? Would love to try and get some of the data off the drive. Thanks Heaps! Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
