I have been configuring a RAID 5 system. I have a 3 disk raid on a promise MAX-II controller. Each was on its own controller port. I had a boot disk on /dev/hda and a disk I was using for restoring on /dev/hdb. The partitions on the latter disk were only mounted when needed. I shutdown and removed the /dev/hdb and reconnected the cdrom to the slave of the 1st ide. Now when I reboot, I get a "corrupt superblock" message suggesting that I try e2fsck -b 8193 to recover it. These messages are for my /dev/mdx raid drives. When I go into maintenance mode, I can mount and e2fsck all my /dev/mdx drives and they check clean. I can mount the file systems and they all work. mdstat indicates all is well. Anyone have any ideas what happened and how to fix it? Thanks, Doug Egan
