boot sequence reverts back to original links
I have a SLES 9 configuration that boots from hard disk and also uses LVM SAN space for Oracle partitions. For this to work, I had to ensure that LVM was started before raw and Oracle in the run level 3 boot sequence. The modifications made to support this were:
1. Delete existing S12raw symbolic link
2. Delete existing S13oracle symbolic link
3. Create new S16lvm link: ln -s ../boot.lvm S16lvm
4. Create new S17raw link: ln -s ../raw S17raw
5. Create new S18oracle link: ln -s ../oracle S18oracle
After rebooting, all works as expected.
However, I've been finding that after subsequent maintenance reboots the original S12raw and S13oracle links have been reestablished and the S17raw and S18oracle links have vanished. The S16lvm link remains, but it now runs after Oracle, so the LV partitions Oracle expects to find are not yet instantiated and Oracle fails to load properly.
I have rebooted the system multiple times in a row and the new links remain in place - they are automagically changing later. I've checked all crontab files and there's nothing that reverts to the original links.
Any idea what is reverting these links or how to make them persistent?