Technically "bootfs ID" is a string which names the root dataset, typically "rpool/ROOT/solarisReleaseNameCode". This string can be passed to Solaris kernel as a parameter manually or by bootloader, otherwise a default current "bootfs" is read from the root pool's attributes (not dataset attributes! - see "zpool get/set bootfs").
In your case it seems that the attribute points to an invalid name, and your root dataset may be named somehing else - just set the pool attribute. I don't know of "bootfs ID numbers", but maybe that's a concept in your company's scripting and patching environment. It is also possible that device names changed (i.e. on x86 - when SATA HDD access mode in BIOS changed from IDE to AHCI) and the boot device name saved in eeprom or its GRUB emulator is no longer valid. But this has different error strings ;) Good luck, //Jim -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
