Tag Info

New answers tagged


I did it by the "hard way": (first if its possible clone this disk before you do anything!) dmesg for the raid-disk or try (example: sdc1) $ fdisk -l Change the RAID-DISK-Flag to your Linux filesystem (ext3 or something), save this and reboot. After that $ mdadm --zero-superblock /dev/sdx and voila you can mount $ mount /dev/sdc1 /mnt


In addition to LVM internal RAID and mdadm RAID that Hauke mentioned Btrfs and ZFS have RAID support built-in. Btrfs has RAID-0, RAID-1, RAID-10 and staring with Linux 3.9 RAID-5 and RAID-6. Those are in compatible with other Btrfs version with at least the same version. ZFS has RAID-0, RAID-1, RAID-10, RAID-5, RAID-6, RAID-0 under different names, as well ...


There are several ways to create a SoftRAID with Linux: LVM's internal RAID and four versions of MD RAID (mdadm): 0.90, 1.0, 1.1, 1.2. Every non-ancient Linux should understand them all. There should not be any problem with a distro change.


I'd go for the dd option. Because that makes sure you have a "snapshot" like state of the disk including the master boot record and your partition table. If restoring you can write the image right back to the disk, without the need for partitioning or fiddling with grub. The "somewhere" should be any fast and reliable storage you can mount into the rescue ...


In my experience 32-bit uses less memory. Once the install was complete I had 8MB used, which is very impressive. I think it was about 16MB with a fresh 64-bit install. So if memory is your main concern, go for 32-bit; I can't judge performance as it requires real testing.


It seems the RAID metadata got damaged somehow. How did that happen? Once you've fixed any misconfigurations, errant scripts, hardware problems, etc., try to mount read-only: mkdir /mnt/{sdb1,sdc1} mount -o ro,loop,offset=$((2048*512)) /dev/sdb1 /mnt/sdb1 mount -o ro,loop,offset=$((2048*512)) /dev/sdc1 /mnt/sdc1 See if either one mounts, verify files of ...

Top 50 recent answers are included