Tag Info

New answers tagged

2

Due to how Linux raid behaves, using a three way raid1 vs a two way+hot spare raid1 setup gives: slightly lower random write performance, because arrays's access latency (seek time+rotational delay) is the worst of the the disks composing the array significantly better random read performance, as Linux raid is capable of issuing multiple, independent reads ...


0

The lspci output: 02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) indicates the presence of an hw raid card. The correct tool to manage this kind of card is: sas2ircu You can find more informations here: http://hwraid.le-vert.net/wiki/LSIFusionMPTSAS2


0

This message indicates that one or more of the three disks is failing, or that the controller/cables are failing. The whole setup seems to be a RAID0 of three disks - a very risky configuration. I would do something like this: backup the data (if you want to), dismantle the RAID and get JBOD. Test each individual disk. Establish what is the failing part. ...


1

Looks like you did an mdadm --create on "Creation Time : Thu Jun 11 23:21:12 2015", that could be a problem if you used the wrong parameters. What command line did you use? Also when the mount fails what is reported by... dmesg | tail And it's a good idea to check the SMART data on the drives to see if they are healthy. Don't despair. I often work on ...


0

If you want you can assemble with three drives in degraded mode... mdadm --assemble --force /dev/md0 /dev/sda /dev/sdb /dev/sdd "missing" is an option that can be used with mdadm --create


0

The entire path the data takes from the OS to the SSD needs to support the pass trough of TRIM commands. Generally the issue is that the hardware RAID controller does not pass trough the TRIM commands. Software RAID should be able to pass trough the TRIM commands as long as you use a normal controller (LSI HBA SAS controller or something). The arguement ...


0

Did you try assembling it with missing in place of the odd third disk sdc, i.e. mdadm --assemble /dev/md0 /dev/sda /dev/sdb missing /dev/sdd --verbose That sounds like it could work because the remaining three appear to be in sync and with RAID-5 N-1 is sufficient to restart the array in degraded mode. It's possible that the device indices aren't right, ...



Top 50 recent answers are included