Hi,
After a reboot I'm having trouble mounting my software raid.
I get the message: mount: /dev/mapper/sil_aiaiagcdagci already mounted or /mnt/ftproot/ busy

This is the exact command I used last time.
Additional info is that I am using this disk in a wmware machine. The machine is currently OFF.

Fdisk output now looks like this:

Disk /dev/sda: 250.0 GB, 250059350016 bytes
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x77221aa1

Device Boot Start End Blocks Id System
/dev/sda1 1 91203 732588066 83 Linux

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/dm-0: 750.1 GB, 750174904320 bytes
255 heads, 63 sectors/track, 91203 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x77221aa1

Device Boot Start End Blocks Id System
/dev/dm-0p1 1 91203 732588066 83 Linux

Disk /dev/dm-1: 750.1 GB, 750170179584 bytes
255 heads, 63 sectors/track, 91202 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/sdd: 73.5 GB, 73555509248 bytes
255 heads, 63 sectors/track, 8942 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ae316

Device Boot Start End Blocks Id System
/dev/sdd1 * 1 8572 68854558+ 83 Linux
/dev/sdd2 8573 8942 2972025 5 Extended
/dev/sdd5 8573 8942 2971993+ 82 Linux swap / Solaris

Disk /dev/sde: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x8d399bc0

Device Boot Start End Blocks Id System
/dev/sde1 1 60800 488375968+ c W95 FAT32 (LBA)

This should end with a number, as in "/dev/mapper/sil_aiaiagcdagci1". Without a number, that's the whole disk, and that's not mountable. What all do you have in your /dev/mapper directory? I'm assuming that you successfully created a partition with "fdisk", and created a filesystem with "mkfs" on the new partition.

Hi,
Thanks for answering.
I did give some wrong information in the tread, it's a fakeraid, and not software raid.
I mounted the disk like that the last time it mounted without problems.
But i've now found a solution. Think the problem was the partition table.
So I've deleted the raid, formatted the disks individually, and created the raid again. Formatted it to ext3, and it mounted up without problems.

OK, if it works for you.

Here is a good explanation of how to use fakeraids for booting. Skip over the parts about setting it up as a boot device, and go directly to the bit for creating partitions and putting filesystems on them. You will see that fakeraid partitions have the same numbering system as regular disk partitions. If you didn't partition it, you will continue to have problems with it. You cannot successfully put a filesystem on the fakeraid itself. Just like a regular disk, you must use a partition.

https://help.ubuntu.com/community/FakeRaidHowto

Ok, thanks alot!
Good that I partitioned it this time then!