Vielen Dank für deine Antwort!
Ja nur leider habe ich das mit "--zero-superblock" von einem anderen Forum, indem stand, dass ich mit dem Befehl die RAID Dateien vom Laufwerk löschen kann und es dann 'ganz einfach' wieder (als normales Laufwerk) einbinden kann und bin erst später auf den Link von ubuntuusers.de mit dem von dir zitierten Kommentar/Hinweiß gestoßen.
Habe mal folgendes probiert, nachdem ich das mit "--zero-superblock" etc. ausgeführt habe:
root@ubuntu:~# fdisk -l /dev/sda
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00003a4e
Device Boot Start End Blocks Id System
/dev/sda1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.
root@ubuntu:~# mount /dev/sda /mnt/
mount: unknown filesystem type 'linux_raid_member'
root@ubuntu:~# mount -t ext3 /dev/sda /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/sda,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
root@ubuntu:~# mdadm --create /dev/md0 --level=raid1 --raid-devices=2 /dev/sda missing
mdadm: /dev/sda appears to be part of a raid array:
level=raid1 devices=2 ctime=Fri Feb 7 10:58:40 2014
mdadm: partition table exists on /dev/sda but will be lost or
meaningless after creating array
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
Continue creating array? yes
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.
root@ubuntu:~# mount /dev/md0 /mnt/
mount: you must specify the filesystem type
root@ubuntu:~# mount -t ext3 /dev/md0 /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Und natürlich auch schon mehrfach:
root@ubuntu:~# fsck.ext3 -v /dev/md0
e2fsck 1.42.8 (20-Jun-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/md0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
root@ubuntu:~# mke2fs -n /dev/md0
mke2fs 1.42.8 (20-Jun-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
122093568 inodes, 488345840 blocks
24417292 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
14904 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
root@ubuntu:~# e2fsck -b 32768 /dev/md0
e2fsck 1.42.8 (20-Jun-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/md0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
root@ubuntu:~# e2fsck -b 98304 /dev/md0
e2fsck 1.42.8 (20-Jun-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/md0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Wie kann ich denn jetzt die Daten wiederherstellen oder wenigstens drauf zugreifen, damit ich noch ne paar Daten retten kann? Wäre euch echt mega dankbar, wenn ich mir helfen könntet, sind wichtige Daten drauf!
Vielen Dank!
Chris
