partitions missing from /dev on bootup
 

Ok the situation in as much detail as possible.

Machine has 13 hdd's and 1 usb memory drive.

All drives from sdb to sdm have 1 primary partition either used in a raid or standalone.

sdc1 is a standalone partition
sde1 is part of a raid

On bootup I am missing /dev/sdc1 and also since upgrading my kernel now missing /dev/sde1. After each boot I would run fdisk /dev/sdc and hit w to save and this then created /dev/sdc1. Until yesterday I had no idea at all why this was happening, but now I do think I know why.

Here is the output of blkid.

/dev/sda1: UUID="c716831f-3a20-40fe-9ffa-d908f210568f" TYPE="ext3"
/dev/sda2: TYPE="swap" UUID="cdb0d3e1-bcd5-4be3-9897-5f3b18015f78"
/dev/sdc: UUID="923255b7-b247-e8bd-1a84-9509b9a2311b" TYPE="mdraid"
/dev/sdh1: UUID="61a47772-7ae3-d8e4-6452-97271f88692d" TYPE="mdraid"
/dev/sdi1: UUID="61a47772-7ae3-d8e4-6452-97271f88692d" TYPE="mdraid"
/dev/sdj1: UUID="61a47772-7ae3-d8e4-6452-97271f88692d" TYPE="mdraid"
/dev/sdk1: UUID="fc32a50b-3b92-1374-6452-97271f88692d" TYPE="mdraid"
/dev/sdl1: UUID="7e8a32a5-f72b-6a42-6452-97271f88692d" TYPE="mdraid"
/dev/sdg1: UUID="61a47772-7ae3-d8e4-6452-97271f88692d" TYPE="mdraid"
/dev/sdf1: UUID="fc32a50b-3b92-1374-6452-97271f88692d" TYPE="mdraid"
/dev/sde1: UUID="7e8a32a5-f72b-6a42-6452-97271f88692d" TYPE="mdraid"
/dev/sdm1: UUID="7e8a32a5-f72b-6a42-6452-97271f88692d" TYPE="mdraid"
/dev/mapper/sdc1: UUID="831d1b2c-2c91-4817-900d-783f47deb110" TYPE="ext3"
/dev/mapper/md0: UUID="aa1b68c4-4e5a-480a-a950-b15d42034c85" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc1: UUID="587bc243-594f-426d-bb56-f5ffef1ee143" TYPE="ext2"
/dev/sdd1: UUID="7e8a32a5-f72b-6a42-6452-97271f88692d" TYPE="mdraid"
/dev/mapper/md1: UUID="c9f0da3e-1bb8-46f5-82a8-b623aad9c180" TYPE="ext3"
/dev/sdb1: UUID="1c330b79-423f-470d-8114-ff440f0a7a67" TYPE="crypt_LUKS"
/dev/md2: UUID="76100691-e16e-4f13-90c8-c905b94d6f09" TYPE="crypt_LUKS"
/dev/sdn1: LABEL="KINGSTON" UUID="3433-3231" TYPE="vfat"
/dev/dm-0: UUID="831d1b2c-2c91-4817-900d-783f47deb110" TYPE="ext3"
/dev/dm-1: UUID="431e04f8-46b0-4118-b93d-435867a53d46" TYPE="ext3"
/dev/dm-2: UUID="aa1b68c4-4e5a-480a-a950-b15d42034c85" TYPE="ext3"
/dev/dm-4: UUID="4d3b55fd-61c2-4f6f-9498-02fdf82ba0d9" TYPE="ext3"
/dev/sde: UUID="94a4d808-c497-b4d9-c5b7-6da3e608d34e" TYPE="mdraid"
/dev/md0: UUID="92858b8d-d04f-4a07-929f-26620a23f16f" TYPE="ext2"
/dev/md1: UUID="035beb46-dd5d-4411-a336-89757d43ae08" TYPE="crypt_LUKS"
/dev/dm-3: UUID="c9f0da3e-1bb8-46f5-82a8-b623aad9c180" TYPE="ext3"

so sde and sdc have id's whilst all the other drives only have id's for the partitions I created, I suspect this is causing my problem on bootup.

If this is the problem is there a way for me to wipe those UUID's for sdc and sde without affecting sdc1 and sde1? as I dont want to lose my data on those drives.

Another guess
 

sdc (the MBR of the drive) has a partition type? To make it even more confusing, type is raid, but
sdc1, the (only) partition inside sdc is said to be "standalone", a degraded RAID array or what else?
sdc should really not have a file system label nor a file system type.

sde is thought to be part of an RAID array as well. Same as with sdc, no idea, how you could have managed to get there. I never saw something similar. Did you try to format the disk instead of the partition? It shouldn't have worked in the first place, but doing bad to the MBR is not good for the partition table/whole disk. I'd recommend to backup and re-partition (from zero partition table) and re-format these disks.

Another hint
 

Here you may find something more corresponding to your problem:
http://go4hofbauer.de/wiki/doku.php?id=linux:uuid