mdadm --create /dev/md0 --level 1 --raid-devices 2 /dev/sdb1 missing --metadata=0.90 mdadm: super0.90 cannot open /dev/sdb1: Device or resource busy mdadm: /dev/sdb1 is not suitable for this array. mdadm: create aborted Sometimes running "partprobe" can fix this. Other times it requires a reboot. One other manual thing that can be done is the following to fix it (if dm is using and blocking it):........

It takes some tinkering the main thing is that the "-dmS" flag allows screen to start without a session which of course sudo won't have. solution: /usr/bin/sudo -u user /usr/bin/screen -dmS nameyouchoose /script/start.bash this doesn't work at all: /usr/bin/sudo -u user "/usr/bin/screen /script/s........

Tired of checking iotop and seeing that your drbd partition is using 99.99% of io all the time and finding your drbd device performs slow in general? This is especially an issue in versions of DRBD in the 8.3 tree in particular one documented case is on "8.3.13" but it likely applies to other devices. The symptoms are that resyncing is fine and normal but any reasonable amount of activity is very slow and lagged and creates a high server load and con........

This was caused by some weird dmraid setup which kind of takes control of drives even if they're blank/unused. 1. Check the table. dmsetup table ddf1_44656c6c202020201000006010281f0b3f5195b77cf86172: 0 3905945600 linear 8:0 0 ddf1_44656c6c202020201000006010281f0b3f5195b77cf86172p3: 0 37124096 linear 253:0 284547072 ddf1_44656c6c202020201000006010281f0b3f5195b77cf86172p2: 0 283496448 linear 253:0 1050624 ddf1_44656c6c2020202010........