I have used e-smith servers for quite a while. I have a fairly standard configuration. I install a small hard drive on IDE0,0 and a cdrom drive on IDE0,1. I install e-smith and then remove the cdrom drive from IDE0,1. I then attach additional hard drives to IDE0,1 IDE1,0 and IDE1,1. Thus I should now have /dev/hda, /dev/hdb, /dev/hdc, and dev/hdd. I then make changes to fstab to mount these hard drives in the appropriate places (usually in the ibays directory) and I have a huge file server.
On a recent new installation I can no longer use /dev/hdb. I have tested every hard drive on every other device point and all the drives work fine and all the device points work fine except for /dev/hdb. Out of curiousity, I reinstalled e-smith on a hard drive on IDE0,0 with the cdrom drive on IDE1,0 and quite to my surprise I lost use of /dev/hdc but regained /dev/hdb.
So, it appears that e-smith is some how grabbing the /dev/hd{b|c|d} device depending on where the cdrom drive was connected during the installation.
I've modified lilo.conf where /dev/hd{b|c|d} were hard coded, I've removed an erroneous symbolic link of /dev/cdrom to /dev/hd{b|c|d} (see bug report forum). I can not get my e-smith box to use the device where the cdrom drive was connected with the OS was installed.
I use e-smith boxes as drop in files servers were needed and I usually populate them with 3 additional 100GB hard drives. This problem is causing me to lose 100GB of storage space in my new esmith boxes.
Any thoughts?