• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

Raid Abgestürzt, brauche Rat DRINGEND!!!!

bumbuminc

Newbie
Hi Leute,
bei mir ist bei meinem Server ein Raid ausgefallen, Netzteil schmierte ab und das Raid wurde gerade benutzt.
Folgendes sind die Daten:

Suse 10.3
Sata Software Raid mit
/dev/sdi1 465.7 GB ST3500641AS
/dev/sdh1 465.7 GB WDC-WD5000AAKS-0 auf /dev/md0
die sdi1 war völlig weg, hab sie dann neu mit der sdh1 synchronisiert:

Code:
Version : 01.00.03
  Creation Time : Tue Feb 12 19:48:38 2008
     Raid Level : raid1
     Array Size : 488383864 (465.76 GiB 500.11 GB)
  Used Dev Size : 976767728 (465.76 GiB 500.11 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Fri Apr  4 21:36:13 2008
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : 0
           UUID : a4335d0a:cd5e6b40:7058b481:7d236739
         Events : 302

    Number   Major   Minor   RaidDevice State
       0       8      113        0      active sync   /dev/sdh1
       1       8      129        1      active sync   /dev/sdi1

Dachte jetzt sei alles in Ordnung aber nein, ein fsck.reiserfs ergab ich sollte doch ein fsck.reiserfs --rebuild-tree /dev/md0 machen:

Code:
fsck.reiserfs --rebuild-tree /dev/md0
reiserfsck 3.6.19 (2003 www.namesys.com)

*************************************************************
** Do not  run  the  program  with  --rebuild-tree  unless **
** something is broken and MAKE A BACKUP  before using it. **
** If you have bad sectors on a drive  it is usually a bad **
** idea to continue using it. Then you probably should get **
** a working hard drive, copy the file system from the bad **
** drive  to the good one -- dd_rescue is  a good tool for **
** that -- and only then run this program.                 **
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will rebuild the filesystem (/dev/md0) tree
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Replaying journal: No transactions found
###########
reiserfsck --rebuild-tree started at Fri Apr  4 13:05:55 2008
###########

Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 95887759 blocks marked used
init_source_bitmap: Bitmap 0 (of 32768 bits) is wrong - mark all blocks [0 - 32768] as used
init_source_bitmap: Bitmap 1 (of 32768 bits) is wrong - mark all blocks [32768 - 65536] as used
init_source_bitmap: Bitmap 3 (of 32768 bits) is wrong - mark all blocks [98304 - 131072] as used
init_source_bitmap: Bitmap 5 (of 32768 bits) is wrong - mark all blocks [163840 - 196608] as used
init_source_bitmap: Bitmap 7 (of 32768 bits) is wrong - mark all blocks [229376 - 262144] as used
init_source_bitmap: Bitmap 9 (of 32768 bits) is wrong - mark all blocks [294912 - 327680] as used
init_source_bitmap: Bitmap 25 (of 32768 bits) is wrong - mark all blocks [819200 - 851968] as used
init_source_bitmap: Bitmap 27 (of 32768 bits) is wrong - mark all blocks [884736 - 917504] as used
init_source_bitmap: Bitmap 49 (of 32768 bits) is wrong - mark all blocks [1605632 - 1638400] as used
init_source_bitmap: Bitmap 81 (of 32768 bits) is wrong - mark all blocks [2654208 - 2686976] as used
init_source_bitmap: Bitmap 125 (of 32768 bits) is wrong - mark all blocks [4096000 - 4128768] as used
init_source_bitmap: Bitmap 243 (of 32768 bits) is wrong - mark all blocks [7962624 - 7995392] as used
init_source_bitmap: Bitmap 343 (of 32768 bits) is wrong - mark all blocks [11239424 - 11272192] as used
init_source_bitmap: Bitmap 625 (of 32768 bits) is wrong - mark all blocks [20480000 - 20512768] as used
init_source_bitmap: Bitmap 729 (of 32768 bits) is wrong - mark all blocks [23887872 - 23920640] as used
init_source_bitmap: Bitmap 2187 (of 32768 bits) is wrong - mark all blocks [71663616 - 71696384] as used
init_source_bitmap: Bitmap 2401 (of 32768 bits) is wrong - mark all blocks [78675968 - 78708736] as used
init_source_bitmap: Bitmap 3125 (of 32768 bits) is wrong - mark all blocks [102400000 - 102432768] as used
Skipping 11937 blocks (super block, journal, bitmaps) 96399375 blocks will be read
0%....20%....40%.                                                         left 0, 13960 /seccc
Could not find a hash in use. Using "r5"
Selected hash ("r5") does not match to the hash set in the super block (not set).
        "r5" hash is selected
Flushing..finished
        Read blocks (but not data blocks) 96399375
                Leaves among those 0
                Objectids found 2

Pass 1 (will try to insert 0 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished

Flushing..finished
        0 leaves read
                0 inserted
####### Pass 2 #######
Flushing..finished


No reiserfs metadata found.  If you are sure that you had the reiserfs
on this partition,  then the start  of the partition  might be changed
or all data were wiped out. The start of the partition may get changed
by a partitioner  if you have used one.  Then you probably rebuilt the
superblock as there was no one.  Zero the block at 64K offset from the
start of the partition (a new super block you have just built) and try
to move the start of the partition a few cylinders aside  and check if
debugreiserfs /dev/xxx detects a reiserfs super block. If it does this
is likely to be the right super block version.
If this makes you nervous, try  www.namesys.com/support.html,  and for
$25 the author of fsck,  or a colleague  if he is out,  will  step you
through it all.

Aborted
Was er da mir jetzt als letzts heraus gibt macht mich ziehmlich nervös.
Nun möchte ich erst mal einigige Tips einsammeln bevor ich was weiters mache, da die Daten sehr wichtig für mich sind.
Schon mal Danke im voraus.
 

scummos

Hacker
Mein Tip wäre, egal was du weiter machst, leg dir ein Image mit disk dump an.
dd if=/dev/sdi1 of=backup.image (wird dann halt 465.7 gb groß) oder
dd if=/dev/sdi1 | gzip -9 > backup.image.gz

Dann kannst du zumindest zum aktuellen Zustand wieder zurückkehren, wenn du die Platte mit fsck kaputt machst.

Replaying journal: No transactions found
beunruhigt mich etwas, wenn du sagst die Platte wurde benutzt! ...
 
OP
B

bumbuminc

Newbie
Als weiter info hab ich noch fdisk -l:

Code:
Disk /dev/sdh: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0008dfa1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1               1       60801   488384001   fd  Linux raid autodetect

Disk /dev/sdi: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0006630a

   Device Boot      Start         End      Blocks   Id  System
/dev/sdi1               1       60801   488384001   fd  Linux raid autodetect

Disk /dev/md0: 500.1 GB, 500105076736 bytes
2 heads, 4 sectors/track, 122095966 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table
 
OP
B

bumbuminc

Newbie
Ok, ich habe mir jetzt noch eine Platte besorgt, komischerweise schreibt er nur 13gb. Wie kann das sein?

Code:
linuxserver:/data1 # dd if=/dev/md0 of=backup.image
dd: writing to `backup.image': Input/output error
25814185+0 records in
25814184+0 records out
13216862208 bytes (13 GB) copied, 392.879 s, 33.6 MB/s
[/quote]
 
A

Anonymous

Gast
bumbuminc schrieb:
dd: writing to `backup.image': Input/output error
25814185+0 records in
25814184+0 records out

da mehr gelesen wurde als geschrieben, gibt es einen Fehler beim Schreiben, Partition/Platte/Filesystem voll oder nicht groß genug oder du schreibst nicht auf diese Platte sondern ins Rootverzeichnis oder sonstwohin ? wenn nicht, dann hat die Schreibplatte nen Schuss,

robi
 
Oben