I've just setup a bootable DMRAID(FakeRaid) RAID 0 on an old FastTrak66 using essentially the instructions on https://help.ubuntu.com/community/FakeRaidHowto. When booting, I see a bunch of messages "Attempt to access beyond end of device". What I think is happening is that DMRAID stores the partition table of the mapped device in the partition table of the first device in the RAID. Since this is a RAID0 using the whole of two drives, that partition table represents a drive that's the sum of the sizes of the two, and is thus seen as invalid for the drive by Linux when the system comes up.

So, my question: is there a way to tell Linux to not nag me about these messages from the drive during boot? If there's a problem with the mapped array, I expect I'll see it when the raid is put together during bootup.

I recently saw that error when I tried to mount an XFS file system as ext3. Something like that might be the cause of your error message.

"I recently saw that error when I tried to mount an XFS file system as ext3. Something like that might be the cause of your error message."

I thought it might be something really bad like that, at first. But, I suppose I should have posted that the addresses it complains about are in the area around the addresses that delimit the two mapped partitions (root and swap) in /dev/mapper/pdc_bebcjgdii. I think it has to be related to the way this thing works. You just don't get coincidences like that. But the question is how to make Linux shut up about it during boot?

There is a short discussion on the web about this problem, and it looks like the messages are coming about from udev's probings. There is a short kernel patch to fs/partitions/check.c that shuts up the great mass of messages, and only prints one warning for each partition.

https://www.redhat.com/archives/atar.../msg00015.html