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):........

Use fdisk on your USB drive to create a bootable NTFS partition (in my case /dev/sdb): sudo fdisk /dev/sdb Welcome to fdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free)........

On a test machine Iwas never able to access to a newly created 4th partiton. As we can see there are dev devices for everything but the 4th partition. The normal "partprobe" or "kpartx" or kernel being told to rescan the block device didn't help (only a reboot did). fdisk -l /dev/sda Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units........

We've all done this at some point, you work on the wrong shell window and this was my first time making this mistake but I deleted a partition table in fdisk, recreated it and saved it with "wq" and even ran partprobe! If you haven't rebooted yet then you can still recover your partition table, otherwise you're in big trouble. Fortunately since it was a live system and in use the kernel still had to use the old table like below:........

In this example we have 2 drives in a RAID array and /dev/sdb is the one that failed. /dev/sda1 is also the /boot partition which we tell grub to install on /dev/sdb eg install root (hd0,0) /dev/sda1 on the new drive /dev/sdb (hd1) First copy the partition table from /dev/sda to /dev/sdb dd if=/dev/sda of=/dev/sdb bs=512 count=1 Run partprobe to detect the new partition table partprobe........

LSi Megaraid At first it was configured as a RAID 0, then I deleted the Virtual Disk Group. I thought both drives would be shown and detected in Linux as sda and sdb but it actually shows nothing. To make them work you have to hit Ctrl+R before the system boots (when prompted) and create a Virtual Disk Group. In my case I created each one as RAID 0 (with a single drive only) as I just wanted JBOD but there is no such option or default in these Dell Pe........

This array is a RAID 1 and in this case 1 of the 2 drives failed (a WD drive and I've found them to be the weakest and most unreliable of any brand and are easily damaged/DOA when shipping them). mdadm --manage /dev/md0 --add /dev/sdb1 The above assumes the array you want to add to is /dev/md0 and the device we are adding is /dev/sdb1 *One thing to remember is to make sure the partition you are adding is the correct size for the array. You can also g........

Neither the blkid or the UUID internal to mdadm work to automount for some reason in Debian partprobe doesn't work but was a good suggestion from: http://pato.dudits.net/2008/11/03/special-device-uuidxxxxxxxxxxxxxxxx-does-not-exist-especially-with-lvm mount: special device /dev/disk/by-uuid/431b9b96-29e8f298-e89bd504-7065bddd does not exist mdadm -D /dev/md_d12 mdadm: metadata format 00.90 unknown, ignored. /dev/md_d12: &nb........

Warning: Unable to open /dev/fd0 read-write (Read-only file system). /dev/fd0 has been opened read-only. That's a very annoying error, it's simply because Centos for some reason thinks it's wise to load the "floppy" kernel module, who has a floppy drive? I haven't seen or used a floppy for over 12 years! It's more than just annoying, if you probe the drives attached to your system, eg. with grub or partprobe, it keeps trying to locate a flopp........

I was creating a RAID array and got this error: mdadm: /dev/sda1 is too small: 0K mdadm: create aborted Of course sda1 is not too small, both partitions sda1 and sdb1 are identical in size: Disk /dev/sda: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Sta........

From the package "parted" you can use the command "partprobe" to re-read the partition table. I really hate rebooting, and that's what Iloved to hear about AHCI motherboards, that they allow hotswap so you don't have to reboot. But that's only as good as the OS, if the OS does not reload the partition table you won't be able to do anything with that new drive you attached without rebooting. Yes, even without re-reading the partiton table Linux will........