my server (Debian Wheezy) has a failed disk. I have sda and sdb and according to the support of my hoster, sdb needs a replacement. I send them this information with the mdstat: ...
I recently moved from a hardware RAID1 enclosure to using two eSATA drives with md. Everything seems to be working fine, except for the fact that directory traversals/listings sometimes crawl (on the ...
I have a server with three identical SATA/600 3TB drives: /dev/sda, /dev/sdb, /dev/sdc. The drives are partitioned, using GPT with three partitions each: 1 MB: Reserved partition for boot loader 1 ...
mdadm - Accidentally ran “mdadm --create” on an existing raid-1. The superblock is now corrupt and I am unable to recover data. Did I bork my data?
I have /dev/sdb1 and /dev/sdc2 that were previously setup into a RAID-1 with mdadm, but then I reinstalled and lost the old configuration. Out of idiocy, I ran sudo mdadm --create /dev/md0 --level=1 ...
I used a Software-RAID I and want to access the data without RAID now. After mdadm --fail /dev/md0 /dev/sda1 mdadm --remove /dev/md0 /dev/sda1 I tried mount -t ext4 /dev/sda1 /mnt but dmesg ...
I want to use two 3 TB drives in a mdadm raid1 setup (using Debian Sequeeze). The drives use 4k hardware sectors instead of the traditional 512 byte ones. I am a bit confused because on the one hand ...