Hi, I have some x4500 where I keep backups of other servers - a separate file system for each server. I noticed that while rebooting the server I got many errors like:
# reboot bootadm: missing /boot/grub on root: /archive-1/backup/XXXXXXX/ bootadm: missing /boot/grub on root: /archive-1/backup/XXXXXXX/ sh: line 1: /archive-1/backup/XXXXXXX//boot/solaris/bin/create_ramdisk: cannot execute [Permission denied] bootadm: Command '/archive-1/backup/XXXXXXXX//boot/solaris/bin/create_ramdisk -R /archive-1/backup/XXXXXX' failed to create boot archive sh: line 1: /archive-1/backup/XXXXXXXX//boot/solaris/bin/create_ramdisk: cannot execute [Permission denied] bootadm: Command '/archive-1/backup/XXXXXX//boot/solaris/bin/create_ramdisk -R /archive-1/backup/XXXXXX' failed to create boot archive [...] These errors are because I have exec=no set on these file systems. It looked like during reboot some script tried to rebuild all boot archives for each client which is Solaris 10 client... strange. After some quick digging thru bootadm code I found that it will try to do exactly that for basically all mounted file systems on a server. Without going into details it basically checks for each mounted file systems for a presence of fs_mount_point/boot/solaris/bin/create_ramdisk and if it's there it will try to rebuild a boot archive within that file system. See details at: http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/boot/bootadm/bootadm.c#2426 There should be better way of identifying BEs than blindly rebuilding an archive in each mounted file system. It could be even harmful in some cases. -- Robert Milkowski http://milek.blogspot.com -- This message posted from opensolaris.org
